Informing development decisions: From data to information

Software engineers generate vast quantities of development artifacts such as source code, bug reports, test cases, usage logs, etc., as they create and maintain their projects. The information contained in these artifacts could provide valuable insights into the software quality and adoption, as well as development process. However, very little of it is available in the way that is immediately useful to various stakeholders. This research aims to extract and analyze data from software repositories to provide software practitioners with up-to-date and insightful information that can support informed decisions related to the business, management, design, or development of software systems. This data-centric decision-making is known as analytics. In particular, we demonstrate that by employing software development analytics, we can help developers make informed decisions around user adoption of a software project, code review process, as well as improve developers' awareness of their working context.

[1]  D HerbslebJames,et al.  Two case studies of open source software development , 2002 .

[2]  J. Herbsleb,et al.  Two case studies of open source software development: Apache and Mozilla , 2002, TSEM.

[3]  Thomas Zimmermann,et al.  Information needs for software development analytics , 2012, 2012 34th International Conference on Software Engineering (ICSE).

[4]  T. Addison,et al.  Controlling software project risks: an empirical study of methods used by experienced project managers , 2002 .

[5]  Michael W. Godfrey,et al.  The Secret Life of Patches: A Firefox Case Study , 2012, 2012 19th Working Conference on Reverse Engineering.

[6]  Jonathan I. Maletic,et al.  Journal of Software Maintenance and Evolution: Research and Practice Survey a Survey and Taxonomy of Approaches for Mining Software Repositories in the Context of Software Evolution , 2022 .

[7]  Gail C. Murphy,et al.  Who should fix this bug? , 2006, ICSE.

[8]  Shahedul Huq Khandkar,et al.  The role of patch review in software evolution: an analysis of the mozilla firefox , 2009, IWPSE-Evol '09.

[9]  Thomas Zimmermann,et al.  Improving bug tracking systems , 2009, 2009 31st International Conference on Software Engineering - Companion Volume.

[10]  Thomas Zimmermann,et al.  Information needs in bug reports: improving cooperation between developers and users , 2010, CSCW '10.

[11]  Michael W. Godfrey,et al.  A tale of two browsers , 2011, MSR '11.

[12]  Michael W. Godfrey,et al.  Situational awareness: Personalizing issue tracking systems , 2013, 2013 35th International Conference on Software Engineering (ICSE).

[13]  Eleni Stroulia,et al.  Mining Software Usage Data , 2004, MSR.

[14]  Daniel M. German,et al.  Open source software peer review practices , 2008, 2008 ACM/IEEE 30th International Conference on Software Engineering.

[15]  Thomas Zimmermann,et al.  What Makes a Good Bug Report? , 2008, IEEE Transactions on Software Engineering.

[16]  Tao Xie,et al.  Software intelligence: the future of mining software engineering data , 2010, FoSER '10.

[17]  Margaret-Anne D. Storey,et al.  Understanding broadcast based peer review on open source software projects , 2011, 2011 33rd International Conference on Software Engineering (ICSE).

[18]  M. Uihlein.  Open , 2018 .

[19]  John Anvik,et al.  Automating bug report assignment , 2006, ICSE.

[20]  Thomas Zimmermann,et al.  Towards the next generation of bug tracking systems , 2008, 2008 IEEE Symposium on Visual Languages and Human-Centric Computing.

[21]  Gerardo Canfora,et al.  How Software Repositories can Help in Resolving a New Change Request , 2005 .

[22]  William Jones,et al.  Managing open source contributions for software project sustainability , 2010, PICMET 2010 TECHNOLOGY MANAGEMENT FOR GLOBAL ECONOMIC GROWTH.

[23]  Dane Bertram,et al.  Communication, collaboration, and bugs: the social nature of issue tracking in small, collocated teams , 2010, CSCW '10.

[24]  Jai Asundi,et al.  Patch Review Processes in Open Source Software Development Communities: A Comparative Case Study , 2007, 2007 40th Annual Hawaii International Conference on System Sciences (HICSS'07).

[25]  Thomas H. Davenport,et al.  Analytics at Work: Smarter Decisions, Better Results , 2010 .

[26]  Dongmei Zhang,et al.  Software analytics as a learning case in practice: approaches and experiences , 2011, MALETS '11.

[27]  Michael W. Godfrey,et al.  Mining usage data and development artifacts , 2012, 2012 9th IEEE Working Conference on Mining Software Repositories (MSR).

[28]  Lorenzo Strigini.  Limiting the Dangers of Intuitive Decision Making , 1996, IEEE Softw..

[29]  Brendan Murphy,et al.  Characterizing the differences between pre- and post- release versions of software , 2011, 2011 33rd International Conference on Software Engineering (ICSE).

[30]  A. Hassan,et al.  Management of community contributions A case study on the Android and Linux software ecosystems , 2013 .

[31]  Gail C. Murphy,et al.  Automatic bug triage using text categorization , 2004, SEKE.

[32]  Daniel M. Germán,et al.  Management of community contributions , 2013, Empirical Software Engineering.