P1-REQ-13-6-007

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:

DataStructureSemanticsInterpretationGovernance and AuthorityTraceabilityEvidence

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 involvedCross-concern relationships preserve each concern’s distinct purposeCross-concern relationships do not redefine a concernCross-concern relationships support traceability where required

Traceability

Related source section:

Related requirement identifiers:

Status

Draft

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