How
to develop Use Cases to capture Scenarios
Most
Concept of Operations document I’ve written
have been a combination of a Word document (describing the
current/proposed system from a non-technical perspective) and
use case diagrams (usually in Microsoft Visio) that illustrate how a
process works.
Download your template
here
Sometimes, I expand on this by showing
an As Is (how things operate today) process flow and a To Be (how it
will be) process diagram.
A typical scenario (use case) describes
the interactions between the individuals involved,
policies/restraints/limitation that influence these operations, and any
data that goes in and comes back out!
Use cases describes system-related
activities.
These describe a specific situation, or
set of circumstances, where the user interacts with the system.
Tip: Write your use cases in
the present tense.
Avoid saying, ‘the user will’ or ‘the
user would.’ Write, “the user enters the credit card details into screen
x” etc.
Download your template
here
The project stakeholders (i.e. those
who are responsible for signing off/funding of this project) will then
review these scenarios.
Write the use cases in plain language—avoid technical jargon—and include
reference to supporting material if necessary.
If another need must be added to the
list, then you need to locate its origin in the scenarios and update the
documents accordingly.
Read more:
1.
How to write the Concept Operations Document
2.
What it a Concept Operations Document?
3.
How to Define the Goals, Objectives and Rationale
4.
What you need to put into a Concept Operations Document
5.
How to Justify the New System to Project Stakeholders
6.
How to develop Use Cases to capture Work Scenarios
7.
What's the Connection Between the Concept of Operations and
Functional Requirements Document
~~~
Concept of Operations Template
Download Now for
$7.99 - Buy Here!
Table of Contents
toc
1 Introduction
1.1 Document overview
1.2 Background
1.3 Identification
1.4 Goals, objectives & rationale
1.5 Points of contact
2 Current System
2.1 Background
2.2 Scope
2.3 Policies and Constraints
2.4 Description of current system
2.5 Modes of Operation
2.6 Users classes & other stakeholders
2.7 Support Environment
3 Justification
3.1 Justification for change
3.2 Description of required changes
3.3 Priorities among the changes
3.4 Changes considered but not included
3.5 Assumptions
3.6 Constraints
4 Proposed System
4.1 Background, objectives, and scope
4.2 Operational policies and constraints
4.3 Description of the new system
4.4 User classes / categories of users
4.5 Modes of operation
4.6 Deployment and support environment
4.7 Non-functional requirements
4.8 Requirements traceability
5 Use Cases & Operation Scenarios
5.1 Process descriptions
5.2 Events
5.3 Use Case
6 Impacts
6.1 Risks
6.2 Issues
6.3 Operational impacts
6.4 Organizational impacts
6.5 Impacts during development
7 Analysis of the Proposed System
7.1 Improvements
7.2 Disadvantages & limitations
7.3 Alternatives
What's included in the template pack
The template is in
Microsoft Word format and can be downloaded online for only $7.99. The template pack includes the following documents:
|
Concept of Operations Template |
30 pages |
 |
Download Now for
$7.99 - Buy Here!
~~~
|
60-day Money-Back Guarantee
Secure Online
Order Form
Supports
Microsoft Word from 2002, 2003, 2007 and works across Windows 97, 2003, XP, Vista
and Apple Mac. 
I'm Ivan Walsh, the person behind this site. I help people improve how they write, publish and extend their business assets.