IT Architecture

Qualities like sustainability, dependability, scalability, and performance don’t emerge naturally from combining functional components. They require deliberate design. IT Architecture provides the structured descriptions that make this possible — without it, systems become opaque, fragile, and expensive to change.

Why Architecture Matters

Architecture makes the invisible visible. These are the qualities that require architectural thinking — they cannot be added as an afterthought.

Sustainability

The system can be maintained and evolved over its useful life without accumulating unmanageable technical debt.

Dependability

The system delivers its intended function reliably, including availability, fault tolerance, and recoverability.

Scalability

The system can handle growth in users, data, or transactions without fundamental redesign.

Performance

The system meets response time, throughput, and resource efficiency requirements under expected and peak loads.

Security

The system protects confidentiality, integrity, availability, accountability, and assurance of the data it processes.

Interoperability

The system can exchange data and integrate with other systems through well-defined interfaces and standards.

Types of IT Architecture

IT Architecture is not one discipline. Six distinct types serve different audiences and operate at different levels of abstraction — from enterprise-wide strategy to specific infrastructure decisions.

Enterprise Architecture

CTO, Enterprise Architects, Business Strategists
“How does our IT landscape support the business?”
Value

Strategic alignment — maps business capabilities to technology investments. Ensures the IT estate serves business objectives and evolves coherently.

Frameworks

TOGAF, Zachman Framework, ArchiMate

Reference Architecture

Solution Architects, Platform Teams
“What does good look like for this type of system?”
Value

Design acceleration — proven blueprints for common scenarios so teams don’t reinvent from scratch. Ensures consistency across projects.

Frameworks

OSA Patterns, AWS Well-Architected, Azure Architecture Centre, Google Cloud Architecture Framework

OSA Patterns →

Solution Architecture

Solution Architects, Development Teams, Project Managers
“How do we build this system?”
Value

Implementation guidance — concrete design for a specific system, including technology choices, integration points, and quality trade-offs.

Frameworks

Project-specific designs, derived from reference architectures and enterprise standards

Security Architecture

Security Architects, Security Engineers, CISOs
“How do we secure this?”
Value

Risk-proportionate protection — defines what controls are required, where they sit, how they reduce risk, and who is accountable.

Frameworks

OSA Patterns, OSA Capability Model, SABSA, NIST 800-53

IT Security Architecture →

Data Architecture

Data Architects, Data Engineers, Privacy Officers
“How does data flow and who owns it?”
Value

Data governance — defines how data is collected, stored, transformed, distributed, and consumed. Essential for compliance and analytics.

Frameworks

DAMA DMBOK, data mesh, data lakehouse patterns

Infrastructure Architecture

Infrastructure Architects, Platform Engineers, SREs
“What runs where, and how reliably?”
Value

Operational foundation — compute, network, storage, and platform services that underpin everything. Drives availability, performance, and cost.

Frameworks

Cloud provider frameworks, IaC patterns, SRE principles

How Leading Organisations Define IT Architecture

Each framework emphasises a different aspect — structure, artefacts, business alignment, or change management. Together they reveal why architecture is both a noun (the structure) and a verb (the practice of designing it).

TOGAF Structure & evolution

Architecture has two contextual meanings: (1) A formal description or detailed plan to guide implementation, and (2) The structure of components, their inter-relationships, and principles governing design and evolution over time.

The Open Group Architecture Framework
Zachman Design artefacts & quality

A set of design artefacts, or descriptive representations, that are relevant for describing an object such that it can be produced to requirements (quality) as well as maintained over the period of its useful life (change).

Zachman Framework
COBIT Business alignment

Description of the fundamental underlying design of the IT components of the business, the relationships amongst them and the manner in which they support the organisation’s objectives.

COBIT 2019
IEEE System fundamentals

The fundamental organisation of a system, embodied in its components, their relationships to each other and the environment, and the principles governing its design and evolution.

IEEE 1471-2000 / ISO/IEC 42010
OSA Visibility & change control

The structured descriptions that allow a system to be built to requirements, operated to expectations, and changed over its useful life. Architecture makes the invisible visible — without it, decisions are ad hoc, inconsistencies are hidden, and change becomes unpredictable.

Open Security Architecture