UML use case diagram Summary

 

To learn UML, you must first learn 14 types of UML graphics. To learn graphs, you must first know what elements are on the graphs.

 

[Note] This document is not a basic tutorial Of the use case diagram, but a graphical Summary of the use case diagram.

The use case diagram is used to describe the relationship between users, requirements, and system functional units.

 

Use EA to open the toolbox of the use case diagram, and you can see the toolset used on the use case diagram.

 

The following elements are used as examples:

 

1. Participants

The participant's version (stereotype) has

1) An ordinary participant, represented as an ordinary villain, actor1

2) The business participant (business worker) is represented as a villain + header with a diagonal line, actor2

3) Other participants, represented as a villain + specific version number, actor3, 4, 5...

A participant is a villain. No matter whether there is a diagonal line or a book name, they still represent the participants. They are only a specific version of the participants.

[Note] the so-called version (stereotype) is only a special case. It is called melon seeds whether it is spiced melon seeds or original melon seeds, you can simply think that the version is only used to describe more specific (except for the business participants )!

 

2. Use Cases

The Use Case version (stereotype) has

1) Common Use Case, represented as an elliptic, Use Case 1

2) test case, represented as an elliptic + cross, Test Case 1

3) Business Use Case, which is an elliptic plus a diagonal line, Use Case 2

4) for other use cases, it is the specific version of an elliptic plus book name. Use Case 3

[Note] note the differences between use cases and business use cases. Use Cases are short for system use cases. The scope of business use cases is generally> system use cases.

 

3. Collaboration

Uml2.x has canceled the collaboration diagram and is defined as the communication diagram, but the collaboration is still retained, which is not explained here.

1) common collaboration, represented as an elliptic of a dotted border, collaboration 1

2) Business Collaboration, representing an elliptical + diagonal line of a dotted border, collaboration 2

 

4. Boundaries (subsystems)

 

5. Package

The painting method is consistent with the package diagram. For more information, see the package diagram section.

 

6. artifact (Product/Project translation is not clear as a uml2.x image)

The painting method is consistent with the artifact diagram. For more information, see the artifact diagram section.

 

The relationships in the use case diagram are:

1. Include

2. Expansion

3. Generalization

4. Dependency

5 ....