• slide1

    Enterprise Architecture 3.0 (EA3.0) - the third wave in Enterprise Architecture approaches

  • slider3

    A3 KAM - Triple A(Architectural, Actionable and  Augmented) Knowledge Assets Management

  • slider4

    ABODE™ business transformation methodology  founded on EA3.0

  • slider2

    Generalized Enterprise Function Framework  (GEFF)

Change Management

Problems and Solutions

In many cases it is not possible to deliver a good analysis of the changes to be made based on already developed components. Often, the solutions provided are container solutions solving just that problem that the requirements ask for. As the already developed components are already available in the metadata model, with the Enterprise Architecture approach it is possible to deliver overviews of all components “touched” by the changes to be made in which case good solutions that build on these components can be provided.

 

Tools to support Change Management

To support Change Management Enterprise Architects offers the following tools:

  • ICA/Impact of Change Analysis  
Impact of Change Analysis – detailed overview of all the changes to be made to components that already have been designed and developed in the Design Continuum
  • AAM/PSA Generation  
Generating the PSA based on the modeling the Product/Service Delivery and the Information Service Delivery
  • BCM/Business Case Development 
Setting up the Business Case based on the ICA and PSA

Advantages of the Enterprise Architects approach

  1. With the Impact of Change Analysis approach it is possible that, based on for example a single question of the change of an article of a law, all necessary changes to all components (lifectime event, business service, business process, business function, presentation services and windows, information, and data services, technical services, and business rulesets can be delivered
  2. When the complete set of new requirements for ICA is accepted the (initial) Project Start Architecture can be generated, including the components of the As-Is solution and (partially) the components of the To-Be solution
  3. Based on the agreed (initial) Project Start Architecture cost-benefit analysis etc. for developing the Business Case can generated
  4. The SAFe™ Core Values are safeguarded and improved as follows
    • 4.1. Alignment
    • 4.2. Built-in Quality
    • 4.3 Transparency
    • 4.4. Program Execution