Enterprise Architecture Management (EAM) is a strategic management tool that helps organizations align their IT infrastructure with their business processes. It creates transparency regarding the organization’s architecture and enables the targeted evolution of business models, applications, and technologies.
Levels
Business Level
The business level describes the strategic objectives, business processes, organizational units, and roles of the enterprise. It forms the foundation for all other levels.
- Objectives: Strategic alignment, value creation, customer benefit
- Processes: End-to-end business processes (e.g., order processing, customer service)
- Organization: Structure, roles, responsibilities
- Information: Business data, key performance indicators, regulations
Example: A banking business describes the processes “submit loan application”, “creditworthiness check”, “contract conclusion”.
Application Level
The application level describes the software systems and applications used to support business processes.
- Applications: ERP systems, CRM tools, portals, microservices
- Integrations: Interfaces between systems (APIs, middleware)
- Data flows: How data is exchanged between applications
- Functional dependencies: Which application supports which business processes
Example: SAP ERP supports accounting, Salesforce CRM supports sales.
Technology Level
The technology level describes the IT infrastructure on which the applications run.
- Hardware: Servers, data centers, end-user devices
- Software: Operating systems, databases, middleware
- Networks: LAN, WAN, cloud infrastructure
- Security & Compliance: Access control, encryption, backup
Example: Virtualized environment with Kubernetes, PostgreSQL database, Azure cloud hosting.
Frameworks
TOGAF (The Open Group Architecture Framework)
TOGAF is the most widely used EAM framework worldwide. It provides a structured approach for developing and managing enterprise architectures.
- ADM (Architecture Development Method): 8-phase process for architecture development
- Content Framework: Templates for architecture artifacts (e.g., views, models)
- Enterprise Continuum: Classification of architectures (from generic to specific)
- TOGAF Standard: Open, extensible, maintained by The Open Group
Advantages: Broad acceptance, well-documented, scalable
Disadvantages: Complex, high learning effort
Zachman Framework
The Zachman Framework is a classification schema that structures architecture information along two dimensions: Perspectives (Who? – from CEO to technician) and Aspects (What? Where? How? When? Why?).
- 6 Perspectives: Planner, Owner, Designer, Builder, Subcontractor, Enterprise
- 6 Aspects: Data, Function, Network, People, Time, Motivation
- 6x6 Matrix: Each cell contains a specific architecture artifact
Advantages: Highly structured, good for documentation and coverage
Disadvantages: No process, no implementation guidance
DYNAMAP (Dynamic Architecture Management)
DYNAMAP is a modern, agile EAM framework specifically designed for digital transformation and dynamic organizations.
- Focus on agility: Rapid adaptation to market and technology changes
- Model-driven architecture: Use of models for automation and simulation
- Integration capability: Links EAM with DevOps, cloud, and AI
- Value orientation: Emphasizes the business value of each architecture component
Advantages: Flexible, digitally oriented, suitable for cloud and platform strategies
Disadvantages: Less established, less standardization
Further Information
Literature
Here some books, I read about Enterprise Architecture and can highly recommend:
Weblinks
Some Links to and around EAM Frameworks:
-
Dynamap SI Framework d’architecture d’entreprise (in french)
Tools for Implementing EAM
There are plenty of software products on the market, to manage your architectures with. I am concentrating on freely available Open Source Systems, you can download and use instantly: