SOFTWARE REQUIREMENT INSPECTION AND DEFECT DETECTION TECHNIQUES
Raghad I. Hussein
Faculty of pharmacy university of Kufa, Najaf, Iraq
Karrar AL-jammali
Faculty of pharmacy university of Kufa, Najaf, Iraq
Noor Sami Razzaq Najjar
Ministry of education, The General Directorate of Education in Najaf, Iraq
Nasrullah Pirzada
Department of Telecommunication Engineering, Mehran University of Engineering and Technology, Jamshoro, Pakistan
Sijjad Ali Khuhro
School of Computer Science and Technology, University of Science and Technology of China, Hefei, China
Abstract
Software requirement is something which is required or we can say that it is something wanted or needed from the software. In Webster’s dictionary requirements are basically, that is difference between needed and wanted, are called requirements? Software requirement defects are those which an inspector found in any aspect of the software during the inspection. There are many different types of defect detection techniques some are based on reading, some on the language used for requirement specifications and some are experimental replication, etc. When we talk about reading-based techniques then we found that Perspective Based Reading (PBR) is one of the best techniques for software inspection and to find defects and errors in it. PBR has been anticipated to advance the efficiency of software requirement inspection. This paper starts discussion from, the very beginning concept, what are defects to the concept of inspection and its importance. It also elaborates software defects, types, and reasons with its main focus on the PBR technique and how it improves the effectiveness of the software. In the end, I try to add a test case that shows the practical implementation of PBR and ad hoc techniques and try to prove my argument that PBR is one of the best.
Keywords:
: DBR, PBR, glimpse of an eye, Requirements
References
[1] V.R.BASILI, “evolving and packaging reading technologies”, Journal of systems and software, 38 (1): 3-12, July 1997.
[2] V.R.BASILI, F. Shull, and F. Lanubile, “Building Knowledge through the families of experiments”, Transactions on Software Engineering, August 1999.
[3] W. Boehm, “Software Engineering Economics”, Englewood Cliffs, 1981.
[4] M. Ciolkowksi, O. Laitenberger, "Empirical Investigation of Perspective-based Reading ", ISERN Report, 1997
[5] M. E. Fagan, "Design and Code Inspections in Program Development", IBM Systems Journal, 1976.
[6] M. E. Fagan, "Advances in Software Inspections", Transactions on Software Engineering, July 1986.
[7] P. Fusaro, F. Lanubile, "A Replicated Experiment to Assess Requirements Inspection Techniques", 1997.
[8] G. Buckberry, and J. Siddiqi, proceedings of the first international conference on Requirements Engineering, IEEE, 1994
[9] O. Laitenberger, T. Beil, T. Schwinn, "An industrial case study to examine a non-traditional inspection implementation for requirements specifications,", Los Alamitos CA, 2002.
[10] M. E. Fagan, "Design and Code Inspection to Reduce Errors in Program Development," IBM Systems Journal, vol. 15, 1976, pp. 182-211.
[11] Oliver Laitenberger, “A Survey of Software Inspection Technologies”, [12]Handbook on Software Engineering and Knowledge Engineering, Citeseer, 2002.
[12] Steven R. Rakitin. Software Verification and Validation for Practitioners and Managers, Artech House Publishers, 2nd edition (August 1, 2001).
Refbacks
- There are currently no refbacks.
