Soft test-Software Engineering-documents + cohesion Coupling

1. Software development lifecycle model:

Waterfall Model: an idealized development model that requires clear demand analysis, which is almost impossible in actual development.

 

Prototype Method: The biggest feature of the prototype method is that it uses a method to dynamically define requirements. In this way, there is no need to clarify the requirements.

Spiral Model: combined with the advantages of Waterfall Model and evolutionary model, the main feature is that risk analysis is added, which is based on planning, risk analysis, implementation engineering, and customer evaluation are a cycle that begins with a conceptual project.

Fountain model: Mainly used to describe the object-oriented development process. iteration is the core feature. There is no obvious boundary for all development activities, and various development activities are allowed to cross-perform.

2. Project Plan and execution

3. Document experiences

Recently, I was reading the part of the document. At that time, I had some new gains through project accumulation and re-entering the document specifications and instructor guidance.

Requirement document:

The requirement document mainly needs to develop software functional, performance, data and interface requirements to determine the logical model of the system.

Participants: users, project owners, and system analysts

Procedure:

Step 1: Architecture Diagram

Part 2: Database Design

Step 3: use case diagram

Summary design:

Outline Design Phase: developers need to transform identified functional requirements into the required architecture. Therefore, the outline design is to design the structure of the software and determine which modules the software consists of. These modules correspond to the functional requirements of the write-in. Therefore, the outline design is to design the structure of the software, determine which modules the software is composed of, the hierarchy of these modules, the call relationships of these modules, and the functions of each module. At the same time, we also need to design the overall data structure and database structure of the project's application system, that is, the data to be stored in the application system, the structure of the data, and the relationship between them.

Reader: System Analyst and software designer

The outline design process mainly includes:

Step 1: Review the basic model

Step 2: review and refine the data flow diagram

Step 3: determine the information flow type of the data flow diagram

Step 4: Perform transformation analysis or transaction analysis based on the stream type

Step 5: further optimize the software structure according to the software design principles

 

Detailed Design:

In the detailed design phase, the main task is to describe the functions completed by each module. The function description should be changed to accurate and the process description of the machine crash. That is, what is the control structure of the module, what to do first, what to do later, what conditions to determine, what to repeat, and so on, and express these control structures with corresponding presentation tools.

Reader: software designers and programmers.

Detailed Design:

Step 1: program flowchart

Step 2: N-S Diagram

Step 3: pad

Step 4: PDL

Step 5: Decision Tree

Step 6: Determine the table

4. Structured Analysis and Design

Grasp the relationship diagram: