Connection Between Concept of Operations
and Functional Requirements Document?
What is the connection between the
Concept of Operations document and the
Functional Requirements Document (FRD)?
Once the Concept of Operations document
is completed—and the project gets the go-ahead—this document can be used
as a starting point by the Business Analyst and those involved in
capturing requirements.
Download your template
here
System requirements will be derived
from the user needs and converted into more formal and exact language as
per the Software Requirements Specification (SRS) and the Functional
Requirements Document (FRD).
The
Software Requirements Specification
is written for IT Architects and Software Developers and must be as
precise as possible. Avoid ambiguity. Keep each requirement as precise
as possible.
Ask yourself: how could the reader
misunderstand this requirement?
Where is it ambiguous, vague or contradictory?
The
Functional Requirements Document (FRD)
is a distillation of the users’ needs, which is later converted into the
Software Requirements Specification (SRS).
Technical writers convert them from
high-level, user-oriented language into exact, technical statements.
What else does the use cases do?
The operation scenarios (use cases) can
also be used to:
- Define the scope of work for
system integration
- Determine facilities that must be
provided
- Estimate the required funding
- Estimate training requirements
- Identify metrics for measuring and
validating the live system
- Identify support requirements
Summary
The Concept of Operations document is a
critical part of the Software Development Lifecycle.
The contents of this document must be
sufficient to allow the decision-maker to evaluate, approve and assess
the worthiness of the proposed system.
This document is necessary to capture
all information required for the development of requirements for, and
design of the system and the associated support environment.
Read more:
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.