A common product life cycle model

Life cycle:

The life cycle of an information system project is generally divided into 4 stages: initiation, planning, implementation, and closure. Monitoring as a process throughout the life cycle. The products of the information system function can be divided into the product life cycle according to the technical work, and the two life cycles are interspersed with each other by the way of the time.

Life cycle Model:

Waterfall model, iterative model and rapid prototyping are typical three product life cycle models.

1. Waterfall model: For projects with clear requirements and the ability to identify all requirements in the early stages of a project without needing to develop two times.

1. Strictly follow the sequence of pre-planned requirements analysis, design, coding, integration, testing, and maintenance steps.

2. The outcome of the above steps is a way to measure progress, such as requirements specification, design documentation, test plan, acceptance report, etc.

3. The main problem is that due to strict grading leads to reduced degrees of freedom, the early commitment of the project leads to changes in late requirements that are difficult to adjust and costly.

4. If the project needs are unclear, or if the requirements may change during the course of the project, it is not feasible.

2, iterative model, applicable to the pre-complete definition of all product requirements, planning multi-phase development projects.

3. Rapid prototyping, suitable for projects that need to demonstrate product prototypes quickly to customers/users.

Maintenance activities for software products:

Maintenance activities of software products can be divided into: corrective maintenance, adaptive maintenance, perfect maintenance, preventive maintenance

(1) Corrective maintenance: After the product has been put into operation for a period of time, it may expose some errors not found during the testing phase, and modify the SOFTWARE PRODUCT to correct these errors.

(2) Adaptive maintenance: Modify software products to adapt to these changes due to changes in the external environment (such as software, hardware) and data environments in which the product operates.

(3) Perfect maintenance: As the user's needs are constantly changing, in the software product use process, the user will put forward new functions and performance requirements for the product, in order to meet these new requirements and modify the software, so that the function and performance are improved and enhanced activities.

(4) Preventive Maintenance: The product owner uses the advanced software engineering method to redesign, encode and test all or part of the products that need to be maintained in order to improve the maintainability and reliability of the software products and to lay the foundation for further improvement of the products.

A common product life cycle model