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] – ↷ Page moved from dido:99_annexes:annex-c-requirements:part-01:p1-req-13-3-004:start to dido:99_annexes:annex-d-requirements:part-01:p1-req-13-3-004:start nick_didodido: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 ====== ====== P1-REQ-13-3-004 ======
  
-[[dido:99_annexes:annex-c-requirements:part-01:start|Return to Part 1 Requirements]]+[[dido:99_annexes:annex-d-requirements:part-01:start|Return to Part 1 Requirements]]
  
 ===== Statement ===== ===== 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 artefacts, and communication boundaries.+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 ===== ===== Source =====
Line 13: Line 13:
 ===== Rationale ===== ===== Rationale =====
  
-Classification Paths express governed conceptual scope. Runtime identifiers, deployment identifiers, repository paths, implementation artefacts, and communication boundaries serve implementation, operational, or organisational purposes.+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. Distinguishing Classification Paths from those identifiers prevents implementation and deployment concerns from redefining conceptual classification.
Line 26: Line 26:
   * Deployment identifiers   * Deployment identifiers
   * Repository paths   * Repository paths
-  * Implementation artefacts+  * Implementation artifacts
   * Communication boundaries   * Communication boundaries
  
 ===== Verification ===== ===== Verification =====
  
-Verification SHALL confirm that the Conceptual Architecture distinguishes Classification Paths from runtime identifiers, deployment identifiers, repository paths, implementation artefacts, and communication boundaries.+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: Verification activities include review checks confirming that:
Line 49: Line 49:
 Related requirement identifiers: Related requirement identifiers:
  
-  * [[dido:99_annexes:annex-c-requirements:part-01:p1-req-13-3-001:start]] +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-3-001:start]] 
-  * [[dido:99_annexes:annex-c-requirements:part-01:p1-req-13-3-002:start]] +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-3-002:start]] 
-  * [[dido:99_annexes:annex-c-requirements:part-01:p1-req-13-3-005:start]]+  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-3-005:start]]
  
 ===== Status ===== ===== Status =====
  
 Draft Draft
  • dido/99_annexes/annex-d-requirements/part-01/p1-req-13-3-004/start.1783799862.txt.gz
  • Last modified: 2026/07/11 12:57
  • by nick_dido