Nine kinds of UML diagrams + package diagrams

Original address: http://blog.csdn.net/caozhangyingfei0109/article/details/8534191 Nine



kinds of UML diagrams + package diagrams (?)[+] Nine kinds of UML diagrams: use case diagram, class diagram, object diagram, state diagram, activity diagram, sequence diagram, collaboration diagram, component diagram, deployment diagram. Plus package map. (1), use case diagram 1. Definition: The dynamic view used to describe the function of the system composed of actors (Actor), use cases (Use Case) and the relationship between them is called use case diagram. 2. Brief introduction: use case diagram It is mainly used to model the functional requirements of the system. It mainly describes the functions of the system, that is, from the perspective of external users, what functions the system should complete, which is helpful for developers to understand the functional requirements of the system in a visual way. At the same time, it is also to facilitate the understanding of users and system analysts as much as possible, and to provide users and system analysts with a popular and consistent method to accurately grasp the needs of the system, which can save time and improve efficiency! The use case approach is to define the system functionality completely from the outside, and it completely separates the requirements from the design. We don't need to care about how various functions are completed inside the system, the system is a black box for us. The use case diagram clearly describes the generalization relationship between users and them, the generalization and extension relationship between use cases and use cases, and the association relationship between use cases and participants. an overall impression. 3. Map overview 4. Use case diagram (computer room charging system) (2) Class diagram 1. Definition: It is a static diagram that is associated with several classes and reflects the structure of the system or subsystem.





















2. Brief introduction: The modeling of class diagram runs through the analysis and design stages of the project.
Class diagrams are used to describe the static parts of a system.

3. Map overview


4. Class diagram (computer room charging system)


(3) Object diagram

1. Definition: The object diagram describes the static structure of a system at a specific moment.
2. Brief introduction: An object diagram is actually an instance of a class diagram.
An object diagram represents a set of objects and their connections. It is a snapshot of the detailed state of the system at a certain moment. It is often used to represent an instance of a complex class diagram.
Object diagrams in UML have the same representation as class diagrams.
In UML, the use of object diagrams is rather limited and is mainly used to express instances of data structures and to understand what the system is like at a particular moment in time.

3. Map overview


4. Object diagram (computer room charging system - registration)



(4), state diagram

1. Definition: used to describe all possible states of a specific object and the relationship between states caused by the occurrence of various events transfer.
2. Brief introduction: Statechart Diagram (Statechart Diagram) describes the dynamic behavior of an entity based on event responses, showing how the entity responds to different events according to the current state. Usually we create a UML state diagram for the following research purposes: to study the complex behavior of a class, role, subsystem, or component.
Generally, a state machine can be used to model the life cycle of an object, and the state diagram is used to display the state machine (State Machine Diagram), focusing on describing the control flow of the state diagram.

3. Map overview


4. State diagram (computer room charging system - registration)


(5) Activity diagram

1. Definition: clarify the workflow of business use case implementation.
2. Brief introduction: Activity diagram is another common tool used by UML to model the dynamic behavior of the system. It describes the sequence of activities and shows the control flow from one activity to another. An activity diagram is essentially a flowchart. Activity diagrams focus on the flow of control from one activity to another, which is an internal process-driven process.
The activity diagram describes the rules followed by the sequence relationship of object activities, and it focuses on the behavior of the system, rather than the processing process of the system. Activity diagram can represent the situation of concurrent activities, activity diagram is object-oriented.
3. Map overview


4. Activity diagram (computer room charging system - registration)




(6) Sequence diagram (also known as sequence diagram, sequence diagram)

1. Definition: It is a visual representation of the time sequence of messages transmitted between objects.
2. Brief introduction: The purpose of the sequence diagram is to describe the interaction process of each object in the system in the order of time.
Sequence diagrams represent interactions as a two-dimensional diagram. The vertical is the time axis, and time runs down the vertical line. The horizontal axis represents the taxonomic roles of individual objects in the collaboration. Class meta roles are represented by lifelines. When the object exists, the character is represented by a dashed line, and when the object's process is active, the lifeline is a two-way line.
Messages are represented by arrows from one object's lifeline to another object's lifeline. The arrows are arranged in chronological order from top to bottom in the figure.

3. Map overview


4. Sequence diagram (computer room charging system - registration)


(7), collaboration diagram (also known as cooperation diagram)

1. Definition: describe the interaction between mutual cooperation objects.
2. Brief introduction: UML collaboration diagram is an interaction diagram that emphasizes the organizational structure between objects that send and receive messages.
UML collaboration diagrams are used to show how objects interact to perform the behavior of a specific use case or a specific part of a use case. Designers use UML collaboration diagrams and sequence diagrams to identify and clarify the roles of objects that perform specific flow of events for a use case. They are the primary source of information for determining class responsibilities and interfaces.
Unlike sequence diagrams, UML collaboration diagrams show the relationships between objects. Sequence diagrams and UML collaboration diagrams represent similar information, but in different ways. UML collaboration diagrams show the relationships between objects, it is better for understanding all the effects on a given object and it is more suitable for process design.
The format of UML collaboration diagrams makes them more suitable for use in analytical activities. They are particularly suitable for describing simple interactions between a small number of objects. Understanding UML collaboration diagrams becomes increasingly difficult as the number of objects and messages increases. Furthermore, UML collaboration diagrams are difficult to display supplementary descriptive information, such as times, decision points, or other unstructured information, which can easily be added to annotations in sequence diagrams.
Sequence diagrams are often used to represent solutions, and collaboration diagrams are used for detailed design of processes.

3. Map overview


4. Collaboration diagram (computer room charging system - registration)


(8) Component diagram

1. Definition: It is mainly used to describe the dependencies between various software components.
2. Brief introduction: Component diagram describes the main functions of a system from the perspective of software architecture, such as subsystems, classes, packages, components, etc.
The most important thing about using components is reuse.
A component is a physical, replaceable part of a system that conforms to the same set of interfaces and provides its implementation.
Component diagrams provide a physical view of the system, showing the dependencies between components in the system at a very high level.

3. Map overview


4. Component diagram (computer room charging system)


(9), deployment diagram

1. Definition: Describes the hardware nodes of a system runtime, a static view of where the software components running on these nodes will physically run and how they will communicate with each other
2. Brief introduction: System developers and deployers can take advantage of Deployment diagrams to understand the physical operation of the system. If the developed software system only needs to run on one computer and uses standard equipment, there is no need to draw a system deployment diagram for it. Deployment diagrams only need to model those complex physical operations.
The deployment diagram shows the hardware of the system, the software installed on the hardware, the various protocols and middleware used to connect the hardware, etc.
The purpose of the deployment model: to describe the main deployment structure of a specific application, through the display of various hardware, software in the hardware and various connection protocols, it can be a good description of how the system is deployed; balance the calculation of system runtime Resource distribution; it can describe the organization's hardware network structure or embedded system and other system operation models related to hardware and software through connections.

3. Map overview


4. Deployment diagram (computer room charging system)


(10), Package diagram (package diagram is not an official UML diagram)

1. Definition: A package diagram is a model element represented by a symbol similar to a folder in UML Combination
2. Brief introduction: Package diagram is an important modeling tool for maintaining and describing the model of the overall structure of the system. dependencies.
The role of the package diagram: the package diagram can describe the requirements and the high-level overview of the design; the package diagram logically decomposes the system into modularized modules by rationally planning the high-level structure of its own function response system; the package diagram is ultimately the way to organize the source code.
A package diagram can be composed of any kind of UML diagram, usually a UML use case diagram or a UML class diagram.
Packages are described as folders and can be used on any UML diagram.
A package diagram just puts some classes in a package, so it can be seen as a type of class diagram.

3. Map overview


4. Package map (computer room charging system)

Link to this article: http://blog.csdn.net/caozhangyingfei0109/article/details/8534191
The author of this article: Zhang Bo, Phase 9, Information Technology Improvement Class of Langfang Normal University