System Architect-Basic to Enterprise Application architecture-System modeling [medium] (bottom)

First, Oberzhang review

First of all, we will review the contents of the previous article, deepen the impression. In the previous chapter we mainly explained the 3 modeling graphs are: Sequence diagram (sequence diagram), component diagram, State diagram.

Specific function description such as: Here is not explained in detail, if not clear see: System Architect-Basic to Enterprise Application architecture-System modeling [medium] (top)

Since all of them are too long in one piece, they are explained separately.

Ii. Summary

This article mainly explains: Activity diagram, deployment diagram, etc. in UML modeling diagram

In this chapter is to explain the content, the essence will be carefully analyzed, deployment diagram and component diagram of the relationship and difference between the activity diagram and the state diagram of the relationship and difference.

Iii. contents of this chapter

1, Oberzhang review.

2, summary.

3. Contents of this chapter.

4, the modeling of the abstract model diagram of the deployment diagram, Activity diagram.

5. Summary of this chapter.

6, Series progress.

7, the next preview.

Iv. deployment diagram of abstract model diagram, Activity diagram deployment diagram

First, let's explain the deployment diagram. A deployment diagram is primarily used to describe the structure in which a series of components are deployed to a node. The deployment diagram shows the structure of the system runtime. The general deployment diagram helps us to understand the distribution

Application System. The deployment diagram also conveys the configuration and deployment of software and hardware elements for building application systems.

Basic elements in the deployment diagram:

1, node: This refers to the environment in which the component is running. It can be software (operating system, other, etc.) or hardware resources (computers, other hardware).

The general graphical representation in the UML modeling language is:

2, Node instances: node instances and nodes are distinguished by an underscore and a colon, the node instance must immediately follow the colon, of course, the node instance name can be empty, the node must have.

3. Component container: A node can contain other nodes, either a component or a node.

4, the relationship between nodes

(1), one-way dependence:

Represents a query statistics component that accesses the SQLSERVER2005 database through. NET-provided ADO.

(2), two-way dependence:

Indicates that the Product Management module writes data to the database, while the information in the product management is read from the database and is bidirectional dependent.

(3), communication:

Means: Application software system and database pass. NET provides a way to communicate with each other, personal understanding of the task is two-way communication (two-way dependency) [error, but also the expert pointed out].

5, the example explains:

Below we have a simple system-to-consumer to explain:

Let's take a look at the corresponding nodes in the consumer-consumer system:

Client access to the consumer-to-consumer site through the browser, first into the member management, if registered, then into the registration system. Manage, pay and publish the purchase in the member management.

Node Description:

Browser: Access the consumer-to-consumer site by typing the web address. This is the only entry that interacts with the consumer-to-consumer system.

Registration system: Complete the user's registration and database communication. The diagram does not show that all the nodes need to communicate with the database except that the browser does not need to interact directly with the database.

Member Management: Complete the management of the Member center. Member's personal information, shop store information, receiving address and so on information management, my purchase, I released products and so on.

Procurement system: Sub-function in the system to complete the buyer's product procurement.

Publishing system: Mainly for sellers to provide services, release product information and so on. Communicating with the database

Payment system: The operation to complete the payment transaction. Communicate with a personal account.

Of course, here is just a simple example, other content, such as the front desk display, and so on, these are currently not considered, nor careful analysis, here is only to achieve the purpose of the introduction.

6. Summary

I believe you have a basic understanding of the deployment diagram through the above explanation, the deployment diagram is mainly used to complete the deployment of components to run on the node structure. The structure of the system runtime is described as a whole. The deployment diagram is

The modeling diagram that must be mastered.

Activity Chart

Activity diagrams are primarily used to describe the dynamic behavior of a system, from one activity to another, to a control flow. The nature of the activity diagram is a flowchart, but it differs from the flowchart. The activities will be explained in detail in this section.

The difference between the nature of diagram and flowchart and the difference between activity diagram and state diagram.

As a rule, let's look at the elements of the activity diagram first:

1. Action State:

An action state is represented by a rectangle of rounded edges. There are several features of the Action State: atomicity (either executed or not), non-disruptive operation, and must be turned to another when the action is completed

State. The action state is the smallest unit of the tectonic activity diagram.

State diagram Differences:

A, the activity diagram in the action state can have into conversion and out of the conversion, meaning can be shifted from the current state to another state, you can also transition from another state to the current state. The graphical representation is as follows:

B Action State, can have into convert a, out convert C.

The action state must have at least one out conversion, which is the starting point for internal completion, regardless of the external event.

Solid Circle: Represents the starting state.

Solid Circle inside Ring: Represents the end state.

B, the action state and the state diagram is different, the action state can not have entrance action and exit action. There is no internal transfer.

2. Activity Status:

The active state is identified by combining two halves with a rectangle.

The active state can first be decomposed into multiple child activities or multiple child action states. Active state he is not as atomic as the State of action. The active state is non-atomic. Activities within the activity diagram, you can use another

An activity diagram to indicate. The active state can be considered as a combination of multiple action states and multiple child activities.

Activity State is different from Action state, action state is a special case of active state, when an activity state has only one action state, this activity state is an action state. Active state can have entry action

and exit actions. There can also be internal transfers. Because the activity diagram is a combination of multiple sub-activities and multiple action states, the direct steering of the action state can be regarded as internal transfer, so it is well understood.

Has basically represented the movement of the dynamic State in the active state and so on. I'm sure everyone can understand.

3, the relationship between the action nodes

A, control flow: The same as the turn in the state diagram, the activity diagram also uses a line with an arrowhead, the arrow points to the state to be transferred.

B, Branch: Active state from a branch out of Active State B, C,

C, Merge: Activity State B is obtained after merging activity State A with C.

D, Swimlane: A swimlane divides multiple activities in an activity diagram into groups. And each group of activities is organized by the object to organize the business, Lane distinguishes the object responsible for activities. and lane-specific tables

Shows which activities are carried out by which objects. Lanes are distinguished by vertical lines. The area of 2 vertical lines is a swimlane. The above explanation may be a bit of a detour, the white Lane is the object above, the object is

Lane. The different lanes are called an object. Each activity state can belong to only one swimlane in an activity diagram with a swimlane.

Here is a legend of the Swimlane:

There are 2 lanes, I am Lane 1, I am Lane, and I am Lane 1 D with me

Is the active state A in the Swimlane has a steering relationship.

E, object flow.

An object flow is a dependency between an object and an action state or an active state. Represents the effect of an action using an object or an action on an object. In general, we can link objects through dependencies and action states or activity states.

Several features of object flow:

(1), generally an object can be manipulated by more than one active state or action state.

(2), an output object of an active state or an action state can be entered as another active state or an action state.

(3), an object can appear more than once in an activity diagram, but it is a little more important to note that this object appears multiple times when the table name is at different times in the life cycle.

Activity diagram containing the object flow:

An object appears in the Swimlane M1. And the object has a dependency on activity State B.

Summarize

This section explains the basic knowledge of the activity diagram, below we are usually familiar with business-to-consumer businesses, e-Mall For example, the member of the product management process. Expressed in the form of a state diagram. To consolidate

The results of our studies.

For example, product management in consumer products. You must first be a member to log into the system, and then I must be the seller before the product can be released.

Members must first open the store, set permissions for product management

V. SUMMARY of this Chapter

This chapter mainly describes the deployment diagram and activity diagram. Now let's review the main points of this chapter.

Deployment diagram: A structure that is used primarily to describe a series of components that are deployed on a node and is a description of the structure in which the system runs. Mainly used in software systems

Activity diagram: Used primarily to describe the dynamic behavior of a system, from one activity to another activity state. The business process is described in the form of a workflow through a series of actions. A series of operations is a series

The active state.

Vi. series of progress. Previous article

1. System Architect-Basic to Enterprise Application Architecture series--Benefits

2. System Architect-Basic to Enterprise Application architecture-System modeling [prev]

3. System Architect-Basic to Enterprise Application architecture-System modeling [medium] (top)

4. System Architect-Basic to Enterprise Application architecture-System modeling [medium] (bottom)

5. System Architect-Basic to Enterprise Application architecture-System modeling [next]

6, System Architect-Basic to Enterprise Application architecture-system design norms and principles [prev]

7. System Architect-Basic to Enterprise Application architecture-system design code and principles [next]

8. System Architect-Basic to enterprise Application architecture-design pattern [prev]

9. System Architect-Basic to enterprise Application architecture-design pattern [medium]

10. System Architect-Basic to enterprise Application architecture-design pattern [next]

Medium

11. System Architect-Basic to enterprise Application architecture-Enterprise Application Architecture

12. System Architect-Basic to enterprise application architecture-layering [prev]

13. System Architect-Basic to Enterprise Application architecture-tiering [medium]

14. System Architect-Basic to Enterprise Application architecture-tiering [next]

15. System Architect-Basic to Enterprise Application architecture-Presentation 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 Services

20. System Architect-Basic to enterprise application architecture-security mechanism

Later chapter

21, single-machine application, client/server, multi-service, enterprise data bus full analysis

22. System Architect-Basic to Enterprise Application architecture-Standalone Application (example and demo)

23. System Architect-Basic to Enterprise Application architecture-client/server (example and demo)

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

25. System Architect-Basic to enterprise Application architecture-enterprise data Bus (example and demo)

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

27. System Architect-Basic to enterprise Application architecture-complete Architectural scenario example [previous]

28. System Architect-Basic to enterprise Application architecture-complete architectural scenario example [medium]

29. System Architect-Basic to enterprise Application architecture-complete Architectural Scenario example [next]

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

Seven, the next announcement.

In the next article we will talk about: simply tell the other UML modeling diagrams, and in combination with consumer-to-consumer instances, detailed analysis of the consumer-consumer system should have functional modules. And each module is represented by a different modeling graphic

And how to use the appropriate modeling diagram for functional analysis.

Post-language

Hope that the Friends of this chapter can learn from this article the corresponding UML modeling knowledge, understand the people can consolidate the UML knowledge, this article hope to be able to offer valuable advice. Because it is my

At ordinary times the understanding and summary of work, the shortcomings of the inevitable, but also please criticize the point! If you have any comments or suggestions, please make a lot! Everyone's support is my greatest motivation!

System Architect-Basic to Enterprise Application architecture-System modeling [medium] (bottom)