Software Design Life Cycle Flashcards

1
Q

SDLC

A

Software Design Life Cycle

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What are the 7 stages of SDLC

A
Planning
Analysis
Design
Development
Test
Deployment
Operations and Maintenance
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What are Functional requirements?

A

Describes a function the software must perform.
Helps capture intended behaviour.
Requirements stated by the user which can be seen directly in the final product

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What are non-functional requirements?

A
Quality attributes of a software system. 
Helps ensure good UX.
Portability
Security
Maintainability
Reliability
Flexibility
Scalability
Performance
Reusability
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

TDD - Technical Design Document

A

written by development team.
describes in detail the entire or parts of design:
interface, data types and structures, detailed designs

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

SRS - Software Requirement Specification

A

Assessing user requirements.
More specific and details requirements in software terms.
Output can be directly used into implementation in programming languages

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

SSD - System Sequence diagram

A

shows the events that external actors generate, their order, and possible inter-system events of a particular scenario of a use case

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

SRS

A

Software Requirement Specification

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

SSD

A

System Sequence Diagram

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

TDD

A

Technical Design Document

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Actor

A

Anyone who interacts with the system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Objects

A

Are entities with attributes and methods.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Classes

A

Generalised description of an object. Defines attributes and methods an object can have.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Messages

A

Consist of the identity of the target object, the name of the requested method and any other action needed (arguments)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Abstraction

A

an abstraction relates to the observable behaviour - how an object and its behaviours are presented to the user

Handles complexity by hiding internal implementation details. Just need to know what methods are available and which input parameters are needed.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Encapsulation

A

encapsulation is the implementation which helps create the experience of abstraction

Data and methods bundles into a single unit e.g. class
Also refer to a mechanism of restricting direct access to components of an object
17
Q

Inheritance

A

one class gaining properties of another class. Allows programmers to create a new class that reuses variables and functions from another class

18
Q

Polymorphism

A

refers to the ability of variable, function or object to take on multiple forms.

19
Q

Multi-tier architecture

A

where a program is separated into three or more computers in a distributed network.