• 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

  • slider2

    Generalized Enterprise Function Framework  (GEFF)

  • slider4

    ABODE™ business transformation methodology  founded on EA3.0

Business Platform as a Service

The ABODE tools are all part of what Enterprise Architects calls the BPaaS – Business Platform as a Service. Instead of only being able to develop apps and applications, the BPaaS offers a complete platform for transition for Transition Delivery (Business, Information and IT Delivery). The BPaaS solution consists of the following capabilities, which of course can be extended based on the customer’s wishes:

  1. Strategy Modeling
  2. Product Lifecycle Management
  3. Information Management
  4. Information Planning
  5. Enterprise Architecture
  6. Transition Delivery
  7. Functional Testing
  8. Information Lifecycle Management

Of course it is not necessary to develop and use all these Capabilities. If only the Transition Delivery should be improved it is possible that parts of the Product Lifecycle Management, the Enterprise Architecture and the Transition Delivery are developed further. Also, not everything should be started at once: starting a pilot based on a partial solution to proof the concept is generally the best approach.

 

The Capabilities consist of one or more sub-capabilities and each capability can consist of the following components as given in the (Archimate) diagram:

  • Products
  • Business Services
  • Business Processes
  • Business Functions

 

Also given in the diagram and explained in more detail in Strategy Modeling are:

  • Strategic components like
    • Goal
    • Outcome
    • Constraint
    • Requirement
    • Principle
  • Business components like
    • Business Actor
    • Cours of Action
  • Application components like
    • Application Service
    • Application Function
    • Application Component

 

The Strategy-to-Capability approach as described in the Strategy to Capability white papers describes how (strategic) goals can be used to define the necessary Capabilities to reach the goals, their architectural business and IT components, and their PROSA, requirements and constraint.

With the ABODE™ approach and the underlying architecture EA3.0™ the SAFe™ Core Values – Alignment, Built-in Quality, Transparency, and Program Execution are safeguarded and in fact improved in several ways.