3.1 The Operational Concept Description (OCD) is a system-centric description, for a system, subsystem, HWCI, CSCI, component or other item, herein referred to generically as “the system”, of who the users of the system are and their relevant characteristics, what are their 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
also describes the expected external conditions during use. Other names for an OCD are CONUSE, OpsCon and Statement of Operating Intent. In addition, a CONEMP is a limited form of OCD.
3.2 The OCD is used as a vehicle for achieving a comprehensive 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 validation of the system requirements, system design, subsystems and the system. Throughout this DID, the term “system” may be interpreted to mean “segment”, “subsystem”, “element”, “HWCI”, CSCI component or other item, as applicable, that is the subject of the
Replaced/Superseded by document(s)
|File||MIME type||Size (KB)||Language||Download|
|PPA-000950-17 PPI DID (OCD) 201119.pdf||application/pdf||461.89 KB||English||DOWNLOAD!|