(Original) UML Overview

I. Types of UML diagrams

1. Use case diagram
2. Sequence Chart
3. Class Diagram and object Diagram
4. Status chart
5. Activity diagram
6. Component Diagram
7. Deployment Diagram

Use case diagram, sequence diagram, and class diagram are commonly used diagrams. We will introduce them in detail later. First, we will explain the status diagram and activity diagram.

Ii. status chart

1. State chart purpose: describes the state of an object during its life cycle and events that cause state changes.

2. When to draw: The status chart is created only when the behavior change is related to the status. If an object, such as a class or component, indicates that the sequence of behavior is irrelevant to the current state, it may be useless to draw a UML state chart.

3. symbol details:

• Initial start point, drawn using solid circles
• Connection line, drawn using a line segment with an open arrow
• Status, draw with rounded rectangle
• Judgment point, drawn using hollow circles
• End Point, drawn using a circle containing a solid circle

3. activity diagram

 

1. Activity diagram purpose: describes the sequence of activities, similar to a flowchart.

2. When to draw: Describe the workflow and operation process.

3. symbol details:

• Initial start point, drawn using solid circles
• Connection line, drawn using a line segment with an open arrow
• Activity, draw with rounded rectangle
• Judgment point, drawn using hollow Diamond
• End Point, drawn using a circle containing a solid circle

4. Basic Concepts

• Activity
• Swimming path: indicates the object of the actual activity.
• Branch: select one from multiple possible activities. There are two representation methods.
• Forking and Confluence: it indicates the concurrent behavior in the object. For example, a single control flow is replaced by multiple control flows. Confluence means the opposite.

 

Figure 1. Example of branch, branch, and convergence

• Object stream: the relationship between activities and objects.

 

Figure 2. In the figure, order is an object with different statuses (entered, filled)

Iv. Component Diagram

Composition of files in the system

5. Deployment Diagram

Composition of system hardware