Accumulation and Presentation of Empirical Evidence: Problems and Challenges

Understanding the effects of software engineering techniques and processes under varying conditions can be seen as a major prerequisite towards predictable project planning and guaranteeing software quality. Evidence regarding the effects of techniques and processes for specific contexts can be gained by empirical studies. Due to the fact that software development is a human-based and context -oriented activity the effects vary from project environment to project environment. As a consequence, the studies need to be performed in specific environments and the results are typically only valid for these local environments. Potential users of the evidence gained in such studies (e.g., project planners who need to select techniques and processes for a project) are confronted with difficulties such as finding and understanding the relevant results and assessing whether and how they can be applied to their own situation. Thereby, effective transfer and use of empirical findings is hindered. Our thesis is that effective dissemination and exploitation of empirical evidence into industry requires aggregation, integration, and adequate stakeholder-oriented presentation of the results. This position paper sketches major problems and challenges and proposes research issues towards solving the problem.

[1]  Leon G. Stucki,et al.  Proceedings of the 44th International Conference on Software Engineering , 1979, ICSE 1979.

[2]  Sira Vegas,et al.  A Process for Identifying Relevant Information for a Repository: A Case Study for Testing Techniques , 2003 .

[3]  Marcus Ciolkowski,et al.  Towards evidence in software engineering , 2004, Proceedings. 2004 International Symposium on Empirical Software Engineering, 2004. ISESE '04..

[4]  Claes Wohlin,et al.  Combining Data from Reading Experiments in Software Inspections: A Feasibility Study , 2003, Lecture Notes on Empirical Software Engineering.