SRR
Systems Engineering Glossary
Systems Engineering — Systems Engineering — Reviews — SRR
Information on SRR
A SRR is one of a number
of such reviews conducted periodically during Conceptual Design to verify
and approve sets of system-level requirements as they are developed.
The main purpose of each SRR is to ensure that
the design is progressing in the correct direction since Conceptual
Design starts with a single sentence (the need statement) and
ends in hundreds of pages of requirement statements (the System
Specification) . Each SRR therefore gives confidence
in the design process through the progressive monitoring and approval
of the system-level requirements that are developed between the User
Requirements Document and the Functional Baseline.
A SRR
may only involve customer personnel if the Conceptual design is
to being conducted in-house, but can also involve contractors to
ensure a better mutual understanding.
The number of SRRs
will depend on the size and complexity of the project,
although even a very small project will have at least
one SRR.
A SRR may
or may not be considered a formal review.
Each System Requirements
Review also reviews the design activities, design artefacts, trade-off
analysis, and so on. Each review will also review other
information such as manufacturing plans, design schedules, personnel plans, and
so on.
Other topics in our resources on Systems Engineering related to SRR include:
To nominate new words or phrases for the glossary, please contact Argos Press. © Argos Press Pty Ltd, Canberra, 2003-2004. All rights reserved. Please contact Argos Press for information on licensing content from this web site (including this entry on SRR).