Indicate whether the statement is true or false.
A use case diagram is a convenient way to summarize system activities.
In all use cases, the actor is always inside the automation boundary of the system.
An actor in a use case analysis is the person who is actually interacting with the computer system.
Use cases always focus on the business processes.
An event table emphasizes the automated part of the system.
Because use cases are usually initiated by external actors, temporal and state events are often overlooked if
the analyst does not carefully identify all events.
An activity diagram can be used to support any level of use case descriptions.
Temporal events cannot be initiated manually.
Activity diagrams are not helpful in developing system sequence diagrams (SSDs).
In the object-oriented approach to systems development, the flow of information is achieved by sending mes-
sages either to and from actors or back and forth between internal objects.
In an interaction diagram, messages are sent and received by individual objects, not by classes.
In a system sequence diagram (SSD), the only object included is one representing the entire system.
In a sequence diagram, a message is considered to be an action that is invoked on the destination object.
Use cases can be described in detail with narrative descriptions or activity diagrams.
Activity diagrams cannot be used to describe processes that involve automated system activities.
State machine diagrams can be considered either as an analysis tool or a design tool.
Actors can be systems or other devices that receive services from the system.
In a use case diagram, more than one use case may use the services of a common subroutine.
Each use case may have only one scenario.
A note can be added to any UML diagram to add explanations.
All problem domain classes require a state machine diagram.
Each unique state in a state machine diagram has a unique name.
A communication diagram is an interaction diagram.
A verical dashed line on an activity diagram represents the object lifeline.
The exception conditions from a use case description can also be documented using an activity diagram.
The heavy bar in an activity diagram is always used to represent concurrent paths.
The true/false condition on a message is evaluated after the message is sent to test if the destination object
should accept the message.
Transitions on a state machine diagram are represented by arrows.
This is the end of the preview. Sign up
access the rest of the document.