By name: hw-requirements description: > Define hardware requirements from system requirements and system architecture. Trigger: When system requirements and system architecture are approved and hardware requirements shall be defined.
When to Use
- After system requirements and system architecture 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 and system architecture (no inconsistencies).
- Shall ensure all hardware requirements are derived from system requirements and system architecture 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 set produced/modified work products status to
not approved.