Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Jacek Sliwerski

dblp:50/5139 · DBLP profile ↗
← Back
1ranked-venue papers
1as first author
0since 2021 · last 2005
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 1 · 1 first-author

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 2 heaviest of 2, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Empirical software engineering › software project management
software risk analysis
0.112005
HATARI: raising risk awareness · ESEC/SIGSOFT FSE 2005
Empirical software engineering
mining software repositories
0.012005
HATARI: raising risk awareness · ESEC/SIGSOFT FSE 2005

Methods — techniques the papers use, named apart from their topics

version history analysis · 0.1bug database linking · 0.1
YearPublicationVenuePosition
2005 HATARI: raising risk awareness
abstract
As a software system evolves, programmers make changes which sometimes lead to problems. The risk of later problems significantly depends on the location of the change. Which are the locations where changes impose the greatest risk? Our HATARI prototype relates a version history (such as CVS) to a bug database (such as BUGZILLA) to detect those locations where changes have been risky in the past. HATARI makes this risk visible for developers by annotating source code with color bars. Furthermore, HATARI provides views to browse through the most risky locations and to analyze the risk history of a particular location.
Jacek Sliwerski, Thomas Zimmermann 0001, Andreas Zeller
ESEC/SIGSOFT FSE1