International Journal of Modern Education and Computer Science (IJMECS)

ISSN: 2075-0161 (Print), ISSN: 2075-017X (Online)

Published By: MECS Press

IJMECS Vol.8, No.10, Oct. 2016

A Comparative Study of Software Inspection Techniques for Quality Perspective

Full Text (PDF, 460KB), PP.9-16

Views:200   Downloads:5


Asad Masood Qazi, Sidra Shahzadi, Mamoona Humayun

Index Terms

Software Inspection;Software Quality Assurance;Software Testing;Software Defects


Software inspection is useful to detect the defects in any stage software development methodology especially in early stages. Inspection of software defects can improve the software product quality by decreasing rework cost and time from documents, code, and other deliverables. The objective of this study is to identify existing software inspection techniques which help practitioners and software engineers to improve the software quality and to compare them according to some quality attributes. Rather than proposing new techniques we focus on synthesize the existing approaches. A comparison of some approaches is conducted and analyzed which approach is more feasible for the detection of defects. The results of this study show that there are many formal and informal techniques available in literature related software inspection, it is difficult to say well to one of them, but our analysis focused on finding such techniques which cover maximum quality factors in an inspection. Software inspection is an umbrella activity of whole software development life cycle and we found different approaches and frameworks in software inspection which can full fill our desired parameters to improve software quality. 

Cite This Paper

Asad Masood Qazi, Sidra Shahzadi, Mamoona Humayun,"A Comparative Study of Software Inspection Techniques for Quality Perspective", International Journal of Modern Education and Computer Science(IJMECS), Vol.8, No.10, pp.9-16, 2016.DOI: 10.5815/ijmecs.2016.10.02


[1]Parnas, D.L., Lawford, M.: "The role of Inspection in Software Quality Assurance". IEEE Transactions on Software Engineering 29(8) (2003)

[2]Abrahamsson, Pekka, Michele Marchesi, and Frank Maurer. Agile processes in software engineering and extreme programming. Springer, 2009.

[3]Radice, Ronald A. "High Quality Low Cost Software Inspections". Andover, Mass.: Paradox icon Publishing, Jan.2002.

[4]Taba, Navid Hashemi, and Siew Hock Ow. "A Scenario-Based Model to Improve the Quality of Software Inspection Process." Computational Intelligence, Modeling and Simulation (CIMSiM), 2012 Fourth International Conference on. IEEE, 2012.

[5]Taba, Navid Hashemi, and Siew Hock Ow. "Improving Software Quality Using a Defect Management-Oriented (DEMAO) Software Inspection Model." 2012 Sixth Asia Modelling Symposium. IEEE, 2012.

[6]Eickelmann, Nancy S., et al. "An empirical study of modifying the Fagan inspection process and the resulting main effects and interaction effects among defects found, effort required, rate of preparation and inspection, number of team members and product 1st pass quality." Software Engineering Workshop, 2002. Proceedings. 27th Annual NASA Goddard/IEEE. IEEE, 2002.

[7]Horta Travassos, Guilherme. "Software Defects: Stay Away from Them. Do Inspections!." Quality of Information and Communications Technology (QUATIC), 2014 9th International Conference on the. IEEE, 2014.

[8]Porter, Adam, Harvey Siy, and Lawrence Votta. "A review of software inspections." Advances in Computers 42 (1996): 39-76.

[9]Aurum, Aybuke, Håkan Petersson, and Claes Wohlin. "State‐of‐the‐art: software inspections after 25 years." Software Testing, Verification and Reliability 12.3 (2002): 133-154.

[10]Fagan, M. E. "Design and code inspections to reduce errors in program development." IBM Journal of Research and Development 15.3 (1976): 182. 

[11]Parnas, David L., and David M. Weiss. "Active design reviews: principles and practices." Proceedings of the 8th international conference on Software engineering. IEEE Computer Society Press, 1985.

[12]Bisant, David B., and James R. Lyle. "A two-person inspection method to improve programming productivity." IEEE Transactions on Software Engineering 10 (1989): 1294-1304.

[13]Martin, Johnny, and Wei Tek Tsai. "N-fold inspection: A requirements analysis technique." Communications of the ACM 33.2 (1990): 225-232.

[14]Knight, John C., and E. Myers. "An improved inspection technique." Communications of the ACM 36.11 (1993): 51-61.

[15]Votta Jr, Lawrence G. "Does every inspection need a meeting?" ACM SIGSOFT Software Engineering Notes 18.5 (1993): 107-114.

[16]Gilb, Tom, Dorothy Graham, and Susannah Finzi. Software inspection. Addison-Wesley Longman Publishing Co., Inc., 1993.

[17]Macdona, F., et al. "A review of tool support for software inspection." Computer-Aided Software Engineering, 1995. Proceedings, Seventh International conference.

[18]Sembugamoorthy, V., and L. Brothers. "ICICLE: Intelligent code inspection in a C language environment." Computer Software and Applications Conference, 1990. COMPSAC 90. Proceedings, Fourteenth Annual International. IEEE, 1990.

[19]Gintell, John, et al. "Scrutiny: A collaborative inspection and review system." Software Engineering—ESEC'93. Springer Berlin Heidelberg, 1993. 344-360.

[20]Mashayekhi, Vahid, et al. "Distributed, collaborative software inspection." Software, IEEE 10.5 (1993): 66-75.

[21]Knight, John C., and E. Myers. "An improved inspection technique." Communications of the ACM 36.11 (1993): 51-61.

[22]Johnson, Philip M., and Danu Tjahjono. "CSRS User Guide." (1993).

[23]Souza, Iuri Santos, et al. "Evidence of software inspection on feature specification for software product lines." Journal of Systems and Software 86.5 (2013): 1172-1190

[24]Elberzhager, Frank, Jürgen Münch, and Danilo Assmann. "Analyzing the relationships between inspections and testing to provide a software testing focus." Information and Software Technology 56.7 (2014): 793-806.

[25]Ackerman, A. Frank, Lynne S. Buchwald, and Frank H. Lewski. "Software inspections: an effective verification process." IEEE software 3 (1989): 31-36.

[26]Waqas Ali, Zia-Ur-Rehman, Akhter Badshah, Ali Javed,"Software Inspection in Software Industry: A Pakistan's Perspective", IJMECS, vol.7, no.3, pp.47-53, 2015.

[27]Jayatilake, S. M. D. J. T., et al. "Role of software inspections in the Sri Lankan software development industry." Computer Science & Education (ICCSE), 2013 8th International Conference on. IEEE, 2013.

[28]Kollanus, Sami, and Jussi Koskinen. "Software inspections in practice: Six case studies." Product-Focused Software Process Improvement. Springer Berlin Heidelberg, 2006. 377-382.

[29]O'Regan, Gerard. "Software Inspections Capability Maturity Model Integration." Introduction to Software Quality. Springer International Publishing, 2014. 101-118

[30]O'Regan, Gerard. Introduction to Software Quality. Springer New York, 2002.

[31]Boehm, Barry W. Software engineering economics. Vol. 197. Englewood Cliffs (NJ): Prentice-hall, 1981.

[32]Tyran, Craig K. "A software inspection exercise for the systems analysis and design course." Journal of Information Systems Education 17.3 (2006): 341.

[33]Porter, Adam, Lawrence G. Votta Jr, and Victor R. Basili. "Comparing detection methods for software requirements inspections: A replicated experiment." Software Engineering, IEEE Transactions on 21.6 (1995): 563-575.

[34]Cockram, Trevor. "Gaining confidence in software inspection using a Bayesian belief model." Software Quality Journal 9.1 (2001): 31-42.

[35]Adams, Edward N. "Optimizing preventive service of software products." IBM Journal of Research and Development 28.1 (1984): 2-14.

[36]Nagappan, Nachiappan, et al. "Preliminary results on using static analysis tools for software inspection." Software Reliability Engineering, 2004. ISSRE 2004. 15th International Symposium on. IEEE, 2004.

[37]Parab, Jivan S. Exploring C for microcontrollers: A hands on approach. Springer Science & Business Media, 2007. 

[38]Van Emden, Maarten H. "Structured inspections of code." Software Testing, Verification and Reliability 2.3 (1992): 133-153.

[39]Lewis, Clayton, et al. "Testing a walkthrough methodology for theory-based design of walk-up-and-use interfaces." Proceedings of the SIGCHI conference on Human factors in computing systems. ACM, 1990.

[40]Hedberg, Henrik, and Jouni Lappalainen. "A preliminary evaluation of software inspection tools, with the DESMET method." Quality Software, 2005. (QSIC 2005). Fifth International Conference on. IEEE, 2005.

[41]Harjumaa, Lasse. "Distributed software inspections-an experiment with Adobe Acrobat." Proceedings of the IASTED International Conferenceon Computer Science and Technology (2003): 26-31.

[42]Lanubile, Filippo, Teresa Mallardo, and Fabio Calefato. "Tool support for geographically dispersed inspection teams." Software Process: Improvement and Practice 8.4 (2003): 217-231.

[43]Powell, Daniel. "Tool support for verification-based software inspection." Software Engineering Conference, 2004. Proceedings. 2004 Australian. IEEE, 2004.

[44]Hussain, Fida, and Muhammad Saeed Shehzad. "" Robust and Flexible Software Inspection model" for Software Re-Engineering Process: Abstraction phase." 14th Asia-Pacific Software Engineering Conference (APSEC'07). 2007.

[45]Hashemitaba, Navid, and Siew Hock Ow. "Generative inspection: an intelligent model to detect and remove software defects." Intelligent Systems, Modeling and Simulation (ISMS), 2012 Third International Conference on. IEEE, 2012.

[46]Christenson, Dennis A., and Steel T. Huang. "A code inspection model for software quality management and prediction." Global Telecommunications Conference, 1988, and Exhibition.'Communications for the Information Age.'Conference Record, GLOBECOM'88, IEEE. IEEE, 1988.

[47]Biffl, Stefan, Michael Halling, and Monika Kohle. "Investigating the effect of a second software inspection cycle. Cost-benefit data from a large-scale experiment on re-inspection of a software requirements document." Quality Software, 2000. Proceedings. First Asia-Pacific Conference on. IEEE, 2000.