Defines standard
Replaced/Superseded by document(s)
Cancelled by
Amended by
| File | MIME type | Size (KB) | Language | Download | |
|---|---|---|---|---|---|
| TAA_ME04_000950_OCD.pdf | application/pdf | 67.17 KB | English | DOWNLOAD! |
Provides definitions
Extract(s)
The Operational Concept Description (OCD) describes, for a system, subsystem, HWCI,
CSCI, component, or other item, herein referred to generically as “the system”, who the
users of the system are, what are the intended uses of the system, how and where the
system is intended to be used, and a representative set of scenarios of use. These scenarios,
each associated with a particular intended use (mission), are chosen to represent both
typical and limit conditions of use.
The OCD is used as a vehicle for achieving a complete and shared understanding of the
information listed above between the system sponsor, users, operators, maintainers,
acquirers, requirements analysts, designers, constructors and testers, as a basis for
specification, procurement, design, qualification testing and operational testing of the
system. Throughout this DID, the term “system” may be interpreted to mean "segment",
"subsystem", "element", "HWCI", CSCI component or other item, as applicable.
This Data Item Description (DID) may be cited in a System/Subsystem Specification (SSS),
Statement of Requirement (SOR), Statement of Work (SOW), a Contract Data
Requirements List (CDRL), or within a standard invoked by a SOR or SOW or CDRL.
This DID incorporates and adopts some non-copyrighted material contained in a draft
Recommended Technical Practice of the American Institute of Aeronautics and Astronautics
(AIAA) of the United States of America, titled “Operational Concept Document (OCD)
Preparation Guidelines”.