Introduction to the functions of the nine types of UML diagrams

UML (Unified Modeling Language): It is an object-oriented visual modeling language.

UML has three types of constructor blocks: Things, relationships, and graphs. Things are the abstraction of the most representative components in the model. links are the combination of things, and graphs aggregate related things.

There are nine types of diagrams in UML:

1. use case diagram

Describes the role and the connection between the role and the use case. It indicates who wants to use the system and what they can do with the system.

2. Class Diagram

A class diagram is a static view that describes the classes in the system and the relationships between classes. This gives us a comprehensive understanding of the system before writing the code correctly. A class chart is a model type. Specifically, it is a static model type.

3. object graph

Similar to a class chart, it is an instance of a class chart. An object chart shows multiple object instances of the class, rather than the actual class. It describes not the relationship between classes, but the relationship between objects.

4. activity diagram

Describing the activities required by the use case and the constraints between the activities helps to identify parallel activities. Demonstrate the functions in the system

5. status chart

Describes all possible states of the object of the class and the transfer conditions of the State when an event occurs. It can capture the lifecycle of objects, subsystems, and systems. They can tell the status that an object can have, and how events (such as message receiving, time passing, errors, and condition becoming true) affect these statuses over time. A status chart should be connected to all classes with clear identifiers and complex behaviors. It can determine the behavior of the class and how the behavior changes according to the current status, it can also show which events will change the object state of the class. A status chart is a supplement to a class chart.

6. Sequence Diagram (sequence diagram)

A sequence diagram is a model used to show how your Participants interact with system objects in a series of sequential steps. A Sequence Chart can be used to show how objects interact. The sequence diagram focuses on the message sequence, that is, how messages are sent and received between objects.

7. Collaboration Diagram

Similar to a sequence diagram, a dynamic cooperative relationship between objects is displayed. It can be seen as the intersection of a class chart and a sequence chart, a collaboration Graph Modeling object or role, and how they communicate with each other. If the time and order are emphasized, a sequence diagram is used. If the upper-and lower-level relationship is emphasized, a collaboration diagram is selected. These two types of diagrams are called interaction diagrams.

8. Component diagram (Component diagram)

Describes the physical structure of code components and the dependencies between various builds. Components used to model software and Their Relationships. These graphs are composed of the relationship between component tags and components. In the component diagram, a single component of the software can be a file, product, executable file, and script.

9. Deployment Diagram

Is the physical deployment used to model the system. For example, computers and devices, and how they are connected. The deployment diagram uses developers, system integrators, and testers.

 

 

In the demand stage: Use Case Diagrams to describe the demand

In the analysis phase: class diagrams are used to describe static structures.

In the design phase: design class interfaces using class charts and package charts

In the implementation phase: implement classes in an object-oriented language

In the integration and delivery phase: component diagram, package diagram, and deployment Diagram

In the test phase: unit test class diagrams and Class Specification

Class diagram, package diagram, component diagram, and contract diagram are used in the integration test phase.

System test use case diagram to test system functions