Definition of enterprise architecture
Enterprise architecture is, in common usage, the discipline that describes an organisation as a whole, from its objectives to its technical infrastructure, in order to guide its transformations and keep them consistent. The French expression “architecture d’entreprise” corresponds to the English “enterprise architecture”: the Club Urba-EA, a cross-company association, gives the two forms as equivalent on its website (urba-ea.org).
The word “enterprise” here refers to the organisation under study, whatever its form. The page that The Open Group devotes to its TOGAF standard (opengroup.org) cites among its users commercial companies of all sizes, government departments, public bodies and defence agencies.
Definitions differ according to frameworks and authors. The one this entry adopts brings together three elements: a description in several interrelated domains, a target state, and a path to reach it.
The decisions that enterprise architecture informs
The discipline prepares decisions that go beyond the scope of a project. In particular, it makes it possible:
- to judge whether a project brings the organisation closer to the target state or moves it further away;
- to spot that the same capability is served by several applications, or by none;
- to assess what a management decision (merger, new offering, transferring an activity to a third party) entails for processes, data and systems.
It also provides a common vocabulary for executive management, the business and IT: a single model links an objective to a process, then to the applications and data that serve it.
Domains described, frameworks and languages
A breakdown in common use distinguishes four domains, whose names vary from one framework to another.
| Domain | What it describes |
|---|---|
| Business | Objectives, processes, organisation, capabilities |
| Data | Business objects, reference data, responsibility for each item of data |
| Applications | Applications, services provided, exchanges |
| Technology | Infrastructure, platforms, networks |
Each domain is described in its current state and in its target state. A roadmap orders the steps between the two, and principles frame the choices made by projects.
Two families of tools support the discipline. Frameworks offer a method: TOGAF, from The Open Group, has its own entry in this glossary. Languages offer a notation: The Open Group presents ArchiMate as an open and independent modelling language, which describes business processes, organisational structures, information flows, IT systems and technical infrastructure.
Enterprise architecture, IT urbanisation, IT master plan, API management: not to be confused
IT urbanisation is a term used in France. The approach it refers to concerns the information system, its breakdown and its rules. Enterprise architecture, the term used in international publications, starts higher up: at objectives and organisation.
The IT master plan is a dated document, approved by executive management, which selects projects and a budget for several years. Enterprise architecture is an ongoing activity: it provides the master plan with an assessment of the current state and a target, and leaves the funding decision to it.
API management operates at another scale. It governs and provides tooling for a single category of exchange, programming interfaces, whose place among the other modes of exchange is indicated by enterprise architecture.
Solution architecture, finally, designs the response to a need within the limits of a project.
Example: a retailer opens click and collect
Take a retail chain that wants to sell online with in-store collection. Read as a project, the subject comes down to an e-commerce website. On the business side, a new process appears: preparing in store an order placed elsewhere. On the data side, each store’s stock must be known at the time of ordering, whereas it is only consolidated once a night. On the applications side, the point-of-sale software, stock management and the future website have to exchange data. On the technology side, the stores’ network link becomes a link in the customer journey.
The description by domain brings out the decision to be made: making stock available for consultation continuously before opening the website.
Building a target, a roadmap and architecture governance is the subject of our page dedicated to IT architecture.