Product · Change management (CCB)
Structured change packages with clear finalization
A change package (ChangeManagement) contains name, description, motivation, status, and serialized changes in changesJson. On finalization the changes apply against the database in a controlled transaction.
Overview
UI status flow: available for review (0) → in review (1) → finalized (2, history).
Finalize (POST .../finalize) requires CHANGE_MANAGEMENT_CHANGE, rejects if already finalized or changesJson missing.
Apply service interprets changesJson v1 and creates/updates/links/soft-deletes requirements per the diff.
Requirement areas are not changed in this flow in the current implementation.
Consequence analysis and history
Orphan detection
The analysis tab lists system requirements that would become unlinked to any stakeholder requirement if the package were applied. A concrete, automated part of 'what happens if we do this?', not a full multi-domain impact simulator.
History with accountability
Finalized packages show who finalized, when, and the free-text decision description, support for audit conversations and internal transparency.