<Project Name>

Change Request Report < CR ID >

 

Version <1.0>

 

 

[Note: The following template is provided for use with the Unified Process for EDUcation. Text enclosed in square brackets and displayed in blue italics (style=InfoBlue) is included to provide guidance to the author and should be deleted before publishing the document. A paragraph entered following this style will automatically be set to normal (style=Body Text).]

[To customize automatic fields in Microsoft Word (which display a gray background when selected), select File>Properties and replace the Title, Subject and Company fields with the appropriate information for this document. After closing the dialog, automatic fields may be updated throughout the document by selecting Edit>Select All (or Ctrl-A) and pressing F9, or simply click on the field and press F9. This must be done separately for Headers and Footers. Alt-F9 will toggle between displaying the field names and the field contents. See Word help for more information on working with fields.]


Revision History

Date

Version

Description

Author

<dd/mmm/yy>

<x.x>

<details>

<name>

 

 

 

 

 

 

 

 

 

 

 

 

 


Table of Contents

1.    Introduction.. 4

1.1      Purpose. 4

1.2      Scope. 4

1.3      Definitions, Acronyms, and Abbreviations. 4

1.4      References. 4

1.5      Overview... 4

2.    Change Request Report.. 5


Change Request Report < CR ID >

1.                  Introduction

[The introduction of the Change Request provides an overview of the entire document. It includes the purpose, scope, definitions, acronyms, abbreviations, references, and overview of this Change Request.]

1.1                Purpose

[Specify the purpose of this Change Request.]

1.2               Scope

[A brief description of the scope of this Change Request; what model it is associated with and anything else that is affected or influenced by this document.]

1.3               Definitions, Acronyms, and Abbreviations

[This subsection provides the definitions of all terms, acronyms, and abbreviations required to properly interpret the Change Request.  This information may be provided by reference to the project's Glossary.]

1.4               References

[This subsection provides a complete list of all documents referenced elsewhere in the Change Request.  Identify each document by title, report number if applicable, date, and publishing organization. Specify the sources from which the references can be obtained. This information may be provided by reference to an appendix or to another document.]

1.5               Overview

[This subsection describes what the rest of the Change Request contains and explains how the document is organized.]

 


2.                  Change Request Report

 

[This template report is used for enhancements, new requirements or other requests, excluding Defects]

Change Request for <Project Name>

Created on: <dd/mm/yy>

Identification

Title:

Priority:

Status: 

Submitted on: 

Change Request ID: <>

Submitter:

Type: <>

 

Current Problem

 

Description:

Critical Failure:

Nuisance:

Source of the Problem:

 

Enhancement/New Requirement/Other:

 

 

Observation conditions:

 

 

Proposed Change (Submitter)

 

Description:

 

 

Proposed Change (Review Team)

 

Approval:

 

Reviewed Description:

Affected Configuration Items

Category

Enhancement/New Requirements/Other

 

 

 

 

 

 

 

Resolution

 

Estimated effort (staff hours): 

 

Change Review Team Disposition

Changes approved and accepted on:

By:

Changes implemented on:

By:

 


[This template report is used for Defects]

Change Request for <Project Name>

Created on: <dd/mm/yy>

Identification

Title:

Priority:

Status: 

Submitted on: 

Change Request ID: <>

Related Defect ID: <>

Submitter:

Type: Defect

 

Defect Information

 

Refer to the following Defect report: []

Defect Review Team Disposition

Defect approved and accepted on:

By:

Defect corrected on:

By: