Knowledge Nugget

The role of assumptions in (system) requirements analysis
person Author: Process Fellows
When deriving system requirements, assumptions fill the gaps. Example: assuming 4G connectivity is always available. Make such assumptions explicit and document their impact. Validate together with stakeholders if such assumptions are correct! If they change, system behavior might too – and that needs tracking.
Mapped with these items:
  • Automotive SPICE 4.0
    • SYS.1.BP2 Agree on requirements.
    • SYS.2.BP3 Analyze system requirements.
  • Automotive SPICE Potential Analysis 1.0
    • REEL.BP2 Agree on requirements.
    • SYRD.BP1 Specify, analyze, structure and prioritize system requirements.