IT Architecture Management: Difference between revisions
From IT Process Wiki
No edit summary |
No edit summary |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
<itpmch><title>IT Architecture Management | IT Process Wiki</title> | <itpmch><title>IT Architecture Management | IT Process Wiki</title> | ||
<meta name="keywords" content="itil architecture management, itil architecture, it architecture management, it architecture management, architecture management process" /> | <meta name="keywords" content="itil architecture management, itil architecture, it architecture management, it architecture management, architecture management process" /> | ||
<meta name="description" content="ITIL Architecture Management | <meta name="description" content="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." /> | ||
<meta property="og:url" content="https://wiki.en.it-processmaps.com/index.php/IT_Architecture_Management" /> | <meta property="og:url" content="https://wiki.en.it-processmaps.com/index.php/IT_Architecture_Management" /> | ||
<meta property="og:title" content="IT Architecture Management | IT Process Wiki" /> | <meta property="og:title" content="IT Architecture Management | IT Process Wiki" /> | ||
<meta property="og:description" content=" | <meta property="og:description" content="The ITIL 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." /> | ||
<meta property="og:site_name" content="IT Process Wiki - the ITIL® Wiki"> | <meta property="og:site_name" content="IT Process Wiki - the ITIL® Wiki"> | ||
<meta property="og:type" content="article" /> | <meta property="og:type" content="article" /> | ||
| Line 11: | Line 11: | ||
<meta property="fb:admins" content="100002592864414" /> | <meta property="fb:admins" content="100002592864414" /> | ||
<meta property="og:image" content="https://wiki.en.it-processmaps.com/images/0/0e/It-architecture-management.jpg" /> | <meta property="og:image" content="https://wiki.en.it-processmaps.com/images/0/0e/It-architecture-management.jpg" /> | ||
<meta property="og:image:width" content=" | <meta property="og:image:width" content="1200" /> | ||
<meta property="og:image:height" content=" | <meta property="og:image:height" content="1200" /> | ||
<link href="https://plus.google.com/108613479011811316823/posts" rel="publisher" /> | <link href="https://plus.google.com/108613479011811316823/posts" rel="publisher" /> | ||
</itpmch> | </itpmch> | ||
<imagemap> | <imagemap> | ||
Image:ITIL-Wiki-de-es.jpg|right|DE - ES - ITIL Architecture Management|163px | |||
Image:ITIL-Wiki-de-es.jpg|DE - ES - ITIL Architecture Management|163px | |||
rect 81 0 114 36 [https://wiki.de.it-processmaps.com/index.php/IT_Architecture_Management diese Seite auf Deutsch] | rect 81 0 114 36 [https://wiki.de.it-processmaps.com/index.php/IT_Architecture_Management diese Seite auf Deutsch] | ||
rect 115 0 163 36 [https://wiki.es.it-processmaps.com/index.php/ITIL_Gestion_de_la_Arquitectura_de_TI esta página en español] | rect 115 0 163 36 [https://wiki.es.it-processmaps.com/index.php/ITIL_Gestion_de_la_Arquitectura_de_TI esta página en español] | ||
| Line 38: | Line 32: | ||
==Process Description== | ==Process Description== | ||
[[Image:It-architecture-management.jpg|right|thumb| | [[Image:It-architecture-management.jpg|right|thumb|500px|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]]] | ||
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 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]. | 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 [[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 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 | 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)]] shows the key information flows (see fig. 1). | ||
[[ITIL 4]] refers to 'Architecture Management' as a [[ITIL_4#General_management_practices|general management practice]]. | |||
==Sub-Processes== | ==Sub-Processes== | ||
No sub-processes are specified for [[IT Architecture Management|ITIL Architecture Management]]. | No sub-processes are specified for [[IT Architecture Management|ITIL Architecture Management]]. | ||
==Definitions== | ==Definitions== | ||
| Line 58: | Line 50: | ||
<html><div itemscope="itemscope" itemtype="https://schema.org/ItemList"><!-- define schema.org/ItemList --> | <html><div itemscope="itemscope" itemtype="https://schema.org/ItemList"><!-- define schema.org/ItemList --> | ||
<meta itemprop="itemListOrder" content="Ascending" /> | <meta itemprop="itemListOrder" content="Ascending" /> | ||
<p><span itemprop="name">The following <a href="/index.php/ | <p><span itemprop="name">The following <a href="/index.php/ITIL_Glossary#ITIL_Glossary_A-Z" title="ITIL Glossary">ITIL terms and acronyms</a> (<i>information objects</i>) are used in ITIL Architecture Management to represent process outputs and inputs:</span> | ||
</p> | </p> | ||
<p><b><span id="Application-Framework" itemprop="itemListElement">Application Framework</span></b> | <p><b><span id="Application-Framework" itemprop="itemListElement">Application Framework</span></b> | ||
</p> | </p> | ||
<ul><li itemprop="description">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. | <ul><li itemprop="description">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. | ||
</li></ul> | </li></ul> | ||
<p><b><span id="Change-Request-Architecture" itemprop="itemListElement">Change Request to Enterprise Architecture</span></b> | |||
</p> | </p> | ||
<ul><li itemprop="description">A request to change or extend the <a href="/index.php/IT_Architecture_Management#Enterprise-Architecture" title="IT Architecture Management">Enterprise Architecture</a>, 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. | <ul><li itemprop="description">A request to change or extend the <a href="/index.php/IT_Architecture_Management#Enterprise-Architecture" title="IT Architecture Management">Enterprise Architecture</a>, 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. | ||
</li></ul> | </li></ul> | ||
<p><b><span id="Enterprise-Architecture" itemprop="itemListElement">Enterprise Architecture (EA)</span></b> | |||
</p> | </p> | ||
<ul><li itemprop="description">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. | <ul><li itemprop="description">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. | ||
</li></ul> | </li></ul> | ||
</div><!-- end of schema.org/ItemList --><p></html> | </div><!-- end of schema.org/ItemList --><p></html> | ||
==Roles | Responsibilities== | ==Roles | Responsibilities== | ||
| Line 86: | Line 74: | ||
<p> </p> | <p> </p> | ||
{| | {| class="wikitable" style="background: white;" | ||
|- | |- | ||
|style=" | |+ style="background:#013b5e; color:#ffffff; font-size: 120%" colspan="2"|'''Responsibility Matrix: ITIL Architecture Management''' | ||
|- | |- | ||
!style="background:#ffffee; width: 50%; text-align:center" | ITIL Role / Sub-Process | !style="background:#ffffee; width: 50%; text-align:center" | ITIL Role / Sub-Process | ||
! style="background:# | ! style="background:#eeeeee;" | [[IT Architecture Management#Enterprise Architect|Enterprise Architect]] | ||
|- | |- | ||
|style="text-align:left;" |[[IT Architecture Management|Architecture Management]]<br /> ''(no sub-processes specified)'' | |style="text-align:left;" |[[IT Architecture Management|Architecture Management]]<br /> ''(no sub-processes specified)'' | ||
| Line 97: | Line 85: | ||
|- | |- | ||
|} | |} | ||
'''Remarks''' | '''Remarks''' | ||
| Line 105: | Line 91: | ||
<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> | <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> | ||
==Notes== | ==Notes== | ||
<html>By:  Stefan Kempter <a rel="author" href="https:// | <html>By:  Stefan Kempter <a rel="author" href="https://www.linkedin.com/in/stefankempter"><img style="margin:0px 0px 0px 0px;" src="/images/bookmarking/linkedin.png" width="16" height="16" title="By: Stefan Kempter | Profile on LinkedIn" alt="Author: Stefan Kempter, IT Process Maps GbR" /></a>, IT Process Maps.</p> | ||
<p> </p> | <p> </p> | ||
<p><small> | <p><small> | ||
<span itemscope="itemscope | <span itemprop="breadcrumb" itemscope itemtype="http://schema.org/BreadcrumbList"> | ||
<a href="https://wiki.en.it-processmaps.com/index.php/IT_Architecture_Management#Process_Description | <span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> | ||
</span> | <a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/IT_Architecture_Management#Process_Description"> | ||
<span | <span itemprop="name">Process Description</span></a> | ||
<a href="https://wiki.en.it-processmaps.com/index.php/IT_Architecture_Management#Definitions | <meta itemprop="position" content="1"></span> › | ||
</span> | <span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> | ||
<span | <a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/IT_Architecture_Management#Definitions"> | ||
<a href="https://wiki.en.it-processmaps.com/index.php/IT_Architecture_Management#Roles_.7C_Responsibilities | <span itemprop="name">Definitions</span></a> | ||
<meta itemprop="position" content="2"></span> › | |||
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> | |||
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/IT_Architecture_Management#Roles_.7C_Responsibilities"> | |||
<span itemprop="name">Roles</span></a> | |||
<meta itemprop="position" content="3"></span> | |||
</span> | </span> | ||
</small></p> | </small></p> | ||
| Line 133: | Line 122: | ||
<link itemprop="citation" href="https://wiki.de.it-processmaps.com/index.php/IT_Architecture_Management" /> | <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" /> | <link itemprop="citation" href="https://wiki.es.it-processmaps.com/index.php/ITIL_Gestion_de_la_Arquitectura_de_TI" /> | ||
<meta itemprop="Headline" content=" | <meta itemprop="Headline" content="Architecture Management" /> | ||
<link itemprop="isPartOf" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Design" /> | <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="primaryImageOfPage" href="https://wiki.en.it-processmaps.com/images/0/0e/It-architecture-management.jpg" /> | ||
<link itemprop="author" href="https:// | <span id="https://wiki.en.it-processmaps.com/images/0/0e/It-architecture-management.jpg" itemprop="image" itemscope itemtype="https://schema.org/ImageObject"> | ||
<meta itemprop="caption" content="Architecture Management"> | |||
<meta itemprop="contentUrl" content="https://wiki.en.it-processmaps.com/images/0/0e/It-architecture-management.jpg" /> | |||
<meta itemprop="width" content="1200" /> | |||
<meta itemprop="height" content="1200" /> | |||
<meta itemprop="representativeOfPage" content="true"/> | |||
<meta itemprop="dateCreated" content="2011-09-19" /> | |||
<meta itemprop="dateModified" content="2020-06-20" /> | |||
<span itemprop="thumbnail" itemscope itemtype="https://schema.org/ImageObject"> | |||
<meta itemprop="url" content="https://wiki.en.it-processmaps.com/images/thumb/0/0e/It-architecture-management.jpg/600px-It-architecture-management.jpg" /> | |||
<meta itemprop="width" content="600" /> | |||
<meta itemprop="height" content="600" /> | |||
</span> | |||
<meta itemprop="keywords" content="Architecture Management" /> | |||
<meta itemprop="keywords" content="ITIL Architecture Management" /> | |||
<meta itemprop="keywords" content="IT Architecture Management" /> | |||
</span> | |||
<link itemprop="author" href="https://www.linkedin.com/in/stefankempter" /> | |||
<meta itemprop="author" content="Stefan Kempter" /> | <meta itemprop="author" content="Stefan Kempter" /> | ||
<meta itemprop="creator copyrightHolder publisher" content="IT Process Maps" /> | <meta itemprop="creator copyrightHolder publisher" content="IT Process Maps" /> | ||
| Line 142: | Line 148: | ||
<!-- This page is assigned to the following categories: --> | <!-- This page is assigned to the following categories: --> | ||
[[Category:ITIL V3]][[Category:ITIL | [[Category:ITIL 4]][[Category:ITIL 2011]][[Category:ITIL V3]][[Category:ITIL practice]][[Category:ITIL process]][[Category:Service Design|Architecture Management]][[Category:Architecture Management|!]] | ||
<!-- --- --> | <!-- --- --> | ||
Latest revision as of 12:54, 31 December 2023
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
Process Description
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).
ITIL 4 refers to 'Architecture Management' as a general management practice.
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.
| 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
