DERIVED REQUIREMENT

Systems Engineering Glossary

Systems EngineeringSystems EngineeringRequirements EngineeringRequirements Management — Derived Requirement

 

 

 

 

 

 

Argos Home

 

 
 


Information on Derived Requirement

A derived requirement is one that was not explicitly stated by a stakeholder but has been derived as part of the requirements analysis process. A derived requirement is therefore not directly stated by a primary source but is derived by systems engineers from an explicit statement of requirement. Derived requirements are therefore inferred during the design process and normally result form some trade-off study as part of the functional and physical design processes. The requirements management process provides a mechanism to trace derived requirements as they are created.


Other topics in our resources on Systems Engineering related to Derived Requirement include: 
 
  • Constraint
  • Verification Requirement
  • Requirements Elicitation
  • Non-Functional Requirement
  • Requirements Traceability
  • Functional Requirement
  • Requirements Allocation
  • Performance Requirement
  • Requirements Negotiation
  •  

    To propose new terms to be added to these glossaries, please contact Argos Press. © Argos Press Pty Ltd, Canberra, 2003-2004. All rights reserved. Please contact Argos Press for all requests to reproduce, broadcast, adapt and communicate content from this web site (including this glossary entry on Derived Requirement).