Figure Defect injection rate in different iterations ACIC project

Table 11.8. Root Causes and Preventive Actions for the ACIC Project

Defect Type (Number of Defects)

Root Cause

Preventive Action

Assigned To

Standards (17)

Lack of programming experience

Training.

Self

Oversight

Developers should read the coding standards carefully and adhere to them strictly.

Self

Lack of understanding of program specs use and need

(i) Come up with a method to generate program specs from Rational Rose. (ii) Prepare a checklist for reviewing program specs. (iii) Prepare guidelines for writing program specs.

xxxx

Coding standards not updated

Update coding standards and prepare a document listing the applicable project-specific UI standards.

xxxx

Redundant Code (11)

Lack of understanding of language

Training.

xxxx

Lack of understanding of object model and database

(i) Training on database structure. (ii) Developer should go through the object model thoroughly.

Session on DB to be taken by xxxxx

Lack of understanding of existing code

Group to discuss in a meeting and finalize the set of general method calls and identify where they should be called from.

Team

Lack of understanding of table model

Understand the functionality of table model and dependency on Table Selection and inform the team about it.

xxxx

Logic (19)

Lack of understanding of existing code

Arrange code reading sessions.

Self

Lack of programming experience

Training.

xxxx

Lack of understanding of sequence diagrams representations

Give training in Rational Rose.

xxxx

Lack of understanding of database and associated processes.

Same as earlier.

xxxx

Lack of understanding of object model

Same as earlier.

Self

Oversight

Self-testing by programmer should be made more thorough. A session on how to test a small part of code to be taken.

Training by xxxx

Lack of understanding of use cases

Developers will do a requirement walkthrough.

Self

Lack of understanding of business rules

(i) Developer to refer to the matrix available that deals with various rules. (ii) Developer to review use cases of earlier application for better understanding of business rules.

Self

Lack of understanding of defect

Follow-up with the reviewer should be taken by the owner of the defect. An attempt shall be made to reduce any existing communication gaps by more frequent follow-ups of the issues with the team/member concerned.

Team

Reduction in defect injection implies that there are fewer defects to be detected and fixed. Hence, a successful defect prevention activity should lead to reduction in the rework effort that follows testing. Figure 11.9 shows the rework effort in the three iterations. (This rework effort is obtained from the WAR because there is a different code for rework, and the program and module are also specified.) The rework effort after the first construction iteration was about 16% of the total effort for that iteration. This effort fell to about 5% and 3% in the next two construction cycles. The effort spent in the causal analysis was a few hours for data analysis, along with a brainstorming meeting of about in defect prevention.

Was this article helpful?

0 0
Project Management Made Easy

Project Management Made Easy

What you need to know about… Project Management Made Easy! Project management consists of more than just a large building project and can encompass small projects as well. No matter what the size of your project, you need to have some sort of project management. How you manage your project has everything to do with its outcome.

Get My Free Ebook


Post a comment