dido:99_annexes:annex-d-requirements:part-03:p3-req-17-9-010

P3-REQ-17-9-010

FX logical interaction patterns SHALL remain independent of DDS, REST, RPC, Protocol Buffers, message queues, event streams, file exchange, shared services, databases, logs, deployment mechanisms, runtime scripts, and evidence-capture tools.

Part 3, Section 17.9: FX Logical Interaction Requirements.

FX logical interaction patterns define architectural behaviour independently of the technologies used to implement them. Constraining the logical architecture to specific communication protocols, messaging technologies, persistence mechanisms, deployment environments, or evidence-capture tools would reduce portability and unnecessarily couple the architecture to particular implementation choices.

Maintaining implementation independence preserves the platform-independent nature of the FX Demo Logical Profile and enables multiple Implementation Profiles to realize identical logical interaction patterns using different communication technologies, deployment architectures, runtime environments, and operational tooling while preserving the same architectural meaning.

This requirement applies to every FX logical interaction pattern defined by the FX Demo Logical Profile.

It applies specifically to:

  • logical interaction architecture;
  • platform-independent modeling;
  • implementation conformance;
  • architectural governance; and
  • derived Implementation Profiles.

Verification SHALL confirm that FX logical interaction patterns remain independent of implementation-specific technologies and runtime mechanisms.

Verification activities should include review checks confirming that:

  • logical interaction patterns are defined independently of implementation technologies;
  • communication protocols and runtime technologies are not prescribed;
  • architectural meaning is preserved independently of implementation choices; and
  • multiple implementation approaches remain possible without altering the logical architecture.

This requirement preserves the separation between logical interaction architecture and implementation-specific communication, deployment, persistence, and operational technologies established throughout the FX Demo Logical Profile.

Related requirement identifiers:

Related source section:

Draft


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

  • dido/99_annexes/annex-d-requirements/part-03/p3-req-17-9-010.txt
  • Last modified: 2026/07/21 16:02
  • by owen