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

This article mainly introduces how many kinds of UML views there are, the text is very detailed, has a certain reference value, interested friends must read!

UML diagrams

UML provides 9 kinds of views in total, which provide powerful support for software system analysis, design and implementation from different application levels and different angles. Different models are built at different stages and for different purposes. The nine UML diagrams are as follows:

(1) Use Case Diagrams

A use case diagram describes a functional unit provided by the system. The primary purpose of use case diagrams is to help the development team understand the functional requirements of the system in a visual way, including relationships between "actors"(other entities that interact with the system) based on basic processes, and relationships between use cases within the system.

(2) Class Diagrams

A class diagram represents how different entities (people, things, and data) relate to each other; in other words, it shows the static structure of the system.

(3) Sequence Diagrams

Sequence diagrams in UML views show the detailed flow of a specific use case (or part of a use case). It is almost self-describing and shows the invocation relationships between different objects in the process, as well as the different invocations to different objects in great detail. A timing diagram has two dimensions: the vertical dimension shows the sequence of messages/calls in chronological order of occurrence; and the horizontal dimension shows the object instances to which messages are sent.

(4) Statechart Diagrams

State diagrams represent the different states a class is in and state transition information for that class. One might argue that every class has state, but not every class should have a state diagram. state diagram descriptions are made only for classes of "interesting" states (that is, classes with three or more potential states during system activity).

(5) Activity Diagrams

An activity diagram in a UML view represents the flow of process control between two or more class objects while processing an activity. Activity diagrams can be used to model higher-level business processes at the level of business units or to model lower-level internal class operations. As a rule of thumb, activity diagrams are best used to model higher-level processes, such as how a company is currently operating its business, or how its business is operating. Because activity diagrams are "less technical" in presentation than sequence diagrams, business-minded people tend to understand them more quickly.

The symbol set of the activity diagram is similar to the symbol set used in the state diagram. Like the state diagram, the activity diagram begins with a solid circle connected to the initial activity. The activity is represented by a rounded rectangle containing the name of the activity. Activities can be connected to other activities by transition segments, or to decision points that connect to different activities protected by the conditions of decision points. The activity that ends the process is connected to a termination point (as in the state diagram). As an alternative, activities may be grouped into swim lanes, which are used to represent objects that actually perform activities.

(6) Component Diagrams

Component diagrams provide a physical view of the system. Its purpose is to show the dependencies of software on other software components (such as library functions) in the system. Component diagrams can be displayed at a very high level, showing only coarse-grained components, or at package level 2.

(7) Deployment Diagrams

A deployment diagram in a UML view represents how the software system is deployed into a hardware environment. Its purpose is to show where the different components of the system will physically run and how they will communicate with each other. Because deployment diagrams model physical behavior, production personnel of the system can make good use of them.

(8) Object Diagrams

Object diagrams describe objects and the relationships between them. Like class diagrams, object diagrams also depict the static design view or static process view of the system, but from an instance perspective.

(9) Collaboration Diagrams

Collaboration diagrams in UML views describe interactions between objects, consisting of objects and relationships between objects, and include interaction diagrams that convey messages between objects. Collaboration diagrams emphasize the structural organization of objects that send and receive messages. They are isomorphic to time series diagrams and can be transformed into each other.

The above is "How many kinds of UML views are there?" All the contents of this article, thank you for reading! Hope to share the content to help everyone, more relevant knowledge, welcome to pay attention to the industry information channel!

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.