waterfall methodology

Get Started. It's Free
or sign up with your email address
Rocket clouds
waterfall methodology by Mind Map: waterfall methodology

1. maintenance

1.1. There are some issues which come up in the client environment. To fix those issues patches are released. Also to enhance the product some better versions are released. Maintenance is done to deliver these changes in the customer environment.

2. deployment

2.1. Once the functional and non functional testing is done, the product is deployed in the customer environment or released into the market.

3. testing

3.1. All the units developed in the implementation phase are integrated into a system after testing of each unit. Post integration the entire system is tested for any faults and failures.

4. requirement analysis

4.1. All possible requirements of the system to be developed are captured in this phase and documented in a requirement specification doc.

5. implementation

5.1. With inputs from system design, the system is first developed in small programs called units, which are integrated in the next phase. Each unit is developed and tested for its functionality which is referred to as Unit Testing.

6. system design

6.1. The requirement specifications from first phase are studied in this phase and system design is prepared. System Design helps in specifying hardware and system requirements and also helps in defining overall system architecture.

7. pros

7.1. Simple and easy to understand and use

7.2. Easy to manage due to the rigidity of the model . each phase has specific deliverables and a review process.

7.3. Phases are processed and completed one at a time.

8. cons

8.1. High amounts of risk and uncertainty.

8.2. Not a good model for complex and object-oriented projects.

8.3. No working software is produced until late in the life cycle.