(UML Summary II) Nine kinds of graphs

Last summed up the relationship in UML, understand the relationship, let us summarize the UML in the nine kinds of diagrams. Graphs are often more intuitive than text, so when we develop software, the document must have a diagram, so these nine kinds of maps we have to master.

I'll split the nine graphs below:

We can also divide these nine graphs into static and dynamic graphs:

First, the basic concept:

1. Use case diagram (uses Casediagram)

A view that is composed of actors, use cases, and their relationships to describe system functions. Use case diagram is mainly used to illustrate the needs of users, the development of software should have what kind of function, realize what value. From the use case diagram we can see who is using the software and software features.

It mainly includes use cases, participants and relationships.

2. Class Diagram (Classdiagram)

The user abstracts the class based on the use case diagram, including the relationships between the internal properties, methods, and classes between the classes.

It mainly includes classes, attributes, methods, and relationships.

3. Object Graph (Objectdiagram)

is an example of a class diagram that describes the static structure of a system at a specific point in time. The object graph corresponding to the same class diagram can have multiple, multiple object graphs together to show the changes over time, different point-in-time system object changes.

It mainly includes objects, connections, and packages.

4. State diagram (Statechartdiagram)

Used to describe all possible states of a particular object and the transition between States due to the occurrence of a variety of things.

Mainly includes state, shift, start and end points.

5. Activity Chart (Activitydiagram)

A diagram describing the active state of a system is a special case of a state diagram. The difference from a flowchart is that you can support parallel activities.

Mainly includes activity state, transfer, judgment, Swimlane, start point, end point, synchronization bar.

6. Sequence Diagram (Sequencediagram)

A type of interaction diagram that describes the process of interaction between objects in chronological order.

Mainly includes objects, messages, lifelines.

7. Collaboration Diagram (Collaborationdiagram)

A kind of interaction diagram that describes the organization relationship of the objects that send and receive messages, focusing on the relationships between objects.

Mainly includes objects and messages.

8. Component Drawing (Componentdiagram)

This paper describes the main functions of a system from the perspective of software architecture, and describes the organization and dependencies between the physical structure of a set of code artifacts.

It mainly includes components, interfaces and relationships.

9. Deployment Diagram (Deploymentdiagram)

Describes the nodes that are processed by the system runtime and the configuration of the artifacts that are active on the nodes. The physical devices used in the system and the connections between them are emphasized.

Mainly include nodes and relationships.

Second, the comparison of graphs and graphs

1. Sequence diagram and collaboration diagram

sequence diagrams and collaboration diagrams are interactive diagrams, which can be transformed from one another, the biggest difference being that the emphasis is not the same. Sequence diagrams emphasize the sequencing of time, and collaboration diagrams focus on the relationships between objects. Here is the collaboration diagram and sequence diagram on the machine.

On-Machine collaboration diagram

On-Machine sequence diagram

2. State diagram and activity diagram

You can say that a state diagram includes an activity diagram. Because a state diagram is a description of all possible states of a particular object on the system. And the activity diagram is the description of the system in the active state, emphasizing the action.

Third, summary

The nine kinds of diagrams in UML are introduced and contrasted separately, but if we want to know better, we should continue to fighting~~~~~ through practice.

(UML Summary II) Nine kinds of graphs