UML use case diagram design

Example

1. Defining system boundaries determines the boundaries between the system's interior and exterior.

2. The main character represents the role played by the external object. An object can assume several roles, so it can be represented by several leading roles.

3. Communication relationships are used to clarify the participation of the main character in the use case.

4. A use case is a group of events that occur when the main character completes a process through the system. Generally, a use case is a large process, rather than a single step or transaction.

Class static structure diagram example

1. To add features, operations, and other properties to a class shape, double-click the shape to openUML attributesDialog box.

2. Double-click an association to add a modifier, such as multiple and oriented.

3. In addition to the name and type shown here, the feature can also contain visibility, which is an initial value. The feature can also specify whether the object belongs to a class or instance.

4. To convey detailed programming specifications, you must define the parameters used for operations in the figure.

Activity diagram example

1. The initial state of the object is the state when no event in the figure takes effect on the object.

2. The action status indicates the status of the completed activity.

3. When an internal action in the action status is completed, the action status changes.

4. To indicate that each concurrent activity must be completed before the next activity occurs, use connection conversion.

5. Double-click the status transition from the action state to add a critical condition and action expression label to it.

6. To indicate activities that can occur at the same time, use a cross-border status switch.

7. The final State indicates that the activity in the scenario as shown in the figure has ended.

Status chart example

1. The initial state of the object is the state when no event in the figure takes effect on the object.

2. Status indicates a moment in the object lifecycle. Double-clickStatusYou can add a name for the shape and list its internal actions and activities.

3. Conversion indicates that, as a response to an event, the object will be converted from one State to another and execute an action.

4. The event that triggers status conversion is named in the status conversion string. Double-click a state conversion task. In addition to the event signature, you can also use a string to add tags such as critical conditions and action expressions to it.

Sequence diagram example

The vertical dimensions in the sequence diagram represent the time, which is sorted sequentially by time. The horizontal dimension represents different protagonists or objects.

1. Objects are represented as the object lifeline, that is, their existence status at a specific time. Adjust the line length to indicate whether the object has been created or died.

2. Arrows indicate messages between objects. Objects can also send messages to themselves.

3. Add an activation point (also called the control focus) to the lifeline to indicate the time period during which the object executes the action.

4. The returned message is represented by a dotted line.

Collaboration diagram example

1. In the role shape of a classifier, the specified character string of an object is underlined to indicate that the object is an instance. You can also add an object name before the colon.

2. The Link (that is, the associated role) indicates the link. If there is an arrow, it also indicates the direction.

3. Double-click a link and then clickMessageYou can define messages transmitted along links. Number of the Process message according to the nested call.

4. The first message is always transmitted out of the graph environment.

Component diagram example

1. In the component diagram, the component is of a common type rather than an instance. To display component instances, use the deployment diagram.

2. Dependency indicates that customer components depend on supplier components to some extent.

Deployment diagram example

1. In the deployment diagram, a node can represent a common type or a specific instance.

2. Adding components and object instances to a node instance indicates that these components and objects reside on the node.

3. You can connect components through dependencies (sometimes using interfaces. You can use constructor to indicate the exact dependency.

This article from: http://www.cnblogs.com/dujun0618/articles/1086243.html