Waterfall Model
The Waterfall model is a sequential (noniterative) approach used in software development processes (see figure below). In this model, progress towards software project completion flows steadily downwards (like a waterfall) through various phases of the life cycle, including requirements, design, implementation, testing, deployment, and maintenance.
4 slides · 1 min read · Domain 8
Typical Waterfall tasks may include
Text on this slide
Scoping and planning
Gathering and documenting requirements
Designing the application
Implementing the design
Coding the application
Performing quality assurance activities
Performing user acceptance testing (UAT)
Deploying the application
Text on this slide
Requirements
Design
Implementation
Testing
Deployment
Maintenance
Requirements
The requirements define the required functionality and operation of the final package. These are driven by what the end user expects the system to provide.
Design
Given a set of user and system requirements, design often takes two steps. First is an overall system architecture followed by a detailed design of the system's modules and interfaces.
Implementation
Program units are developed according to the detailed design. These are often functionality tested as a unit before integration into the complete system.
Testing
Testing is one of the most important phases of a system's development. It probes the functionality of each component, then tests the complete, integrated system.
Deployment and Maintenance
Deployment and maintenance of the system are the final steps in the process but are often two of the hardest. A badly designed and implemented system can be very difficult to maintain.