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

This article introduces the relevant knowledge of "how to build UML graphics". In the operation of actual cases, many people will encounter such a dilemma. Next, let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

Steps to create a use case diagram in a 1.UML 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.

Steps to create an object class diagram in a 2.UML 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.

3. Exception modeling in the 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 its exception, marked with the stereotype "send", indicating the send dependency from the operation to its exception.

Steps to create a sequence diagram in a 4.UML 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.

Steps to create a collaborative diagram in a 5.UML diagram:

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 them are placed in the neighborhood.

3 > set the initial properties of the object.

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

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.

This is the end of the content of "how to build UML graphics". Thank you for reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

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.