1
Q
Waterfall definition
A
System development flows downwards.
From one activity/phase to the next in a strict order you don’t go back
2
Q
waterfall advantages
A
- 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.
3
Q
waterfall disadvantages
A
- Slow
*Delays - Distance from users.
- Testing is left for the last phases
- Detailed documentation requires resources and time – for small projects limited added value.
4
Q
3 constraints in waterfall
A
- Requirements fixed first.
- Delivery when ready.
- Costs/resources expand as needed to meet requirements.
5
Q
Structured systems analysis and design method
A
- An example of an industry standard methodology that follows the Waterfall Model.
6
Q
When do we use a waterfall methodology?
A
- 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.
7
Q
Incremental delivery model
A
- 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
