Introduction to the concept and model of UML: nine types of UML diagrams

Folder:

1. UML View
2. Nine types of UML diagrams
3. Relationships between classes in UML

As described above, the UML view includes one or more diagrams in each view. This article focuses on the details of each UML diagram:

1. Use Case Diagrams)

[Concept] describes user requirements, and describes system functions from the user's perspective.

Description: an elliptic represents a use case. A humanoid symbol represents a role.

Objective: To help the development team understand the functional requirements of the system in a visual manner

[Example]

2. Static Graph

1. Class Diagrams)

[Concept] displays the static structure of the system, indicating how different entities are associated.

Description: three rectangles.

Objective: To represent a logic class or implementation class. A logical class is generally the thing involved in the user's business. An implementation class is the entity processed by the program ape.

Class Diagram]

1. Object diagrams)

[Concept] An example of a class chart describes the objects included in the system at a detailed time point and the relationships between objects.

[Object diagram]

3. Interaction Diagram

Used to describe the interaction between objects.

1. Sequence Diagram (sequence diagram)

[Concept] describes the interaction sequence between objects and focuses on the time sequence of message transmission between objects.

Description Method: spans the top of the graph. Each box indicates the instance or object of each class. The class instance names and class names are separated by colons.

[Objective] To display the call relationships between different objects in a process and different calls of different objects.

[Sequence diagram]

1. Collaboration diagrams)

[Concept] describes the cooperative relationship between objects, and refers to message transmission between objects.

4. behavior diagram: Describes the interaction between the dynamic model of the system and objects.

1. Status chart (statechart diagrams)

[Concept] describes the entire state of an object and the transfer between States caused by events.

[Description]

1. Starting point: solid circle
2. Transition between States: line segments with arrows
3. Status: rounded rectangle
4. Inferred point: hollow circle
5. One or more ending points: contains the circle of the solid circle.

Objective: To indicate the different states of a class and the conversion process of the class in these states

2. Activity Diagrams)

[Concept] describes the activities required to meet the requirements of use cases and the constraints of the activity time.

[Description]

1. Starting point: solid circle
2. Activity: rounded rectangle
3. End Point: contains the circle of the solid circle.
4. Swimming track: the object that actually runs the activity

Objective: Process Control Process for processing an activity between two or more objects

Activity diagram]

Differences between the activity chart and the status chart:

5. Implementation Diagram

1. Component diagram (Component diagrams)

[Concept] describes the physical structure of code components and their dependencies.

Description Description: Component

Objective: To provide a physical view of the system and display the entire physical structure of the system code based on the system code Components

[Architecture diagram]

1. Deployment Diagrams)

Concept: physical architecture of hardware in the system

[Description]

1. 3D cube Representation component
2. The node name is located at the top of the cube.

Objective: To display the physical structure of the hardware and software of the system

[Deployment diagram]

The nine types of UML diagrams have been explained so far. The next article will explain the relationships between classes in UML. Thank you for your attention.