P4-REQ-21-15-014

Return to Requirements

Part 5 SHALL NOT redefine the Phase 0 implementation artifacts defined by Part 4.

Part 4, Section 21.15: Part 5 Handoff Requirements.

Part 5 deploys, tests, observes, operates, and evidences the Phase 0 implementation artifacts defined by Part 4. It does not become a second source of implementation-profile definitions.

Preventing Part 5 from redefining Part 4 artifacts preserves a clear authority boundary and ensures that implementation changes remain subject to Part 4 implementation governance.

This requirement applies to:

• implementation node mappings;
• DDS Topic mappings;
• IDL and generated type mappings;
• QoS profile mappings;
• Runtime Plane realizations;
• interaction realizations;
• repository and script models; and
• other Phase 0 implementation artifacts.

Verification SHALL confirm that Part 5 uses rather than redefines the Phase 0 implementation artifacts defined by Part 4.

Verification activities should include review checks confirming that:

• implementation definitions remain governed by Part 4;
• Part 5 deployment choices do not alter implementation mappings;
• Part 5 tests and evidence do not create replacement implementation definitions;
• implementation changes discovered during Part 5 activities return through Part 4 governance; and
• Part 5 records preserve the applicable Part 4 baseline identity.

This requirement preserves the authority boundary between Part 4 implementation definition and Part 5 deployment, testability, operation, observation, and evidence activities.

Related requirement identifiers:

• P4-REQ-21-15-001
• P4-REQ-21-15-013
• P4-REQ-21-13-005

Related source section:

• 21.15 Part 5 Handoff Requirements

Draft