Assessing defect detection performance of interacting teams in object-oriented design inspection

Sabaliauskaite, Giedre; Kusumoto, Shoichi; Inoue, Katsuro

doi:10.1016/j.infsof.2004.03.004

Cited by 20 publications

(9 citation statements)

References 26 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Several studies [32,[53][54][55] have later supported Votta's findings. All these studies have reported that meetings did not improve defect finding as compared to various optional arrangements.…”

Section: Inspection Meetingsmentioning

confidence: 78%

Survey of Software Inspection Research

Kollanus¹,

Koskinen²

2009

TOSEJ

View full text Add to dashboard Cite

There is a great need to assure and improve the reliability and quality of software. Software inspections were introduced over 30 years ago as an answer for this need and they have inspired a lot of research covering many different kinds of aspects. There is a need for an up-to-date survey revealing the current state and the overall evolution of the most prominent research on the area. This paper presents a comprehensive survey focusing on the most relevant 16 international high-impact scientific publication series. There are 153 articles included in the survey covering both technical and management aspects. The main results include a description of the research trends during 1980-2008 and a description of the main results of the included studies. The description is organized based on a taxonomy of the inspection research as having emerged based on the survey. At general level the surveyed research provides clear evidence that inspections generally benefit software development and quality assurance. There are several proposed theoretical variations for the inspection process but also many empirical studies. Although the conducted research is relatively scattered, proper sciencebased understanding about some of the most studied issues has been achieved. Our main conclusion is that conducting empirical research needs to be continued in order to validate the effects of the different kinds of proposed theoretical constructs in practice. Empirical studies are needed especially in order to better understand the proper implementation and the actual impacts of applying inspections in different kinds of industrial and organizational settings.

show abstract

Section: Inspection Meetingsmentioning

confidence: 78%

Survey of Software Inspection Research

Kollanus¹,

Koskinen²

2009

TOSEJ

View full text Add to dashboard Cite

show abstract

“…Despite their initial success, Fagan inspections have several disadvantages that hinder their continuous and widespread use across organizations: They mandate a number of formal requirements that do not adapt well to agile development methods, most notably a fixed, formal, waterfall process [33]. Several studies have shown that review meetings do not improve defect finding [10,36,45,50]. Only one study reported contrary results [17].…”

Section: Related Workmentioning

confidence: 99%

Modern code reviews in open-source projects: which problems do they fix?

Beller

Bacchelli

Zaidman

et al. 2014

Proceedings of the 11th Working Conference on Mining Software Repositories

203

140

View full text Add to dashboard Cite

Code review is the manual assessment of source code by humans, mainly intended to identify defects and quality problems. Modern Code Review (MCR), a lightweight variant of the code inspections investigated since the 1970s, prevails today both in industry and open-source software (OSS) systems. The objective of this paper is to increase our understanding of the practical benefits that the MCR process produces on reviewed source code. To that end, we empirically explore the problems fixed through MCR in OSS systems. We manually classified over 1,400 changes taking place in reviewed code from two OSS projects into a validated categorization scheme. Surprisingly, results show that the types of changes due to the MCR process in OSS are strikingly similar to those in the industry and academic systems from literature, featuring the similar 75:25 ratio of maintainability-related to functional problems. We also reveal that 7-35% of review comments are discarded and that 10-22% of the changes are not triggered by an explicit review comment. Patterns emerged in the review data; we investigated them revealing the technical factors that influence the number of changes due to the MCR process. We found that bug-fixing tasks lead to fewer changes and tasks with more altered files and a higher code churn have more changes. Contrary to intuition, the person of the reviewer had no impact on the number of changes.

show abstract

“…In replications conducted by He and Carver [26] as well as Maldonado et al [27] this finding is supported. Also Porter et al [28] and [29], Laitenberger et al [30], Berling and Runeson [31], and Sabaliauskaite et al [32] report similar experiments with comparable findings.…”

Section: Related Experimentsmentioning

confidence: 64%

On the Impact of the Model-Based Representation of Inconsistencies to Manual Reviews

Daun

Brings

Weyer

2017

Conceptual Modeling

View full text Add to dashboard Cite

To ensure fulfilling stakeholder wishes, it is crucial to validate the documented requirements. This is often complicated by the fact that the wishes and intentions of different stakeholders are somewhat contradictory, which manifests itself in inconsistent requirements. To aid requirements engineers in identifying and resolving inconsistent requirements, we investigated the usefulness for manual reviews of two different model-based representation formats for inconsistent requirements; one that represent the inconsistent requirements in separate diagrams and one that represents them integrated into one diagram using annotations. The results from a controlled experiment show that the use of such integrated review diagrams can significantly increase efficiency of manual reviews, without sacrificing effectiveness.

show abstract

Assessing defect detection performance of interacting teams in object-oriented design inspection

Cited by 20 publications

References 26 publications

Survey of Software Inspection Research

Survey of Software Inspection Research

Modern code reviews in open-source projects: which problems do they fix?

On the Impact of the Model-Based Representation of Inconsistencies to Manual Reviews

Contact Info

Product

Resources

About