• 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

  • slide1

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

Data Management

Data Management is an essential part of transition delivery. Enterprise Architects supports the DAMA-DMBoK processes. Within the Enterprise Architects approach Meta Data Management and Master Data Management plays an important role.

Also see Strategy Modeling/Conceptual Object Modeling


Problems and Solutions

The contemporary approach often doesn’t use a 3-layer data approach resulting in the impossibility to apply master data management, meta data management, data governance, etc.

The Enterprise Architects solution uses the 3-layer (conceptual, logical, physical) data approach in which the business objects of the logical layer are specializations of the enter objects of the conceptual layer – thus diminishing duplicates, enabling the business to define their required data and information independent of the storage (data objects in the physical layer) structure in databases and enabling the possibility to map data attributes between the different objects and thus generated messages and services or APIs between the layers. This results in higher flexibility, loosely coupling, the 5-layer architecture, the possibility to contain the physical data as a solution for solving legacy problems, etc.


Tools to support Data Management

The following tools and solutions support Data Management:

  • Solutions
    • DAMADMBoK processes
      The Enterprise Architects’ solution supports the 11 DAMADMBoK processes:
  1. Data Governance
  2. Data Architecture
  3. Data Modeling & Design
  4. Data Storage & Operations
  5. Data Security
  6. Data Integration & Interoperability
  7. Documents & Content
  8. Reference & Master Data
  9. Data Warehousing & Business Intelligence
  10. Meta Data
  11. Data Quality
  •  Tools
  •  Object Modeling
  •  AOM/Conceptual Modeling 

designing the Conceptual Object Model with Enterprise Objects based on the Proposition Model

  •  AOM/Business to Enterprise
mapping objects from Business (Logical model) to Enterprise (Conceptual model) Objects as specializations
  •  AOM/Business to Interaction
mapping objects from Business to Presentation Objects (both Logical model) to generate for Presentation Services
  •  AOM/Business to Data 
mapping objects from Business (Logical model) to Data (Physical model) Objects to generate messages for Information Services and Data Services/APIs that will be used by Service Management See Transition Delivery/Service Management

Advantages of the Enterprise Architects approach

  1. Use the full DAMA DMBok stack of processes
  2. Use 3-layer approach resulting in higher data quality, ease of use to generate services, etc.
  3. The SAFe™ Core Values are safeguarded and improved as follows
    • Alignment
    • Built-in Quality
    • Transparency