Waterfall model is believed to be the first software method to be used in software development. This model follows a procedure where next phase of cycle is started only when the previous phase is completed. This model can be used for small scale project and mainly if there is no uncertainty in the software requirements. Waterfall model is also called as linear sequential life cycle model. Waterfall model may not be applicable to today's world as requirements are dynamic and keep changing as a phase is completed.
As word suggests, it flows downwards with phase mentioned below.
1. Requirement Analysis and Gathering:
2. Design
3. Implementation
4. Testing
5. Deployment
6. Maintenance
Pros and Cons of Waterfall model
Pros
- It is easy to understand and manage
- Since the requirements are frozen there would be no confusions and phase can be carried out in ease
- Product can be delivered on time as each phase would be assigned with efforts and there would be no rescheduling the efforts or dates
Cons
- If a defect is found during testing phase then it becomes difficult to get back to development stage and change the entire set of code or logic
- Next phase team especially testing team would be idle until the implementation phase is completed unless they are made to test some other project
- Clients will be only able to check the working condition of product only when the implementation is completed
As word suggests, it flows downwards with phase mentioned below.
1. Requirement Analysis and Gathering:
2. Design
3. Implementation
4. Testing
5. Deployment
6. Maintenance
Pros and Cons of Waterfall model
Pros
- It is easy to understand and manage
- Since the requirements are frozen there would be no confusions and phase can be carried out in ease
- Product can be delivered on time as each phase would be assigned with efforts and there would be no rescheduling the efforts or dates
Cons
- If a defect is found during testing phase then it becomes difficult to get back to development stage and change the entire set of code or logic
- Next phase team especially testing team would be idle until the implementation phase is completed unless they are made to test some other project
- Clients will be only able to check the working condition of product only when the implementation is completed