waterfall model
Download as PPTX, PDF8 likes6,396 views
The document describes the waterfall model, a sequential software development process where progress flows in one direction from conception to maintenance. It involves requirements gathering, analysis, design, coding, testing, and release/maintenance phases, where each phase must be completed before the next begins. While it provides structure, the waterfall model works best for projects with stable requirements and is not suitable for dynamic or changing requirements.
waterfall model
- 1. Waterfall MODEL Presented by.. Shiva Krishna Santhosh Chandra Varsha Nihanth Aparna Archana Anusha
- 2. SDLC Models • Sequential model • Incremental model
- 3. DIFFERENT MODELS IN SDLC 1.SEQUENTIAL MODELS: -Waterfall Model -V-Model 2.INCREMENTAL MODELS: -Incremental Model -Spiral Model -RAD Model
- 4. Waterfall Model Linear sequential model. Application is developed in a sequential approach. Each phase must be completed fully before the next phase begin Provides structure to inexperienced staff.
- 5. History The first formal description of the waterfall model is often cited as a 1970 article by Winston W.Royce. Presented this model as an example of a flawed, non-working model. Widely used for software projects ever since.
- 6. Where to use waterfall model Requirements are very well known Product definition is stable Technology is understood New version of an existing product.
- 7. How the process is
- 8. Requirements Gathering Business analyst will collect the requirements with an interaction of client
- 9. Requirement Analysis System analyst will study the client requirements and prepare the system requirement specification.
- 10. Design Design architecture is responsible to decide architecture of an application
- 11. Coding Developers will write the program using programming languages or scripting languages in order to develop the application
- 12. Testing Initially developers will perform unit testing and integration testing using of white box testing After that separate team will perform system testing using black box testing
- 13. Release &Maintenance Application is delivered to the customer While using this application if client identifies any defects in existing system then he sends the CR to CCB .
- 14. ADVANTAGES Easy to implement Helps to find errors earlier Easy to understand, easy to use. Works well when quality is more important than cost or schedule Documentation is produced at every stage Testing is done at every stage.
- 15. disadvantages Suitable for the small size projects. Constant testing of the design is needed. If requirements changes the Waterfall model may not work. Difficult to estimate time and cost Adjust scope during the life cycle can kill a project. High amount of risk and uncertainty. Not suitable to handle dynamic changes in the requirements
- 16. ANY QUERIES