UML Modeling Learning 4:uml basic building block diagram

continue today to see the diagrams in the UML basic building blocks.

a diagram of a UML basic building block

A diagram of a UML basic building block is an abstract description of the system in a specific perspective. A graph is the classification of a collection of things, and UML contains many diagrams. Let's look at the categories first:

UML defines 5 classes, 10 model diagrams

Five kinds of diagram definition:

1 Use case diagram: Describe the system function from the user's point of view and refer to the operator of each function.

2 static diagram: Includes class diagram, package diagram, object graph.

2.1 Class Diagram: Describes the static structure of classes in the system.

2.2 Package diagram: is a package and class that represents the relationship between packages and packages, and package diagrams describes the hierarchical structure of the system.

2.3 Object graph: An instance of a class diagram.

3 behavior diagram: Describes the exchange relationship between the system dynamic model and the object composition. Includes a state diagram and an activity diagram.

3.1 Activity diagram: Describes the workflow of the business implementation use case.

3.2 State diagram: is a state-to-state control flow that is often used to model dynamic properties.

4. Interaction diagram: Describes the interaction between objects, including sequence diagrams and collaboration diagrams.

4.1 Sequence diagram: A dynamic partnership between objects that emphasizes the order in which the objects send messages, and shows the interaction between objects.

4.2 Collaboration diagram: Describes the assistance relationships between objects.

5. Implementation diagram:

5.1 Deployment diagram: Defines the physical architecture of hardware and software in the system.

5.2 Component diagram: Describes the physical structure of the code part and the dependencies between the components.

Two UML five types of 10 diagrams Overview use case diagram:

(1) Use case diagram (use-case Diagram)

use case diagram describes the functions and requirements of the system from the user's point of view, and displays various roles and departments outside the system . the relationship between the various use cases within the system;

use case diagrams describe the role and the connection between roles and use cases. It explains who wants to use the system and what they can do with the system. A

A use case diagram contains several model elements, such as systems, actors, and use cases, and each of these elements is shown relationships, such as generalization, correlation, and dependency.

Use case diagrams are used to describe the user's needs, describe the functions of the system from the user's perspective, and point out the performers of each function, emphasizing who is using the system, the system

What functions are performed for performers.

such as (from the network):

static diagram:

(2) class diagram (class Diagram)

class diagrams are used to define classes in the system, including the classes that the system contains, the internal structure of the class, and the relationships between classes. Class Diagrams are primarily used to describe the system's

Static structure.

A class diagram is a static view that describes a class in a system and the relationships between classes. Allows us to have a comprehensive overview of the system before writing the code correctly

The understanding. A class diagram is a model type, exactly, a static model type. Class diagrams represent classes, interfaces, and collaborative relationships between them.

such as (from the network):

(3) object graph (Diagram)

An object graph is very similar to a class diagram, which is a concrete instance of a class diagram that shows multiple object instances of a class rather than the actual class. It describes the

is not a relationship between classes, but a relationship between objects. The object graph describes the objects that the system contains at a specific point in time, as well as the closing of individual objects.

System.

such as (from the network):

(4) package Diagram

Package diagrams indicates the dependency class diagram of a package and its dependencies, which are used to describe the hierarchical structure of a system, consisting of a package or class that represents the relationship between packages and packages.

such as (from the network):

behavior diagram:

(5) state diagram (Statechart Diagram)

A state diagram describes all possible states of a class of objects and the transition condition of the state when an event occurs. Can capture the life cycle of objects, subsystems, and systems

Period. They can tell the state that an object can have, and how the event (such as the receipt of a message, the passage of time, the error, the condition becomes true, etc.) will follow

Affect these states over time. A state diagram should be connected to all classes that have a clear, identifiable state and complex behavior, and the graph can determine the class

Behavior, and how the behavior changes depending on the current state, or what events will change the state of the object of the class. A state diagram is a complement to a class diagram.

Filled.

such as (from the network):

(6) Activity Map (active Diagram)

activity diagrams Describe the sequence of execution of various activities in the system, describe the activities that are required by the use cases, and the activities the relationship between the two is advantageous to identify and

line activity. Ability to demonstrate where functions exist in the system, and how these functions and the capabilities of other components in the system meet the previous use case diagram

Modeling business needs.

such as (from the network):

interaction diagram:

(7) Sequence diagram (Sequence Diagram, also known as sequence diagram)

A sequence diagram represents a dynamic cooperative relationship between objects. Describes the order of interactions between objects, focusing on the time sequence of message passing between objects, emphasizing

The order in which messages are sent between images, and also shows the order of interactions between objects.

A sequence diagram is a model that shows how your participants interact with the system's objects in a series of sequential steps. Sequence diagrams can be used to show objects between

How the interaction is done. The sequence diagram will focus on the message sequence, emphasizing how messages are sent and received between objects.

such as (from the network):

Implementation diagram:

(8) Collaboration diagram (collaboration Diagram, also known as co-operation Chart)

A collaboration diagram describes the collaboration between objects, and it focuses more on what objects have message passing between them. Similar to the sequence diagram, showing the dynamic between objects

Cooperative relationship. Can be seen as the intersection of a class diagram and a sequence diagram, a collaborative diagram modeling object or a role, and how they communicate with each other.

such as (from the network):

If the time and order are emphasized, the sequence diagram is used, and if the subordinate relationship is emphasized, the collaboration diagram is selected, and the two graphs are called interaction graphs. Sequence Diagrams and

Collaboration diagrams can be transformed into one another.

(9) Component Diagram (Compoment Diagram, also called component diagram)

The component diagram describes the physical structure of the code part and the dependencies between the parts. A component can be a resource file, a binary file, or

An executable file for the user.

Component diagrams are used to model software components and their relationships with each other, and these graphs are composed of the relationship between the component marker and the component. In the component diagram, the structure

Piece is a single component of the software, it can be a file, product, executable file and script, etc.

such as (from the network):

(10) Deployment diagram (Deployment Diagram, also known as implementation diagram or configuration diagram)

The deployment diagram defines the physical architecture of hardware and software in the system to describe the actual physical device and the connection between them. The deployment diagram is used to build

The physical deployment of the modular system. such as computers and devices, and how they are connected. The users of the deployment diagram are developers, system integrators, and

Testers. The deployment diagram is used to represent a set of physical nodes and the relationship between nodes, thus establishing a system physical level model.

such as (from the network):

three UML modeling mechanisms

From the application point of view, when using object-oriented technology to design the system, the first is to describe the requirements, secondly, according to the requirements of the system to establish a static model, to construct

Structure of the system; The third step is to describe the behavior of the system. The models established in the first and second steps are static, including use case diagrams, Class diagrams (Package

including package), object graph, Component diagram and heat map, etc. five graphs, is the standard modeling language UML static modeling mechanism. The model created in the third step is either

Can execute, or indicate the timing state or interaction at execution time. It includes four diagrams, such as state, activity, sequence, and collaboration diagrams in UML model diagrams.

is the dynamic modeling mechanism of UML in standard modeling language. Therefore, the main content of UML in standard modeling language can be summed up as static modeling mechanism and dynamic building

Two main types of mold mechanism.

Summary of UML Basic building blocks:

Things are abstractions of the most representative components of a model; relationships combine things together; graphs gather related things.

UML Modeling Learning 4:uml basic building block diagram