Togaf 9 template architecture change request
•
1 like•1,289 views
Togaf 9 template,architecture change request
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Togaf 9 template architecture change request
Similar to Togaf 9 template architecture change request (20)
More from Sandeep Sharma IIMK Smart City,IoT,Bigdata,Cloud,BI,DW
More from Sandeep Sharma IIMK Smart City,IoT,Bigdata,Cloud,BI,DW (20)
Recently uploaded
Recently uploaded (20)
Togaf 9 template architecture change request
- 1. 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.>>
- 2. Table of Contents 1 Purpose of this Document...........................................................................................................................................3 2 Basic Details...............................................................................................................................................................4 3 Change Description.....................................................................................................................................................5 4 Change Rationale and Impacts....................................................................................................................................6 Document Information Project Name: Project XXX Prepared By: Document Version No: 0.1 Title: Architecture Change Request Document Version Date: Reviewed By: Review Date: Distribution List From Date Phone/Fax/Email To Action* Due Date Phone/Fax/Email * Action Types: Approve, Review, Inform, File, Action Required, Attend Meeting, Other (please specify) Document Version History Version Version Number Date Revised By Description Filename TOGAF™ 9 Template: Architecture Change Request 2 Copyright © 2010 The Open Group. All rights reserved. TOGAF™ is a trademark of The Open Group.
- 3. 1 Purpose of this Document This document is an Architecture Change Request for the <<XXX project>>. The goal of an architecture change management process is to ensure that the architecture achieves its original target business value. This includes managing changes to the architecture in a cohesive and architected way. The change management process will determine: · The circumstances under which the enterprise architecture, or parts of it, will be permitted to change after deployment, and the process by which that will happen · The circumstances under which the architecture development cycle will be initiated again to develop a new architecture The Architecture Board assesses and approves Architecture Change Requests. TOGAF™ 9 Template: Architecture Change Request 3 Copyright © 2010 The Open Group. All rights reserved. TOGAF™ is a trademark of The Open Group.
- 4. 2 Basic Details Change ID <<ID to uniquely identify this change request>> Change Title <<One-line summary title for the change>> Change Requestor <<Name>> <<Position>> <<Organization>> <<Email>> <<Tel>> Change Sponsor(s) <<Details of business sponsors for this change>> Deadline <<Any deadline for implementing the change, including reason>> TOGAF™ 9 Template: Architecture Change Request 4 Copyright © 2010 The Open Group. All rights reserved. TOGAF™ is a trademark of The Open Group.
- 5. 3 Change Description <<Describe the change that is proposed. (Other documents may be referenced where necessary.)>> TOGAF™ 9 Template: Architecture Change Request 5 Copyright © 2010 The Open Group. All rights reserved. TOGAF™ is a trademark of The Open Group.
- 6. 4 Change Rationale and Impacts 4.1 Drivers for Change The following drivers for change are relevant (provide notes on all that apply). Business Drivers Business-as-usual developments Business exceptions Business innovations Business technology innovations Strategic change Technology Drivers New technology reports Asset management cost reductions Technology withdrawal Standards initiatives Operational Drivers Improvements based on operational experience Capacity planning 4.2 Change Rationale <<Any further rationale to justify the change. Include an analysis of the implications of no change.>> 4.3 Anticipated Impacts <<Provide, as far as possible, a brief initial view on the likely impacts of the change. For example, anticipated architecture rework required, system changes likely to result, affected business areas.>> <<An initial indication only is required here – a full Requirements Impact Assessment may be done as a follow-up activity if further investigation is deemed necessary.>> TOGAF™ 9 Template: Architecture Change Request 6 Copyright © 2010 The Open Group. All rights reserved. TOGAF™ is a trademark of The Open Group.
- 7. 4 Change Rationale and Impacts 4.1 Drivers for Change The following drivers for change are relevant (provide notes on all that apply). Business Drivers Business-as-usual developments Business exceptions Business innovations Business technology innovations Strategic change Technology Drivers New technology reports Asset management cost reductions Technology withdrawal Standards initiatives Operational Drivers Improvements based on operational experience Capacity planning 4.2 Change Rationale <<Any further rationale to justify the change. Include an analysis of the implications of no change.>> 4.3 Anticipated Impacts <<Provide, as far as possible, a brief initial view on the likely impacts of the change. For example, anticipated architecture rework required, system changes likely to result, affected business areas.>> <<An initial indication only is required here – a full Requirements Impact Assessment may be done as a follow-up activity if further investigation is deemed necessary.>> TOGAF™ 9 Template: Architecture Change Request 6 Copyright © 2010 The Open Group. All rights reserved. TOGAF™ is a trademark of The Open Group.