URD
Systems Engineering Glossary
Systems Engineering — Systems Engineering — Requirements Engineering — URD
Information on URD
The URD is a seminal
document in the systems engineering and requirements engineering processes. The
User Requirement Document contains the requirements from the stakeholders particularly
the users (operators, maintainers, trainers, marketers, etc). All stakeholders must
be involved or at least considered during the development of
the User Requirement Document.
As a minimum, the User Requirement Document
should reveal: applications and missions; operational characteristics; operational constraints; external
systems and interfaces; operational and support environment; and support concepts
and responsibilities.
The User Requirement Document should be written in the
customer’s or user’s language (as opposed to the more precise
specification language).
The User Requirement Document can also be called an
Operational Concept Document (OCD); a Concept of Operation Document (COD);
or a System Design Document (SDD). These names tend to
have a specific application, however, and are invoked by particular
standards (ANSI/AIAA G-043-1992, IEEE P1362, etc).
Other topics in our resources on Systems Engineering related to URD include:
If you would like to propose related terms for these glossaries, please contact us. © Argos Press Pty Ltd, Canberra, 2003-2009. All rights reserved. Please contact Argos Press Pty Ltd to seek permission to broadcast, adapt, reproduce and communicate our content (such as this entry on URD).