Detailed application of UML in Software Project Development

Most software developers know UML, but how can UML play a major role in software project development? The following describes the special features of different phases of the project.
The special requirements of the situation refer to the use of UML.

Application of UML in different stages of software:

I. Demand analysis stage: In the process of developing software, the biggest task in the demand analysis stage is to find out what the user needs to develop and what functions the software has. The use case diagram of UML can represent the customer's requirements. Using Case modeling, you can model external user roles and the system functions they need. At this time, each use case intuitively reflects the customer's needs (the use case diagram is understandable to most people who have not done any software .). In this way, it is good to confirm the function with the customer, review the function with the QA personnel, and establish the test case with the QA personnel. At the same time, the use case chart can also analyze the needs of the business process.

Ii. system analysis stage:In the analysis phase, the problems to be solved can be described using the logic view and dynamic view of UML. Class View is the static structure required to describe the system, A collaboration diagram, a state diagram, a sequence diagram, an activity diagram, and a State Diagram describe the dynamic characteristics of the system. In the analysis phase, only the categories in the problem field are modeled, without defining the detailed problems required by the software system solution. (Such as user interface classes and databases );

Iii. Overall system design stage: In the design phase, the results of the analysis phase should be extended into technical solutions. Add new classes to provide technical infrastructure, including user interfaces and database operations. Domain question categories in the analysis phase are embedded in this technical infrastructure. The result of the design phase isProgramDetailed specifications of the design (encoding stage.

Iv. programming stage:Converts a class in the overall design stage into an object-oriented programming languageCode. It is recommended that you do not directly convert the model into code when you convert the analysis and design model represented by UML. In the early stages, models were a means of understanding the system and structuring the system.

V. Test phase:System Tests are usually divided into several different stages: unit test, integration test system test, and acceptance test. Unit testing tests are performed on several classes, a group of classes, or some functional modules. Generally, some programmers perform tests on their own. Integration Testing integrates components and classes, A combination of multiple modules is used for testing to determine whether collaboration is appropriate between these "units. System Testing tests the entire system to verify whether the system meets the requirements at the beginning of the system design. Different tests can use different UML diagrams as the basis for work: class diagrams and class specification descriptions are used for unit tests, and component diagrams and collaborative diagrams are typically used for integration tests, in the system test, you can use the example view to check whether all the functions of the system meet the requirements defined in the diagrams in the analysis phase.

I am not very skilled in this aspect. I hope you can point out more mistakes. Haha.