Abstract

High quality and cost effective software development entails early detection of errors from requirement specification artifact/s. For this purpose, various inspection techniques have been presented to identify requirement specification errors. In most reported studies, comparison of two commonly used inspection techniques CBR (Checklist Based Reading) and PBR (Perspective Based Reading) had been conducted to identify defects from the UCS (Use Case Specification); however no comparison was done based on IEEE STD 830-1998 defects’ types. Therefore, a novel checklist was developed to identify the IEEE STD 830-1998 specified defects’ types namely Ambiguousness, Incorrectness, Inconsistency and Incompleteness from UCS, a major contribution of this research. This developed checklist was later validated to be utilized during this experimental research. In this study, a quasi-experiment was conducted with industrial professionals to compare the effectiveness and efficiency of CBR and PBR using the developed checklist to inspect the UCS that was specified in Use Case 2.0 format. The result of this research showed significant difference between CBR and PBR, i.e. PBR found more defects for all defects’ types compared to the CBR technique, but CBR reported less False Positive defects by applying the developed checklist for all defects’ types. It was also proved that CBR is more efficient (time based) than PBR for all defects’ types. These findings will provide guidelines to industry practitioners for the selection of an inspection technique based on effectiveness, efficiency and false positive ratio for a particular type of defect.

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 call

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.