Software development model with waterfall Model rapid Prototyping model incremental model spiral Model fountain model
The main difference between the waterfall model and the rapid prototyping model is the different ways to obtain the user's requirements
The waterfall model is a feedback loop when the previous stage error is found in the later stage, it is necessary to return the previous phase of the product along the feedback line to correct the previous phase of the products before returning to continue with the tasks in the later stages
The rapid prototyping model is the main advantage of this process model without the feedback loop: the development of software products is essentially a linear sequence of rapid prototyping that is fast
When developing software using a waterfall model or rapid prototyping model, the goal is to submit a product that satisfies all requirements to the user incremental model in the opposite direction. It submits the product to the user in batches. The entire software PRODUCT is broken down into a number of incremental component developers a component to the user to submit products
Although the adoption of incremental models requires more careful design than the use of waterfall models and rapid prototyping models, more labor in the design phase will pay off during the maintenance phase.
The basic idea of the Helix model is to use prototypes and other methods to minimize risk. An easy way to understand this model is to think of it as a rapid prototyping model that adds risk analysis processes before each phase.
Spiral Model If you successfully exclude all risks, start the next development step the process in this step is equivalent to a pure waterfall model.
Fountain models do not start coding activities until after the end of the analysis activity as the waterfall model does not begin the encoding activity at all stages of the model no significant boundaries developers can develop synchronously
To avoid the development process when developing software using fountain models a linear process, such as a rapid prototyping model, should be used as an overall goal, but it should also be remembered that the object-oriented paradigm itself requires frequent iterative or refinement of development activities
Several major development model differences and linkages