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-2-003: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-2-003:start [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== P1-REQ-13-2-003 ======
  
 +[[dido:99_annexes:annex-d-requirements:part-01:start|Return to Part 1 Requirements]]
 +
 +===== Statement =====
 +
 +The Conceptual Architecture SHALL NOT allow implementation technologies to redefine conceptual elements.
 +
 +===== Source =====
 +
 +Part 1, Section 13.2: Conceptual Separation Requirements.
 +
 +===== Rationale =====
 +
 +Implementation technologies realize architectural intent within a selected technical environment. They do not establish the conceptual meaning of the architecture. When implementation technology redefines a conceptual element, the conceptual model becomes dependent on a selected platform, tool, language, middleware, database, runtime, or deployment mechanism.
 +
 +This requirement protects the Conceptual Architecture from technology lock-in and preserves stable meaning across multiple logical models, implementation profiles, and deployment approaches.
 +
 +===== Applies To =====
 +
 +This requirement applies to all references to implementation technologies within the Conceptual Architecture.
 +
 +It applies specifically to technologies such as:
 +
 +  * Programming languages
 +  * Middleware
 +  * Databases
 +  * Runtime platforms
 +  * Container technologies
 +  * Network technologies
 +  * Development tools
 +  * Generated artifacts
 +
 +===== Verification =====
 +
 +Verification SHALL confirm that implementation technologies do not redefine conceptual elements.
 +
 +Verification activities include review checks confirming that:
 +
 +  * Conceptual elements remain technology-neutral
 +  * Technology examples appear only as examples, notes, or later implementation mappings
 +  * Implementation profiles map to conceptual elements without changing their meaning
 +  * Tool-specific or platform-specific terms do not replace conceptual terms
 +
 +===== Traceability =====
 +
 +Related source section:
 +
 +  * [[fxdemo:01-part:13-conceptual-requirements:13-2-conceptual-separation-requirements]]
 +
 +Related requirement identifiers:
 +
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-2-001:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-2-002:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-2-004:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-2-005:start]]
 +
 +===== Status =====
 +
 +Draft