P0-REQ-10-004

Return to Part 0 Requirements

Statement

The document set SHALL NOT allow implementation technologies to redefine conceptual architecture.

Source

Part 0, Section 10: Document Set Requirements.

Rationale

The Financial Systems Archetype document set separates architectural meaning from implementation choice. Conceptual architecture defines what the financial system means, what responsibilities it has, and how its major concepts relate. Implementation technologies provide mechanisms for realising those concepts, but they do not define the concepts themselves.

If implementation technologies are allowed to redefine conceptual architecture, the architecture becomes dependent on a particular tool, platform, messaging technology, data format, programming model, or deployment environment. This would weaken portability, reduce long-term governance, and make it harder to compare or evolve implementations without changing the underlying architectural meaning.

Applies To

This requirement applies to the organisation, authoring, review, maintenance, and interpretation of the Financial Systems Archetype document set.

It applies specifically to:

* conceptual architecture sections; * logical models; * implementation profiles; * deployment profiles; * technology mappings; * platform-specific artefacts; and * evidence or verification material that refers to implementation technologies.

Verification

Verification SHALL confirm that implementation technologies are treated as realisation mechanisms and not as sources of conceptual meaning.

Verification activities should include review checks confirming that:

* conceptual architecture sections do not depend on a specific implementation technology; * implementation profiles map logical elements to technology artefacts without redefining the logical or conceptual elements; * technology-specific terminology is not used as a substitute for conceptual definitions; * deployment choices do not alter the architectural meaning of the elements being deployed; * implementation constraints are identified as implementation constraints rather than conceptual rules; and * alternative implementation technologies could be introduced without rewriting the conceptual architecture.

Traceability

This requirement supports traceability from conceptual architecture to logical models and implementation profiles while preserving the direction of authority from concept to implementation.

Related requirement identifiers:

* P0-REQ-10-001 * P0-REQ-10-002 * P0-REQ-10-003 * P0-REQ-10-005

Related source section:

* 10. Document Set Requirements

Status

Draft