Hw Requirements

When to Use

• After system requirements, system architecture, and mechanical-hardware interface are approved.
• When any hardware requirements activity is required.

Critical Patterns

• Shall strictly follow the provided resources and recursively review all referenced documents required to understand the current process, inputs, outputs, rules and directly referenced work products.
• Shall align with system requirements, system architecture, and the mechanical-hardware interface (no inconsistencies).
• Shall ensure all hardware requirements are derived from system requirements, system architecture, and the mechanical-hardware interface by adding explicit traceability between them.
• Shall avoid embedding design implementation details in hardware requirements.
• Shall keep documentation DRY (Don't Repeat Yourself) by adding references instead of duplicating content.
• Shall ask for approval when hardware requirements are incomplete, ambiguous, or conflicting.
• Shall request final validation before closing the hardware requirements to ensure no further iterations are needed.

Resources