EA Definition

We are used to talking about architecture when it comes to buildings and bridges. We then know it is a coherent set of concepts and principles. However, architecture is new for government institutions and commercial enterprises. Enterprise Architecture appears to be different from traditional architecture. But is it? Or is it not?

Definition

EA is defined by Dragon1 as a total concept for an enterprise structure comprising coherent constructive, operative, and decorative concepts (and their principles) for governance, business, information, applications, data, and technology.

Like building architecture, Enterprise Architecture is a coherent set of concepts and principles. Still, now for business concepts, data concepts, IT principles, and security principles.

EA is often used in organizations that employ a method, framework, and dossier for products (such as concept design sketches, principle details diagrams, heatmaps, roadmaps, blueprints, and landscapes).

EA often refers to the overall design and structure of the systems, processes, data, applications, and IT of an organization.

EA is used as a strategic approach to align technology with business goals and objectives and to create a conceptual blueprint for the organization's tech infrastructure.

In this sense, EA has a lot of similarities with building architecture, as in the architecture (total concept) of a building (structure).

Geometric Shape

The shape for EA in Dragon1 is an arch:

Usage

Today, organizations are busier with EA Frameworks than ever. As new technologies like IoT, Blockchain, and artificial intelligence emerge more rapidly, Big Data Lakes are on the doorstep, and no single software supplier can do it all. Every organization must make its current (as-is) and target (to-be) Enterprise Architecture visible.

Misunderstandings about EA

EA is more than just IT or business processes + software applications. It is the architecture of the whole enterprise.

Here is one of the articles about Misunderstandings in EA: https://www.informationweek.com/software/information-management/ten-pitfalls-in-establishing-an-enterprise-architecture/d/d-id/1082883 (we link it like this as it provides a broken link sometimes).

Examples

The definition states that an architecture is a total concept, thus a set of coherent concepts. So, if you visualize the architecture of a structure, you would see concepts grouped. Often divided into layers. An EA often has layers like governance, business, information (systems), application, data, and technology or IT infrastructure.

An EA example (in 2D) is presented here below. You see layers, and on each layer, you see concepts (the oval shapes are the icons for concepts).

You can use this diagram to score the presence and maturity of concepts in your organization. It is exciting to see the new, unique concepts within your organization that put you ahead of the competition.

The diagram below shows many generic concepts that are present in every organization and implemented at different levels of maturity (m).

Use the two diagrams to match your situation with them.

More Examples of EA are:

The company is only present online. No employees. No offices.
eGovernment: the ability to do business with the government online and in brick-and-mortar.
eFulfillment: the ability to do every logistic action after receiving an order smoothly and interchangeably online or physically.