• slide1

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

  • slider2

    Generalized Enterprise Function Framework  (GEFF)

  • slider4

    ABODE™ business transformation methodology  founded on EA3.0

  • slider3

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

Design Continuum Optimization

During the transition architects are involved in weighing the quality and control the contents of the design components for the coherence and consistency of the delivered components in the design continuum. This should also result in optimizing the Design Continuum and the (To Be) Architecture Continuum, in which case no unforeseen duplication of components takes place. After the transition has delivered the Design Components final check are made and the components can be duplicated into the Architecture Continuum.


Problems and Solutions

The contemporary architecture approach often focuses on delivery project start documents while the design and development teams are focused on delivering usable processes, information systems and apps. So whether these latter deliveries support value creation, are aligned with what the business needs and wants, are coherent and consistent with earlier or future architectures and deliveries is often of minor interest to the design and development teams: it is a quality and architecture issue. Therefore architects should evaluate all components that are delivered and accept that they are designed and developed conform the earlier requirements (PROSA) and architecture.  


Tools to support Optimization of the Design Continuum

Enterprise Architects delivers methodologies, techniques and tools to accept (or reject) the delivered components with the following tools:

  • AAM/PEA Generation and checking
Generating the PEA based on the delivered components and checking the PEA against the PSA
  • AFR/Function Requirement 
Checking the PROSA requirements for each Knowledge Function of the solution components
  • AOM/Conceptual Mapping
Checking the Business Objects and generalizing/specializing them against Enterprise Objects. Checking the Business to Data mapping and optimizing the mapping
  • ISE/Integrated Service Engineering 
Generalization and Specilization of Service types
  • APR/PROSA Modeling
Checking the details of the Principles, the Requirements, design Objectives, Standards & Agreements for the solution components
  • AEM/Environment Management    
Moving accepted components from one environment (Acceptance) to the other (Operations)

Advantages of the Enterprise Architects approach

  1. Acceptance of Design Components for Assessment and Improvement of Architecture and Design Results
  2. Assessment, discussion and advise of designed components
  3. Acceptance and registration of validated and accepted components in the Architecture and Design Continuum
  4. The SAFe™ Core Values are safeguarded and improved as follows
    • Alignment
    • Built-in Quality
    • Transparency
    • Program Execution