Requirements interaction management
ACM Computing Surveys (CSUR)
Combining data from reading experiments in software inspections: a feasibility study
Lecture notes on empirical software engineering
The benefits and challenges of executable acceptance testing
Proceedings of the 2008 international workshop on Scrutinizing agile practices or shoot-out at the agile corral
| Hi-index | 4.10 |
In software, “benchmarking” usually compares two companies' practices and results, but, occasionally, it involves sets of companies. For example, there are benchmark comparisons of industry software, such as insurance software, military software, telecommunication software, commercial software, and the like. In other domains, “benchmark” usually means the collection of a substantial body of quantitative data. Benchmark comparisons of various computers, for example, rate their relative performance in at least half a dozen categories. Historically, software benchmarks have been qualitative rather than quantitative. Even the Software Engineering Institute's Capability Maturity Model (SEI CMM) is essentially a qualitative benchmark that ranks company performance on a five-point scale that lacks quantification for specific quality and productivity levels