"UML Practice"--Summary of actual combat

UML diagram for a long time, read a lot of people's blog, but also with others to communicate a lot, this UML diagram exactly how to draw, many people feel good after watching UML video, can really to draw when, do feel powerless, do not know where to start, at this time, Also can only read the early brother Siang of the blog to borrow, Master told me that this part of the main is to learn some drawing skills, to figure can understand to what extent, learn to what extent. Go through this section as soon as possible. The following is their own understanding of the computer room management system drawing out of the picture, in the case of not knowing right and wrong, there must be a lot of shortcomings. We also hope to point out that:

One, use case diagram : To describe the user's needs, from the user's perspective to describe the function of the system, and the performance of each function, emphasizing who is using the system, the system for the performers to complete those functions.

class Diagram : Used to define classes in a system, including describing the internal structure of a class and the relationship between classes. Class diagrams are mainly used to describe the static structure of a system. Classes are the most important building blocks in object-oriented, and class diagrams show a set of classes, interfaces, collaborations, and relationships between them. The class diagram is oneself originally felt most tangled, because do not know how abstract, communicate with others also disagree, now also can only be based on the feeling to draw, later deepen understanding and then re-revise.

sequence Diagram : Describes the order of interactions between objects, focusing on the time sequence of message delivery between objects, emphasizing the order in which messages are sent between objects. The sequence diagram weighs the interaction of the object, and it can be transformed with the collaboration diagram.

Iv. Collaboration diagram: describes the collaborative relationships between objects and focuses more on explaining which objects have message passing. The time order of a collaboration diagram can only be represented by the number of messages.

v. Activity diagram: used to describe all possible states of an object of a class and the transition condition of the state at the time the event occurred. It shows how entities react to different events based on their current state.

vi. State diagram : A condition that describes all possible states of an object of a class and the state at which the event occurred. It shows how entities react to different events based on their current state.

vii. Component Diagrams: build diagrams are used to describe the physical structure of code components and the dependencies between them. A component can be a resource file, a binary file, or an executable file.

viii. deployment diagram: The deployment diagram defines the physical structure of the hardware in the system to describe the actual physical device and the connection between them.

Summary: by drawing these kinds of diagrams, feel very tangled, especially to the drawing class diagram, do not know how to abstract out the class, from where to start to abstract, and finally through the exchange with the students have a point. In this process I realize the importance of communicating with others, and when you are confused to communicate with others, the collision of ideas will always produce new sparks.