Abstract
Software inspection has been used to guarantee and control the quality of products by detecting defects, which can be spread out throughout the entire software life cycle. Therefore, the main premise is to identify and reduce the number of defect types in software artifacts during inspections. This work focuses on providing an up to dated overview of existing defects in the context of software inspection techniques. A systematic mapping was carried out, from which 2096 primary studies were retrieved and 32 were final selected. From the analysis, classification and aggregation of the retrieved studies, important different defect types were identified. Most studies encompass defect types by means of experiments and proposed techniques and approaches. Thus, as a main result, the identification of several different studies with distinct proposals concerned on defect types is evident. Although researchers have conducted studies over time, a general pattern on the detection of defects could not be established. Therefore, the scenario in which this study was carried out provides researchers with the capability of conducting further research in a motivating and challenging research topic, as well as practitioners with the adoption of empirically evaluated inspection techniques and respective defect types.
Highlights
A software system can incorporate different defect types that must be detected and removed throughout its life cycle
Amongst the discussed studies we observed distinct researches and issues in several scenarios, mostly experimental. This carried out Systematic Mapping (SM) is considered essential to identify studies that might mitigate any kind of support when detecting defects in software inspection techniques
It is important to emphasize the taxonomies and classification of defect types usually adapted for detecting defects based on requirements engineering
Summary
A software system can incorporate different defect types that must be detected and removed throughout its life cycle Such defects increase development and maintenance costs (Boehm and Basili, 2001). In this scenario, software inspection is a singular type of software review conducted by inspectors and formally applied in different software artifacts to maximize the number of defects found, in order to minimize defects in software systems to be delivered (Cheng and Jeffery, 1996; Fagan, 1986). The study of van Lamsweerde (2009) is evident in the literature by the singularity of the established classification scheme of defect types This classification can be used independently of the inspection techniques, usually adapted for detecting defects based on requirements engineering
Sign-in/Register to view highlights & summary 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 callDisclaimer: 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.
