Why do I need to write a Concept of Operations document?

You can use the Concept of Operations document to answers questions such as.

Download your template here

• What is the proposed system?
• What are the typical user classes?
• What are the different modes of operation?
• How do I clarify conflicting and ambiguous user requirements?
• How do I prioritize user’s requirements?
• How do I assist project stakeholder in determining if the proposed system should be developed
• What will help me start writing the Functional Requirements Document (FRD)?
• How to communicate the user’s expectations of the proposed system to the Buyer and/or Software Development team
• How to build consensus among user groups, buyer organizations, and/or among developers.

Remember that the aim of this document is NOT to identify the technology to be used or how it will be designed – that comes later.

This is a fore-runner to these documents and helps place the high-level needs in context.

However, the Concept of Operations document can be used to describe the current system environment and operational scenarios as well as identifying existing facilities, policies, resource, etc. that represent significant constraints or limitations that need to be considered during the design and implementation phase.

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

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. 

Q: What file formats are the templates?

A: Microsoft Word. 

Q: How soon can I download them?

A: You can download the file instantly. After you pay online, you are sent to a page where you can download the template online.

A: You can read the License Agreement here

Need to know more?

Email me at ivan at klariti dot com and I'll get back to you within 24 hours.