Loading content
Enterprise architecture defines an organization’s high-level structure, principles, and standards to align business strategy with IT systems. It provides models, decision rules and roadmaps for capability development and integration. EA guides governance, technology choices and organizational change by making architectures explicit and traceable across initi…
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What you need to understand to reason about a domain.
Enterprise Architecture (EA) is the organization-wide practice of organizing and evolving business strategy, processes, information, and technology through shared architectural decisions.
EA emerged from the need of large organizations to manage business, information, process, and technology change together instead of only within individual projects. Early descriptions focused on integration problems across heterogeneous systems; later frameworks such as TOGAF and modeling languages such as ArchiMate provided a common way to describe principles, target states, transition paths, and governance.
Think of EA as a map, rulebook, and renovation plan combined: strategy and principles sit at the top, then capabilities, processes, data, and applications, then platforms and infrastructure. Architecture models expose dependencies, governance decides on standards and exceptions, and roadmaps turn the target picture into staged change.
EA treats the organization as a socio-technical whole made up of people, processes, information, and technology.
Guiding rules narrow design freedom and make architecture decisions consistent.
Instead of only looking at org charts, EA describes the enduring abilities the enterprise must provide.
Architecture representations condense the relevant relationships for different audiences and decisions.
Boards, standards, and decision rights steer exceptions, risks, and priorities.
A widely used framework that organizes EA work into methods, content, and governance structures.
EA helps when IT landscapes grow, platforms are consolidated, mergers must be integrated, or transformation efforts need prioritization. Its value increases with clear decision rights and maintained models; without sponsorship and discipline, EA can become documentation without impact. Too much detail makes it heavy, too little detail makes it noncommittal.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.