dido:99_annexes:annex-d-requirements:part-01:p1-req-13-6-007: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-6-007: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-6-007:start [2026/07/11 12:57] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== P1-REQ-13-6-007 ======
  
 +[[dido:99_annexes:annex-d-requirements:part-01:start|Return to Part 1 Requirements]]
 +
 +===== Statement =====
 +
 +Cross-concern relationships SHALL preserve the distinction between the concerns involved.
 +
 +===== Source =====
 +
 +Part 1, Section 13.6: Separation of Concerns Requirements.
 +
 +===== Rationale =====
 +
 +Structured-information processing concerns interact across the architecture. Data relates to structure, structure relates to semantics, semantics relates to interpretation, governance relates to authority, and traceability relates to evidence. These relationships need to preserve the distinction among the concerns involved.
 +
 +This requirement prevents cross-concern relationships from collapsing separate architectural concerns into a single undifferentiated concept.
 +
 +===== Applies To =====
 +
 +This requirement applies to cross-concern relationships described within the Conceptual Architecture.
 +
 +It applies specifically to relationships involving:
 +
 +  * Data
 +  * Structure
 +  * Semantics
 +  * Interpretation
 +  * Governance and Authority
 +  * Traceability
 +  * Evidence
 +
 +===== Verification =====
 +
 +Verification SHALL confirm that cross-concern relationships preserve the distinction between the concerns involved.
 +
 +Verification activities include review checks confirming that:
 +
 +  * Cross-concern relationships identify the concerns involved
 +  * Cross-concern relationships preserve each concern’s distinct purpose
 +  * Cross-concern relationships do not redefine a concern
 +  * Cross-concern relationships support traceability where required
 +
 +===== Traceability =====
 +
 +Related source section:
 +
 +  * [[fxdemo:01-part:13-conceptual-requirements:13-6-separation-of-concerns-requirements]]
 +
 +Related requirement identifiers:
 +
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-6-001:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-6-008:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-6-012:start]]
 +
 +===== Status =====
 +
 +Draft
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>