Water Fall Model

Water Fall Model

This is simplest and most widely used model in the software development process. The sequence of activities involved are feasibility analysis, requirement analysis and project planning, system design, detailed design, coding and unit testing, system integration and testing At the end of each phase, validation and some certification of the intermediate, work product is made to ensure that the output of a phase is consistent with its input, and the output of a phase is consistent with the overall requirement of the system. It is suited for routine type of projects where all the requirements are well understood.

Minimum set of documents that must be produced to produce a successful product are:
  1. Requirement document
  2. Project plan
  3. System design document
  4. Detailed design document
  5. Test plan and test reports
  6. Final code
  7. Software manuals (use, installation etc.)
  8. Review reports
Limitations of water fall model:
  • Suitable to automate the existing manual system where requirement is completely known.
  • If the project takes long time then h/w for which it was developed becomes obsolete
  • The model is document driven so it generates large amounts of documents

Maintanance<< Previous
Next >>ProtoType Model

Our aim is to provide information to the knowledge seekers. 

comments powered by Disqus