CT015-3-2 Design Methods

Documenting Use Case

 Learning objectives

At the end of this lecture, you should be

able to :
Documenting use cases in use case
model

Module Code and Module Title Title of Slides #

 Use Case Description

Each use case in the use case model

need to be documented in a use case
description.
A textual description of the sequence of
transactions of a use case is needed to
understand what really happens in a use
case.
The flow-of-events is written in terms of
what the system should do, not how the
system does it.
Module Code and Module Title Title of Slides #
 Templates for a Use Case Flow
of Events
Use case : Each use case is given a name.
Summary: A brief description of the use case
Dependency: A use case depends on other use
cases whether it includes or extends another
use case.
Actors: Names the actors in the use case.
Generally, primary actor that initiates the use
case. In addition, there may be secondary actors
that also participate in the use case.

Module Code and Module Title Title of Slides #

 Templates for a Use Case Flow
of Events
Preconditions: One or more conditions that
must be true at the start of use case, from the
perspective of this use case; eg. the ATM
machine is idle, displaying a Welcome
message.
Description of main sequence: A series of
declarative steps - sequence of interactions
between the actor and the system. The
description is in the form of the input from the
actor, followed by the response of the system.

Module Code and Module Title Title of Slides #

 Templates for a Use Case Flow
of Events
Description of alternative sequences:
Narrative description of alternative branches off
the main sequence. Eg., if the customers
account has insufficient funds, display apology
and eject card.
The alternative sequence branches off from
the main sequence is identified as well as a
description of the alternative.

Module Code and Module Title Title of Slides #

 Templates for a Use Case Flow
of Events
Description of alternative sequences: Narrative
description of alternative branches off the main
sequence. Eg., if the customers account has
insufficient funds, display apology and eject card.
The alternative sequence branches off from the main
sequence is identified as well as a description of the
alternative.
Postcondition: Condition that is always true at the
end of the use case (from the perspective of this use
case) if the main sequence has been followed; for
example, customers funds have been withdrawn.

Module Code and Module Title Title of Slides #

 Sample of Use Case Description

Module Code and Module Title Title of Slides #

Module Code and Module Title Title of Slides #
 Review

Explain flows-of-event.
Defines preconditions.

Module Code and Module Title Title of Slides #

 Q&A

Module Code and Module Title Title of Slides #