Waterfall approach

Software development has gradually evolved from unstructured to structured, both in producing programs and in managing projects

The waterfall approach assumes all requirements are written down before producing them. Each definition is "signed off" by the user before starting work

Advantages: Planned duration, responsibility pinned down, orderly, should result in few corrections late in project


Waterfall approach

Waterfall approach


All is not rosy

It can be difficult to state when a stage is complete, ie. we may have to correct to previous work

Causes of failure once a project has started:

Alternative approach: Rapid Application Development (RAD)


 
UpOther topics Comments please to: dwfarthi@glam.ac.uk © 2001, University of Glamorgan