4.6 Relationship to Later Development Phases

Go To Phase 0 Implementation Profile Overview

Later development phases may define additional implementation profiles.

A later phase may broaden the implementation scope, add FX logical Nodes, add communication mappings, add information structures, replace or refine DDS Topic mappings, revise IDL structures, change generated-type approaches, introduce additional language bindings, adopt new Quality of Service (QoS) profiles, strengthen logging and exception handling, or change repository and build conventions.

A later phase may also introduce implementation maturity that Phase 0 deliberately excludes. Examples include production deployment packaging, operational hardening, extended security controls, expanded evidence capture, multi-jurisdiction deployment support, additional policy enforcement mechanisms, and stronger replay or reconstruction capabilities.

A later Phase 2 implementation profile may introduce a Policy / Governance Plane and Release Plane implementation that is broader than the Phase 0 policy and release demonstration. Such a profile may add distributed Policy Enforcement Point capabilities, replicated Policy Decision Point capabilities, Policy Administration Point capabilities, Policy Information Point capabilities, local policy caches, metadata or aggregate view builders, release gateway capabilities, recipient-specific release topics or equivalent exchanges, release obligations, and release evidence. Those additions belong to the later phase profile. They do not become Phase 0 implementation requirements unless this Phase 0 profile is explicitly revised.

Each later implementation profile preserves traceability to the applicable logical and conceptual sources. Later profiles do not use technology changes to redefine the FX logical architecture. They record how the later phase realizes, extends, or replaces the implementation baseline established by Phase 0.