Evaluation of the Design Metric to Reduce the Number of Defects in Software Development

Full Text (PDF, 239KB), PP.9-17

Views: 0 Downloads: 0


M. Rizwan Jameel Qureshi 1,* Waseem A. Qureshi 2

1. Faculty of Computing & Information Technology of King Abdul Aziz University, Jeddah, Saudi Arabia

2. Corporate Operations Division, Banque Saudi Fransi, Head Office, Riyadh 11554, Saudi Arabia

* Corresponding author.

DOI: https://doi.org/10.5815/ijitcs.2012.04.02

Received: 20 May 2011 / Revised: 7 Oct. 2011 / Accepted: 26 Dec. 2011 / Published: 8 Apr. 2012

Index Terms

CK Metrics, Defects, Design, Quality, Case Study


Software design is one of the most important and key activities in the system development life cycle (SDLC) phase that ensures the quality of software. Different key areas of design are very vital to be taken into consideration while designing software. Software design describes how the software system is decomposed and managed in smaller components. Object-oriented (OO) paradigm has facilitated software industry with more reliable and manageable software and its design. The quality of the software design can be measured through different metrics such as Chidamber and Kemerer (CK) design metrics, Mood Metrics & Lorenz and Kidd metrics. CK metrics is one of the oldest and most reliable metrics among all metrics available to software industry to evaluate OO design. This paper presents an evaluation of CK metrics to propose an improved CK design metrics values to reduce the defects during software design phase in software. This paper will also describe that whether a significant effect of any CK design metrics exists on total number of defects per module or not. This is achieved by conducting survey in two software development companies.

Cite This Paper

M. Rizwan Jameel Qureshi, Waseem A. Qureshi, "Evaluation of the Design Metric to Reduce the Number of Defects in Software Development", International Journal of Information Technology and Computer Science(IJITCS), vol.4, no.4, pp.9-17, 2012. DOI:10.5815/ijitcs.2012.04.02


[1]S. Cara, E. Letha, and U. Dawn, “Computing Software Metrics from Design Documents,” in Proc. of the 42nd Annual Southeast Regional Conference, USA, p. 146-151, 2004.

[2]J. Capers, Software Quality: Analysis and Guidelines for success, International Thomson Computer Press, USA, 2000.

[3]S. Ramanath and M. Krishnan, “Empirical Analysis of CK Metrics for Object-Oriented Design Complexity: Implications for Software Defects,” IEEE Transactions on Software Engineering, vol. 29, pp. 297-310, 2003.

[4]H. T. Richard and J. C. Mark, Software Engineering, The Development Process, Wiley-IEEE Computer Society Press, USA, 2005.

[5]BORLAND ALM, Available at: http://www.borland.com/us/solutions/index.html (accessed 6 July 2011).

[6]K. Emam, “A Primer on Object-Oriented Measurement,” in Proc. of the 7th International Symposium on Software Metrics, UK, p. 185-187, 2001.

[7]S. R. Chidamber and C. F. Kemerer, “A Metrics Suite for Object-Oriented Design,” IEEE Transactions On Software Engineering, vol. 20, pp. 476-493, 1994.

[8]B. Saida, K. Emam, G. Nishith and N. R. Shesh, “Thresholds for Object-Oriented Measures,” In Proc. 11th International Symposium on Software Reliability Engineering, USA, p.24-38, 2000. 

[9]R. S. Pressman, Software Engineering A practitioner’s Approach, international edition, McGraw Hill, USA, 2005.

[10]Objecteering / UML, Objecteering / Metrics User Guide Version 5.3, Available at: http://www.objecteering.com/products_packaging.php, (accessed 6 July 2011).

[11]SD Metrics, “The Software Design Metrics tool for the UML”, Available at: http://www.sdmetrics.com/, (accessed 6 July 2011).