Abstract
“Discovering the unexpected is more important than confirming the known [7]. In software development, the “unexpected” one relates to defects. These defects when unattended would cause failure to the product and risk to the users. The increasing dependency of society on software and the crucial consequences that a failure can cause requires the need to find out the defects at the origin itself. Based on the lessons learnt from the earlier set of projects, a defect framework highlighting the 5 Dimensions (Ds) of defect origin is proposed in this work. The defect framework is based on analyzing the defects that had emerged from various stages of software development like Requirements, Design, Coding, Testing and T imeline (defects due to lack of time during development). This study is not limited to just identifying the origin of defects at various phases of software development but also finds out the reasons for such defects, and defect preventive (DP) measures areproposed for each type of defect. This work can help practitioners choose effective defect avoidance measures. In addition to arriving at defect framework, this work also proposes a defect injection metric based on severity of the defect rather than justdefect count, which gives the number of adjusted defects produced by a project at various phases. The defect injection metric value, once calculated, serves as a yardstick to make a comparison in the improvements made in the software process development b etween similar set of projects.
Highlights
Profound confusion prevails at the final stages of software development as to which defect discovered belongs to which phase of software development life cycle
This paper proposes defect injection metric that finds out the defect count under each phase of software development and for the project as a whole
4.1 Overall Results Based on defect type, the appropriate defect prevention action as suggested in this study was implemented in the set of projects done during the year 2011
Summary
Profound confusion prevails at the final stages of software development as to which defect discovered belongs to which phase of software development life cycle. Techniques like rootcause analysis and orthogonal defect classification are some of the commonly used practices. These Techniques are applied jointly with the software process to determine each defect attribute in terms of its type, trigger, source etc [3]. The need is to find a mechanism to determine the origin of those defects and ways to eliminate them at origin itself and the same has been realised in this study by way of proposing defect prevention mechanism for each defect type under 5Ds. Everybody likes Defect prevention as nobody likes defects, especially those defects that are found by our customers. We need to stop defects from reaching our customers by catching them before
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callMore From: International Journal of Software Engineering & Applications
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
