Business Architecture: Evolution, Definition, and Its Relationship with IT Architecture

The excerpt, taken from the book *Enterprise Business Architecture Design: Methodology and Practice*, introduces business architecture, a concept rarely covered in traditional software engineering textbooks, and explains why understanding its role is essential for modern enterprises.

Chapter 1 – Development History

The Zachman model (1987) introduced a 5W1H framework (What, Where, Who, When, Why, How) across six layers, providing an early inspiration for business architecture even though it did not name the concept explicitly.

In 1995, TOGAF explicitly defined business architecture, separating it from IT architecture and describing it as the translation of enterprise strategy into operational processes, organizational structures, and geographic distribution.

TOGAF also provides a detailed set of deliverables (Table 1‑2), illustrating the artifacts produced at each stage of business architecture development.

Subsequent frameworks such as the Federal Enterprise Architecture (FEA) and the Department of Defense Architecture Framework (DODAF) introduced additional reference models and viewpoints, applying business‑architecture thinking to large‑scale government initiatives.

Despite its long history, business architecture faces practical challenges: limited adoption in development projects, difficulty designing comprehensive models for complex enterprises, risk of deviation during implementation, and high maintenance costs.

Definition

The article defines business architecture as a structured enterprise‑capability analysis method that translates strategy into technology implementation, serving as a bridge between business and IT and fostering a common language for both sides.

It also notes that the popular “mid‑platform” concept is essentially a product of business‑architecture planning, representing a top‑down approach to capability design.

Chapter 2 – Role and Relationship with IT Architecture

Business architecture acts as the connective tissue between business needs and IT solutions, enabling digital transformation by aligning processes, data, and technology. Real‑world examples such as Starbucks, Didi, and Meituan illustrate how architecture‑driven digital strategies create new business models.

The relationship between business and IT architecture is likened to a soul (business architecture) and a container (IT architecture). Four IT‑architecture domains—application, technical, data, and security—interact with business architecture to varying degrees, with application and data architectures being the most tightly coupled.

Ultimately, successful enterprise transformation requires both business and technical staff to adopt a shared, architecture‑centric mindset, ensuring that strategic intent is faithfully realized in the technical implementation.