1. Requirements analysis and definition: Gathering needs the full and then analyzed and defined the needs that must be met by a program that will be built. This phase should be done to complete the design, which can produce complete.
2. System and software design: Design is done after the needs of finished collected in full.
3. Implementation and unit testing: design of the program translated into code by using a programming language that has been determined. The program is built directly tested in both units.
4. Integration and system testing: The unit tested the program and overall (system testing).
5. Operation and maintenance: operate the program and perform maintenance, such as adjustments or changes because of adaptation to the actual situation.
Lack of a major model is the difficulty in accommodating the changes after traveled. The previous phase should be complete and finished before the next phase.
Problems with the Waterfall:
1. Changes are difficult because of the rigid.
2. Because of the nature kakunya, this model is appropriate when the needs were collected in full so that changes can be pressed to a possible. But in fact rarely consumers / users who can needs to give full, the changes need something that is reasonable occurred.
3. Waterfall generally used for engineering a system where the big projects done in several different places, and is divided into several parts of sub-projects.
Excess the Waterfall
This model is conducting a systematic approach and sequence from the level of the system and the need to phase analysis, design, coding, testing / verification, and maintenance. Waterfall called because the step-by-step must be passed by the previous stage, awaiting the completion and run sequentially. For example stage must await the completion of the design stage of the previous stage fun