logo

Artefact overview of artefact "System requirements specification"

spem diagram of an artefact overview: System requirements specification

Artefact break down of artefact "System requirements specification"

spem diagram of the artefact breakdown: System requirements specification

Artefact dependency of artefact "System requirements specification"

spem diagram of artefact dependency: System requirements specification

Brief description of artefact "System requirements specification"

17-12 System requirements specification

Detailed description of artefact "System requirements specification"

17-12 System requirements specification

  • System requirements include: functions and capabilities of the system; business, organizational and user requirements; safety, security, human-factors engineering (ergonomics), interface, operations, and maintenance requirements; design constraints and qualification requirements.
  • Identifies the required system overview
  • Identifies any interrelationship considerations/constraints between system elements
  • Identifies any relationship considerations/constraints between the system elements and the software
  • Identifies any design considerations/constraints for each required system element, including:
    • memory/capacity requirements
    • hardware interface requirements
    • user interface requirements
    • external system interface requirements
    • performance requirements
    • command structures
    • security/data protection characteristics
    • system parameter settings
    • manual operations
    • reusable components
  • Describes the operation capabilities
  • Describes environmental capabilities
  • Documentation requirements
  • Reliability requirements
  • Logistical Requirements
  • Describes security requirements
  • Diagnosis requirements

17-00 Requirement specification

  • Each requirement is identified
  • Each requirement is unique
  • Each requirement is verifiable or can be assessed (see 17-50)
  • Includes statutory and regulatory requirements
  • Includes issues/requirements from (contract) reviews

17-50 Verification Criteria

  • Each requirement is verifiable or can be assessed
  • Verification criteria define the qualitative and quantitative criteria for verification of a requirement.
  • Verification criteria demonstrate that a requirement can be verified within agreed constraints. (Additional Requirement to 17-00 Requirements specification)

Extended Markdown

Extended Markdown is a special format (actually a DSL), used in this process for tracability. While the file is 100% markdown compliant, there are some additional tags to identify relations (links).

Because this links can be easily identified by text searches, a small helper (script) is able to collect all links and add the corresponding backward links. This ensures, that forward and backward links are always consistent (not more than that).

  • All reqirement documents are written in “Extended Markdown”.

  • The “Extended Markdown” files are considered to be “sourcefiles” of the requirement document (and are configuration items).