A structured approach to managing EA requirements through a central register and unified steps: adopt, track status, and study impact of change until closure.
Document and adopt incoming requirements; assess the impact of each new requirement on the approved list and reprioritize based on dependencies, strategic priorities, and national compliance.
Track requirements from creation to closure. Update status after each cycle phase, when a stakeholder changes a requirement, or when a new requirement affects priority.
Assess the size of impact on cycle scope: minor impact (no change), moderate impact (rescope and reschedule), or major impact (stop the cycle and restart scope definition).
| Inputs | Outputs |
|---|---|
| EA development cycle charter | Updated EA requirements |
| Incoming EA requirements | EA requirements status |
| EA governance procedure outputs | Impact of change study |
| EA requirements repository | Requirements list linked to target state, principles, and compliance status |
