IT Architecture Management: Difference between revisions
From IT Process Wiki
No edit summary |
No edit summary |
||
| Line 11: | Line 11: | ||
<br style="clear:both;"/> | <br style="clear:both;"/> | ||
<p> </p> | <p> </p> | ||
'''<span id="Overview">Objective:</span>''' <html><span | '''<span id="Overview">Objective:</span>''' <html><span id="md-webpage-description" itemprop="description"><i>ITIL Architecture Management</i> aims to define a blueprint for the future development of the technological landscape, taking into account the service strategy and newly available technologies.</span></p> | ||
<p><b>Part of</b>: <a | <p><b>Part of</b>: <a href="https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Design" title="ITIL Service Design">Service Design</a></html> | ||
'''Process Owner''': [[IT Architecture Management#Enterprise Architect|Enterprise Architect]] | '''Process Owner''': [[IT Architecture Management#Enterprise Architect|Enterprise Architect]] | ||
| Line 23: | Line 22: | ||
==Process Description== | ==Process Description== | ||
[[Image:It-architecture-management.jpg|right|thumb|375px|alt=ITIL Architecture Management ITIL|[https://wiki.en.it-processmaps.com/images/pdf/process_overview_it_architecture_management_itilv3.pdf ITIL Architecture Management]]] | [[Image:It-architecture-management.jpg|right|thumb|375px|alt=ITIL Architecture Management ITIL|link=https://wiki.en.it-processmaps.com/index.php/File:It-architecture-management.jpg|[https://wiki.en.it-processmaps.com/images/pdf/process_overview_it_architecture_management_itilv3.pdf ITIL Architecture Management]]] | ||
ITIL provides guidance on architecture issues as part of a chapter on "technology-related activities". Having a well-defined architecture blueprint in place is very important for IT organizations, so at IT Process Maps we decided to assign clear responsibilities for managing the [[IT Architecture Management#Enterprise-Architecture|architecture]], which meant introducing a specific Architecture Management process as part of the [https://en.it-processmaps.com/products/itil-process-map.html ITIL® Process Map]. | ITIL provides guidance on architecture issues as part of a chapter on "technology-related activities". Having a well-defined architecture blueprint in place is very important for IT organizations, so at IT Process Maps we decided to assign clear responsibilities for managing the [[IT Architecture Management#Enterprise-Architecture|architecture]], which meant introducing a specific Architecture Management process as part of the [https://en.it-processmaps.com/products/itil-process-map.html ITIL® Process Map]. | ||
| Line 29: | Line 28: | ||
ITIL does not provide a detailed explanation of all aspects of Architecture Management. A well-structured and up-to-date [[#Enterprise-Architecture|Enterprise Architecture]], however, is commonly regarded as a key element for successfully managing organizations. | ITIL does not provide a detailed explanation of all aspects of Architecture Management. A well-structured and up-to-date [[#Enterprise-Architecture|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 | Following the introduction of Design Coordination in '''''ITIL 2011''''' the information flows have been adapted slightly. The process overview of [[Media:It-architecture-management.jpg|ITIL Architecture Management (.JPG)]] is showing the most important interfaces (see Figure 1). | ||
<p> </p> | <p> </p> | ||
| Line 89: | Line 88: | ||
<span id="Accountable">[1] ''A: Accountable'' according to the RACI Model: Those who are ultimately accountable for the correct and thorough completion of the Architecture Management process.</span> | <span id="Accountable">[1] ''A: Accountable'' according to the RACI Model: Those who are ultimately accountable for the correct and thorough completion of the Architecture Management process.</span> | ||
<span id="Responsible">[2] ''R: Responsible'' according to the RACI Model: Those who do the work to achieve a task within | <span id="Responsible">[2] ''R: Responsible'' according to the RACI Model: Those who do the work to achieve a task within ITIL Architecture Management.</span> | ||
<p> </p> | <p> </p> | ||
== | ==Notes== | ||
<html>By:  Stefan Kempter <a rel="author" href="https://plus.google.com/111925560448291102517/about"><img style="margin:0px 0px 0px 0px;" src="/skins/Vector/images/itpm/bookmarking/gplus.png" width="16" height="16" title="By: Stefan Kempter | Profile on Google+" alt="Author: Stefan Kempter, IT Process Maps GbR" /></a>, IT Process Maps.</p> | |||
< | <p> </p> | ||
</ | |||
<p><small> | <p><small> | ||
| Line 126: | Line 109: | ||
</span> | </span> | ||
</small></p> | </small></p> | ||
</ | |||
<!-- define schema.org/WebPage --> <span itemscope itemtype="https://schema.org/WebPage" itemref="md-webpage-description"> | |||
<meta itemprop="alternativeHeadline" content="ITIL Architecture Management" /> | |||
<meta itemprop="name" content="Architecture Management" /> | |||
<link itemprop="url" href="https://wiki.en.it-processmaps.com/index.php/IT_Architecture_Management" /> | |||
<meta itemprop="inLanguage" content="en" /> | |||
<link itemprop="citation" href="https://wiki.de.it-processmaps.com/index.php/IT_Architecture_Management" /> | |||
<link itemprop="citation" href="https://wiki.es.it-processmaps.com/index.php/ITIL_Gestion_de_la_Arquitectura_de_TI" /> | |||
<meta itemprop="Headline" content="IT Architecture Management" /> | |||
<link itemprop="isPartOf" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Design" /> | |||
<link itemprop="primaryImageOfPage" href="https://wiki.en.it-processmaps.com/images/0/0e/It-architecture-management.jpg" /> | |||
<link itemprop="author" href="https://plus.google.com/111925560448291102517/about" /> | |||
<meta itemprop="author" content="Stefan Kempter" /> | |||
<meta itemprop="creator copyrightHolder publisher" content="IT Process Maps" /> | |||
</span><p></html> | |||
<!-- This page is assigned to the following categories: --> | <!-- This page is assigned to the following categories: --> | ||
[[Category:ITIL V3]][[Category:ITIL 2011]][[Category:ITIL process]][[Category:Service Design|Architecture Management]][[Category:Architecture Management|!]] | [[Category:ITIL V3]][[Category:ITIL 2011]][[Category:ITIL process]][[Category:Service Design|Architecture Management]][[Category:Architecture Management|!]] | ||
<!-- --- --> | <!-- --- --> | ||
Revision as of 14:42, 15 May 2016
Objective: ITIL Architecture Management 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
Process Description
ITIL provides guidance on architecture issues as part of a chapter on "technology-related activities". Having a well-defined architecture blueprint in place is very important for IT organizations, so at IT Process Maps we 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) is showing the most important interfaces (see Figure 1).
Sub-Processes
No sub-processes are specified for ITIL Architecture Management.
Definitions
The following ITIL terms and acronyms (information objects) are used in ITIL Architecture Management to represent process outputs and inputs:
Application Framework
- 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.
| Responsibility Matrix: ITIL Architecture Management | |
| ITIL Role / Sub-Process | Enterprise Architect |
|---|---|
| Architecture Management (no sub-processes specified) |
A[1]R[2] |
Remarks
[1] A: Accountable according to the RACI Model: Those who are ultimately accountable for the correct and thorough completion of the Architecture Management process.
[2] R: Responsible according to the RACI Model: Those who do the work to achieve a task within ITIL Architecture Management.
Notes
By: Stefan Kempter 
, IT Process Maps.
Process Description › Definitions › Roles
