Chp 2 - Structured Methodologies Flashcards

(45 cards)

1
Q

How is development organized in structured methodologies?

A

Organized into phases with deliverables and milestones

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

When were structured methodologies developed?

A

1970s

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

What is another name for structured methodologies?

A

Traditional methodologies

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

What are requirements like in structured methodologies?

A

Clear and fixed

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

What do structured methodologies focus on?

A

Error free product

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

What kind of rules do structured methodologies enforce?

A

Rigid and strict rules

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

What do structured methodologies emphasize?

A

Full documentation

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

List out 3 example of traditional/structured methodologies

A
  1. Waterfall Model
  2. Structured Systems Analysis and Design Methodology ( SSADM )
  3. V-Model
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Who introduced the Waterfall methodology?

A

Dr. Winston W. Royce

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

When was the Waterfall methodology introduced?

A

1970s

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

What characterizes the Waterfall development process?

A

Highly structured and rigid sequential development

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

What does Waterfall promote?

A

Quality control of process and product

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

What does Waterfall emphasize?

A

Good documentation

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

When can one move to the next phase in Waterfall?

A

Only after completing and perfecting the preceding phase

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

What are the phases of the Waterfall methodology? ( 6 )

A
  1. Requirements
  2. Design
  3. Implementation
  4. Testing
  5. Deployment
  6. Maintenance
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What document captures all system requirements?

A

System Requirement Specification (SRS) Phases inside Requirement Gathering and Analysis

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

What document is required in System Design?

A

System Requirement Specification (SRS)

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

What does System Design helps?

A

Specifying hardware and system requirements and helps in defining overall system architecture

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

What is the system being developed in Implementation?

A

Units

Which are integrated at the next phase ( Integration and Testing )

20
Q

What is Unit Testing?

A

Small Units tested for its functionality

21
Q

What document captures all possible requirements of the system to be developed?

Integration and Testing in Waterfall Model

A

System Requirement Specification (SRS)

22
Q

What is done in Integration and Testing?

A

Integrate small units and perform testing

23
Q

When was SSADM popular?

A

Late 1980s ( Popular at UK )

24
Q

What approach does SSADM use?

A

Rigid and document-led approach to system design

25
Up to which stage does SSADM ends?
Design stage ## Footnote Outsource to other developers
26
What strategies that SSADM provides?
Has strategies to align business needs with system development
27
What projects suit SSADM?
Complex database design
28
What are the SSADM phases? ( 5 )
1. Feasibility Study 2. Requirements Analysis 3. Requirements Specification 4. Logical System Specification 5. Physical Design
29
What feasibility aspects are assessed?
Technical economic operational and risk feasibility
30
What does investigation document in SSADM?
Current system and requirements catalogue
31
What are Business System Options?
Alternative system development approaches for user choice
32
What does definition of requirements refine?
Requirements catalog data and process models
33
What do technical system options evaluate?
Best hardware/software to meet requirements
34
What does logical design specify?
Processing data and HCI ( Human Computer Interfaces) dialogues
35
What does physical design cover?
Specify physical data
36
Name 3 design technique in SSADM.
1. Logical Data Modeling 2. Data Flow Modeling 3. Entity Event Modeling
37
From which model is V-Model derived and modified?
Waterfall Model
38
What do the horizontal and vertical of the V-Model represent?
Time (horizontal) and system levels (vertical)
39
List out 3 tasks for Project Definition on V-Model Phase
1. Concept of Operation 2. Requirements and Architecture 3. Detailed Design | At the \ of V
40
List out 3 task for Project Test and Integration on V-Model Phase
1. Integration Test and Verification 2. System Verification and Validation 3. Operation and Maintenance | At the / of V
41
What phases mirror testing in the V-Model?
Concept ops Requirements Design Implementation Testing Maintenance
42
What approach does the V-Model take?
Top-down approach with associated testing phases
43
List out 4 testing that is conducted using V-Model Techniques
1. Unit Testing 2. Integration Testing 3. System Testing 4. User Acceptance Testing ETC
44
List out 3 Strengths with Structured Methodologies
1. A hierarchical approach tends to generate well-organized systems. Its step-by-step approach. 2. Simplifies project management, risk management, ad resource management 3. Structured methodology’s tools and techniques can all be used to support other methodologies.
45
List out 5 Problems with Structured Methodologies
1. Rigid phases, discourage skipping of unimportant steps. 2. Emphasize of process and product quality rather than customer satisfaction 3. Requirement need to be defined at the beginning of the project and not encouraged to change towards the end. 4. Cost and time is often unpredictable for large projects. 5. Too many ‘red-tapes’, wasting time and resources | ( Red taps -> Approval Unecessary Process )