Visual patterns in issue tracking data

Authors:
Patrick Knab;Martin Pinzger;Harald C. Gall
Affiliations:
Department of Informatics, University of Zurich, Switzerland;Department of Software Technology, Delft University of Technology, The Netherlands;Department of Informatics, University of Zurich, Switzerland
Venue:
ICSP'10 Proceedings of the 2010 international conference on New modeling concepts for today's software processes: software process
Year:
2010

Citing 8
Cited 0

Polymetric Views-A Lightweight Visual Approach to Reverse Engineering

IEEE Transactions on Software Engineering
Populating a Release History Database from Version Control and Bug Tracking Systems

ICSM '03 Proceedings of the International Conference on Software Maintenance
Coping with an open bug repository

eclipse '05 Proceedings of the 2005 OOPSLA workshop on Eclipse technology eXchange
Who should fix this bug?

Proceedings of the 28th international conference on Software engineering
A Linguistic Analysis of How People Describe Software Problems

VLHCC '06 Proceedings of the Visual Languages and Human-Centric Computing
Designing task visualizations to support the coordination of work in software development

CSCW '06 Proceedings of the 2006 20th anniversary conference on Computer supported cooperative work
How Long Will It Take to Fix This Bug?

MSR '07 Proceedings of the Fourth International Workshop on Mining Software Repositories
Modeling bug report quality

Proceedings of the twenty-second IEEE/ACM international conference on Automated software engineering

Quantified Score

Hi-index	0.00

Visualization

Abstract

Software development teams gather valuable data about features and bugs in issue tracking systems. This information can be used to measure and improve the efficiency and effectiveness of the development process. In this paper we present an approach that harnesses the extraordinary capability of the human brain to detect visual patterns. We specify generic visual process patterns that can be found in issue tracking data. With these patterns we can analyze information about effort estimation, and the length, and sequence of problem resolution activities. In an industrial case study we apply our interactive tool to identify instances of these patterns and discuss our observations. Our approach was validated through extensive discussions with multiple project managers and developers, as well as feedback from the project review board.