• slide1

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

  • slider2

    Generalized Enterprise Function Framework  (GEFF)

  • slider3

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

  • slider4

    ABODE™ business transformation methodology  founded on EA3.0

User Interaction Design

The User Interaction design starts with defining the modus operandi: the EPIC and user stories that Product Owners, Super Users, etc.

 

Problems and Solutions

In the contemporary approach Product Owners, etc. are focused on the delivery of one Product type. This more than once leads to “reinventing the wheel” and Transition Delivery is often confronted with more or less duplication of already designed and developed applications and information systems.

In the case of the Enterprise Architects’ approach also the Service Delivery approach is relevant: which Actor based on what Life Event approaches the organization to retrieve Products and why, how the delivery is supported by Business Services that form rational steps in the delivery, including Contracts or Service Level Agreements, and which Business Processes support these delivery. As a Business Processes is a chain of actionable Knowledge Functions, often already “enriched” Knowledge Functions are also taken into account.

In this way, before starting the design of EPICs, etc. patterns of Service Delivery can be recognized resulting in generalizing the Product Delivery Services, and other components.

 

Tools to support User Interaction Design

To support the User Interaction Design Enterprise Architects offers the following tools:

  • AAM/Service Delivery Modeling   
 Modeling the Service Delivery (Actor to Knowledge Function) incl. attention for Value Creation improvement
  • AUM/EPIC Modeling    
 Modeling the EPIC based on the Service Delivery
  • AUM/User Story Design 
 Designing the different User Stories per EPIC and Knowledge Function
  • AUM/Presentation Design
 Designing the different User Interactions and Windows
  • AUM/Presentation Object Modeling  
 Designing and Defining the Presentation Object per window for the generation of Presentation Services
  • AUM/Presentation DME 
 Directly Executing/Testing the User Interaction

Advantages of the Enterprise Architects approach

  1. With the Enterprise Architects approach duplication of solutions is brought to the minimum
  2. The design and definition of the User Interaction is a logical process that starts with the Service Delivery
  3. Value Creation is taken into account from the beginning of the Service Delivery: supporting the Life Event
  4. The User Interaction is realized by generating the Presentation Services based on the Business to Presentation Data Mapping
  5. Testing of the Presentation, User Interaction and User Stories is embedded in the design process
  6. The SAFe™ Core Values are safeguarded and improved as follows
    • Alignment
    • Built-in Quality
    • Program Execution