Share This Author
Two case studies of open source software development: Apache and Mozilla
This work examines data from two major open source projects, the Apache web server and the Mozilla browser, and quantifies aspects of developer participation, core team size, code ownership, productivity, defect density, and problem resolution intervals for these OSS projects.
An Empirical Study of Speed and Communication in Globally Distributed Software Development
This work uses both data from the source code change management system and survey data to model the extent of delay in a distributed software development organization and explores several possible mechanisms for this delay.
A large-scale empirical study of just-in-time quality assurance
- Yasutaka Kamei, Emad Shihab, Naoyasu Ubayashi
- BusinessIEEE Transactions on Software Engineering
- 1 June 2013
The findings indicate that “Just-In-Time Quality Assurance” may provide an effort-reducing way to focus on the most risky changes and thus reduce the costs of developing high-quality software.
A case study of open source software development: the Apache server
- A. Mockus, R. Fielding, J. Herbsleb
- Computer ScienceProceedings of the International Conference on…
- 1 June 2000
This analysis of the development process of the Apache web server reveals a unique process, which performs well on important measures, and concludes that hybrid forms of development that borrow the most effective techniques from both the OSS and commercial worlds may lead to high performance software processes.
Predicting risk of software changes
The model is built on historic information and is used to predict the risk of new changes in 5ESS® software updates and finds that change diffusion and developer experience are essential to predicting failures.
Identifying reasons for software changes using historic databases
From this study several suggestions are arrived at on how to make version control data useful in diagnosing the state of a software project, without significantly increasing the overhead for the developer using the change management system.
Does Code Decay? Assessing the Evidence from Change Management Data
This work defines code decay and proposes a number of measurements (code decay indices) on software and on the organizations that produce it, that serve as symptoms, risk factors, and predictors of decay.
Distance, dependencies, and delay in a global collaboration
The results show a significant relationship between delay in cross-site work and the degree to which remote colleagues are perceived to help out when workloads are heavy, particularly troubling in light of the finding that workers generally believed they were as helpful to their remote colleagues as to their local colleagues.
Expertise Browser: a quantitative approach to identifying expertise
A tool, called Expertise Browser (ExB), that uses data from change management systems to locate people with desired expertise and uses a quantification of experience, and presents evidence to validate this quantification as a measure of expertise.
An empirical study of global software development: distance and speed
- J. Herbsleb, A. Mockus, T. Finholt, Rebecca E. Grinter
- Computer Science, BusinessProceedings of the 23rd International Conference…
- 1 July 2001
This work uses both survey data and data from the source code change management system to model the extent of delay in a multi-site software development organization, and investigates several possible mechanisms for this delay.