Object-Oriented Design: Class Assistant and Actor Relationships

Actors are considered part of the system boundaries.

Actors are part of the system boundaries.

Identifying actors involves determining who uses the main use cases.

Conditions define under which circumstances the behavior is integrated.

Actors interact with the system by initiating the execution of use cases.

Use case diagrams model processes and workflows.

An actor can only adopt one role at a time.

User data is not administered within the system.

Identifying use cases involves understanding the main tasks actors must perform.

Actors provide functionality for the execution of use cases.

Actors requiring support for their daily work are considered during use case identification.

Actor Assistant interacts with the system Laboratory Assignment by issuing certificates.

The class Assistant represents objects related to user data like name and social security number.

An Actor can be either Human or Non-human, such as an Email Server.

An Actor that initiates the execution of a use case is considered Passive.

Every actor must communicate with at least two use cases.

The «include» relationship between use cases means the behavior of the included use case is integrated into the base use case.

In the «extend» relationship between use cases, both use cases must always be executed independently of each other.