Change-cases-work-product.doc

Change Cases Work Product for [XYZ Project]

Author: [Author Name] Date: [Date] Version: [Version Number] Filename: 413715700.doc

413715700.doc

1 Document Control 1.1 Change History Version

Author

Date

Change Description

1.2 Security Classification This document is classified as [Unclassified, Internal Use Only, Confidential, etc].

413715700.doc

2 Introduction This document captures the Change Cases for [insert project or scope]. [Change Cases are known or likely future requirements which may in some way influence the design of the current system (i.e. ensure the architecture can easily accommodate them). They often arise from deferring requirements from a current project to meet the desired schedule or from Enterprise Architecture Target Architecture when the current project moves us toward the Target to some degree but does not moves us completely to the Target. Change Cases are discussed in ‘Best Practice for Application Management’ [OGC2002].] [OGC2002] [Title: ‘Best Practice for Application Management’, ITIL, The Key to Managing IT services. Publisher: The Stationary Office (TSO) / Office of Government Commerce (OGC) ISBN: 0 11 330866 3, 2002 Edition. Chapter 5.2.5.]

413715700.doc

3 Change Cases 3.1 Change Case [xxx] – Change Case Name Change Case id

[A unique reference for each Change Case in the document, for instance 001, 002, etc]

Requirement

[A description of the requirement.]

Impact Analysis

[A description of how the Change Case may impact the solution architecture, this may alter any part of the architecture. Consider how the application, integration and technology (infrastructure) maybe need to be altered to accommodate the future change.]

- End of Document -

413715700.doc