Appendix A Acronyms
Appendix B Glossary
Appendix C How to Write a Good Requirement— Checklist
Appendix D Requirements Verification Matrix
Appendix E Creating the Validation Plan with a Validation Requirements Matrix
Appendix F Functional, Timing, and State Analysis
Appendix G Technology Assessment/Insertion
Appendix H Integration Plan Outline
Appendix I Verification and Validation Plan Outline
Appendix J SEMP Content Outline
Appendix K Technical Plans
Appendix L Interface Requirements Document Outline
Appendix M CM Plan Outline
Appendix N Guidance on Technical Peer Reviews/Inspections
Appendix O Reserved
Appendix P SOW Review Checklist
Appendix Q Reserved
Appendix R HSI Plan Content Outline
Appendix S Concept of Operations Annotated Outline
Appendix T Systems Engineering in Phase E
1.0 Introduction
1.1 Purpose and Scope
State the purpose of this document and briefly identify the interface to be defined. (For example, “This IRD defines and controls the interface(s) requirements between ______ and ______.”)
1.2 Precedence
Define the relationship of this document to other program documents and specify which is controlling in the event of a conflict.
1.3 Responsibility and Change Authority
State the responsibilities of the interfacing organizations for development of this document and its contents. Define document approval authority (including change approval authority).
2.0 Documents
2.1 Applicable Documents
List binding documents that are invoked to the extent specified in this IRD. The latest revision or most recent version should be listed. Documents and requirements imposed by higher-level documents (higher order of precedence) should not be repeated.
2.2 Reference Documents
List any document that is referenced in the text in this subsection.
3.0 Interfaces
3.1 General
In the subsections that follow, provide the detailed description, responsibilities, coordinate systems, and numerical requirements as they relate to the interface plane.
3.1.1 Interface Description
Describe the interface as defined in the system specification. Use tables, figures, or drawings as appropriate.
3.1.2 Interface Responsibilities
Define interface hardware and interface boundary responsibilities to depict the interface plane. Use tables, figures, or drawings as appropriate.
3.1.3 Coordinate Systems
Define the coordinate system used for interface requirements on each side of the interface. Use tables, figures, or drawings as appropriate.
3.1.4 Engineering Units, Tolerances, and Conversion
Define the measurement units along with tolerances. If required, define the conversion between measurement systems.
3.2 Interface Requirements
In the subsections that follow, define structural limiting values at the interface, such as interface loads, forcing functions, and dynamic conditions. Define the interface requirements on each side of the interface plane.
3.2.1 Mass Properties
Define the derived interface requirements based on the allocated requirements contained in the applicable specification pertaining to that side of the interface. For example, this subsection should cover the mass of the element.
3.2.2 Structural/Mechanical
Define the derived interface requirements based on the allocated requirements contained in the applicable specification pertaining to that side of the interface. For example, this subsection should cover attachment, stiffness, latching, and mechanisms.
3.2.3 Fluid
Define the derived interface requirements based on the allocated requirements contained in the applicable specification pertaining to that side of the interface. For example, this subsection should cover fluid areas such as thermal control, O2 and N2, potable and waste water, fuel cell water, and atmospheric sampling.
3.2.4 Electrical (Power)
Define the derived interface requirements based on the allocated requirements contained in the applicable specification pertaining to that side of the interface. For example, this subsection should cover various electric current, voltage, wattage, and resistance levels.
3.2.5 Electronic (Signal)
Define the derived interface requirements based on the allocated requirements contained in the applicable specification pertaining to that side of the interface. For example, this subsection should cover various signal types such as audio, video, command data handling, and navigation.
3.2.6 Software and Data
Define the derived interface requirements based on the allocated requirements contained in the applicable specification pertaining to that side of the interface. For example, this subsection should cover various data standards, message timing, protocols, error detection/correction, functions, initialization, and status.
3.2.7 Environments
Define the derived interface requirements based on the allocated requirements contained in the applicable specification pertaining to that side of the interface. For example, cover the dynamic envelope measures of the element in English units or the metric equivalent on this side of the interface.
3.2.7.1 Electromagnetic Effects
3.2.7.1.a Electromagnetic Compatibility
Define the appropriate electromagnetic compatibility requirements. For example, the end-item-1-to-end-item-2 interface shall meet the requirements [to be determined] of systems requirements for electromagnetic compatibility.
3.2.7.1.b Electromagnetic Interference
Define the appropriate electromagnetic interference requirements. For example, the end-item-1-to-end-item-2 interface shall meet the requirements [to be determined] of electromagnetic emission and susceptibility requirements for electromagnetic compatibility.
3.2.7.1.c Grounding
Define the appropriate grounding requirements. For example, the end-item-1-to-end-item-2 interface shall meet the requirements [to be determined] of grounding requirements.
3.2.7.1.d Bonding
Define the appropriate bonding requirements. For example, the end-item-1-to-end-item-2 structural/mechanical interface shall meet the requirements [to be determined] of electrical bonding requirements.
3.2.7.1.e Cable and Wire Design
Define the appropriate cable and wire design requirements. For example, the end-item-1-to-end-item-2 cable and wire interface shall meet the requirements [to be determined] of cable/wire design and control requirements for electromagnetic compatibility.
3.2.7.2 Acoustic
Define the appropriate acoustics requirements. Define the acoustic noise levels on each side of the interface in accordance with program or project requirements.
3.2.7.3 Structural Loads
Define the appropriate structural loads requirements. Define the mated loads that each end item should accommodate.
3.2.7.4 Vibroacoustics
Define the appropriate vibroacoustics requirements. Define the vibroacoustic loads that each end item should accommodate.
3.2.7.5 Human Operability
Define the appropriate human interface requirements. Define the human-centered design considerations, constraints, and capabilities that each end item should accommodate.
3.2.8 Other Types of Interface Requirements
Define other types of unique interface requirements that may be applicable.