IT Architecture Management
Objective: According to ITIL the IT Architecture Management process aims to define a blueprint for the future development of the technological landscape, taking into account the service strategy and newly available technologies.
Part of: Service Design
Process Owner: Enterprise Architect
IT Architecture management is not on the list of official ITIL 2011 processes, but ITIL provides guidance on architecture issues as part of a chapter on "technology-related activities", and having a well-defined architecture blueprint in place is very important for IT organizations. So there are good reasons for organizations to define and implement an architecture management process, and at IT Process Maps we have decided to assign clear responsibilities for managing the architecture, which meant introducing a specific Architecture Management process as part of the ITIL® Process Map.
ITIL does not provide a detailed explanation of all aspects of Architecture Management. A well-structured and up-to-date Enterprise Architecture, however, is commonly regarded as a key element for successfully managing organizations.
Following the introduction of Design Coordination in ITIL 2011 the information flows have been adapted slightly. The process overview of ITIL Architecture Management (.JPG) shows the key information flows (see fig. 1).
No sub-processes are specified for ITIL Architecture Management.
The following ITIL terms and acronyms (information objects) are used in ITIL Architecture Management to represent process outputs and inputs:
- Application Frameworks aim to promote the re-use of components and the standardizing of technologies on which applications are based. For this reason, they have to be planned and managed separately from software development projects – but must be carefully aligned with the needs of software developers. Application Frameworks define classes of applications, typically with common non-functional requirements.
Change Request to Enterprise Architecture
- A request to change or extend the Enterprise Architecture, usually issued from the Service Design process when the introduction or modification of a service is not possible within the constraints of the existing application, infrastructure and information/ data architectures.
Enterprise Architecture (EA)
- An Enterprise Architecture (EA) is a description of the essential components of a business, including their interrelationships. In most cases, an EA covers the following domains: Business, Information, Applications and Technology.
Roles | Responsibilities
Enterprise Architect - Process Owner
- The Enterprise Architect is responsible for maintaining the Enterprise Architecture (EA), a description of the essential components of a business, including their interrelationships.
- Bigger organizations may opt to introduce specialist EA roles like Business Architect, Application Architect, Information Architect, or Infrastructure Architect.
|ITIL Role / Sub-Process||Enterprise Architect|
(no sub-processes specified)
 A: Accountable according to the RACI Model: Those who are ultimately accountable for the correct and thorough completion of the Architecture Management process.
 R: Responsible according to the RACI Model: Those who do the work to achieve a task within ITIL Architecture Management.