The interactive feature part of the use Case view is referred to as a use case.
participants
as an external user interacting with the system, this is a feature of the participants.
in the actual operation of the system,
an actual
user may correspond to multiple participants in the system . different users can also correspond to only one participant , thereby representing the same participating
different instances of the user. A participant can be defined by a generalization relationship in which an abstract description of a participant can be shared by one or more specific participants.
Use Cases
Use cases are used to define coherent behavior without revealing the internal structure of the system.
A use case definition contains all the behaviors necessary for a use case-the main line order of the execution case function, the different variants of the standard behavior, all the anomalies under the general behavior, and their expected responses. the dynamic execution of the use case can be explained by the interaction of U M L, which can be expressed by state diagram, sequence diagram, collaborative diagram or informal text description. A use case is a logical description of a part of a system's functionality and is not an obvious component for system implementation. Instead, each use case must be mapped to the class that implements the system. the behavior of a use case corresponds to the state transition of the class and the operation defined by the class. As long as a class acts as a multi-role in the implementation of a system, it implements a subset of the functions of several use cases. Part of the design process is to identify classes with distinct multiple roles without introducing confusion to implement the use-case capabilities involved in these roles. Use case functionality is implemented by collaboration between classes.
uml--use Case view
