This site uses cookies to improve your experience and analyze visits.
Stage Seven of the national methodology: a continuous stage that runs in parallel with every phase of the development cycle, carried out through three steps that cover approving requirements, monitoring their status, and assessing the impact of change on them.
Once the incoming requirements pass the "Defining the Scope of the EA Development Cycle" stage, the Chief Enterprise Architect documents them across the eight fields, then assesses the impact of each new requirement on the approved list and re-prioritises based on the dependencies between requirements, the entity strategic priorities, compliance with national policies and regulations, time constraints, and the availability of capabilities and staff.
The EA work team tracks each requirement from inception to closure and updates its state after every phase of the development cycle, when a requirement is cancelled for technical or procedural reasons, when the relevant stakeholder changes it, during initiative execution under the EA governance procedures, or when a newly approved requirement affects priority. The team contacts stakeholders to explain the reason behind any update.
The size of impact on the cycle scope is measured: no scope change for minor impact, rescope and reschedule for moderate impact, or stopping the cycle and re-running "Defining the Scope of the EA Development Cycle" for substantial change. The same logic applies to digital initiatives and projects through the EA governance procedures.
| Inputs | Outputs |
|---|---|
| Enterprise Architecture Development Cycle Charter | Updated Enterprise Architecture Requirements |
| Incoming Enterprise Architecture Requirements | Status of Enterprise Architecture Requirements |
| Outputs of the EA Governance Procedures | Assessment of the Impact of Changes in EA Requirements |
| Enterprise Architecture Requirements Repository | Requirements list linked to the future state, the domain principles, and compliance status |
