Objectives

1. Ensure architecture lifecycle is maintained
2. Ensure arch governance is executed
3. Ensure arch capability meets current requirements

Approach

Drivers for change

• Can be top-down or bottom-up
• Governance is responsible for handling RFCs Requests for Change
• New tech
• Business
  • innovations
  • strategic change
• lessons learned

Enterprise Architecture management process

• categorize changes
  • simplification change
  • incremental change
  • re-architecting change
• how to determine change category
  • register all events impacting the architecture
  • resource allocation
  • change impacts on specific architecture development phases

Guidelines for maintenance versus architecture redesign

• Changes impacting 2 or more stakeholders often require re-architecting.
  • Ex: Changes significant for the business strategy may necessitate re-architecting
• Changes impacting 1 stakeholder are candidates for change management
  • Ex: Infrastructure-level changes may not affect the architecture above the physical layer, making them candidates for change management techniques.
• Refreshment Cycle: Re-architecting may be require when arch must realign with strategy
  • when refreshment cycle is needed, a new Request for Architecture Work must be issued