Case modeling is a part of UML modeling and the most basic part of UML. The main function of case modeling is to express the functional requirements or behaviors of the system.
The participants of use cases are not specific to users, but also those outside the system that play a role in using the system or interacting with the system.
Help
1> the roles played by common employees in the one-Use Case study can be completely different.
2> other minor systems can also be used as use cases.
The participants are illustrated with simple characters, and the names of the participants are attached to the figures.
Use Cases are what the participants want the system to do. For case naming, we can give the case a simple and descriptive name, generally a word with attention. The use case is represented by an ellipse in the drawing. The name of the use case is attached to the ellipse.
The system boundary is used to represent the boundary of the modeling system. Within the boundary, it indicates the components of the system, and outside the boundary, it indicates the system exterior. The system boundary is displayed in a box in the drawing, and the system name is attached. The participant is drawn outside the boundary, and the use case is drawn inside the boundary.
Arrows are used to indicate the associations between participants and the system by sending signals or messages to each other. The tail of the arrow is used to indicate the Start side of the interaction, and the head of the arrow is used to indicate the Start side. The use case is always started by the participants.
The following is an example:
<! -- The above content mainly comes from the Internet and is sorted out --->
