<Project Name> <Sub-Project Name>

Document Version <0.1>

 

 

Use Case Specification

Date: 20-Oct-07

 

 

Template Name: UseCaseSpecification

Template Version: 0.1

 

 

Main Flow

Actor Action

Black Box Step

White Box Step

White Box

Budgeted

Requirements

Locality

Process

]

6 Alternative Flows

[Alternatives are described in this section, referred to in the Basic Flow subsection of Flow of Events section. Think of the Alternative Flow subsections like alternative behavioreach alternative flow represents alternative behavior usually due to exceptions that occur in the main flow. They can be as long as necessary to describe the events associated with the alternative behavior.

Start each alternative flow with an initial line clearly stating where the alternative flow can occur and the conditions under which it is performed.

End each alternative flow with a line that clearly states where the events of the main flow of events are resumed. This must be explicitly stated.

Using alternative flows improves the readability of the use case. Keep in mind that use cases are just textual descriptions, and their main purpose is to document the behavior of a system in a clear, concise, and understandable way.

Be sure to find and describe ALL of the alternate flows.]

<indicate if Confidential>

copyright <COMPANY>, 2007

Page 6 of 9

188Model Driven Systems Development with Rational Products

Page 204
Image 204
IBM SG24-7368-00 manual Alternative Flows