The waterfall model is a breakdown of project activities into linear sequential phases, where each phase depends on the deliverables of the previous one and corresponds to a specialisation of tasks. The approach is typical for certain areas of engineering design.In software development, it tends to be among the less iterative and flexible approaches, as progress flows in largely one direction (“downwards” like a waterfall) through the phases of conception, initiation, analysis, design, construction, testing, deployment and maintenance.
The consequent phases we abide by in the Waterfall Model are as follows:
All requirements are taken into consideration in product requirement documents.
The requirements are based on analysis that define the schemas, models, and business rules.
Based on the analysis, we design the software architecture.
We implement the software in tiny units with functional testing.
Integration and Testing
Integration of each unit developed is done during the earlier phases to look for any faults and bug fixes.
Deployment of system
The product goes live once functional and non-functional testing has been finished.
Fixing of issues, once done, release new versions with the issue patches as needed.