Copyright © 2004-2010 BSSE.
All rights reserved.
Impressum Legal Notice

Systematic Requirements Mangement

Systematic Requirements Management (SRM) increases the efficiency of requirement management and the quality of requirements through systematic classification of requirement elements, tailored to the respective application area.

The systematic capability implies an immediate verifiability of requirements and guidance of the user aimed at resilient, i.e. complete and high-quality specifications without any contradictions. With an iterative approach and incremental refinement a check can be carried out after every step and errors can be immediately corrected. The ultimate goal, which can be achieved with SRM, is the “Zero Defect“ status of the requirements.

Approach

  • Domain-specific orientation: For each domain principal requirement elements are classified and linked through rules. The schemes for recording them are defined in agreement with the user or are already defined.
  • Guided specification: the user utilises the predefined schemes and the methodology feedback to identify the requirements (Requirements Elicitation).
  • Derived information: SRM automatically derives further implicit requirements (derived information) about the specified product, respectively service, from the primary requirements defined by the user.
  • Reports: the user defines the content of the reports from a list of documentation modules for text and graphics. Three principal reports are generated: on the content of the requirements (requirements documentation, specification), inputs to project management and on errors.
  • Checking / verification: SRM checks the provided requirements against the rules and identifies errors.
  • Checking / validation: SRM visualises original and derived requirements, enabling the user to assess the result of all requirements in the total context from different perspectives and to compare them with the intended goals. The user must identify deviations between desired intentions and actual situation.
  • Iterative: errors are corrected or requirements are modified.
  • Incremental: the requirements are refined through a topdown process and the number of requirements increases.