(1) Class diagram: A class diagram describes a set of classes, interfaces, collaborations, and the relationships between them. In the modeling of 00 system, the most common diagram is the class diagram. The class diagram gives the static design view of the system, and the class diagram of the active class gives the static process view of the system.
(2) object diagram (object diagram): object diagram describes a set of objects and the relationship between them. Object diagrams describe static snapshots of instances of things created in class diagrams. Like class diagrams, these diagrams give a static design view or a static process view of the system, but they are built from the perspective of a real or prototype case.
(3) Component diagram (component diagram): A component diagram describes an encapsulated class and its interfaces, ports, and the internal structure composed of embedded components and connectors. A component diagram is used to represent a static design implementation view of a system. Component diagrams are important for building large systems from small parts. Component diagram is a variant of class diagram.
(4) Composite structure diagram: A composite structure diagram describes the internal structure of a structured class (eg, a component or class), including the interaction points between the structured class and the rest of the system. Composite structure diagrams are used to draw the internal content of structured classes.
(5) Use case diagram (use case diagram): A use case diagram describes a set of use cases, actors and their relationships. A use case diagram gives a static use case view of the system. These diagrams are very important in organizing and modeling the behavior of the system.
(6) Sequence diagram (sequence diagram, also known as sequence diagram): A sequence diagram is an interaction diagram . An interaction diagram presents an interaction, which consists of a set of objects or actors and messages that may be sent between them. Interaction diagrams focus on a dynamic view of the system. A sequence diagram is an interaction diagram that emphasizes the temporal order of messages.
(7) Communication diagram: A communication diagram is also an interaction diagram that emphasizes the structural organization of objects or participants who send and receive messages. Sequence diagrams and communication diagrams express similar basic concepts, but they emphasize different concepts. Sequence diagrams emphasize timing, while communication diagrams emphasize the organizational structure (relationship) between objects. In the UML IX version, communication diagrams are called collaboration diagrams.
(8) Timing diagram (timing diagram, also known as timing diagram): A timing diagram is also an interaction diagram that emphasizes the actual time of messages across different objects or participants, not just the relative order of messages.
(9) State diagram (state diagram): A state diagram describes a state machine, which consists of states, transitions, events and activities. A state diagram gives a dynamic view of an object. It is particularly important for modeling the behavior of interfaces, classes, or collaborations, and its emphasis on event-induced object behavior is very useful for modeling reactive systems.
(10) Activity diagram (activity diagram): An activity diagram shows a process or other computational structure as a step-by-step control flow and data flow within the computation. Activity diagrams focus on a dynamic view of the system. It is particularly important for functional modeling of systems and business process modeling, and emphasizes the flow of control between objects.
(11) Deployment diagram (deployment diagram): The deployment diagram describes the configuration of the runtime processing nodes and the components that live in them. A deployment diagram gives a static deployment view of the architecture, usually a section contains one or more deployment diagrams.
(12) Artifact diagram: The artifact diagram describes the physical structure of a system in a computer. Artifacts include files, databases, and similar collections of physical bits. Artifact diagrams are often used in conjunction with deployment diagrams. Artifacts also give the classes and components they implement.
(13) Package diagram (package diagram): The package diagram describes the organizational units decomposed by the model itself, and the dependencies between them.
(14) Interaction overview diagram: The interaction overview diagram is a mixture of activity diagrams and sequence diagrams.