The waterfall model shows a process, where developers are to follow these phases in order:
- Requirements specification (Requirements analysis)
- Software design
- Implementation and Integration
- Testing (or Validation)
- Deployment (or Installation)
- Maintenance
- Waterfall Methodology
- The team creates a list of all requirements before any
design is done.
- Upon requirements completion, a detailed design is
created for each requirement.
- Upon design completion, all tasks are estimated and
submitted for approval.
- Upon approval, coding begins and test cases are created
in preparation for quality assurance.
- Upon code completion, testing begins and continues
until all test cases are run and all defects are fixed.
- Upon quality assurance completion, the software is
documented and moved to production.
The disadvantage of the Waterfall methodology is that it takes a long time to deliver software to production (normally more than a year). The reason is due to the effort involved in defining all features of the software and creating detailed designs for all of them. It is also problematic because if major flaws are found in the requirements or design, it does not appear until the testing phase, and reworking a flawed design adds risk to the project as well as a lot of effort. Last, because the duration of Waterfall tends to span a year or more, business rules and needs can change, and the original design of the software may not still apply, making features of the new software obsolete before it ever makes it to production
http://www.qanews.com/print.php?sid=359
No comments:
Post a Comment