Software development model in SSD9

The day after tomorrow, I will take an examination of ssd9. The software development model in it is quite complicated. I just want to write the content that may be tested.

A total of seven models are introduced: rapid prototyping model, edge-Based Edge modification model, waterfall model, incremental model, spiral model, synchronous and stable model, and fountain model.

First, the rapid prototyping model is called the rapid protype module.

This is a development model used to better clarify the customer's needs, because the user generally does not express it, so first create a prototype to let it feel so as to better clarify the needs. it is usually quickly created and expected to be modified. Because the prototype is only a simulation, we cannot use the prototype code during formal development, therefore, it is best to use different languages for formal development. prototype can be used as a focus to discuss requirements with users and reduce technical risks. disadvantage: 1. users will think that changing a formal product will be as easy as changing the Prototype 2. the developer will try to use the prototype code here

The second is to change the model while doing it. The name is build-and-fix module.

It is usually used in the following situations: the product is very small and the requirements are simple and clear. because it needs to be modified, there are several iterations in the development process, so there are no other instructions and specifications before development. this is an old development model. disadvantage: 1. defects cannot be found until the entire task is completed. 2. if you want to change it, it will be difficult because it is not designed. 3. no documentation, product hard to understand, difficult to maintain

The waterfall model is called waterfall module.

It is a continuous process that includes all development stages, and the previous stage is often used as the input for the next stage. This is the most widely used development model in 1980.

The second is the incremental model, called the increment module.

The incremental model requires that the software architecture be relatively open, and the danger is that you cannot afford the test time when adding new features. if the demand changes too quickly, the development model degrades to an edge-based model.

The second is synchronize-and-stabilize.

It is divided into three to four components, separated and completed separately. Frequent integration test. early testing, working version, and early feedback are required every day.