Podcast
Questions and Answers
Actors are considered part of the system boundaries.
Actors are considered part of the system boundaries.
False (B)
Actors are part of the system boundaries.
Actors are part of the system boundaries.
False (B)
Identifying actors involves determining who uses the main use cases.
Identifying actors involves determining who uses the main use cases.
True (A)
Conditions define under which circumstances the behavior is integrated.
Conditions define under which circumstances the behavior is integrated.
Actors interact with the system by initiating the execution of use cases.
Actors interact with the system by initiating the execution of use cases.
Use case diagrams model processes and workflows.
Use case diagrams model processes and workflows.
An actor can only adopt one role at a time.
An actor can only adopt one role at a time.
User data is not administered within the system.
User data is not administered within the system.
Identifying use cases involves understanding the main tasks actors must perform.
Identifying use cases involves understanding the main tasks actors must perform.
Actors provide functionality for the execution of use cases.
Actors provide functionality for the execution of use cases.
Actors requiring support for their daily work are considered during use case identification.
Actors requiring support for their daily work are considered during use case identification.
Actor Assistant interacts with the system Laboratory Assignment by issuing certificates.
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.
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 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.
An Actor that initiates the execution of a use case is considered Passive.
Every actor must communicate with at least two use cases.
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.
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.
In the «extend» relationship between use cases, both use cases must always be executed independently of each other.
