Derived Requirement are requirements that are not explicitly stated in the set of Stakeholder requirements yet is required to satisfy one or more of them. They also arise from constraints, consideration of issues implied but not explicitly stated in the requirements baseline, factors introduced by the selected architecture, Information Assurance (IA) requirements and the design. Derived requirements are developed through Requirements Analysis as part of the overall Systems Engineering Process (SEP) and are part of the Allocated Baseline.
Derived Technical Requirements
Derived Technical Requirements are those that result from the analysis and allocation of Technical Requirements to logical functional architectures that are developed as part of the Requirements Analysis process; or from the Analysis of Alternative (AoA) solutions done later as part of the Architecture Design Process. Derived Technical Requirements become the basis for the solution-specified requirements for the system model and is a ‘design-to’ requirement for the system.
Example Derived Requirement:
The missile shall be aimed within 2 degrees of the target so that the warhead terminal seeker can lock on and perform the terminal intercept. 
AcqLinks and References:
- Defense Acquisition Guidebook (DAG)
- Requirements Development Checklist
- DAU Systems Engineering Fundamentals Guide
- Space and Missile Systems Center (SMC) Systems Engineering Primer & Handbook
- NASA Systems Engineering Handbook (large 9M file)
- White Paper: Writing a Requirements Document “For Multimedia and Software Projects” by Rachel S. Smith
- White Paper: Requirements Development, Verification, and Validation Famous Failures by Bahill & Henderson