8. Design Process Flashcards

(14 cards)

1
Q

System Development Life Cycle Phases

A

Analysis phase
Design phase
Implementation phase
Testing phase

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

SDLC Analysis Phase

A

Defines a programs goals

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

SDLC Design Phase

A

Defines specifics of how to build a program.

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

SDLC Implementation Phase

A

Writing the program.

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

SDLC Testing Phase

A

Checks that the programs correctly meets the goals.

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

Waterfall Approach

A

A program can be built by carrying out the SDLC phases in sequence

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

Agile Approach (or Spiral Approach)

A

A program can be built by doing small amounts of each SDLC phases in sequence, and then repeating

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

Object

A
  • A grouping of data (variables)
  • Operations that can be performed on that data (functions).
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Abstraction

A

To have a user interact with an item at a high-level, with lower-level internal details hidden from the user (aka information hiding or encapsulation)

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

Abstract Data Type (ADT)

A
  • A data type whose creation and update are constrained to specific well-defined operations.
  • A class can be used to implement an ADT.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Universal Modeling Language (UML)

A
  • A modeling language for software design
  • Uses different types of diagrams to visualize structure and behavior of programs.
  • UML consists of several structural and behavioral diagrams
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Software Requirements Rpecification (SRS),

A
  • Document describing all requirements for the software product.
  • Analysis phase
  • UML diagrams for several use cases.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Waterfall pro/con

A

Pros

  • Requirements set early, in agreement with client
  • Progress and time to completion easily measured

Cons

  • Mistakes noticed late may require starting over
  • When requirements change, can’t go back to an
    earlier phase
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Agile pro/con

A

Pro

  • Frequent developer communication
  • Easier to handle requirement changes

Con

  • Final design uncertain as iterations repeat
  • Cycles repeat as more and more problems are found, making product completion difficult
How well did you know this?
1
Not at all
2
3
4
5
Perfectly