[Defect Tracking]

Document Basic Information

Project Name: PM Name:

[Document Version History]

Ver. No. Ver. Date Prepared By Reviewed By Approved By Description PIO No.

[Template Version History]

Ver. No. Ver. Date Prepared By Reviewed By Approved By Description PIO No.
V1.0 24-Feb-12 Lily Guo E2E Group Jerry Song Initial Baseline
WARNING: The following disclaimer and copyright notices must be customised for your local territory - if you
need assistance with appropriate wording, contact your local Risk Management or Office of General Counsel.

This publication has been prepared for general guidance on matters of interest only, and does not constitute professional advice.
You should not act upon the information contained in this publication without obtaining specific professional advice. No
representation or warranty (express or implied) is given as to the accuracy or completeness of the information contained in this
publication, and, to the extent permitted by law, PricewaterhouseCoopers Information Technologies (Shanghai) Co., Ltd.. &
PricewaterhouseCoopers Service Delivery center (Bangalore) Pvt Ltd., its members, employees and agents do not accept or assume
any liability, responsibility or duty of care for any consequences of you or anyone else acting, or refraining to act, in reliance on the
information contained in this publication or for any decision based on it.

2012 PricewaterhouseCoopers Information Technologies (Shanghai) Co., Ltd.. & PricewaterhouseCoopers Service Delivery center
(Bangalore) Pvt Ltd.. All rights reserved. In this document, PwC refers toPricewaterhouseCoopers Information Technologies
(Shanghai) Co., Ltd.. & PricewaterhouseCoopers Service Delivery center (Bangalore) Pvt Ltd. which is a member firm of
PricewaterhouseCoopers International Limited, each member firm of which is a separate legal entity.
 Document Title 04/04/2017 350467244.xlsx:Instructions

Instructions
1 This document to be used in the absence of the defect tracking tool in the project.
2 This document is to be tailored as per the individual project requirements.

Field Name Description/Instructions

Defect ID Continuous serial number of the defect
Status Status of the defect as per the defect life cycle defined in the test plan. The values are prepopulated
Headline Short description of the defect
Priority Priority owner to fix the defect
Severity Severity of the defect which has prepopulated values
Module Module of the defect
TestCaseID Defect found in the Test Case
Defect Category Pre-delivery Defect or Post-delivery Defect
Defects caused by outside PwC Advisory SDC, such as:
Customer provides the wrong requirements
Customer don't know their requirements clearly
Root Cause Materials from outside contains defects
Phase Found In which phase of the project defect is reported
Version Found The version number of the release
Test Type Review, Unit Test,Module Test, System Test, Integration Test and UAT
Submitter Who found the defect
Submit Date Date of report the defect
Owner Who fix the defect
Defect Type Refer to tab of Defect Type
Root Cause Refer to tab of Root Cause
Phase Introduced Phase in the lifecycle of the project where origin of defect
Rework Effort Man hours to fix defect
Affect Work Product Products are modifed
Fix Date Date the defect pass testing

Project - Doc Number - Doc Version - Disposition {Draft/Final} - INDUSTRY NAME - 3

 Document Title 04/04/2017 350467244.xlsx:DefectTracking

plate can be re-arranged according to each project's needs>

Submit Fields
Headline/Descripti TestCase
Defect ID Status on Priority Severity Component ID
1
2
3
4
5
6
7
8
9

Project - Doc Number - Doc Version - Disposition {Draft/Final} - INDUSTRY NAME - 4

 Document Title 04/04/2017 350467244.xlsx:DefectTracking

t Fields Analysis Field

Defect Phase Submit
Category Found Test Type Submitter Date Owner Defect Type
Testing 01/01/04
Testing
Testing
Testing
Testing
Testing
Testing
Testing
Testing
Testing
Testing
Testing
Testing
Testing
Testing

Project - Doc Number - Doc Version - Disposition {Draft/Final} - INDUSTRY NAME - 5

 Document Title 04/04/2017 350467244.xlsx:DefectTracking

Analysis Field Fix Field

Phase Rework Affect Work
Root Cause Introduced Effort Fix Date Product Comments
Requirement 01/02/12

Project - Doc Number - Doc Version - Disposition {Draft/Final} - INDUSTRY NAME - 6

 Document Title 04/04/2017 350467244.xlsx:Defect Type

Defect Type - Anomaly Classification by Type

IEEE Standard
1 Logic problem
1.1 Forgotten cases or steps
1.2 Duplicate logic
1.3 Extreme condition neglected
1.4 Unnecessary functions
1.5 Misinterpretation
1.6 Missing condition test
1.7 Checking wrong variable
1.8 Iterate loop incorrectly
2 Computational problem
2.1 Equation insufficient or incorrect
2.1.1
Development environment or tools contain defects, 2.1.2
it is out of PwC Advisory SDC control
2.1.3

Defects caused by outside PwC Advisory SDC, such Precision loss

as:
Customer provides the wrong requirements
Customer don't know their requirements clearly
Materials from outside contains defects

2.2.1
2.2.2
2.3 Sign convention fault
3 Interface problem
3.1 Interrupt handled incorrectly
3.2 I/O timing incorrect
3.2.1
3.3 Subroutine module mismatch
3.3.1
3.3.2
3.3.3
3.3.4
3.4 User Interface Problem
4 Data handling problem
4.1 Initialize data incorrectly
4.2 Accessed or stored data incorrectly
4.2.1
4.2.2
4.2.3
4.2.4
4.3 Scaling or units of data incorrect
4.4 Dimensioned data incorrectly
4.4.1
4.4.2
4.5 Scope of data incorrect
4.6 Sensor data incorrect or missing
4.7 Operator data incorrect or missing

2007 BearingPoint, Inc. and/or its affiliate(s) Project - Doc Number - Doc Version - Disposition {Draft/Final} - INDUSTRY NAME - 7
 Document Title 04/04/2017 350467244.xlsx:Defect Type

4.8 External data incorrect or missing

4.9 Embedded data in tables incorrect or missing
4.10 Output data incorrect or missing
4.11 Input data incorrect or missing
5 Format problem
6 Enhancement
6.1 Output style enhancement
6.2 User interface enhancement
7 Requirements
7.1 Missing Requirement
7.2 Incorrect Requirement
8 Documentation
9 Others

2007 BearingPoint, Inc. and/or its affiliate(s) Project - Doc Number - Doc Version - Disposition {Draft/Final} - INDUSTRY NAME - 8
 Document Title 04/04/2017 350467244.xlsx:Defect Type

Classification by Type
andard

Forgotten cases or steps

Duplicate logic
Extreme condition neglected
Unnecessary functions
Misinterpretation
Missing condition test
Checking wrong variable
Iterate loop incorrectly

Equation insufficient or incorrect

Missing computation
Operand in equation incorrect

Parentheses used incorrectly or not used

Precision loss

Rounding or truncation fault

Mixed mode
Sign convention fault

Interrupt handled incorrectly

I/O timing incorrect
Timing fault cases data loss
Subroutine module mismatch
Wrong subroutine called
Incorrectly located subroutine call
Nonexistent subroutine
Inconsistent subroutine arguments
User Interface Problem

Initialize data incorrectly

Accessed or stored data incorrectly
Flag or index set incorrectly
Packed/Unpacked incorrectly
Referenced wrong data variable
Data referenced out of bounds
Scaling or units of data incorrect
Dimensioned data incorrectly
Variable type incorrect
Subscripted variable incorrectly
Scope of data incorrect
Sensor data incorrect or missing
Operator data incorrect or missing

2007 BearingPoint, Inc. and/or its affiliate(s) Project - Doc Number - Doc Version - Disposition {Draft/Final} - INDUSTRY NAME - 9
 Document Title 04/04/2017 350467244.xlsx:Defect Type

External data incorrect or missing

Embedded data in tables incorrect or missing
Output data incorrect or missing
Input data incorrect or missing

Output style enhancement

User interface enhancement

Missing Requirement
Incorrect Requirement

2007 BearingPoint, Inc. and/or its affiliate(s) Project - Doc Number - Doc Version - Disposition {Draft/Final} - INDUSTRY NAME - 10
Document Title 04/04/2017 350467244.xlsx:Root Cause

Possible Root Causes

Root Cause
Lacks knowledge/skills

Inadequate training

External Communication Gap

Internal Communication Gap

Manual Errors
Not accounting for all details of the problem
Incomplete process/guidelines/standards
Process Deviation
Corrective actions not implemented
Inadequate Monitoring and control
Inadequate inspection /review

Defective development tool

Inefficient Development Technology Method (Architectural
Failure)

Insufficient and/or unclear requirements.

Development environments

Incomplete/Inconsistent requirements/design/code
Unstable Requirement
Lack of UT
Operation outside of SDC's scope

2007 BearingPoint, Inc. and/or its affiliate(s) Project - Doc Number - Doc Version - Disposition {Draft/Final} - INDUSTRY NAME - 11
 Document Title 04/04/2017 350467244.xlsx:Root Cause

Possible Root Causes

Explanation
The defect is caused due to the lack of technical knowledge/skill of
the individual.
The defect is caused due to insufficient/inadequate training provided
to the project team.
The defect is caused due to communication errors with clients or
external groups.
The Defect is caused due to insufficient communications within
internal groups.
The defect is caused due to inexperience staff or carelessness.
The defect is caused due to non detail-orientated working style.
The defect is caused due to inadequate process/guidelines/standards.
The defect is caused due to not following the defined process or non-
compliance.
The defect is caused due to the failure of implementation of the
corrective
The defectactions bydue
is caused the to
project.
the failure of project monitoring and
control
The activity.
defect is caused due to improper inspection/review of work
product.
The defect is caused due to development tools.
The defect is caused due to inefficient development
technology/methodology (Architectural Failure) for meeting the
requirement.
The defect is caused due to lack of clarity of requirement from the
customer.
The defect For example
is caused duedefective artifact received
to inconsistencies in the as input.
environment/infrastructure used for software development.
The defect
Defects is caused
caused due toSDC,
by outside lack such
of clarity
as: of Design/Code
Requirement
Customer changed
provides themore
wrong than twice during the development
requirements
No unit testing
Customer don'tor not their
know enough unit testingclearly
requirements was performed
Materials from outside contains defects

2007 BearingPoint, Inc. and/or its affiliate(s) Project - Doc Number - Doc Version - Disposition {Draft/Final} - INDUSTRY NAME - 12