dido:99_annexes:annex-d-requirements:part-01:p1-req-13-10-006: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-10-006: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-10-006:start [2026/07/11 12:57] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== P1-REQ-13-10-006 ======
  
 +[[dido:99_annexes:annex-d-requirements:part-01:start|Return to Part 1 Requirements]]
 +
 +===== Statement =====
 +
 +A later part that introduces a new term SHALL identify whether the term is conceptual, logical, implementation-specific, deployment-specific, or evidence-specific.
 +
 +===== Source =====
 +
 +Part 1, Section 13.10: Profile and Layering Requirements.
 +
 +===== Rationale =====
 +
 +New terms introduced in later parts need clear placement within the architecture layering model. Identifying a term as conceptual, logical, implementation-specific, deployment-specific, or evidence-specific prevents ambiguity about the term’s role and authority.
 +
 +This requirement supports controlled vocabulary growth and prevents later parts from introducing terms that blur architectural layers.
 +
 +===== Applies To =====
 +
 +This requirement applies to new terms introduced in later parts of the document set.
 +
 +It applies specifically to terms classified as:
 +
 +  * Conceptual
 +  * Logical
 +  * Implementation-specific
 +  * Deployment-specific
 +  * Evidence-specific
 +
 +===== Verification =====
 +
 +Verification SHALL confirm that each new term introduced in a later part identifies whether it is conceptual, logical, implementation-specific, deployment-specific, or evidence-specific.
 +
 +Verification activities include review checks confirming that:
 +
 +  * New terms identify their architectural layer
 +  * New terms do not conflict with existing conceptual definitions
 +  * New terms include appropriate traceability to related terms
 +  * New terms preserve separation among conceptual, logical, implementation, deployment, and evidence concerns
 +
 +===== Traceability =====
 +
 +Related source section:
 +
 +  * [[fxdemo:01-part:13-conceptual-requirements:13-10-profile-and-layering-requirements]]
 +
 +Related requirement identifiers:
 +
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-10-001:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-10-002:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-10-003:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-10-007:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-2-001:start]]
 +
 +===== Status =====
 +
 +Draft
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>