UML simple example Diagram

UML, a unified modeling language, is an object-oriented modeling language. It is mainly used to help users perform object-oriented descriptions and Modeling of software systems (by ing users' business needsCodeTo ensure that the Code meets these requirements and can easily trace back the process of requirements), it can describe the entire process of the software development process from requirement analysis to implementation and testing.

 

Composition of UML:
UML is composed of several parts: View, divisor, model element, and general mechanism.
View: it is a subset of UML modeling elements that express one aspect of the system's features. It consists of Multiple Graphs and is an abstract representation of the system at a certain abstraction layer.
Digrams: a graphical representation of a model element set. It is usually composed of an arc (Link) and a vertex (other model elements.
Model element: it represents the concepts of classes, objects, messages, and relationships in object-oriented systems, and is the most basic and common concept for creating graphs.
General mechanisms: used to represent other information, such as comments and semantics of model elements. In addition, UML provides an extension mechanism that enables the UML language to adapt to a special method (or process) or expand to an organization or user.

 

Classification of UML views:
UML is used to describe a model. A model is used to describe the institutional or static features of a system, as well as behavior or dynamic features. Model the system architecture from different perspectives to form different views of the system.
(1) Use Case view (Use Case view), which emphasizes the system functions you can see or need from the user's perspective, is a model diagram of the system functions observed by external users called participants.
(2) logical view: displays the static or structural components and features of the system, also known as structural model view or static view ).
(3) the concurrent view reflects the system's dynamic or behavioral characteristics, also known as the Behavioral Model View or dynamic view ).
(4) component view (Component view) reflects the structure and behavior characteristics of the system implementation, also known as implementation model view ).
(5) The configuration view reflects the structure and behavior characteristics of the system's implementation environment, also known as the environment model view or the physical view ).

 

A view is composed of graphs. UML provides nine different diagrams:
(1) Use Case digraphs to describe system functions;
(2) Class digraphs, which describe the static structure of the system;
(3) object digraphs, which describe the static structure of the system at a specific time point;
(4) component diagram (Component digoal) describes the organization of elements that implement the system;
(5) Deployment divisor describes the configuration of Environment Elements and maps the elements that implement the system to the configuration;
(6) State divisor describes the state conditions and responses of system elements;
(7) sequence digoal, which describes the interaction between system elements in chronological order;
(8) Collaboration digraphs: Describes the interaction between system elements and their relationships in chronological and spatial order;
(9) activity digraphs, which describe the activity of system elements;

 

Based on their applications in different architecture views, nine types of graphs can be divided:
(1) User Model View: use case diagram;
(2) Structure Model View: class chart and object chart;
(3) Behavior Model View: status chart, sequence chart, collaboration diagram, and activity diagram (dynamic diagram );
(4) Model View: component diagram;
(5) Environment Model View: configuration chart.

 

UML modeling mechanism:
UML has two modeling mechanisms: static modeling and dynamic modeling. Static Modeling mechanisms include the use case diagram, class diagram, object diagram, package, component diagram, and configuration diagram. The dynamic modeling mechanism includes the status chart, sequence chart, collaboration diagram, and activity diagram.
(1) use case diagram: A visualization tool for use cases. It provides a high-level user view of the computer system, indicating how the system will be used from the perspective of other activists.
The use case diagram includes the following three aspects:
(1) Use Case)
(2) Participants)
(3) Dependency, generalization, and Association
Example diagram:

(2) class diagram: a diagram describing classes, interfaces, collaboration, and relationships between them.
Class legend:

(3) object graph: a graph showing a group of objects and their relationships at a time. An object chart can be seen as an instance of a class chart at a certain time point of the system.

(4) component diagram: describes the relationship between software components and components. The component itself is the physical module of the code, and the component diagram shows the structure of the Code.
Component legend:

(5) configuration diagram: Describes the physical topology of the system hardware and the software executed on this structure. The configuration chart displays the topology and communication path of the computing node, the software components running on the node, and the logical units (objects and classes) contained in the software components. A configuration chart is often used to help you understand distributed systems.
Configure the legend:

(6) status chart: Describes the dynamic behavior of objects that change over time by creating a model based on the lifecycle of objects.
Status chart example:

(7) Time Sequence diagram: an interaction diagram describes an interaction. It consists of a group of objects and their relationships, and contains information transmitted between objects. Interactive charts form interactions between objects. They are modeling tools that describe how a group of objects collaborate to complete a behavior. A time sequence diagram is an interaction diagram that emphasizes the time sequence of messages.
Sequence Chart example:

(8) Collaboration diagram: Includes class meta-roles and associated roles, not just class meta-associations. The collaboration diagram emphasizes the organizations of the objects participating in the interaction. A collaboration diagram only models the relationships between objects that interact with each other and these objects, while ignoring other objects and associations.
Collaboration legend:

(9) activity diagram: used to show the activities or actions of the classes involved in the behavior.
Activity legend: