P3-REQ-17-12-003

Return to Requirements

An Implementation Profile / PSM SHALL map FX logical elements to selected implementation artefacts without redefining them.

Part 3, Section 17.12: Implementation Boundary Requirements.

The purpose of an Implementation Profile or Platform-Specific Model is to realize the logical architecture using implementation-specific technologies. This realization is achieved by mapping logical elements to implementation artefacts rather than redefining the architecture itself. Maintaining this distinction preserves architectural intent while allowing flexibility in technology selection, deployment strategies, and implementation techniques.

This separation ensures that multiple implementations can realize the same logical architecture while remaining conformant to the FX Demo Logical Profile.

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

It applies specifically to:

• logical Nodes;
• logical Communication Endpoints;
• logical information structures;
• Runtime Planes;
• implementation artefacts; and
• Platform-Specific Models.

Verification SHALL confirm that implementation artefacts map FX logical elements without redefining them.

Verification activities should include review checks confirming that:

• mappings exist between logical elements and implementation artefacts;
• logical definitions remain unchanged;
• implementation artefacts realize rather than replace the logical architecture; and
• technology selections preserve architectural meaning.

This requirement establishes the mapping relationship between the logical architecture and implementation artefacts.

Related requirement identifiers:

• P3-REQ-17-12-002
• P3-REQ-17-12-004
• P3-REQ-17-12-005

Related source section:

• 17.12 Implementation Boundary Requirements

Draft