02 — Capability · BC-530.10
Requirements & Product Definition
Translate a concept into a precise statement of what the product must do, for whom, under what constraints, so design and engineering build the right thing and testing knows what right means.
- Product Requirements
- Specification Definition
In scope
- Customer and user needs elicitation
- Functional and non-functional requirements
- Regulatory and standards requirements applicable to the product
- Requirements traceability from need to test
Out of scope
- Product vision and positioning (see BC-510)
- Determining which regulations apply (see BC-140)
Realized by · 1
Used in · 1
Build it · 0
- Nothing in the library points here yet.
Decomposes into · 4
- BC-530.10.10Needs ElicitationGather what users and customers actually need, by observing and asking, and separate it from what they say they want.
- BC-530.10.20Requirements SpecificationWrite requirements that are specific enough to design against and testable enough to verify, and keep them under change control.
- BC-530.10.30Constraint & Standards AnalysisIdentify the regulatory, safety, interoperability and cost constraints the product must satisfy and build them into the specification early.
- BC-530.10.40Requirements TraceabilityLink each requirement forward to the design element and test that satisfy it, so nothing is built without a reason or shipped without proof.