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

The drawing method of commonly used diagrams in system Design with EA

1.1 static View

1.1.1 package diagram

Create a package diagram:

Package diagram is the most commonly used diagram, because our projects are usually composed of layers of packages, such as the following package diagram:

The hidden method of the properties in the package can be seen in Show Hidden. Double-clicking the package will open its internal first view by default, which is also a display technique that can adjust the order of the views through the Project Browser toolbar.

1.1.2 Class Diagram

Create a class diagram:

Settings of properties and methods:

A) right-click class, select Attributes from the pop-up menu, and set the properties in Operations:

B) double-click class to set it through the Details tab in the pop-up Properties:

The establishment of class relationship:

Click on a class, click the pop-up relationship tool icon, and drag to the class where you want to build the relationship:

Release the left button and select the type of relationship you want to establish in the pop-up relationship menu:

For example, if you select the relationship of Generalization, the method to be overridden will pop up:

After clicking OK, the relationship is established:

Sometimes, when the relationship is aggregated, you need to represent the relationship between them, such as an one-to-many relationship, you need to double-click the connection and set it through Source Role and: Target Role:

Create the relationship as follows:

1.1.3 robust graph

Creation method:

Robust graph is often used in requirement analysis and scenario analysis. Robust graph is divided into three elements: boundary object, control object and entity object. The use of the three elements of the robust graph can well summarize the three types of responsibilities in the system: interaction, control and information.

The relationship between three elements of robust Graph and MVC

Robust graph modeling rules:

1.1.4 component diagram

Create a component diagram:

Component diagrams are often used for design work such as subsystem partition or module partition, and only the representation of interface dependency is introduced here.

Through the component diagram toolbox, you can establish interfaces for components, and component interface dependencies are represented as follows:

1.2 dynamic View 1.2.1 use case Diagram

Creation method:

The pictures you often draw only show that there are many relationships between use cases:

Several commonly used relationships: from left to right is implementation, dependence, extension

In addition to use case diagrams, for requirements, we can also use the requirements diagram extended by UML:

Creation method:

Requirements are divided into requirements and feature elements. A requirement can be associated with multiple features:

In addition, there can be many types of requirements, and different types of requirements are represented by different colors:

To display different types of requirements for different colors, you need to make sure that the following settings are set in Options:

1.2.2 activity diagram

Create an activity diagram:

Activity diagrams are mostly used to describe the activities that the process needs to expand, and are often used to describe the use of the scene process.

If you want to reflect the division of labor from the activity to the executor, you can introduce swimming lanes:

To change the direction of the swimming lane, you can click the swimming lane and click the tool icon in the upper right corner to achieve:

1.2.3 sequence diagram

It is probably the longest used diagram to express the process, such as a sequence diagram of the discovery equipment:

Just introduce a few of the techniques involved here

A) whether the main message type is asynchronous or synchronous, asynchronous is, and the synchronous arrow is:

The setting method is double-click Link. In the pop-up properties dialog box, the settings are as follows:

B) if the object is not of the entire timeline, but is temporarily created, it is set to new during the life cycle:

C) if the synchronous method requires a return message, the main return message is dotted and asynchronous, and the setting method of the return message:

1.2.4 collaboration Diagram

Compared with timing diagrams, collaboration diagrams better reflect the relationships and subprocesses between objects.

How to draw a collaboration diagram:

A) first draw the object relationship through Direct Link:

B) right-click the first Link in the process and add a message to it:

If you are creating a message for a new process, you need to box "Start New Group", otherwise do not check it.

As shown in the figure below, we need to select "Start New Group" on the connection numbered 2

Sometimes you need to adjust the order of messages, there are two ways:

A) right-click any message and select from the pop-up menu, as shown in the following figure

B) or select Sequence Messages from the Diagram menu:

The following interface pops up to set the order of messages:

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.