1. What are the models that describe use cases in more detail?: Fully
developed use case description, activity diagrams, and system sequence diagrams.
2. What two UML diagrams are used to model domain classes?: Problem
domain class diagram and state machine diagram.
3. Which part of a use case description can also be modeled by using an
activity diagram?: The "flow of activities" section.
4. Explain the difference between a use case and a scenario. Give a specific
example of a use case with a few possible scenarios.: A use case is the entire
function or user goal or event. A scenario is one specific version or instance of that
use case. From RMO we have Create customer account as a use case. But we
might have Create online Customer account and Create instore customer account
and even Create phone customer account as different scenarios.
5. List the parts or compartments of a fully developed use case
description.: Use case name
Scenario
Triggering event
Brief description
Actors
Related use cases
Stakeholders
Preconditions
Postconditions
Flow of activities
Exception conditions
6. Compare/contrast precondition and postcondition.: A precondition
describes the "states" of data and the system that must exist before the use case
can begin. For example to add an item to a shopping cart, the item must exist in the
database. A postcondition describes the states of data and the system that must
exist after the use case completes. For example after Create a customer account
use case, a customer account object (record) must exist.
7. Compare/contrast postcondition and exception condition.: A post
condition, as explained about describes states of the data and the system. An
exception condition describes some non-normal situation in the processing, i.e. in
the flow of activities, that must be handled in some way.
1/3
developed use case description, activity diagrams, and system sequence diagrams.
2. What two UML diagrams are used to model domain classes?: Problem
domain class diagram and state machine diagram.
3. Which part of a use case description can also be modeled by using an
activity diagram?: The "flow of activities" section.
4. Explain the difference between a use case and a scenario. Give a specific
example of a use case with a few possible scenarios.: A use case is the entire
function or user goal or event. A scenario is one specific version or instance of that
use case. From RMO we have Create customer account as a use case. But we
might have Create online Customer account and Create instore customer account
and even Create phone customer account as different scenarios.
5. List the parts or compartments of a fully developed use case
description.: Use case name
Scenario
Triggering event
Brief description
Actors
Related use cases
Stakeholders
Preconditions
Postconditions
Flow of activities
Exception conditions
6. Compare/contrast precondition and postcondition.: A precondition
describes the "states" of data and the system that must exist before the use case
can begin. For example to add an item to a shopping cart, the item must exist in the
database. A postcondition describes the states of data and the system that must
exist after the use case completes. For example after Create a customer account
use case, a customer account object (record) must exist.
7. Compare/contrast postcondition and exception condition.: A post
condition, as explained about describes states of the data and the system. An
exception condition describes some non-normal situation in the processing, i.e. in
the flow of activities, that must be handled in some way.
1/3
