IT Architecture

Why do we need IT Architecture? Abstract system descriptions are essential to achieve qualities like sustainability, dependability, scalability, and performance - these don't emerge naturally from simply combining functional components.

Definitions

COBIT

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.

TOGAF

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.

Zachman Framework

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).

Types

Enterprise IT Architecture

Models business processes mapped to applications, then infrastructure components

Reference Architecture

Describes desired future state reflecting best practices

Solution Architecture

Describes particular solutions including technical, software, information, network, and data architecture

Security Architecture

The focus of OSA - see our dedicated definition page