• slider4

    ABODE™ business transformation methodology  founded on EA3.0

  • slider2

    Generalized Enterprise Function Framework  (GEFF)

  • slider3

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

  • slide1

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

Transition Management

The financial and time planning are solved in Change Management. Here the decision processes between Information Managers and Product Owners, and  Architects is discussed besides how the acceptance of the delivered products.

 

Problems and Solutions

In most cases the complete set requirements and the Principles, Requirements, design Objectives, Standards & Agreements, or PROSA, is not taken into account. With the Enterprise Architects approach

  • Information Managers, in cooperation with Product Owners and Architects, update the requirements and redefine the Value Creation of Business Functions, select the relevant PROSA, generate the PSA – if not already available – and complete the whole set of requirements
  • Process Models are designed based on Value Creation requirements, PROSA and PSA; when necessary the set of requirements will be adapted or extended
  • Within Transition Delivery the solution is further developed so results can be Functionally Tested by Information Management

Often however, the set of requirements at the beginning of projects or specifications is not complete. Because of the capability to change objects, services, business rulesets, business functions, and business process in a very short time (see Transition Delivery), and then retest them (see Functional Testing) within the Enterprise Architects solution it is possible to define, adapt, and extend the requirements and redesign the models, and regenerate the services instantly.

 

Tools to support Transition Management

To support Transition Management Enterprise Architects offers the following tools:

  • APR/PROSA Modeling 
Defining the details of Principles, Requirements, design Objectives, Standards & Agreements
  • ARS/Requirement Specification 
Examining, Defining, and Extending Requirements for Requirement Management
  • DME/Functional Testing
Direct Model Execution on Business RuleSets, Services, Business Functions, and Business Processes
  • ARS/Requirement Specification
Defining, Adapting, and Extending Requirements for Functional Testing and Transition Delivery

Advantages of the Enterprise Architects approach

  1. Based on requirement management solutions before designing (APR/PROSA Modeling and ARS/Requirement Specification) and the possibility to instantly test the requirements after design (DME/Functional Testing) the results – and probable misinterpretations – become clear at a very early stage of the Change and Transition Delivery processes
  2. Based on requirement management solutions after testing the requirements, any misinterpretations become clear and can be defined, adapted and extended and changing the components (see Transition Delivery) can be instantly performed and tested
  3. The SAFe™ Core Values are safeguarded and improved as follows
    1. a. Alignment
    2. b. Built-in Quality
    3. c. Transparency
    4. d. Program Execution