dido:99_annexes:annex-d-requirements:part-01:p1-req-13-10-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-10-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-10-004:start [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== P1-REQ-13-10-004 ======
  
 +[[dido:99_annexes:annex-d-requirements:part-01:start|Return to Part 1 Requirements]]
 +
 +===== Statement =====
 +
 +A later part SHALL NOT use a technology selection to redefine a conceptual element.
 +
 +===== Source =====
 +
 +Part 1, Section 13.10: Profile and Layering Requirements.
 +
 +===== Rationale =====
 +
 +Technology selections belong to implementation or deployment concerns. A selected technology may realize, support, or constrain an implementation profile, but it does not define conceptual architecture meaning.
 +
 +This requirement prevents technology choices from altering conceptual elements inherited from Part 1. It also preserves portability across alternative implementation technologies.
 +
 +===== Applies To =====
 +
 +This requirement applies to later parts that introduce or use technology selections.
 +
 +It applies specifically to technology selections involving:
 +
 +  * Middleware
 +  * Programming languages
 +  * Data modeling technologies
 +  * Runtime platforms
 +  * Container technologies
 +  * Deployment tools
 +  * Generated artifacts
 +  * Vendor products
 +
 +===== Verification =====
 +
 +Verification SHALL confirm that later parts do not use technology selections to redefine conceptual elements.
 +
 +Verification activities include review checks confirming that:
 +
 +  * Technology selections appear as implementation or deployment concerns
 +  * Conceptual elements retain Part 1 definitions
 +  * Implementation profiles map technologies to inherited conceptual or logical elements
 +  * Technology-specific terminology does not replace conceptual terminology
 +
 +===== 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-002:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-10-006:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-10-008:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-2-003:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-9-005:start]]
 +
 +===== Status =====
 +
 +Draft
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>