Mobile Project Development notes (UML overview Reading Notes)

Hi all,
Some time ago, I participated in the project mainly in the implementation of usecase, state chart, and avti.pdf in UML. It can be said that it was the first time I drew UML in the actual project, I used to think that UML is useless. Maybe it is the reason why the project is not large. In a relatively large project, UML can be used to better understand the project, clarify the project functions, and clarify the data flow. This is to make it easy to have a glimpse of the UML diagram. The following is a summary: I hope you can give me more advice.
1. Names and functions of various UML figures (Summary)
1. usecase
The role of actor use case document use cases in development, the relationship between Use Case paths and extension points, use case diagrams, and Use Cases
2. Static System Modeling
Class Diagram
3. Dynamic System Modeling
Sequence, collaboration, state chart, avtivity
4. System Architecture
Component deploy
1. Describe the system structure:
Use case diagram: requirement capture, test basis
Class diagram: static structure
Object graph: association between objects
Build association between graph Construction
Physical deployment of deployment chart Components
2. Describe system behavior:
Sequence diagram: Capture Time Sequence
Collaboration diagram: force object collaboration
Status chart: Declares periodic State Transition
Activity diagram: Workflow Model

Ii. use UML in the development process (Summary)
1. Complete Use Case digoal & document.
2. Auxiliary description of complicated usecase using activity diagrams.
3. According to use case document and activity digoal, this paper analyzes the concepts of the business field and abstracts the conceptual model.
4. Analyze the conceptual model and abstract the class.
5. Analyze the responsibilities and relationships of the class and make a class diagram.
6. Create sequence, collaboration, state chart, and other diagrams based on the class chart.
7. Repeat 5-6 until "perfect ".
8. Coding
9. Test and modify. If necessary, start from the previous step, or start from 1 or 5.
10. Deploy and test with the user.
11. Drive the next 1-> 11 from implementation and test feedback

Finally, I hope my friends can provide valuable comments! Thx
Regards,
Charles