Relationship between UML diagram and software development process

First, the soft work documentation,

Soft work documents, that is, plans, designs, descriptions, and documents using software, are fixed and used for reading by different people and computers. during this period, the document played the role of a bridge. It looks like this image:

 

 

Here, I will take a look at the relevant knowledge of the 13 documents uniformly stipulated by the state. Let's take a look at the classification of the documents:

 

 

Content of each document:

1. Feasibility study report: Describe the technical, economic, and social feasibility of the software development project, comment on various possible implementation schemes that can be selected to reasonably achieve the development goal, and explain and demonstrate the reasons for the selected implementation scheme.

2. Project Development Plan: formulate a specific plan for the software project implementation plan, it should include the person in charge of each part of the work, the development progress, the development budget, the required hardware and software resources. The project development plan should be provided to the management department and used as a reference for the development stage review.

3. Software Requirement Specification: Also known as the software specification, which provides detailed descriptions of the features, performance, user interface and operating environment of the developed software. It is an agreement between the user and the developer on the basis of mutual understanding of the software requirements and the basis for implementation and development.

4. Data Requirements Specification: This specification should provide the data logic description and data collection requirements to prepare for the production and maintenance of system data volumes.

5. Summary Design Manual: This manual is the work result of the outline design stage, it shall describe the function allocation, module division, overall program structure, input and output, interface design, operation design, data structure design and error handling design, and lay the foundation for detailed design.

6. Detailed Design Description: describes how each module is implemented, including algorithms and logical processes.

7. User Manual: This Manual describes in detail the functions, performance, and user interface of the software, so that you can understand how to use the software.

8. Operation Manual: This Manual provides the operator with relevant knowledge about the various running conditions of the software, especially the detailed operation methods.

9. Test Plan: an implementation plan should be prepared for the purpose of testing assembly and validation. The plan should include the testing content, progress, conditions, personnel, selection principles of test cases, and allowable deviation range of test results.

10. Test Analysis Report: after the test is completed, a description of the execution of the test plan should be submitted. Analyze the test results and put forward the test conclusions.

11. Development Progress Monthly Report: This monthly report is a monthly project progress report submitted by software personnel to the management department. The report should include the comparison of the progress plan and actual implementation, the results of the phase, the problems encountered and solutions, and the plans for the next month.

12. Project Development Summary Report: after the software project is developed, it should be compared with the project implementation plan to summarize the actual implementation status, such as progress, results, resource utilization, costs and manpower invested. In addition, it is necessary to evaluate the development work and summarize the experiences and lessons learned.

13. software maintenance and modification suggestions: This is used for recording later maintenance and modification.

 

The document classification and basic functions are described above. We can see the position of the document in the software life cycle below:

 

 

Finally, let's take a look at the macro functions of these documents, that is, the tasks they need to complete. This figure shows:

 

I will explain the following simple characters:

1. "What": Answers what to do and what needs to be met;

2. "Where" refers to the answer, that is, the environment in which the developed software is implemented and where the required information comes from;

3. "When" is the answer, that is, how the development work is scheduled;

4. "Who" means that some development (or maintenance) work is intended to be done by "who? "·

5. "How" means how certain requirements are met;

6. Why?

 

 

The above is the relevant content of the soft work document. Let's take a look at the relationship between the UML diagram and the document below:

 

First, the UML diagram does not correspond to the document one by one, except for several core diagrams, such as the use case diagram and class diagram. Other diagrams can appear in any document. below is a brief introduction to the development process:

In the demand analysis stage, it is mainly filled with the use case digoal (use case diagram), which is intended for system analysts, demanders, and even users. In the design stage, that is, the outline design and detailed design instructions are the main carriers of UML diagrams. They can be mainly UML diagrams, such as class diagrams, InterAction diagrams, activity diagrams, state diagrams, and sequence diagrams, it is intended for analysts and programmers. In other documents, it can be based on the actual situation, actual needs, flexibility, and appropriate UML diagrams.

 

To sum up, for the relationship between the macro soft work document and the UML diagram, it is necessary for us to understand the functions and objectives of the document and the corresponding document of the UML diagram before we draw a picture, there is also a relationship with the software development process. A simple understanding of the shortcomings. Please submit them!

Reprinted from: http://blog.csdn.net/liujiahan629629/article/details/8582054

Relationship between UML diagram and software development process