P2-REQ-16-7-009

Return to Requirements

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.

Part 2, Section 16.7: Logical Interaction Requirements.

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.

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; and
• Technology mappings.

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; and
• Domain Logical Profiles preserve inherited Logical Interaction Patterns.

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

Related requirement identifiers:

• P2-REQ-16-4-008
• P2-REQ-16-6-007
• p2-req-16-10-007

Related source section:

• 16.7 Logical Interaction Requirements

Draft