Knowledge Nugget

How do I bring levels to my requirement chaos?
person Author: Timo Karasch
First, our processes constantly ask us to specify requirements. Then we have to bother with quite a lot of documents and specifications. Even the relevant literature cannot explain to me in an understandable way what the difference between all these requirements is supposed to be. And finally, an assessor comes and evaluates my specification as insufficient. This is the end of it! In this webinar we want to bring levels into our requirements chaos. Using simple examples, we will show the different types of requirements and learn a few helpful methods for working with requirements.
  • school Webinar recording and slides
Mapped with these items:
  • Automotive SPICE 4.0
    • SYS.1 Requirements Elicitation
    • SYS.2 System Requirements Analysis
    • SYS.2.BP2 Structure system requirements.
    • SWE.1 Software Requirements Analysis
    • SWE.1.BP2 Structure software requirements.
    • MLE.1 Machine Learning Requirements Analysis
    • MLE.1.BP2 Structure ML requirements.
    • HWE.1 Hardware Requirements Analysis
    • HWE.1.BP2 Structure hardware requirements.
  • Automotive SPICE Potential Analysis 1.0
    • SWDI.BP1 Specify, analyze, structure and prioritize software requirements.
    • REEL Requirements Elicitation
    • SYRD.BP1 Specify, analyze, structure and prioritize system requirements.
  • Mechanical SPICE 2.1
    • MEE.1 Mechanical Requirements Analysis
    • MEE.1.BP2 Structure Mechanical Requirements.
  • Automotive SPICE for Cybersecurity Engineering 2.0
    • SEC.1 Cybersecurity Requirements Elicitation