P2-REQ-16-7-009

Return to Requirements

Statement

Logical Interaction Patterns SHALL remain independent of DDS, REST, RPC, Protocol Buffers, message queues, event streams, file exchange, shared services, databases, logs, or deployment mechanisms.

Source

Part 2, Section 16.7: Logical Interaction Requirements.

Rationale

Logical Interaction Patterns describe architectural behaviour independently of the technologies used to realise that behaviour. Maintaining this separation allows multiple Implementation Profiles to realise the same interaction patterns while preserving architectural meaning, interoperability, governance, and traceability.

Applies To

This requirement applies to the Logical Interaction Model and all profiles that realise it.

It applies specifically to:

Logical Interaction Patterns;Domain Logical Profiles;Implementation Profiles;Deployment Profiles; andTechnology mappings.

Verification

Verification SHALL confirm that Logical Interaction Patterns remain independent of implementation technologies and deployment mechanisms.

Verification activities should include review checks confirming that:

interaction patterns are defined independently of implementation technologies;deployment mechanisms do not redefine Logical Interaction Patterns;Implementation Profiles preserve interaction semantics during technology mapping; andDomain Logical Profiles preserve inherited Logical Interaction Patterns.

Traceability

This requirement supports traceability between Logical Interaction Patterns and the implementation mechanisms that realise them while preserving platform independence.

Related requirement identifiers:

Related source section:

Status

Draft

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.