Explorer

Content

System Requirements Document (SRD) Parts 4 and 5: Context Documents and Glossary

SRD Part 4: Context Documents

Part 4 references context documents and supporting papers so that the System Requirements Document (SRD) is self-contained and can stand alone.

Context documents may be included at the discretion of the Requirements Manager.

Most supporting documentation is included to provide additional understanding or because it is referred to frequently in the SRD.

Additional documents are particularly valuable to readers who may not be familiar with the background to the requirement, for example industry. All system requirements must be included in Part 3 of the SRD regardless of these documents.

Context documents must provide the supplementary information required for verification and system acceptance, expressing the conditions under which the performance must be achievable.

Possible context documents include:

The User Requirement Document (URD) - including its Part 4 Context Documents.
The Acquisition Strategy.
The Acceptance Strategy and associated verification test conditions.
The Concept of Use (CONUSE) for the system.
The operational process or mission profiles that will use the system - not the system’s operating procedure.
The SRD or specification of the legacy system to be updated or upgraded - if applicable.
Reference to specifications for DLoD solutions, including the Equipment Contract Specifications.
Reference to SRDs for interoperating systems, or associated Information Exchange Requirements (IERs) or Interface Control Documents if they exist.
Reference to associated architectures or models.
Operational Analysis and trade study reports, associated scenarios and vignettes.
Other references, MOD policies or Standards.

SRD Part 5: Glossary

The Glossary should include definitions and explanations for all terms that could cause confusion, as well as references and acronyms.

Change History