Scribd
Upload
518 views6 pages

TOGAF 9 Template - Architecture Change Request

This Architecture Change Request document proposes a change to Project XXXX for client YYYY. It includes sections for the purpose of the document, basic details of the change request, a description of the proposed change, and an analysis of the rationale for change and potential impacts. The Architecture Board will assess and approve the proposed change documented in this request.

Uploaded by

piero_zidane
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
518 views6 pages

TOGAF 9 Template - Architecture Change Request

This Architecture Change Request document proposes a change to Project XXXX for client YYYY. It includes sections for the purpose of the document, basic details of the change request, a description of the proposed change, and an analysis of the rationale for change and potential impacts. The Architecture Board will assess and approve the proposed change documented in this request.

Uploaded by

piero_zidane
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 6

Architecture Change Request

Project XXXX
Client YYYY
<<Note: This document provides a generic template. It may require tailoring to suit a specific client and
project situation.>>
Table of Contents
1 Purpose of this ocument...........................................................................................................................................!
" #asic etails...............................................................................................................................................................$
! %hange escription.....................................................................................................................................................&
$ %hange 'ationale and Impacts....................................................................................................................................(
Document Information
Project Name: Project )))
Prepared By: Document Version No: *.1
Title: +rchitecture %hange 'equest Document Version Date:
Reviewed By: Review Date:
Distribution List
From Date Phone/Fax/mail
To !ction" Due Date Phone/Fax/mail
, +ction Types: +pprove- 'evie.- Inform- /ile- +ction 'equired- +ttend 0eeting- 1ther 2please specify3
Document Version Histor
Version
Num#er
Version
Date Revised By Description Filename
T14+/5 6 Template: +rchitecture %hange 'equest "
%opyright 7 "*1* The 1pen 4roup. +ll rights reserved. T14+/5 is a trademar8 of The 1pen 4roup.
! Pur"ose of this Document
This document is an +rchitecture %hange 'equest for the <<))) project>>.
The goal of an architecture change management process is to ensure that the architecture achieves its
original target 9usiness value. This includes managing changes to the architecture in a cohesive and
architected .ay. The change management process .ill determine:
The circumstances under .hich the enterprise architecture- or parts of it- .ill 9e permitted to change
after deployment- and the process 9y .hich that .ill happen
The circumstances under .hich the architecture development cycle .ill 9e initiated again to develop
a ne. architecture
The +rchitecture #oard assesses and approves +rchitecture %hange 'equests.
T14+/5 6 Template: +rchitecture %hange 'equest !
%opyright 7 "*1* The 1pen 4roup. +ll rights reserved. T14+/5 is a trademar8 of The 1pen 4roup.
# $asic Details
$han%e &D <<I to uniquely identify this change request>>
$han%e Title <<1ne:line summary title for the change>>
$han%e Re'uestor <<Name>>
<<Position>>
<<1rgani;ation>>
<<<mail>>
<<Tel>>
$han%e (ponsor)s* <<etails of 9usiness sponsors for this change>>
Deadline <<+ny deadline for implementing the change- including reason>>
T14+/5 6 Template: +rchitecture %hange 'equest $
%opyright 7 "*1* The 1pen 4roup. +ll rights reserved. T14+/5 is a trademar8 of The 1pen 4roup.
% Change Descri"tion
<<escri9e the change that is proposed. 21ther documents may 9e referenced .here necessary.3>>
T14+/5 6 Template: +rchitecture %hange 'equest &
%opyright 7 "*1* The 1pen 4roup. +ll rights reserved. T14+/5 is a trademar8 of The 1pen 4roup.
& Change Rationale an' Im"acts
&(! Dri)ers for Change
The follo.ing drivers for change are relevant 2provide notes on all that apply3.
Business Drivers
Business+as+usual developments
Business exceptions
Business innovations
Business technolo%y innovations
(trate%ic chan%e
Technolo%y Drivers
New technolo%y reports
!sset mana%ement cost reductions
Technolo%y withdrawal
(tandards initiatives
,perational Drivers
&mprovements #ased on operational experience
$apacity plannin%
&(# Change Rationale
<<+ny further rationale to justify the change. Include an analysis of the implications of no change.>>
&(% Antici"ate' Im"acts
<<Provide- as far as possi9le- a 9rief initial vie. on the li8ely impacts of the change. /or e=ample-
anticipated architecture re.or8 required- system changes li8ely to result- affected 9usiness areas.>>
<<+n initial indication only is required here > a full 'equirements Impact +ssessment may 9e done as a
follo.:up activity if further investigation is deemed necessary.>>
T14+/5 6 Template: +rchitecture %hange 'equest (
%opyright 7 "*1* The 1pen 4roup. +ll rights reserved. T14+/5 is a trademar8 of The 1pen 4roup.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy