logo

Artefact overview of artefact "Stakeholder requirements"

spem diagram of an artefact overview: Stakeholder requirements

Artefact break down of artefact "Stakeholder requirements"

spem diagram of the artefact breakdown: Stakeholder requirements

Artefact dependency of artefact "Stakeholder requirements"

spem diagram of artefact dependency: Stakeholder requirements

Brief description of artefact "Stakeholder requirements"

17-03 Stakeholder requirements

Detailed description of artefact "Stakeholder requirements"

17-03 Stakeholder requirements

  • Purpose/objectives defined
  • Includes issues/requirements from (contract) reviews
  • Identifies any:
    • time schedule/constraints
    • required feature and functional characteristics
    • necessary performance considerations/constraints
    • necessary internal/external interface considerations/constraints
    • required system characteristics/constraints
    • human engineering considerations/constraints
    • security considerations/constraints
    • environmental considerations/constraints
    • operational considerations/constraints
    • maintenance considerations/constraints
    • installation considerations/constraints
    • support considerations/constraints
    • design constraints
    • safety/reliability considerations/constraints
    • quality requirements/expectations

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).