Beyond Herding Cats: Aligning Quantitative Technology Evaluation in Large-Scale Research Projects

A large-scale research project involving many research and industry organizations working on a common goal should be an ideal basis for profound technology evaluations. The possibility for industrial case studies in multiple settings ought to enable reliable quantitative assessment of the performance of new technologies in various real-world settings. However, due to diverse challenges, such as internal agendas, implicit constraints, and unaligned objectives, leveraging this potential goes beyond the usual challenge of cat-herding in such projects. Based on our experience from coordinating technology evaluations in several research projects, this paper sketches the typical issues and outlines an approach for dealing with them. Although new in its composition, this approach brings together principles and techniques perceived to have been useful in earlier projects (e.g., cross-organizational alignment, abstract measures, and internal baselining). Moreover, as we are currently applying the approach in a large research project, this paper presents first insights into its applicability and usefulness.

[1]  B. Kitchenham,et al.  Case Studies for Method and Tool Evaluation , 1995, IEEE Softw..

[2]  Laura Lehtola,et al.  Using the focus group method in software engineering: obtaining practitioner and user experiences , 2004, Proceedings. 2004 International Symposium on Empirical Software Engineering, 2004. ISESE '04..

[3]  Pearl Brereton,et al.  Systematic literature reviews in software engineering - A tertiary study , 2010, Inf. Softw. Technol..

[4]  David Greene,et al.  A research design for generalizing from multiple case studies , 1984 .

[5]  Victor R. Basili,et al.  Linking Software Development and Business Strategy Through Measurement , 2010, Computer.

[6]  Miguel A. Fernández,et al.  An empirical study of the state of the practice and acceptance of model-driven engineering in four industrial cases , 2012, Empirical Software Engineering.

[7]  Natalia Juristo Juzgado,et al.  Effectiveness of Requirements Elicitation Techniques: Empirical Results Derived from a Systematic Review , 2006, 14th IEEE International Requirements Engineering Conference (RE'06).

[8]  Lucas Layman,et al.  On establishing the essential components of a technology-dependent framework: a strawman framework for industrial case study-based research , 2005, ACM SIGSOFT Softw. Eng. Notes.

[9]  Shari Lawrence Pfleeger,et al.  Software Metrics : A Rigorous and Practical Approach , 1998 .

[10]  Vladimir Tosic,et al.  Guidelines for industrially-based multiple case studies in software engineering , 2009, 2009 Third International Conference on Research Challenges in Information Science.

[11]  David R. Lindstrom Five Ways to Destroy a Development Project , 1993, IEEE Softw..

[12]  Guilherme Horta Travassos,et al.  Action research use in software engineering: An initial survey , 2009, ESEM 2009.

[13]  Reidar Conradi,et al.  Quality, productivity and economic benefits of software reuse: a review of industrial studies , 2007, Empirical Software Engineering.

[14]  Marcus Ciolkowski,et al.  Empirical results from using custom-made software project control centers in industrial environments , 2008, ESEM '08.

[15]  Forrest Shull,et al.  Improving Evidence about Software Technologies: A Look at Model-Based Testing , 2008, IEEE Software.

[16]  Stephen G. MacDonell,et al.  Qualitative research on software development: a longitudinal case study methodology , 2011, Empirical Software Engineering.

[17]  Lucas Layman,et al.  Toward a framework for evaluating extreme programming , 2004, ICSE 2004.

[18]  Laurie A. Williams,et al.  Early estimation of defect density using an in-process Haskell metrics model , 2005, ACM SIGSOFT Softw. Eng. Notes.

[19]  Shari Lawrence Pfleeger,et al.  Software metrics (2nd ed.): a rigorous and practical approach , 1997 .

[20]  Per Runeson,et al.  Guidelines for conducting and reporting case study research in software engineering , 2009, Empirical Software Engineering.