P3-REQ-17-12-004

Return to Requirements

An Implementation Profile / PSM SHALL preserve traceability from implementation artefacts to the FX logical elements they realise.

Part 3, Section 17.12: Implementation Boundary Requirements.

Implementation artefacts derive their architectural meaning from the FX Demo Logical Profile. Preserving traceability between implementation artefacts and the logical elements they realize enables architectural review, impact analysis, governance, conformance assessment, and lifecycle management. This traceability ensures that implementation decisions remain demonstrably connected to the platform-independent logical architecture.

Maintaining this relationship supports multiple implementation technologies without altering the architectural meaning of the logical profile.

This requirement applies to all Implementation Profiles and Platform-Specific Models derived from the FX Demo Logical Profile.

It applies specifically to:

• implementation artefacts;
• logical profile elements;
• traceability relationships;
• architectural governance; and
• conformance assessment.

Verification SHALL confirm that implementation artefacts preserve traceability to the FX logical elements they realize.

Verification activities should include review checks confirming that:

• implementation artefacts identify their originating logical elements;
• traceability relationships are complete and consistent;
• architectural meaning is preserved throughout implementation; and
• implementation technologies do not disrupt traceability.

This requirement establishes implementation-to-logical traceability.

Related requirement identifiers:

• P3-REQ-17-12-002
• P3-REQ-17-12-003
• P3-REQ-17-12-006

Related source section:

• 17.12 Implementation Boundary Requirements

Draft