Practical code inspection techniques for object-oriented systems: An experimental comparison

Dunsmore, Alastair; Roper, Marc; Wood, Murray

doi:10.1109/ms.2003.1207450

Cited by 27 publications

(5 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Studies reporting the use of code review and inspection techniques in the classroom are very limited. One of these studies is written by [33], in which three classroom exercises were created to detect errors in object-oriented systems. This study concludes that traditional reading techniques are not appropriate in the process of inspecting the code in large object-oriented (OO) systems, because this development paradigm can lead to delocalization problems.…”

Section: Literature Reviewmentioning

confidence: 99%

Framework for Software Code Reviews and Inspections in a Classroom Environment

Almeida¹

2018

IJMECS

View full text Add to dashboard Cite

Code reviews and inspections have the purpose to ensure that the code has sufficient quality to be released. It is generally seen as an economical way of finding errors, increase team productivity and sharing technical and product knowledge among team members. This approach is traditionally adopted in software development companies, but their practices may be useful in other contexts, such as in the process of learning software engineering. In this sense, this study proposes an innovative framework for conducting code reviews in a Computer Science course. The proposed framework can be applied in any object-oriented program language, and it is sufficiently concise to be applied in the classroom, namely in a 90-minute session in which all students are invited to collaborate in this process. The findings suggest that code reviews in an academic context can help students to strategically reflect about the performed work, enhance their soft skills, and increase their ability to work in groups. On the other hand, as the main challenges, the findings reveal that students typically don't have previous experience in performing inspections and it can become difficult to perform a complete inspection in a classroom session.

show abstract

Section: Literature Reviewmentioning

confidence: 99%

Framework for Software Code Reviews and Inspections in a Classroom Environment

Almeida¹

2018

IJMECS

View full text Add to dashboard Cite

show abstract

“…Using undergraduates as subjects of controlled experiments in software engineering for research purpose is a common practice according to the research literature [19], [63], even though this may have some disadvantages, as discussed in Section 6.4.1. Applying this approach, we have used 74 undergraduates to conduct an experiment on our FSBI method, comparing it with one of the popular inspection techniques known as perspective-based reading [8].…”

Section: An Experimentsmentioning

confidence: 99%

Formal Specification-Based Inspection for Verification of Programs

Liu

Chen

Nagoya

et al. 2012

IIEEE Trans. Software Eng.

View full text Add to dashboard Cite

Software inspection is a static analysis technique that is widely used for defect detection, but which suffers from a lack of rigor. In this paper, we address this problem by taking advantage of formal specification and analysis to support a systematic and rigorous inspection method. The aim of the method is to use inspection to determine whether every functional scenario defined in the specification is implemented correctly by a set of program paths and whether every program path of the program contributes to the implementation of some functional scenario in the specification. The method is comprised of five steps: deriving functional scenarios from the specification, deriving paths from the program, linking scenarios to paths, analyzing paths against the corresponding scenarios, and producing an inspection report, and allows for a systematic and automatic generation of a checklist for inspection. We present an example to show how the method can be used, and describe an experiment to evaluate its performance by comparing it to perspective-based reading (PBR). The result shows that our method may be more effective in detecting function-related defects than PBR but slightly less effective in detecting implementation-related defects. We also describe a prototype tool to demonstrate the supportability of the method, and draw some conclusions about our work.

show abstract

“…However, empirical studies of code inspection indicate that, although it is clearly beneficial, it still fails to reveal many defects [6] [30]. Boundary value testing [31] and special value testing are software testing techniques that are intended to reveal certain types of neglected conditions.…”

Section: Introductionmentioning

confidence: 99%

Finding what's not there

Chang

Podgurski

Yang

2007

Proceedings of the 2007 International Symposium on Software Testing and Analysis

View full text Add to dashboard Cite

Neglected conditions are an important but difficult-to-find class of software defects. This paper presents a novel approach to revealing neglected conditions that integrates static program analysis and advanced data mining techniques to discover implicit conditional rules in a code base and to discover rule violations that indicate neglected conditions. The approach requires the user to indicate minimal constraints on the context of the rules to be sought, rather than specific rule templates. To permit this generality, rules are modeled as graph minors of program dependence graphs, and both frequent itemset mining and frequent subgraph mining algorithms are employed to identify candidate rules. We report the results of an empirical evaluation of the approach in which it was used to discover conditional rules and neglected conditions in ∼25,000 lines of source code.

show abstract

Practical code inspection techniques for object-oriented systems: An experimental comparison

Cited by 27 publications

References 16 publications

Framework for Software Code Reviews and Inspections in a Classroom Environment

Framework for Software Code Reviews and Inspections in a Classroom Environment

Formal Specification-Based Inspection for Verification of Programs

Finding what's not there

Contact Info

Product

Resources

About