P3-REQ-17-12-005

Return to Requirements

An Implementation Profile / PSM SHALL NOT use a technology selection to redefine an FX logical Node, FX logical Node Role, FX logical Communication Endpoint, FX logical information structure, FX Runtime Plane, FX logical interaction pattern, FX logical governance relationship, or FX logical traceability relationship.

Part 3, Section 17.12: Implementation Boundary Requirements.

Technology selections determine how the logical architecture is implemented, not what the logical architecture means. Allowing implementation technologies to redefine logical Nodes, Node Roles, Communication Endpoints, information structures, Runtime Planes, interaction patterns, governance relationships, or traceability relationships would compromise platform independence and prevent multiple implementations from realizing the same logical architecture consistently.

Preserving this boundary maintains architectural integrity while permitting different implementation technologies to realize equivalent logical behaviour.

This requirement applies to every Implementation Profile and Platform-Specific Model derived from the FX Demo Logical Profile.

It applies specifically to:

• technology selection;
• logical Nodes;
• logical Node Roles;
• Communication Endpoints;
• logical information structures;
• Runtime Planes;
• logical interaction patterns;
• governance relationships; and
• traceability relationships.

Verification SHALL confirm that technology selections do not redefine FX logical architecture.

Verification activities should include review checks confirming that:

• implementation technologies realize rather than redefine logical elements;
• architectural meaning remains unchanged;
• logical relationships remain intact; and
• platform independence is preserved.

This requirement preserves the architectural boundary between logical architecture and implementation technology.

Related requirement identifiers:

• P3-REQ-17-12-001
• P3-REQ-17-12-002
• P3-REQ-17-12-003
• P3-REQ-17-12-004
• P3-REQ-17-12-007

Related source section:

• 17.12 Implementation Boundary Requirements

Draft