Filter
Top Products
Appendix A. MDSD use case specification template 189
6.1 <Area of Functionality>
[Often there are multiple alternative flows related to a single area of functionality
(for example specialist withdrawal facilities, card handling or receipt handling for
the Withdraw Cash use case of an Automated Teller Machine). It improves
readability if these conceptually related sets of flows are grouped into their own
clearly named sub-section.]
6.1.1 < <n><a> First Alternative Flow >
[Describe the alternative flow, just like any other flow of events. Alternates are
numbered according to guidelines in the Use Case Checklist.
Like the main flow, alternate flows can be expressed in a numbered list of steps:
1.If <condition> then …
2.…
3.…
4.… and the use case returns to … <or ends>.
Or, if using the operation specification style, a table can be used. Note the guard
condition at the top of the table specifying the condition under which the alternate
occurs.]
Alternate Flow
[guard condition]
<Project Name> <Sub-Project Name> Document Version <0.1>
Use Case Specification Date: 20-Oct-07
Template Name: UseCaseSpecification Template Version: 0.1
Actor
Action
Black Box Step White Box Step White Box
Budgeted
Requirements
Locality Process
<indicate if Confidential> copyright <COMPANY>, 2007 Page 7 of 9