Business Systems Analyst

Term
1 / 33
What are the basic elements of a Use Case Diagram?
Click the card to flip 👆
Terms in this set (33)
What are the basic elements of a Use Case Diagram?
Actors, Use Cases, and Relationships
A Use Case is depicted graphically by the following symbol:
Oval
In the following diagram which actor(s) could invoke use case E?
A
In the following, diagram, which two use cases are related with the generalization relationship?
D and C
In the following diagram which use can be initiated by actor b?
D
In a use case diagram for a system, an Actor can be placed inside the system boundary.
false
In the following diagram, which use case cannot stand alone, but is incorporated in the behavior of another use case?
H
Which of the following statements are applicable to an Actor in a Use Case Diagram?
a) An Actor can be placed inside the system boundary to show it belongs to the system
b) An Actor is represented in the use diagram with a "stickman" icon.
c) An Actor specifies a role played by a user or an external system that interacts with the system being depicted.
d) Each Actor in a Use Case Diagram can interact with only one Use Case.
b) An Actor is represented in the use case diagram with a "stickman" icon
c) An actor specifies a role played by a user or an external system that interacts with the system being depicted.
When creating a use case diagram, each actor symbol must have a direct relationship to at least one use case.
false
In the following diagram, which use case behavior is optionally incorporated in the behavior of another use case at a specific point?
G
A relationship that specifies how and when the behavior defined in one use case can be inserted into the behavior defined in another use case. This relationship is intended to be used when there is some additional behavior that should be added, possibly conditionally, to the behavior defined in a use case.Extend relationshipA relationship between two use cases indicating that the behavior of the first use case is inserted into the behavior of the second use case. The first use case must be available for the behavior of the second use case to be completely described.Include RelationshipDefines a specialization relationship between use cases. This relationship relates a specific use case to a more general use case.Generalization RelationshipA relationship which doesn't exist in a Use Case diagram.Improve RelationshipWhich definition below best describes a use case? a) A use case represents the behavior of the actor which results from the adequate performance of the system. b) A use case is a method used by a business analyst to make his case for how the actor should behave. c) A use case represents a set of steps performed by an actor as he tries to act out an application behavior. d) A use case represents a set of behaviors performed by a subject (such a system) and which yields an observable result one or more Actors.d) A use case represents a set of behaviors performed by a subject (such a system) and which yields an observable result one or more ActorsThe <<extend>> relationship shows: a) One use case includes the behavior of an external actor in its behavior b) One use case inherits the behavior of another use case c) Behavior of one use case that does not stand alone, but is incorporated as apart of some larger use d) That a use cases optionally provides additional functionality to another use case at certain pointsd) That a use cases optionally provides additional functionality to another use case at certain points.In the following diagram, which actor(s) could trigger the behavior of use cases F and G?B,CIn the following diagram which use case can be initiated by actor G?noneIn the following diagram, which actor(s) could invoke use case F?B,CWhich template below would be best suited to name actors:[noun]Use Cases are means of capturing the requirements of a system and they specify what a system is supposed to be able to do.trueIn the following diagram which use case is similar in behavior to use case D?cWhen creating a use case diagram, each use case must have a direct relationship to at least one actor.FalseMatch the Use Case Diagram symbols with their names:Actor, Use Case, generalization, association, system boundaryIn the following diagram, which actor(s) cannot invoke the behavior of any use case?J,K,LIn the following diagram, which actor(s) could invoke the behavior of at least one use case?A,B,CWhich UML diagram below cannot below cannot be used to illustrate the detailed behavior of a use case? a) Activity Diagram b) Class Diagram c) Sequence Diagramb) Class DiagramWhich template below would be best suited to name use cases: a) verb b) noun c) verb & noun d) adverb e) verb & adverb f) noun & verbverb & nounAn Extend is a relationship between two use cases showing that one use case can take longer to execute then the other use case.FalseSelect the best name for a use case from the following options: a) enrollStudent() b)Enrollment c) Enroll Student d) Student Enrollment e) Studentc) Enroll StudentSelect the best name for for an actor from the following options: a) Enroll Student b) student() c) Enroll Immediately d) Immediately e) Student f) Enrolle) StudentThe <<include>> relationship shows: a) Behavior of one use case that does not stand alone, but is incorporated as part of some larger use case b) One use case includes the behavior of an external actor in its behavior c) That a use cases optionally provides additional functionality to another use case at certain point(s) d) One use case inherits the behavior of another use casea) Behavior of one use case that does not stand alone, but is incorporated as part of some larger use caseThe generalization relationship shows: a) One use case includes the behavior of an external actor in its behavior b) Behavior of one use case that does not stand alone, but is incorporated as part of some larger use c) That a use cases optionally provides additionally functionality to another use case at certain points(s) d) One use case inherits the behavior of another use case.d) one use case inherits the behavior of another use case