P1-REQ-13-2-003

Return to Part 1 Requirements

Statement

The Conceptual Architecture SHALL NOT allow implementation technologies to redefine conceptual elements.

Source

Part 1, Section 13.2: Conceptual Separation Requirements.

Rationale

Implementation technologies realize architectural intent within a selected technical environment. They do not establish the conceptual meaning of the architecture. When implementation technology redefines a conceptual element, the conceptual model becomes dependent on a selected platform, tool, language, middleware, database, runtime, or deployment mechanism.

This requirement protects the Conceptual Architecture from technology lock-in and preserves stable meaning across multiple logical models, implementation profiles, and deployment approaches.

Applies To

This requirement applies to all references to implementation technologies within the Conceptual Architecture.

It applies specifically to technologies such as:

Programming languagesMiddlewareDatabasesRuntime platformsContainer technologiesNetwork technologiesDevelopment toolsGenerated artifacts

Verification

Verification SHALL confirm that implementation technologies do not redefine conceptual elements.

Verification activities include review checks confirming that:

Conceptual elements remain technology-neutralTechnology examples appear only as examples, notes, or later implementation mappingsImplementation profiles map to conceptual elements without changing their meaningTool-specific or platform-specific terms do not replace conceptual terms

Traceability

Related source section:

Related requirement identifiers:

Status

Draft