<Project Name>

Defect Report < Defect 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. Defect Report.. 5

Defect Report < Defect ID >

1. Introduction

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

1.1 Purpose

[Specify the purpose of this Defect.]

1.2 Scope

[A brief description of the scope of this Defect; 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 Defect.  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 Defect.  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 Defect contains and explains how the document is organized.]

2. Defect Report

[This template report is used in conjunction with its related Change Request Report]

Defect for <Project Name>					Created on: <dd/mm/yy>
Identification
Title:			Priority:			Status:
			Submitted on:
			Defect ID: <> Related Change Request ID: <>
Submitter:			Type: Defect
Current Defect
Description:			Critical Failure:
			Nuisance:
			Source of the defect:
Observation conditions:
Current Environment § Hardware : § Operating System : § Compiler :
Proposed Change (Submitter)
Description:
Proposed Change (Review Team)
Approval:	Reviewed Description:
Affected Configuration Items	Category			Error Fix
Resolution
Affected number lines of code:
Estimated effort (staff hours):
Assessment
Tests methods: §		Test Platforms: §
Test cases: