• Publications
  • Influence
Predicting Fault Incidence Using Software Change History
TLDR
This paper uses change management data from a very large, long-lived software system to explore the extent to which measurements from the change history are successful in predicting the distribution over modules of these incidences of faults. Expand
Understanding the sources of variation in software inspections
TLDR
Acting on the hypothesis that the “inputs” into the inspection process (reviewers, authors, and code units) were significant sources of variation, they were responsible for much more variation in detect detection than was process structure. Expand
Parallel changes in large scale software development: an observational case study
TLDR
An observational case study in which the change and configuration management history of a legacy system is collected and analyzed to delineate the boundaries of, and to understand the nature of, the problems encountered in parallel development. Expand
Does the modern code inspection have value?
  • H. Siy, L. Votta
  • Computer Science
  • Proceedings IEEE International Conference on…
  • 7 November 2001
TLDR
It is concluded that even if advances in software technology have diminished the value of inspections as a defect detection tool, in most cases, it continues to be of value as a maintenance tool. Expand
If your ver-sion control system could talk
TLDR
Some ways to use contextual information captured in version control systems to better understand a program's development history are illustrated. Expand
Software product lines: a case study
TLDR
This paper shows how to use FAST to document precisely the key abstractions in a domain, exploit design patterns in a generic product‐line architecture, generate documentation and Java code, and automate testing to reduce costs. Expand
Parallel changes in large scale software development: an observational case study
TLDR
An observational case study in which the change and configuration management history of a legacy system is collected and analyzed to delineate the boundaries of, and to understand the nature of, the problems encountered in parallel development. Expand
A Review of Software Inspections
TLDR
It is concluded that the benefits of inspections are often overstated and the costs (especially for large software development projects) are understated. Expand
An Experiment ot Assess the Cost-Benefits of Code Inspections in Large Scale Software Development
TLDR
The results showed that these treatments did not significantly influence the defect detection effectiveness, but that certain combinations of changes dramatically increased the inspection interval. Expand
An empirical validation of object-oriented class complexity metrics and their ability to predict error-prone classes in highly iterative, or agile, software: a case study
TLDR
This study explores the predictive ability of several complexity-related metrics for OO software that have not been heavily validated by exploring their ability to measure quality in an evolutionary software process, and shows that these metrics are useful in identifying fault-prone classes in software developed using highly iterative or agile software development processes. Expand
...
1
2
3
4
5
...