The Operational Concept Description (OCD) describes
a proposed system in terms of the user needs it will fulfill,
its relationship to existing systems or procedures and the ways
it will be used. See DID for further
The OCD is used to obtain consensus among the acquirer, developer, support, and user agencies on the operational concept of a proposed system.
Insert the "Table of Contents" here.
Consult DI-IPSC-81430 and the 'Documentation Standard' when preparing this document.
Identify the system to which this document applies, including, as applicable, identification number(s), title(s), abbreviation(s), version number(s), and release number(s).
State the purpose of the system or subsystem to which this document applies.
Summarize the purpose and contents of this document.
This document comprises of six sections:
Describe any security or privacy considerations associated with its use.
Identify the project management systems documents here.
This section contains information of a general or explanatory nature that may be helpful, but is not mandatory.
This system/subsystem design description shall ...
Insert here an alphabetic list of definitions and their source if different from the declared sources specified in the 'Documentation standard'.
Insert here an alphabetic list of the abbreviations and acronyms if not identified in the declared sources specified in the 'Documentation Standard'.
Will be "not applicable" for the initial issue.
Revisions shall identify the method used to identify changes from the previous issue.
This page is under construction
Back to Home page MANAGING STANDARDS Home page
Please send any beneficial comments or identification of errors
using the following form to: firstname.lastname@example.org