dido:99_annexes:annex-d-requirements:part-02:p2-req-16-2-005

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-02:p2-req-16-2-005 [2026/07/11 12:57] – removed - external edit (Unknown date) 127.0.0.1dido:99_annexes:annex-d-requirements:part-02:p2-req-16-2-005 [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== P2-REQ-16-2-005 ======
  
 +[[dido:99_annexes:annex-d-requirements:part-02:start| Return to Requirements]]
 +
 +===== Statement =====
 +
 +The Logical Architecture / PIM SHALL NOT prescribe execution granularity, deployment granularity, runtime packaging, deployment topology, communication technology, data serialisation format, programming language, middleware product, orchestration platform, or runtime infrastructure.
 +
 +===== Source =====
 +
 +Part 2, Section 16.2: Distributed Node-Based Architecture Requirements.
 +
 +===== Rationale =====
 +
 +The purpose of the Logical Architecture / PIM is to define platform-independent logical structure rather than implementation choices. Preserving technology independence allows multiple Implementation Profiles to realize the same Logical Architecture while maintaining common architectural meaning.
 +
 +===== Applies To =====
 +
 +This requirement applies to the definition, maintenance, review, interpretation, and implementation mapping of the Logical Architecture / PIM.
 +
 +It applies specifically to:
 +
 +  * Logical architectural definitions;
 +  * Domain Logical Profiles;
 +  * Implementation Profiles;
 +  * Deployment Profiles; and
 +  * Technology mappings.
 +
 +===== Verification =====
 +
 +Verification SHALL confirm that the Logical Architecture does not prescribe implementation or deployment technologies.
 +
 +Verification activities should include review checks confirming that:
 +
 +  * no execution mechanism is mandated;
 +  * no deployment topology is required;
 +  * no communication technology is prescribed;
 +  * no programming language or middleware product is required; and
 +  * implementation choices remain deferred to Implementation Profiles.
 +
 +===== Traceability =====
 +
 +This requirement supports traceability from the platform-independent Logical Architecture to multiple technology-specific Implementation Profiles.
 +
 +Related requirement identifiers:
 +
 +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-2-001]]
 +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-2-002]]
 +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-2-003]]
 +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-2-004]]
 +
 +Related source section:
 +
 +  * [[fxdemo:02-part:16-logical-requirements:16-2-distributed-node-based-architecture-requirements:start]]
 +
 +===== Status =====
 +
 +Draft
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>