Waterfall Model
The waterfall model is a sequential software development process, in which progress is seen as flowing steadily downwards (like a waterfall) through the phases of Conception, Initiation, Analysis, Design (validation), Construction, Testing and maintenance.
This is the basic and standard life cycle models, also cited to as a linear-sequential life cycle model. It's very simple to understand and apply. In a waterfall model, each phase must be accomplished in its totality before the following phase can begin. At the finish of each phase, a review takes place to ascertain if the project is on the right course and whether or not to continue or discard the project.
Here these following phases are followed in order:
1. Requirements specification
2. Design Specification
3. Construction ( implementation or coding)
4. Integration
5. Testing and debugging ( Validation)
6. Installation
7. Maintenance
Advantages
* Simple and easy to use.
* Easy to manage due to the rigidness of the model – each phase has specific deliverables and a review process.
* Phases are processed and finished one at a time.
* Works comfortably for smaller projects wherever requirements are very well defined.
Disadvantages
* Setting scope during the life cycle can scrap a project
* No working package is produced until the end phase of the life cycle.
* High amounts of risk and uncertainty.
* Poor model for complex and object-oriented projects.
* Bad model for long and ongoing projects.
* Bad model where demands are constantly changing
Subscribe to this comment's feed
| < Prev |
|---|
