Embedding EAM into operation and monitoring - Managing operational changes

6 important questions on Embedding EAM into operation and monitoring - Managing operational changes

Why are even small changes relevant in EAM?

Because its side-effects and implications are often underestimated.

Why should operational changes be managed?

  • If the organisation doesn’t track tactical and operational changes systematically and consider their impact on architecture, it will deviate from the EA roadmap.
  • To avoid unforeseen side-effects 

How are operational changes to the enterprise architecture managed best?

Changes should be atomic, consistent, isolated and durable (ACID). An ITIL (IT infrastructure library) process can be used.
  • Higher grades + faster learning
  • Never study anything twice
  • 100% sure, 100% understanding
Discover Study Smart

What is important in the collect phase?

Systematically collect and record requests for change from different sources.

How to assess changes?



Assess changes to identify the 1-10% of all operational changes that are architecturally relevant. Criteria are: business critically, interface dependence, business continuity, security, external factors and compliance.
Check the impact on EA and all the side-effects of architecturally relevant changes.

What to do with the EA after planned changes?

You have to keep the EA consistent and up to date after implementing a change.

The question on the page originate from the summary of the following study material:

  • A unique study and practice tool
  • Never study anything twice again
  • Get the grades you hope for
  • 100% sure, 100% understanding
Remember faster, study better. Scientifically proven.
Trustpilot Logo