Demo Data from EDBT 2026 / reviewers in the wild / expert
Hans Alberg
dblp:29/1500
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 1996
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 1
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Software engineering, system software, and programming languages
1 paper |
Empirical software engineering · 100% |
Topics — the 4 heaviest of 4, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Empirical software engineering › software metrics
design metrics |
0.0 | 1 | 1996 | Predicting Fault-Prone Software Modules in Telephone Switches · IEEE Trans. Software Eng. 1996 |
Empirical software engineering
fault prediction |
0.0 | 1 | 1996 | Predicting Fault-Prone Software Modules in Telephone Switches · IEEE Trans. Software Eng. 1996 |
Empirical software engineering › software defect prediction
fault-prone module prediction |
0.0 | 1 | 1996 | Predicting Fault-Prone Software Modules in Telephone Switches · IEEE Trans. Software Eng. 1996 |
Empirical software engineering
mining software repositories |
0.0 | 1 | 1996 | Predicting Fault-Prone Software Modules in Telephone Switches · IEEE Trans. Software Eng. 1996 |
Methods — techniques the papers use, named apart from their topics
logistic regression · 0.0linear regression · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 1996 | Predicting Fault-Prone Software Modules in Telephone SwitchesabstractAn empirical study was carried out at Ericsson Telecom AB to investigate the relationship between several design metrics and the number of function test failure reports associated with software modules. A tool, ERIMET, was developed to analyze the design documents automatically. Preliminary results from the study of 130 modules showed that: based on fault and design data one can satisfactorily build, before coding has started, a prediction model for identifying the most fault-prone modules. The data analyzed show that 20 percent of the most fault-prone modules account for 60 percent of all faults. The prediction model built in this paper would have identified 20 percent of the modules accounting for 47 percent of all faults. At least four design measures can alternatively be used as predictors with equivalent performance. The size (with respect to the number of lines of code) used in a previous prediction model was not significantly better than these four measures. The Alberg diagram introduced in this paper offers a way of assessing a predictor based on historical data, which is a valuable complement to linear regression when prediction data is ordinal. Applying the method described in this paper makes it possible to use measures at the design phase to predict the most fault-prone modules. Niclas Ohlsson, Hans Alberg |
IEEE Trans. Software Eng. | 2 |