From Ancient Blueprints to Modern IT Architecture: Origins, Definitions, and Frameworks
This article traces the historical origins of architecture from Vitruvius’s ancient treatise to contemporary IT frameworks such as Zachman, TOGAF, and FEA, explains core definitions, compares various architect roles, and offers practical guidance on applying architectural frameworks to drive enterprise transformation and operational efficiency.
Architecture Origins
Western: Architecture—originating from the Roman architect Vitruvius (c. 80‑25 BC) whose ten‑book treatise is the oldest surviving architectural encyclopedia.
This work served as a comprehensive building code and encyclopedia.
Book 1: architects and construction management
Book 2: history of building and materials
Book 3: temple construction methods
Book 4: Roman column construction
Book 5: public buildings and acoustics
Book 6: climate and residential construction
Book 7: ground and wall treatments
Book 8: water supply and drainage
Book 9: astronomy
Book 10: machines and tools
Vitruvius was a Roman citizen with broad knowledge spanning architecture, engineering, geometry, physics, astronomy, philosophy, history, linguistics, aesthetics, and music.
His treatise, written around 32‑22 BC, has influenced architects for over two millennia.
Eastern Architectural Roots
“Two pillars form a frame; three‑rank halls have five bays, doors three bays with five frames.” – New Tang History
The earliest Eastern diagram can be seen in the Bagua, representing a primitive architectural schema.
Modern Architectural Foundations
1962: Herbert Simon first used “architecture” in a systems‑theory paper, though without definition. 1986: DEC’s PRISM project addressed enterprise architecture challenges.
1987: John Zachman’s “Information Systems Architecture Framework” is often cited as the first enterprise architecture model.
1992: Steven Spewak introduced the term “enterprise architecture” in his book “Enterprise Architecture Planning”.
2000: IEEE 1471 defined architecture for software‑intensive systems.
2007 & 2011: ISO 42010 adopted and refined this definition, which is widely used today.
Definition of Architecture
Architecture is the fundamental organization of system components, their relationships, and the principles guiding their design and evolution.
The diagram above positions various architecture domains: business (information), data (application), and infrastructure (server) architects, with solution architects focusing on specific business goals, and enterprise architects covering the full IT landscape.
Why Build Architecture?
Enterprise architecture enables successful digital transformation and reduces maintenance costs while increasing innovation investment.
Shifting the IT budget from “20 % innovation + 80 % maintenance” to “80 % innovation + 20 % maintenance” can dramatically lower costs and create a leading enterprise.
Correct architecture reduces the “8” (maintenance) and frees funds for the “2” (innovation).
Architecture Frameworks
Effective architecture requires a framework, analogous to a martial arts style.
An architecture framework is a set of foundational structures used to develop a wide range of architectures.
It provides a collection of building blocks, a common vocabulary, toolsets, and standards.
Zachman Framework
Comprehensive classification of architecture concepts
36‑cell matrix covering “who, what, when, why, how” for an enterprise
Links business goals to technical implementation
Highly customizable for diverse environments
FEA – Federal Enterprise Architecture
FEA is a performance‑based, cross‑departmental framework for U.S. federal agencies, aiming to simplify processes, share IT investments, and integrate government business lines.
TOGAF – The Open Group Architecture Framework
TOGAF provides a detailed method and supporting tools for developing enterprise architecture; since 1995 it has evolved through nine versions and is used by many Fortune 500 companies.
Enterprise Architecture Implementation Advice
A framework provides an organized, repeatable method.
Adopt the framework to fit your organization’s context.
Establish an architecture team to design, implement, and maintain outcomes.
Effective governance of deliverables is critical.
Start small and scale up.
Architecture and Operations
Enterprise architecture drives transformation, while operations preserve results and uncover new opportunities. TOGAF and ITIL complement each other across different layers, as illustrated in the diagram.
Efficient Ops
This public account is maintained by Xiaotianguo and friends, regularly publishing widely-read original technical articles. We focus on operations transformation and accompany you throughout your operations career, growing together happily.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.