dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-007:start

This is an old revision of the document!


P1-REQ-13-5-007

The Conceptual Architecture SHALL distinguish Runtime Planes from implementation mechanisms.

Part 1, Section 13.5: Runtime Plane Requirements.

Runtime Planes classify runtime communication and behaviour by architectural purpose. Implementation mechanisms realise selected aspects of those planes in a particular technology environment.

Distinguishing Runtime Planes from implementation mechanisms prevents DDS topics, middleware constructs, APIs, services, scripts, generated types, containers, or other mechanisms from redefining the conceptual plane.

This requirement applies to all Runtime Plane definitions and references within the Conceptual Architecture.

It applies specifically to distinctions between Runtime Planes and:

  • Middleware mechanisms
  • DDS mechanisms
  • APIs
  • Services
  • Scripts
  • Generated types
  • Containers
  • Deployment tooling

Verification SHALL confirm that the Conceptual Architecture distinguishes Runtime Planes from implementation mechanisms.

Verification activities include review checks confirming that:

  • Runtime Planes classify architectural purpose
  • Implementation mechanisms realise Runtime Planes without redefining them
  • Technology examples do not become conceptual plane definitions
  • Later profiles preserve the conceptual meaning of each Runtime Plane

Related source section:

Related requirement identifiers:

Draft


© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

  • dido/99_annexes/annex-d-requirements/part-01/p1-req-13-5-007/start.1783799863.txt.gz
  • Last modified: 2026/07/11 12:57
  • by nick_dido