Agile learning notes (2) --- structured development method

Document directory

• Question
• Introduction to structured development

Question

To learn agility and make good use of agility, we must have a profound understanding of agility. The best way to understand agility is to understand the development methods compared with it, naturally, it is a structured development method.

Introduction to structured development

The traditional structured development process describes the entire process, activity, and task structure framework that spans the entire life cycle from software requirement analysis and definition to software maintenance.

The development model of the machine learning platform has a common feature, that is, each step has an exit and an entrance. After the entrance conditions are completed, the next step can be taken, and the exit conditions are completed, this step is complete. TakeWaterfall ModelFor example:

1. Plan

2. Demand Analysis

Entry: Project Plan approved

Exit: Software Requirement Specification approved

3. Design

Entry: Software Requirement Specification approved

Exit: Software Design Specification (including: Outline Design and detailed design)

4. Encoding

Entry: The Design Instruction is approved.

Exit: code is approved and checked, and compiled and tested.

5. Test

Entry: code is approved and checked, and compiled and tested.

Exit: For details, see function and performance verification.

Test types: unit test, integration test, and system test. The importance of unit test is self-evident. However, the structured model makes unit test take too little time.

6. Delivery deployment and maintenance

Waterfall disadvantages: strict entrance and exit

Coding and testing can only be performed after the project's needs and design are completed, and testing cannot proceed first. The unit test is ended in a rush, resulting in a decrease in the quality of the entire project and the product.

 

V model (improvements based on the waterfall model allow testing and design first)

 

Prototype/spiral model: Improves the project impact caused by Changing users' demands.

 

On the whole, although the structured model has perfect steps and development documentation support, its ability to respond to the customer's changing needs is poor, and even leads to a miscarriage of the project in the future, it is very difficult to maintain the later stage. Development risks are relatively high.