• slide1

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

  • 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

Transition Delivery

 Transition Delivery is concerned with developing the solution as requested in information planning and business cases based on the strategic choices of top management and the necessary capabilities that enables the organization to deliver the strategic changes. Essential in this area are the following Capabilities:

  • Requirement Management
    Requirement Management is concerned with defining the functional and non-functional requirements based on the PID and PSA, including delivering EPICs and User Stories
  • Data Management
    Data Management models and updates Business Objects, maps them against Enterprise Objects, Data Objects, and Presentation Objects
  • Service Management
    Service Management is concerned with the further development of Information, Presentation, Data and Technical Services based on the Data Mappings and managing them both functionally and technically
  • Business RuleSet Management
    Business Rule Management is concerned with registering, managing and testing the Business Logic and their sources like judicial texts, jurisprudence, laws and regulations, capabilities, service delivery and their contracts, etc., defined in Business RuleSets per (Actionable) Knowledge Function and Business Processes
  • User Interaction Design
    User Interaction Design is about the further development of EPICs and User Stories by defining different Presentation Objects in a user-friendly way
  • Activity Competence Definition
    Activity Competence Defintion defines the necessary competences which Users need to effectively and efficiently use the Business Activities in the form of Actors and their Roles within Business Processes
  • Knowledge Function Management
    Knowledge Function Management concerns the different components of Knowledge Functions based on the Knowledge type:
    • Actionable Knowledge by defining the sequence of internal, actionable components and the related business rules in a microflow
    • Augmented Knowledge by defining the “way-of-work” of the business functionality by defining and explaining the used methodologies, techniques, and tools, the models to be used, etc. by delivering textual or interactive multimedia files like documents, audios, movies, augmented reality apps, etc.
    • Architectural Knowledge by defining the relationships with other architecture components in a coherent and consistent way
  • Business Process Design
    Business Process Design is concerned with the modeling of workflows, cases and business processes up to the details of OTOPOP (One Time, One Place, One Person) of actionable Knowledge Functions, including the used Business Logic