IS-A&D Study
IS332 Midterm & Final Prep
Exam in
-- : -- : --
Home
Home
Materials
Lectures & Guides
Satzinger Textbook
Practice
Practice Mode
By Chapter
Case Study Exams
Saved Questions
Analysis
Question Analysis
GitHub Repository
Toggle Sidebar
IS-A&D Study
Chapter 5: Use Case Modeling
38 questions
Practice this lecture
chapter-bank
T/F
Chapter 5: Use Case Modeling
An activity diagram and the flow of activities in a fully developed use case description serve the same purpose.
chapter-bank
T/F
Chapter 5: Use Case Modeling
An Opt frame and an Alt frame do essentially the same thing.
chapter-bank
T/F
Chapter 5: Use Case Modeling
In an interaction diagram, messages are sent and received by individual objects, not by classes.
chapter-bank
T/F
Chapter 5: Use Case Modeling
In the object-oriented approach to systems development, the flow of information is achieved by sending messages either to and from actors or back and forth between internal objects.
chapter-bank
T/F
Chapter 5: Use Case Modeling
In a sequence diagram, a message is considered to be an action that is invoked on the destination object.
chapter-bank
T/F
Chapter 5: Use Case Modeling
In a system sequence diagram a box refers to a class of objects.
chapter-bank
T/F
Chapter 5: Use Case Modeling
An actor is always outside of the automation boundary.
chapter-bank
T/F
Chapter 5: Use Case Modeling
Activity diagrams are not helpful when the flow of activities is too complex.
chapter-bank
T/F
Chapter 5: Use Case Modeling
A true/false condition on a sequence diagram indicates whether the message can be processed or not.
chapter-bank
T/F
Chapter 5: Use Case Modeling
Since an activity diagram is not object-oriented (e.g. no objects), it is not a standard model of the object-oriented Unified Modeling Language (UML).
chapter-bank
T/F
Chapter 5: Use Case Modeling
Activity diagrams cannot be used to describe processes that involve automated system activities.
chapter-bank
T/F
Chapter 5: Use Case Modeling
In an activity diagram, a separate use case may be used as part of the workflow.
chapter-bank
T/F
Chapter 5: Use Case Modeling
A good way to describe a use case scenario is with a state chart.
chapter-bank
T/F
Chapter 5: Use Case Modeling
A loop frame and an asterisk mean the same thing in a sequence diagram.
chapter-bank
T/F
Chapter 5: Use Case Modeling
Two different scenarios of a use case would normally be described in a single fully developed use case description.
chapter-bank
T/F
Chapter 5: Use Case Modeling
In a system sequence diagram the order of the messages is determined by numbering the messages.
chapter-bank
T/F
Chapter 5: Use Case Modeling
On a sequence diagram, a message represents a service request.
chapter-bank
T/F
Chapter 5: Use Case Modeling
Activity diagrams are not helpful in developing system sequence diagrams (SSDs).
chapter-bank
T/F
Chapter 5: Use Case Modeling
In a use case description, exception conditions must relate to the flow of system activities.
chapter-bank
T/F
Chapter 5: Use Case Modeling
CRUD technique validates use cases in system sequence diagram.
chapter-bank
MCQ
Chapter 5: Use Case Modeling
An important step in using the CRUD technique is to
chapter-bank
T/F
Chapter 5: Use Case Modeling
In a System Sequence Diagram (SSD), analysts show all internal database tables, controller classes, and view classes interacting inside the system.
chapter-bank
T/F
Chapter 5: Use Case Modeling
Preconditions specify the exact database states and records that must be guaranteed to be true after a use case finishes executing.
chapter-bank
T/F
Chapter 5: Use Case Modeling
In a System Sequence Diagram, output data returning from the :System to the external actor is represented by a dashed return arrow.
chapter-bank
T/F
Chapter 5: Use Case Modeling
When deriving a System Sequence Diagram from an Activity Diagram, every internal system processing step inside the system swimlane becomes a separate input message on the SSD.
chapter-bank
T/F
Chapter 5: Use Case Modeling
According to the CRUD completeness rule, if a domain class lacks a "Read" use case, data can enter the database but is trapped forever without adding business value.
chapter-bank
T/F
Chapter 5: Use Case Modeling
A Brief Use Case Description is the best format to use for core, complex, mission-critical use cases with heavy exception handling.
chapter-bank
T/F
Chapter 5: Use Case Modeling
In a fully developed use case description, the Flow of Activities is typically organized into two columns separating Actor Steps from System Responses.
chapter-bank
MCQ
Chapter 5: Use Case Modeling
Which of the following compartments in a Fully Developed Use Case Description specifies the mandatory system and database state BEFORE the use case can begin execution?
chapter-bank
MCQ
Chapter 5: Use Case Modeling
Which compartment in a Fully Developed Use Case Description serves as the primary validation criteria for QA testers to verify database updates after completion?
chapter-bank
MCQ
Chapter 5: Use Case Modeling
In a System Sequence Diagram (SSD), the automated software system is modeled as a single black-box object labeled
chapter-bank
MCQ
Chapter 5: Use Case Modeling
What is the correct formal UML syntax for an input message on a System Sequence Diagram?
chapter-bank
MCQ
Chapter 5: Use Case Modeling
On a System Sequence Diagram, an asterisk (*) placed before a message name indicates that the message
chapter-bank
MCQ
Chapter 5: Use Case Modeling
Which UML interaction frame is used in a System Sequence Diagram to model mutually exclusive if-then-else conditional branches?
chapter-bank
MCQ
Chapter 5: Use Case Modeling
What is the first step when developing a System Sequence Diagram (SSD) from an Activity Diagram?
chapter-bank
MCQ
Chapter 5: Use Case Modeling
In the CRUD validation technique, what do the four letters stand for?
chapter-bank
MCQ
Chapter 5: Use Case Modeling
During CRUD analysis, if a domain class has Create, Read, and Update use cases, but lacks a Delete/Archive use case, what is the likely consequence?
chapter-bank
MCQ
Chapter 5: Use Case Modeling
Which analysis model answers the core question: "What data parameters cross the automation boundary between the actor and the system?"