OUM

RA.024 USE CASE SPECIFICATION

<Company Long Name>
<Subject>

Author: <Author>
Creation Date: October 28, 2018
Last Updated: October 28, 2018
Document Ref: <Document Reference Number>
Version: DRAFT 1A

Approvals:

<Approver 1>

<Approver 2>
RA.024 Use Case Specification Doc Ref: <Document Reference Number>
October 28, 2018

1 DOCUMENT CONTROL

1.1 Change Record

3

Date Author Version Change Reference

28-Oct-18 <Author> Draft 1a No Previous Document

1.2 Reviewers

Name Position

<Subject> Document Control iii

File Ref: 400685135.doc (v. DRAFT 1A )
RA.024 Use Case Specification Doc Ref: <Document Reference Number>
October 28, 2018

Contents

1 Document Control.................................................................................................... iii

1.1 Change Record........................................................................................................... iii
1.2 Reviewers................................................................................................................... iii

2 Introduction............................................................................................................... 1
2.1 Scope and Purpose..................................................................................................... 1
2.2 Definitions, Acronyms, and Abbreviations...................................................................1

3 <UC number>: <Scope symbol> <UC name> <Level symbol>..............................2

3.1 Context of Use............................................................................................................ 2
3.2 Scope and Level......................................................................................................... 2
3.3 Primary and Secondary Actors....................................................................................2
3.4 Stakeholder and Interest............................................................................................. 2
3.5 Assumptions................................................................................................................ 3
3.6 Pre-Conditions............................................................................................................ 3
3.7 Post-Conditions........................................................................................................... 3
3.8 Trigger......................................................................................................................... 3
3.9 Main Success Scenario............................................................................................... 3
3.10 Extension – Alternate Flows........................................................................................ 4
3.11 Exception Flows.......................................................................................................... 4
3.12 Technology and Data Variations List...........................................................................5
3.13 Related Information..................................................................................................... 5
3.14 Decisions..................................................................................................................... 5
3.15 Open Issues................................................................................................................ 5

4 References................................................................................................................. 6

5 Notation...................................................................................................................... 7

6 How to Review............................................................................................................ 9

<Subject> Document Control iii

File Ref: 400685135.doc (v. DRAFT 1A )
 Doc Ref:

2 INTRODUCTION

2.1 Scope and

Purpose

This document presents the Use Case Specifications, which contains the textual properties of the use
case. This template proposes the use of the use case notation suggested in "Writing Effective Use
Cases" from Alistair Cockburn. Refer to the Use Case Technique file associated with the RA.024 Use
Case Details task guideline for more information. Refer to the References at the end of this work
product to see notation on how to review use cases.

The system use case should describe how the system behaves from the actor’s point of view. In
some cases it may not necessary to go to multiple levels of detail for the design scope and goal level.

2.2 Definitions,
Acronyms, and
Abbreviations
Term Meaning

SuD System under Discussion

Document Control iii

File Ref: 400685135.doc (v. )
 Doc Ref:

3 <UC NUMBER>: <SCOPE SYMBOL> <UC NAME> <LEVEL

SYMBOL>

3.1 Context of Use

3.2 Scope and Level

Scope Level

3.3 Primary and

Secondary Actors

Primary Actor

Name Description

Secondary Actors

Name Description

3.4 Stakeholder and

Interest

Name Interest

Document Control iii

File Ref: 400685135.doc (v. )
 Doc Ref:

Name Interest

3.5 Assumptions

3.6 Pre-Conditions

3.7 Post-Conditions

Main Success Scenario Post-Conditions

<Brief Description/Background>

3.8 Trigger

3.9 Main Success

Scenario

What the Actor Does What the System Does

1. This use case begins when the <actor> selects 2. The <system name> <action description>
the option to <use case name>

3. The <system name> <action description>

4. The <actor name> <action description>

Document Control iii

File Ref: 400685135.doc (v. )
 Doc Ref:

N. This use case ends when the <actor name>

<action description>

3.10 Extension –
Alternate Flows

What the Actor Does What the System Does

1. <step altered><branch letter> <condition>: 2. <step altered><branch letter><step number>.

<action or sub-use case>

Extension - Alternate Flow Scenarios Post-Condition(s)

<extension step> <condition description>

3.11 Exception Flows

What the Actor Does What the System Does

1. <step altered><branch letter> <condition>: 2. <step altered><branch letter><step number>.

<action or sub-use case>

Document Control iii

File Ref: 400685135.doc (v. )
 Doc Ref:

Exception Flow Scenarios - Failed Post-Condition(s)

<exception step> <condition description>

3.12 Technology and

Data Variations List

<step or variation # > <list of variations>

<step or variation # > <list of variations>

3.13 Related
Information
 …
 …

The following meeting notes, documents, and email message contents

are of relevance to the use case:

 …
 …

3.14 Decisions

The following provides a summary of important decisions made by the business or technical teams
that impact the individual use case

<Issue>. <Decision/Action>

<Brief Description/Background>

3.15 Open Issues

1. …
2. …

Document Control iii

File Ref: 400685135.doc (v. )
 Doc Ref:

Document Control iii

File Ref: 400685135.doc (v. )
 Doc Ref:

4 REFERENCES

Alistair Cockburn, Writing Effective Use Cases, Addison-Wesley, 2001, ISBN 0-201-70225-8.

Jan Kettenis, Getting Started with Use Case Modeling, 2005.

Document Control iii

File Ref: 400685135.doc (v. )
 Doc Ref:

5 NOTATION

Design Scope

Level in which the system is inserted in the use case. Am I checking up on organization or on
system? Am I describing its internal structure or not?

Attention: In general OUM Prescribes writing Use Cases Details as System

Use cases at the black box scope level. Basically anything that the Actor is
aware the system is doing, is shown in the Use Case Details. **

Organization black-box
Consider the organization where the system is inserted, without revealing
its internal structure.

Organization white-box
Consider the organization where the system is inserted, revealing its
internal structure.

System black-box **
Consider the system, without revealing its internal actions.

System white-box
Consider the system, revealing its internal actions.

Component
Describes the functioning of a system component.

Document Control iii

File Ref: 400685135.doc (v. )
 Doc Ref:

Goal Level

Level in which the user requirements are met, and operation way

Attention: In general OUM Prescribes writing Use Cases Details as User-

Goal Level. ***

User-Goal ***
Corresponds to a user interaction with the system in which one of his goals
is met.

Summary & Very high summary

More abstract level than user-goal, commonly used to provide the context in
which the use cases are inserted.

Subfunction & Too low

Detailed user-goal, used when some operational detail is necessary.

Document Control iii

File Ref: 400685135.doc (v. )
 Doc Ref:

6 HOW TO REVIEW

Please use the following criteria when reviewing the Use Case Specification suggested in "Writing
Effective Use Cases" from Alistair Cockburn (all of them should produce a "yes" answer):

Use Case Name

 Is it an active-verb goal phrase that names the goal of the primary actor?
 Can the system deliver that goal?

Primary Actor

 Does he/she/it have behavior?

 Does he/she/it have a goal against the SuD that is a service promise of the SuD?

Pre-Conditions

 Are they mandatory?

 Is it true that they are never checked in the use case?

Main Success Scenario

 Does it have 3-9 steps?

 Does it run from trigger to delivery of the success guarantee?
 Does it allow the right variations in sequence?

Each Step in Any Scenario

 Is it phrased as a goal that succeeds?

 Does the process move distinctly forward after its successful completion?
 Is it clear which actor is operating the goal--who is "kicking the ball"?
 Is the intent of the actor clear?
 Is the goal level of the step lower than the goal level of the overall use case? Is it,
preferably, just a bit below the use case goal level?
 Are you sure the step does not describe the user interface design of the system?
 Is it clear what information is being passed in the step?

Extension Condition

 Can and must the system both detect and handle it?
 Is it what the system actually needs?

Document Control iii

File Ref: 400685135.doc (v. )