dido:99_annexes:annex-d-requirements:part-01:p1-req-13-10-002: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-002: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-002:start [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== P1-REQ-13-10-002 ======
  
 +[[dido:99_annexes:annex-d-requirements:part-01:start|Return to Part 1 Requirements]]
 +
 +===== Statement =====
 +
 +An Implementation Profile / [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_specific_model|PSM]] SHALL preserve the conceptual definitions inherited from this part.
 +
 +===== Source =====
 +
 +Part 1, Section 13.10: Profile and Layering Requirements.
 +
 +===== Rationale =====
 +
 +An Implementation Profile / PSM maps logical and conceptual meaning to selected technologies, platforms, tools, languages, middleware, and implementation artifacts. It inherits conceptual definitions from Part 1 and realizes them through implementation-specific choices.
 +
 +This requirement prevents implementation-specific mechanisms from changing inherited conceptual meaning. It preserves the separation between conceptual architecture and platform-specific realization.
 +
 +===== Applies To =====
 +
 +This requirement applies to Implementation Profiles and PSM artifacts that inherit conceptual definitions from Part 1.
 +
 +It applies specifically to:
 +
 +  * Implementation Profile content
 +  * PSM content
 +  * Implementation mappings
 +  * Platform-specific artifacts
 +  * Inherited conceptual definitions
 +
 +===== Verification =====
 +
 +Verification SHALL confirm that each Implementation Profile / PSM preserves the conceptual definitions inherited from Part 1.
 +
 +Verification activities include review checks confirming that:
 +
 +  * Implementation artifacts trace to logical or conceptual elements
 +  * Implementation mappings preserve inherited conceptual meaning
 +  * Platform-specific mechanisms do not redefine conceptual elements
 +  * Implementation-specific terms remain distinct from conceptual terms
 +
 +===== 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-004: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-9-005:start]]
 +
 +===== Status =====
 +
 +Draft
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>