1. Visualization of version control and issue tracking data as a tool of software analytics

2. Need for speed –project N4S is a research concortium funded by Tekes and coordinated by Digile Its goal is to increase competitiviness of Finnish software companies by researching real-time business models

3. What is software analytics? Software analytics aims to analyze computer programs and the processes with which they are developed. Software analytics needs to produce actionable advice to be useful Ie. It needs to provide concrete advice with which to either increase productivity or quality

4. What is software analytics? In the past software analytics aimed to find a general model of software development Later it has been accepted that there is no general model that suits all projects Nowadays software analytics aims to find methods, with which to find locally useful advice

5. Why visualizations? Visualizations are an intuitive way to get a picture of large datasets A good visualization can ’reveal’ information in data even without statistical analysis

6. Data to be visualized Data from version control systems, such as Git Data from issue tracking systems, such as Jira CVSAnalY was used to get data from Git repositories: there were some problems with the tool

7. Visualization tools Google Charts: Easy to use, but not very flexible D3.js: very flexible, but not easy to use There are large number of visualization libraries, but mostly they weren’t suitable

8. Early experiments

10. Later visualizations

11. Reusability of visualizations Custom made visualization was useful for the project, but not very reusable As such it was quite cumbersome to make visualizations for other companies Due to these reasons, we decided to make a reusable visualization library for N4S project

12. Visualization library We made an visualization library with D3.js, it takes csv files as input. It is also possible to draw charts on top of existing charts. Some drawbacks, such as that the user needs to implement parsing of csv files. Also, collecting data had to be done manually

13. Visualization library

14. For the mentioned reasons, this version remains a proof of concept that isn’t very practical in real use cases However, lessons learned from this version can be used in making the next version: a database for the data, and a proper web UI will make it easier to use