P1-REQ-13-2-005
Statement
The Conceptual Architecture SHALL NOT treat runtime identifiers as substitutes for conceptual elements.
Source
Part 1, Section 13.2: Conceptual Separation Requirements.
Rationale
Runtime identifiers support execution, addressing, routing, partitioning, discovery, correlation, and operational management. They do not define conceptual meaning. Treating a runtime identifier as a conceptual element collapses operational representation into conceptual architecture.
This requirement preserves the distinction between governed conceptual elements and runtime-specific identifiers such as domain identifiers, topic names, endpoint names, service identifiers, container names, process identifiers, and generated type names.
Applies To
This requirement applies to all references to runtime identifiers within the Conceptual Architecture.
It applies specifically to identifiers such as:
-
DDS Domain IDs
-
Topic names
-
Endpoint names
-
Node instance identifiers
-
Container names
-
Process identifiers
-
Generated type names
-
Environment-specific runtime labels
Verification
Verification, process identifiers, and generated type names.
Applies To
This requirement applies to all references to runtime identifiers within the Conceptual Architecture.
It applies specifically to identifiers such as:
-
DDS Domain IDs
-
Topic names
-
Endpoint names
-
SHALL confirm that runtime identifiers do not substitute for conceptual elements.
Verification activities include review checks confirming that:
-
Runtime identifiers support implementation or deployment concerns only
-
Conceptual elements retain stable names and definitions independent of runtime identifiers
-
DDS Domain IDs and other runtime identifiers do not appear as conceptual classifications
-
Runtime labels do not replace governed architectural terms
Traceability
Related source section:
Related requirement identifiers:
Status
Draft