dido:99_annexes:annex-d-requirements:part-01:p1-req-13-3-004:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
dido:99_annexes:annex-d-requirements:part-01:p1-req-13-3-004:start [2026/07/11 12:57] – removed - external edit (Unknown date) 127.0.0.1dido:99_annexes:annex-d-requirements:part-01:p1-req-13-3-004:start [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== P1-REQ-13-3-004 ======
  
 +[[dido:99_annexes:annex-d-requirements:part-01:start|Return to Part 1 Requirements]]
 +
 +===== Statement =====
 +
 +The Conceptual Architecture SHALL distinguish [[dido:99_annexes:annex-b-terms-and-definitions:c:classification_path|Classification Paths]] from runtime identifiers, deployment identifiers, repository paths, implementation artifacts, and communication boundaries.
 +
 +===== Source =====
 +
 +Part 1, Section 13.3: Classification Requirements.
 +
 +===== Rationale =====
 +
 +Classification Paths express governed conceptual scope. Runtime identifiers, deployment identifiers, repository paths, implementation artifacts, and communication boundaries serve implementation, operational, or organizational purposes.
 +
 +Distinguishing Classification Paths from those identifiers prevents implementation and deployment concerns from redefining conceptual classification.
 +
 +===== Applies To =====
 +
 +This requirement applies to all references to Classification Paths within the Conceptual Architecture.
 +
 +It applies specifically to distinctions between Classification Paths and:
 +
 +  * Runtime identifiers
 +  * Deployment identifiers
 +  * Repository paths
 +  * Implementation artifacts
 +  * Communication boundaries
 +
 +===== Verification =====
 +
 +Verification SHALL confirm that the Conceptual Architecture distinguishes Classification Paths from runtime identifiers, deployment identifiers, repository paths, implementation artifacts, and communication boundaries.
 +
 +Verification activities include review checks confirming that:
 +
 +  * Classification Paths identify conceptual classification scope
 +  * Runtime identifiers do not replace Classification Paths
 +  * Deployment identifiers do not replace Classification Paths
 +  * Repository paths do not replace Classification Paths
 +  * Communication boundaries do not replace Classification Paths
 +
 +===== Traceability =====
 +
 +Related source section:
 +
 +  * [[fxdemo:01-part:13-conceptual-requirements:13-3-classification-requirements]]
 +
 +Related requirement identifiers:
 +
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-3-001:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-3-002:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-3-005:start]]
 +
 +===== Status =====
 +
 +Draft