Continuous Product-Focused Project Monitoring with Trend Patterns and GQM

It is important for project stakeholders to identify the states of projects and quality of products. Although metrics are useful for identifying them, it is difficult for project stakeholders to select appropriate metrics and determine the purpose of measuring metrics. We propose an approach that defines the measured metrics by GQM method, and supports identifying tendency in projects and products based on Trend Pattern. Additionally, we implement a tool as a Jenkins Plug in which to visualizes an evaluation results based on GQM method. We perform an experiment with OSS and industrial case study with two software development projects. In our experiment, we can identify the problem and project tendency. In our industrial case study, we can also identify the problem that project contains. As our future work, we will adopt our approach and GQM Plug in to software development project continuously to assess their effectiveness in the long term.

[1]  Yasuyuki Tanaka,et al.  Initial Industrial Experience of GQM-Based Product-Focused Project Monitoring with Trend Patterns , 2014, 2014 21st Asia-Pacific Software Engineering Conference.

[2]  Jürgen Münch,et al.  Software project control centers: concepts and approaches , 2004, J. Syst. Softw..

[3]  Ademar Aguiar,et al.  Continuous Inspection A Pattern for Keeping your Code Healthy and Aligned to the Architecture , 2013 .

[4]  Cmmi Product Team CMMI for Systems Engineering/Software Engineering, Version 1.1, Staged Representation (CMMI-SE/SW, V1.1, Staged) , 2001 .

[5]  Akito Monden,et al.  Customizing GQM Models for Software Project Monitoring , 2012, IEICE Trans. Inf. Syst..

[6]  Hiroyuki Tanabe,et al.  Reusability Metrics for Program Source Code Written in C Language and Their Evaluation , 2012, PROFES.

[7]  Hironori Washizaki,et al.  A Generalized Software Reliability Model Considering Uncertainty and Dynamics in Development , 2013, PROFES.

[8]  Katsuro INOUE,et al.  Empirical Project Monitor: A System that Automatically Collects and Analyzes Quantitative Development Data toward Process Improvement , 2004 .

[9]  Jürgen Münch,et al.  Goal-Oriented Setup and Usage of Custom-Tailored Software Cockpits , 2008, PROFES.

[10]  H. D. Rombach,et al.  The Goal Question Metric Approach , 1994 .

[11]  Katsuro Inoue,et al.  Empirical Project Monitor: A Tool for Mining Multiple Project Data , 2004, MSR.

[12]  Jürgen Münch,et al.  Evaluating Software Project Control Centers in Industrial Environments , 2007, First International Symposium on Empirical Software Engineering and Measurement (ESEM 2007).

[13]  Reinhold Plösch,et al.  The Quamoco product quality modelling and assessment approach , 2012, 2012 34th International Conference on Software Engineering (ICSE).

[14]  Mark C. Paulk,et al.  Capability Maturity Model , 1991 .

[15]  Peter Liggesmeyer,et al.  Visualization of Software and Systems as Support Mechanism for Integrated Software Project Control , 2009, HCI.

[16]  Katsuro Inoue,et al.  A Proposal for Analysis and Prediction for Software Projects using Collaborative Filtering, In-Process Measurements and a Benchmarks Database , 2006 .

[17]  Markus Herrmannsdoerfer,et al.  The quamoco tool chain for quality modeling and assessment , 2011, 2011 33rd International Conference on Software Engineering (ICSE).

[18]  Hironori Washizaki,et al.  A Framework for Measuring and Evaluating Program Source Code Quality , 2007, PROFES.