Waterfall Model in SDLC

Advantages	Dis-Advantages
Before the next phase of development, each phase must be completed	Error can be fixed only during the phase
Suited for smaller projects where requirements are well defined	It is not desirable for complex project where requirement changes frequently
They should perform quality assurance test (Verification and Validation) before completing each stage	Testing period comes quite late in the developmental process
Elaborate documentation is done at every phase of the software’s development cycle	Documentation occupies a lot of time of developers and testers
Project is completely dependent on project team with minimum client intervention	Clients valuable feedback cannot be included with ongoing development phase
Any changes in software is made during the process of the development	Small changes or errors that arise in the completed software may cause a lot of problems

Requirement Collection

• Business Analyst
• Product Analyst

---

Feasibility Study

• Product Manager
• Business Analyst
• Architecture
• Finance Team
• HR Team

---

Design

• High Level Design
• Low Level Design

• Architecture

---

Coding

• Developers

---

Testing

• QA

---

Installation/Implementation

• Field Engineers/Site Engineers

---

Maintenance

• Developers
• QA