Shulou(Shulou.com)06/01 Report--

This article mainly introduces the relevant knowledge of "what are the legends of UML design". Xiaobian shows you the operation process through actual cases. The operation method is simple and fast, and the practicability is strong. I hope this article "what are the legends of UML design" can help you solve the problem.

9 Illustrations of UML Design

First of all, a brief introduction to the function of each diagram in UML:

1. Use case diagram

Describe roles and the connections between roles and use cases. It describes who is going to use the system and what they can do with it. A use case diagram contains multiple model elements, such as systems, actors, and use cases, and shows the relationships between these elements, such as generalizations, associations, and dependencies.

2. Class diagram

A class diagram in UML design is a static view that describes the classes in a system and the relationships between them. It allows us to have a comprehensive view of the system before writing code correctly. A class diagram is a type of model, specifically, a static model type.

3. Object diagram

Much like a class diagram, it is an instance of a class diagram, with an object diagram showing multiple object instances of a class rather than the actual class. It describes not relationships between classes, but relationships between objects.

4. Activity chart

Describing the activities required by the use case and the constraints between them is helpful for identifying parallel activities. Demonstrate where functionality exists in the system, and how that functionality, along with the functionality of other components in the system, meets the business requirements modeled earlier using use case diagrams.

5. State diagram

Describes all possible states of an object of a class, as well as transition conditions for states when events occur. You can capture the lifecycle of objects, subsystems, and systems. They can tell what states an object can have and how events (such as message receipt, passage of time, errors, conditions becoming true, etc.) affect those states over time. A state diagram should be connected to all classes with clearly identifiable state and complex behavior; the diagram can determine the behavior of the class and how that behavior changes based on the current state, and can show which events will change the state of the class's objects. State diagrams are complementary to class diagrams.

6. Sequence diagram (sequence diagram)

A sequence diagram in UML design is a model used to show how your participants interact with the objects of a system in a sequence of steps. Sequence diagrams can be used to show how objects interact. The sequence diagram focuses the display on the sequence of messages, emphasizing how messages are sent and received between objects.

7. Collaboration Chart

Similar to sequence diagrams, it shows dynamic collaboration between objects. Think of it as the intersection of class diagrams and sequence diagrams, collaboration diagrams modeling objects or roles, and how they communicate with each other. Use sequence diagrams if you emphasize time and sequence; choose collaboration diagrams if you emphasize hierarchy; these two diagrams are collectively called interaction diagrams.

8. Component drawing (assembly drawing)

Describes the physical structure of code artifacts and dependencies between various builds. Used to model software components and their relationships to each other. These diagrams consist of component markers and relationships between components. In a component diagram, a component is a single component of software. It can be a file, product, executable file, script, etc.

9. Deployment diagram (configuration diagram)

Deployment diagrams in UML design are used to model the physical deployment of a system. Computers and devices, and how they connect. The consumers of deployment diagrams are developers, system integrators, and testers.

There are several differences in UML design:

I: Each of these nine models has its own emphasis

1: Use case diagrams focus on describing user requirements,

2. Class diagrams emphasize on describing the specific implementation of the system;

2: The descriptions are different.

1: The class diagram describes the structure of the system,

2: Sequence diagrams describe the behavior of the system;

3: The level of abstraction is also different

1: Component diagram describes the module structure of the system, with a high level of abstraction,

2: Class diagram is to describe the structure of specific modules, abstract level is general,

3: Object diagrams describe concrete module implementations at a lower level of abstraction.

In some literature books, UML design divides these nine model diagrams into three categories:

Structural classification, dynamic behavior, and model management:

1: Structure classification includes use case diagram, class diagram, object diagram, component diagram and deployment diagram.

2: Dynamic behavior includes state diagram, activity diagram, sequence diagram and collaboration diagram,

3: Model management includes class diagrams.

About "UML design legend what" content is introduced here, thank you for reading. If you want to know more about industry-related knowledge, you can pay attention to the industry information channel. Xiaobian will update different knowledge points for you every day.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.