Software Process Model

First, introduceSoftware lifecycle model:

Clearly describe software development activities from a macro perspective, and divide the entire life cycle of software from production to waste into various stages. Each stage includes its main work and executors, these stages constitute a sequential development process, namely the software life cycle model.

There are six phases: Demand engineering-software design-software implementation-software testing-Software Delivery-software maintenance.

Software Process ModelThat is, a more detailed description of the software lifecycle model. There are mainly the following models:

Build-repair model:

The earliest and most natural software development process model. However, because there is no specific planning and organization in development, relying solely on the individual will not regard it as a software process model.

Waterfall Model (document-driven)

People's earliest cognition of software process models. Organize software development activities into: Demand Analysis-software design-software implementation-software testing-Software Delivery-software maintenance, it also defines the top-down and cohesive order (which allows repetition and iteration ).

Incremental-iterative model (demand-driven)

At the beginning of the project, design the project prospects and scope, and organize subsequent activities into multiple iterative and parallel waterfall development activities.

Evolutionary Model (demand-driven)

Similar to incremental-iterations, the difference is applicable to software development activities with frequent and unstable requirements. Both incremental and iterative models have the advantages of shortening the development time (parallel development) and reducing the development risk (progressive delivery.

Prototype Model (demand or risk-driven)

Before a real product is built, the prototype can be divided into two types: one is an evolutionary model, which will become part of the product in the future, and the other is a discarded prototype, which will not become a real product in the future.

Spiral Model (risk-driven)

Driven by risks, software development activities are fully organized in the form of Risk Solutions.

 

Software Process Model