ICSE '94 Proceedings of the 16th international conference on Software engineering
Emerald: Software Metrics and Models on the Desktop
IEEE Software
Hipikat: recommending pertinent software development artifacts
Proceedings of the 25th International Conference on Software Engineering
Identifying Reasons for Software Changes Using Historic Databases
ICSM '00 Proceedings of the International Conference on Software Maintenance (ICSM'00)
Populating a Release History Database from Version Control and Bug Tracking Systems
ICSM '03 Proceedings of the International Conference on Software Maintenance
ISSTA '04 Proceedings of the 2004 ACM SIGSOFT international symposium on Software testing and analysis
Use of relative code churn measures to predict system defect density
Proceedings of the 27th international conference on Software engineering
MSR '05 Proceedings of the 2005 international workshop on Mining software repositories
Predicting Faults from Cached History
ICSE '07 Proceedings of the 29th international conference on Software Engineering
Improving defect prediction using temporal features and non linear models
Ninth international workshop on Principles of software evolution: in conjunction with the 6th ESEC/FSE joint meeting
Learning from bug-introducing changes to prevent fault prone code
Ninth international workshop on Principles of software evolution: in conjunction with the 6th ESEC/FSE joint meeting
Change Distilling: Tree Differencing for Fine-Grained Source Code Change Extraction
IEEE Transactions on Software Engineering
Predicting buggy changes inside an integrated development environment
Proceedings of the 2007 OOPSLA workshop on eclipse technology eXchange
SpyWare: a change-aware development toolset
Proceedings of the 30th international conference on Software engineering
Recommending method invocation context changes
Proceedings of the 2008 international workshop on Recommendation systems for software engineering
What is the long-term impact of changes?
Proceedings of the 2008 international workshop on Recommendation systems for software engineering
Change impact graphs: Determining the impact of prior codechanges
Information and Software Technology
BUGINNINGS: identifying the origins of a bug
Proceedings of the 3rd India software engineering conference
Fault-prone module detection using large-scale text features based on spam filtering
Empirical Software Engineering
Recurring bug fixes in object-oriented programs
Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 1
The code orb: supporting contextualized coding via at-a-glance views (NIER track)
Proceedings of the 33rd International Conference on Software Engineering
Proceedings of the 19th ACM SIGSOFT symposium and the 13th European conference on Foundations of software engineering
A topic-based approach for narrowing the search space of buggy files from a bug report
ASE '11 Proceedings of the 2011 26th IEEE/ACM International Conference on Automated Software Engineering
Inferring project-specific bug patterns for detecting sibling bugs
Proceedings of the 2013 9th Joint Meeting on Foundations of Software Engineering
| Hi-index | 0.00 |
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.