Waterfall

Question 1

Waterfall definition

Answer 1

System development flows downwards.
From one activity/phase to the next in a strict order you don’t go back

Question 2

waterfall advantages

Answer 2

• Practical and easy to use.
• Simple structured approach to all software activities on agreed content and tasks.
• Emphasis on documentation – you always know in which phase you are.
• Traceability and management facilitated.
• Versions and change control, allowing e.g. other teams to continue previous work.

Question 3

waterfall disadvantages

Answer 3

• Slow
  *Delays
• Distance from users.
• Testing is left for the last phases
• Detailed documentation requires resources and time – for small projects limited added value.

Question 4

3 constraints in waterfall

Answer 4

• Requirements fixed first.
• Delivery when ready.
• Costs/resources expand as needed to meet requirements.

Question 5

Structured systems analysis and design method

Answer 5

• An example of an industry standard methodology that follows the Waterfall Model.

Question 6

When do we use a waterfall methodology?

Answer 6

• Computerising existing manual systems without major changes
• Systems not expected to change over time.
• Supporting processes well understood and defined (e.g. common transactions, such as sales).
• Systems rather ‘isolated’, not integrated (rarely the case any more).
• Safety Critical Systems.

Question 7

Incremental delivery model

Answer 7

• Incremental delivery model allows for a product/service to be developed and delivered in stages.
• It breaks large projects into smallest possible units.
• Start with a plan