logo

Artefact overview of artefact "System architectural design"

spem diagram of an artefact overview: System architectural design

Artefact break down of artefact "System architectural design"

spem diagram of the artefact breakdown: System architectural design

Artefact dependency of artefact "System architectural design"

spem diagram of artefact dependency: System architectural design

Brief description of artefact "System architectural design"

04-06 System architectural design

Detailed description of artefact "System architectural design"

04-06 System architectural design

  • Provides an overview of all system design
  • Describes the interrelationship between system elements
  • Describes the relationship between the system elements and the software
  • Specifies the design for each required system element, consideration is given to aspects such as:
    • memory/capacity requirements
    • hardware interface requirements
    • user interface requirements
    • external system interface requirements

04-00 Design

  • Describes the overall product/system structure
  • Identifies the required product/system elements
  • Identifies the relationship between the elements
  • Consideration is given to:
    • any required performance characteristics
    • any required interfaces
    • any required security characteristics

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