Software life cycle Model selection

Waterfall model/Improved waterfall model

Spiral Model

Incremental iteration is a software development lifecycle model commonly used in RUP Unified Process

Prototype method

　

Rapid and agile development

We generally use rapid and agile development as a methodology, it is rarely a software development lifecycle model. Agile is designed to reduce the heavy and unnecessary output of the workpiece and improve efficiency. Instead of trying to pick a stage or process, not analyze the design and do the development. So for the waterfall, Incremental iterations or prototypes we can all learn from some good practices in agile methodologies, which complement the traditional life cycle model. There is no longer much to be said about agile methodologies.

A final summary of choosing a life cycle model

1. Use waterfall models or improved waterfall models as far as possible in the early stages of demand.
2. In the absence of user experience in information systems, the need for analyst skills needs to use the prototype.
3. In many uncertain factors, many things can not be planned in front of the case as far as possible using incremental iteration and helix model
4. Use incremental iterative model as much as possible in case of unstable demand
5. The incremental model can be adopted when the funds and costs cannot be put into place once, and the software products are distributed in multiple versions.
6. For full multiple independent function development can be divided into functional parallel in the requirements phase, but each function should follow the waterfall model
7. Development of a new system must be incremental or parallel after the overall design has been completed.
8. The use of agile or iterative lifecycle models is not recommended for coders with less experience.
9. Increments, iterations, and prototypes can be used synthetically, but each increment or iteration must have clear delivery and export guidelines.