The FX Transaction and Contract Lifecycle Model SHALL NOT prescribe a state-machine implementation, workflow engine, database status field, event store, rules engine, orchestration mechanism, API, DDS topic, REST resource, or runtime persistence mechanism.
Part 3, Section 17.8: FX Lifecycle Requirements.
The FX Transaction and Contract Lifecycle Model is a platform-independent architectural model that defines logical lifecycle behaviour rather than implementation technology. Prescribing a specific state-machine implementation, workflow engine, database representation, messaging technology, orchestration mechanism, API, persistence approach, or other runtime technology would unnecessarily constrain Implementation Profiles and reduce portability.
Maintaining this separation preserves architectural independence, supports multiple implementation strategies, and ensures that equivalent logical lifecycle behaviour can be realized across different technology stacks without changing the architectural model.
This requirement applies to the FX Transaction and Contract Lifecycle Model and all derived Implementation Profiles.
It applies specifically to:
Verification SHALL confirm that the FX Transaction and Contract Lifecycle Model does not prescribe implementation-specific lifecycle technologies.
Verification activities should include review checks confirming that:
This requirement preserves the separation between logical lifecycle architecture and implementation technologies established throughout the FX Demo Logical Profile.
Related requirement identifiers:
Related source section:
Draft
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.