Article Directory
Preface
A programmer who doesn't want to be an architect is not a good team leader.
Yesterday, I showed my "architecture diagram" to my senior, and I realized that it is not an architecture diagram. It is almost half the use case diagram plus half the flow chart.
Therefore, it is too embarrassing to know the shame and be brave.
I don’t intend to write too many words in this article, everything is in no words, a picture is worth a thousand words.
Architecture diagram
I collected some architecture diagrams some time ago, and the senior also gave me a demonstration:
Example I am looking for:
Reference material:
Software architecture overview
Participation phase:
needs analysis phase
Use case diagram
Use case diagram: A use case diagram refers to a view composed of actors (Actor), use cases (Use Case), boundaries, and the relationships between them to describe system functions. It is the blueprint of the system.
It mainly describes system functions, that is, from the perspective of external users, what functions the system should complete, which is helpful for developers to understand the functional requirements of the system in a visual way. At the same time, it is also to facilitate the understanding of users and system analysts to be as consistent as possible, and to provide users and system analysts with a common and consistent method to accurately grasp the needs of the system, which can save time and improve efficiency!
Reference material:
Use case
Participation phase:
needs analysis phase
flow chart
I won't say much about what is a flowchart. The compulsory third of high school mathematics is taught.
Participation phase:
needs analysis phase
Deployment diagram
The deployment diagram (deployment diagram, configuration diagram) is used to show the physical architecture of the software and hardware in the system. From the deployment diagram, you can understand the physical relationship between the software and hardware components and the distribution of processing nodes. Use deployment diagrams to show the structure of the runtime system, while also conveying how the hardware and software elements that make up the application are configured and deployed.
Next enter the outline design stage
Class Diagram
Class diagram: Class diagram (Class diagram) shows the static structure of the model, especially the classes that exist in the model, the internal structure of the classes, and their relationships with other classes.
I have a lot of class diagrams, and I have written so many design patterns
Reference materials:
UML class diagram quick start
Participation phase:
outline design phase
Next enter the detailed design stage
Timing diagram
Sequence diagram: (Sequence Diagram), also known as sequence diagram, sequential diagram, is a UML interaction diagram. It shows the dynamic collaboration between multiple objects by describing the time sequence of sending messages between objects.
Knot
It is recommended to collect, you may not find it when you paddle.
