How to write the Concept of Operations document?
The development of a
Concept of Operations document involves the following steps:
1. Current System
Describe the current system. If no
current system is in place, describe what motivates the development of
the proposed system. Divide this chapter into paragraphs that describe
the system or situation as it currently exists.
Download your template
here
If possible, provide details of the
operational environment, components, interconnections, interfaces to
external systems, descriptions of inputs, outputs,
data flow, and current cost of the system’s operations, risk factors, performance
characteristics and quality attributes.
2. Justification of Changes
Discuss the shortcomings of the current
system.
Then describe how the development of the new system will address
the limitations of the current setup.
Summarize user needs, strategic goals, limitations,
interfaces to other systems, personnel requirements,
or other factors that require a new or modified system.
3. Use Case Scenarios
Prepare
use cases that show work scenarios, how users perform or need to perform their duties.
Capture this is a Word narrative and/or use case Visio diagram.
Highlight data exchanges between
department, partners, and customers. Identify who triggers these
actions, what are the inputs and outputs and exceptions.
4. Proposed System
Describe the proposed system. Outline
the environment in which the proposed systems will be built and how it
will be operated and maintained.
This involves describing the existing
system, communications, infrastructure, volume of users, special
requirements.
5. Evaluation
To determine the effectiveness of the
proposed system,
prepare a list of metrics for evaluating the performance of the new
system. Use these metrics after the system is
operational to determine if the system is performing as expected.
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. 
