System Architect-Basic to enterprise application architecture-system modeling [Part II]

ArticleDirectory

• I. Review in the previous chapter
• Ii. Summary
• Iii. Contents of this Chapter
• Iv. Structure Diagram
• 5. behavior diagram
• 6. Summary in this chapter.
• VII. Progress of the series.
• 8. next announcement.
• Background

I. Review in the previous chapter

Previous Article: System Architect-Basic-to-enterprise application architecture-system modeling [Part 2] (Part 2) describes the deployment diagram and activity diagram. Here we also refer to the previous article, I will not go into details here. Previous Article

The following two modeling diagrams are explained:

Ii. Summary

This article will explain several other types of modeling diagrams, of course, just a simple explanation, and will be combined with B2C electronic mall system for analysis by using the modeling diagram we have explained as an example. Sub-functions of the Analysis System

Module, the internal operation steps of each function module, and so on.

The above two modeling charts of different types are described in this chapter.

Iii. Contents of this Chapter

1. Review in the previous chapter.

2. Summary.

3. Content in this chapter.

4. structure diagram.

5. behavior diagram.

6. Summary in this chapter.

7. Series progress.

8. next announcement.

Iv. Structure Diagram 1. Object Diagram

First, let's talk about the object graph. An object graph is used to describe the state of each object in the system at a certain time point. Objects are static structure charts like class charts. They are expressed in actual or prototype scenarios.

. The object graph shows the relationship between objects and objects at a certain time point. An object graph can be seen as a special use case of a class graph. The relationships in the class graph are also applicable to the object graph. It can be understood that an object graph is an instance of a class graph. Pair

An image has a lifecycle. Therefore, an object graph only exists within a certain period of time.

The elements in the object graph can be found in the class graph. You only need to replace the class Element in the class graph with an object. The relationship between class elements in a class diagram also applies to the object diagram. We will not repeat it here. If the class graph is not

I am particularly familiar with it. Please refer to the introduction in this article: System Architect-Basic to enterprise application architecture-system modeling [Part I].

The following is an example of an object diagram:

The object here refers to an instance of a class.

This format indicates the instance format of a class. The colon ":" is followed by the class name, that is, the "parent class" here ". You must add the following items.

Line.

The object is first determined, so in general, the object attribute columns the value directly. The format is as follows:

All object names in the object graph can be empty. However, we do not recommend that you do this to better identify objects in the object graph, if the object name is not specified, the class format of the object must be specified as follows:

An object instance without an object name.

The following uses the status of a new order in the B2C order system as an example to describe the status of each object.

The link here represents the composite link.

Status of the order information in: Order (New Order)-logistics information (not delivered)-payment information (not paid)-product status (product information ).

2. Package Diagram

A package diagram consists of the relationship between the package and the package.

A package chart is also a static structure that contains the following elements:

I think all of the above elements have some knowledge. I will give different examples here. The following example shows how to use the package diagram.

Package access restriction: it is the same as the three access permission setting keywords we know at ordinary times.

Relationship between packages:

A. Introduction and access dependency: first, this relationship is different from the class inheritance relationship we usually call. The access domains including packages cannot be inherited.

It is used to introduce the elements output by another package in one package. Therefore, a depends on B, and Package A introduces the B method in Package B. B. The access permission here is public. The method in a is protected.

B. General relationship:

Generalized relationships describe an inheritance relationship. That is, the relationship between the base class and the special class

System, the description on the way means that as long as the position of Package A appears, it can be replaced with Package B.

3. Combined Structure Diagram

Composite Structure Diagram: the internal structure of the type is given in a structured manner. A composite structure is a static structure that shows the relationships between members and members of a type. The composite structure can be understood as follows,

It is a modeling graph that describes the internal structure of a class and the call relationship between members. The composite structure chart is used to capture internal details of a class and describes how objects work collaboratively in a class.

In a composite diagram, the result is the internal description of the class. The basic elements include: Class, object, and others. For specific relationships, see the relationships in the class diagram.

Graph combination instance:

Shows the combination of products and product brands and product categories. The product brand and product category are associated (the association can be

The value is 1: N) and is linked in a straight line. If you have any questions, see the introduction of the class diagram: System Architect-Basic to enterprise application architecture-system modeling [Part 1].

5. behavior diagram 1. Communication Diagram

In UML modeling, in addition to the sequence diagram (sequence diagram), it can represent the interaction between objects, and the communication diagram can also complete a general description. Generally, two types of graphs can be converted to one another.

First, let's analyze the differences between the two types of graphs.

Let's take a look at the elements in the communication diagram first:

Is an object. The relationships between objects are completed through links. Then, a line segment with an entity triangle points to the object where the message is to be sent.

The following describes the relationships between objects.

There is also a special message that a message sends to itself.

Type of the returned message:

The following is a simple example:

Briefly describes the process of sending emails. We can see that the communication diagram pays more attention to

Link. Through the communication diagram, we can know the direct link between objects in a process in a system and the complete information transmission process.

First, let's talk about the object graph. An object graph is used to describe the state of each object in the system at a certain time point.

2. Time chart

Time chart: Mainly used to describe the behavior of objects (state changes, executed actions, and so on) within a period of time ). It is mainly used to simulate real-time system models. Similar to the object graph, the difference is that the time graph describes a time period, while

A time point in the object graph description. The object graph cares about the object status, while the time graph cares about the object behavior.

After the timer is set, the object status will jump from A to automatically after the timer time arrives.

To status B. Here, the timer is used to control the State migration.

Asynchronous information is supported in the time graph, and the time graph uses a vertical graph to describe the execution sequence of the system.

The time sequence diagram is equivalent to the time limit added to the sequence diagram (sequence diagram.

From the vertical point of view, that is to say, a calls B before B returns a value to a, and the line of the object can be clearly displayed from the time graph.

Yes. In general, we can use a sequence diagram to complete the corresponding description. The time graph is used only when an object of a time period needs to be defined. Including the call from an object to an object.

Behavior Control.

6. Summary in this chapter.

This chapter briefly describes several types of modeling diagrams added by uml2.0 compared to uml1.0. Although we may use less, some specific fields are used, these images may be clearer.

Express the abstract model.

1. Object diagram: describes the status of the system at a certain time point.

2. Package diagram: Describes the internal structure of a module in the system, which consists of the relationship between elements and elements.

3. composite structure diagram: describes a type of internal structure in the system in a structured manner.

4. Communication diagram: it describes the interaction between objects and the sequence diagram. The interaction diagram focuses more on the links and communication between objects.

5. Time graph: Describes the behavior of objects within a period of time.

Of course, how to use a specific modeling graph and how to apply it for analysis in actual projects is the main purpose. Of course, this requires theory and practice to achieve the desired effect. Next, I will talk about it

For B2C electronic Mall as an example, detailed analysis of the specific application of UML modeling.

VII. Progress of the series. Previous

1. System Architect-from basic to enterprise application architecture series-useful for volume opening

2. System Architect-Basic to enterprise application architecture-system modeling [Part 1]

3. System Architect-Basic to enterprise application architecture-system modeling [Part 1] (Part 1)

4. System Architect-Basic to enterprise application architecture-system modeling [Part 1] (Part 2)

5. System Architect-Basic to enterprise application architecture-system modeling [Part II]

6. System Architect-Basic to enterprise application architecture-system design specifications and principles [Part 1]

7. System Architect-Basic to enterprise application architecture-system design specifications and principles [Part II]

8. System Architect-Basic to enterprise application architecture-design mode [Part 1]

9. System Architect-Basic to enterprise application architecture-design mode [Part 1]

10. System Architect-Basic to enterprise application architecture-design mode [Part II]

Part II

11. System Architect-Basic to enterprise application architecture-enterprise application architecture

12. System Architect-Basic to enterprise application architecture-hierarchy [Part 1]

13. System Architect-Basic to enterprise application architecture-hierarchy [Part 1]

14. System Architect-Basic to enterprise application architecture-hierarchy [Part II]

15. System Architect-Basic to enterprise application architecture-performance Layer

16. System Architect-Basic to enterprise application architecture-service layer

17. System Architect-Basic to enterprise application architecture-business logic layer

18. System Architect-Basic to enterprise application architecture-data access layer

19. System Architect-Basic to enterprise application architecture-Component Service

20. System Architect-Basic to enterprise application architecture-Security Mechanism

Later

21. Full Analysis of stand-alone applications, clients/servers, multiple services, and Enterprise Data Bus

22. System Architect-Basic to enterprise application architecture-standalone application (instance and demo)

23. System Architect-Basic to enterprise application architecture-Client/Server (instance and demo)

24. System Architect-Basic to enterprise application architecture-Multi-Service (instance and demo)

25. System Architect-Basic to enterprise application architecture-Enterprise Data Bus (instance and demo)

26. System Architect-Basic to enterprise application architecture-performance optimization (Architecture bottleneck)

27. System Architect-Basic to enterprise application architecture-complete architecture solution example [Part 1]

28. System Architect-Basic to enterprise application architecture-complete architecture solution example [Part 1]

29. System Architect-Basic to enterprise application architecture-complete architecture solution example [Part 2]

30. System Architect-Basic to enterprise application architecture-Summary and follow-up

8. next announcement.

In the next article, I will deeply analyze the B2C e-mall that I am familiar with, how to use the UML modeling tool to analyze a system and how to analyze the process of a module, including deployment. Through what we have already said

UML modeling graphics are used in combination with examples. If you have good comments and suggestions, you can give feedback in a timely manner. Thank you for your valuable comments.

Background

I hope that my friends who have read this chapter can learn the corresponding UML modeling knowledge from this article, and those who know it can consolidate the UML knowledge. I hope this article will help you to give more valuable suggestions. Because it is me

In normal work, understanding and summarization are inevitable. Please criticize and point out the shortcomings! If you have any comments or suggestions, please submit them more! Everyone's support is my greatest motivation!