logo

Artefact overview of artefact "System requirements allocation"

spem diagram of an artefact overview: System requirements allocation

Artefact break down of artefact "System requirements allocation"

spem diagram of the artefact breakdown: System requirements allocation

Artefact dependency of artefact "System requirements allocation"

spem diagram of artefact dependency: System requirements allocation

Brief description of artefact "System requirements allocation"

a detailed linkage between design elements and the corresponding requirements.

Detailed description of artefact "System requirements allocation"

13-22 Traceability record

  • All requirements (customer and internal) are to be traced
  • Identifies a mapping of requirement to life cycle work products
  • Provides the linkage of requirements to work product decomposition (i.e., requirement  design  code  test  deliverables, etc.)
  • Provides forward and backwards mapping of requirements to associated work products throughout all phases of the life cycle

NOTE: this may be included as a function of another defined work product (example: A CASE tool for design decomposition may have a mapping ability as part of its features)

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