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

This article mainly introduces how to establish nine kinds of UML graphics, with a certain reference value, interested friends can refer to, I hope you can learn a lot after reading this article, the following let the editor take you to understand it.

The steps of establishing various graphs in UML language

1.UML induces the steps to build a use case diagram:

1 > find out the activists and external systems outside the system, and determine the boundary and scope of the system.

2 > determine the system behavior that each activist wants.

3 > name these system behaviors as use cases.

4 > decompose some common system behaviors into a number of new use cases for reference by other use cases. Break down the behavior of some changes into extension use cases.

5 > draw up a script for each use case.

6 > draw use case diagrams.

7 > distinguish between the main business flow and the event flow of exceptions. The use case diagram of the event flow that represents the exception can be drawn as a separate subuse case diagram.

8 > refine the use case diagram, solve the problem of repetition and inrush in the use case, simplify the dialogue sequence in the use case, the use case of the high-level system can be decomposed into sub-use cases in several subordinate subsystems.

2.UML induces the steps of establishing an object class diagram:

1 > study and analyze problem areas and determine the requirements of the system.

2 > discover objects and object classes, define their meaning and responsibilities, and determine attributes and operations.

3 > discover static relationships between classes. This paper focuses on analyzing and finding out the general and special relations between object classes, the relationship between parts and the whole, studying the inheritance and polymorphism of classes, and expressing the static relations between classes by association, generalization, aggregation, combination, dependence and so on. although the object class diagram expresses the static structural characteristics of the system, the static analysis and dynamic analysis of the system should be combined to understand the static structural characteristics of the system more accurately.

4 > Design classes and connections. Adjust and refine the relationship between the obtained object classes and classes to solve problems such as naming conflicts, function duplication and so on.

5 > draw the object class diagram and compile the corresponding description. The above approach begins with the extraction of objects and object classes directly from domain analysis, which is the practice of conventional object-oriented system analysis and design. The Rational unified process advocates a use case-driven system analysis and design approach. The actors and use cases are extracted from the analysis of the business domain, and the business model is established. Business model includes business use case model, design model, implementation model and test model.

Exception modeling in the 3.UML induction system:

1 > for each object class and interface, identify possible exceptions and conditions for exceptions.

2 > each exception is described as a signal class, preceded by a constructive "exception".

3 > establish a hierarchical structure of exceptions, put general exceptions at a high level and special exceptions at a lower level.

4 > identify possible exceptions for each operation. There is a dotted arrow connection between the operation and the signal diagram of his exception, marked with the stereotype "send", indicating the send dependency from the operation to his exception.

The steps to establish the 4.UML inductive sequence diagram:

1 > determine the context of the interaction.

2 > find out the object class roles that participate in the interaction, arrange them horizontally at the top of the sequence diagram, the most important objects are placed on the far left, and the objects that interact closely are as close as possible. Objects created in the interaction should be placed vertically at the point in time at which they were created.

3 > set a vertical downward lifeline for each object.

4 > starting from initializing the interactive information, place the information between the lifelines of the object from top to bottom. Note the difference between synchronous and asynchronous messages in the form of arrows. According to whether the sequence diagram belongs to the description layer or the instance layer, the content of the message label, as well as the necessary constructs and constraints are given.

5 > draw the activation period of the object on the lifeline, as well as the stereotypes and tags for the creation or destruction of the object.

6 > more information about the relationship between messages, determine the loop structure, loop parameters and exit conditions.

5.UML induces the steps of establishing a collaborative graph:

1 > determine the context of the interaction.

2 > find out the object class roles involved in the interaction and place them as the nodes of the graph in the collaboration diagram. The most important objects are placed in the center of the diagram, and the objects that interact directly with him are placed in the vicinity.

3 > set the initial properties of the object.

4 > describe the links between objects. First, the associated connections between objects are given, then other connections are given, and the necessary decorations are given, such as the stereotype "global" and "local".

5 > starting from initializing the interactive message, place the corresponding message on the link and give the sequence number of the message. Note the difference between synchronous and asynchronous messages in the form of arrows. According to whether the sequence diagram belongs to the description layer or the instance layer, the content of the message label, as well as the necessary constructs and constraints are given.

6 > handle some special cases, such as loops, self-invocations, callbacks, multiple objects, etc.

The steps to establish the 6.UML inductive state diagram:

1 > determine the context of the state machine, which can be a class, a subsystem, or the entire system.

2 > Select the initial state and the final state.

3 > discover the various states of the object. Note that you should carefully identify the object state attributes that are meaningful to the problem, these attributes have a small number of values, and the conversion of the value of that attribute is limited. The combination of state attribute values, combined with events and actions related to behavior, can determine the state with specific behavior characteristics.

4 > determine the possible assembly shift of the state. Note that it is possible to move from one state to those states, which behaviors of the object can cause the state transition, and find out the events that trigger the state transition.

5 > add the necessary actions to the state or transfer.

6 > it is necessary to organize and simplify a complex state machine with concepts such as hyperstates, sub-states, branches, and historical states.

7 > analyze the concurrency and synchronization of states.

8 > draw a state diagram.

9 > make sure that each state is reachable under a certain combination of times. Confirm that there is no dead-end state from which the object cannot be transferred.

7.UML induces the steps for establishing the activity diagram:

1 > find out the business object responsible for implementing the workflow. These objects can be entities in the real business domain, or they can be an abstract concept or thing. Create a swimming lane for each important business object.

2 > determine the initial state and final state of the workflow, and define the boundary of the workflow.

3 > start from the initial state of the workflow, find out the activities and actions that occur over time, and express them as an active state or action state.

4 > for complex actions or a group of actions that occur repeatedly, they can be grouped into an activity state and represented by another activity diagram.

5 > gives the transfer of connecting activities and actions (action flow). The sequential action flow is processed first, and then the conditional branch is processed. * handle split and joint.

6 > give the important objects related to the workflow in the activity diagram and connect them with the active state or action state with virtual arrows.

8.UML induces the steps to build the package diagram:

1 > analyze system model elements (usually object classes) and incorporate conceptual or semantically similar model elements into a package.

Note that the object classes included in the package can be determined from the functional relevance of the class. The following points can be used as a reference for analyzing the functional correlation of object classes.

(1) if a change in the behavior and / or structure of one class requires another corresponding change, the two classes are functionally related.

(2) if after deleting one class, another class becomes redundant, then the successive classes are functionally related, which means that the remaining classes are only used by the deleted class, and there is a dependency between them.

(3) if there is a large amount of frequent interaction or communication between the two classes, the two classes are functionally related.

(4) if there is a general / special relationship between the two classes, the two classes are functionally related.

(5) if one class fires an object that creates another class, the two classes are functionally related.

(6) if two classes do not involve unifying an external activity, the two classes should not be placed in the same package.

(7) A package should be highly cohesive, and the object classes in the package should be functionally relevant.

2 > for each package, mark the visibility of its model elements: public, protected, or private.

3 > determine the dependencies between packages, especially input dependencies.

4 > determine the generalization relationship between package and package, and determine the polymorphism and overloading of package elements.

5 > draw the package diagram.

6 > refine the package map.

9.UML summarizes the steps to build the component diagram:

1 > identify the component. First of all, it is necessary to decompose the system, consider the composition management of the system, the reuse of the software, the configuration of nuclear physics nodes and other factors, classify the closely related executable programs and object libraries into components, and find out the corresponding model elements such as object classes and interfaces.

2 > add the necessary stereotypes to the components. You can use uml's standard stereotype "executable", "library", "table", "file", "document", or customize a new stereotype to describe the nature of the component.

3 > determine the relationships between components. The most common connection between components is through interface dependencies. One component uses an interface, and another component implements that interface.

4 > organize components into packages if necessary. Components can be organized into packages as well as model elements such as object classes and collaboration.

5 > draw the component diagram.

10.UML inductive configuration diagram establishment steps:

1 > determine the node. Note: Mark the hardware devices in the system, including mainframe, server, front-end, network equipment, input / output devices, etc. A processor is a node, which has processing function and can execute a component; a device is also a node, it has no processing function, but it is the interface between the system and the real world.

2 > add the necessary stereotype to the node. You can use uml's standard stereotype or customize a new stereotype to illustrate the nature of the node.

3 > confirm the contact. This is a key step. The relationship in the configuration diagram includes the connection between nodes, the relationship between power saving and components, and the relationship between components. You can use standard stereotype or custom new stereotype to describe the nature of the connection.

Assign the components of the system, such as executable programs, dynamic link libraries, etc., to nodes, and determine the relationships between nodes, nodes and components, components and components, as well as their properties.

4 > draw the configuration diagram.

Thank you for reading this article carefully. I hope the article "how to build nine UML graphics" shared by the editor will be helpful to everyone. At the same time, I also hope you will support us and pay attention to the industry information channel. More related knowledge is waiting for you to learn!

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.