Abstract
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.
- Jedlitschka, A.; Ciolkowski, M.: Towards Evidence in Software Engineering; In Proc. of ACM/IEEE Intern. Symposium on Software Engineering 2004 (ISESE2004), Redondo Beach, California, August 2004, IEEE CS, 2004, pp. 261--270 Google ScholarDigital Library
- W. Hayes, Research Synthesis in SE: A case for Meta analysis, Metrics99, 1999, pp. 143--151. Google ScholarDigital Library
- B. A. Kitchenham, T. Dybå, M. Jørgensen, Evidence-based Software Engineering, Proceedings of 26th International Conference on Software Engineering, 2004 Google ScholarDigital Library
- J. Miller, Can results from SE experiments be safely combined?, Metrics99, 1999, pp. 152--158L. Google ScholarDigital Library
- Vegas, S.; Juristo, N.; Basili, V.: A Process for Identifying Relevant Information for a Repository: A Case Study for Testing Techniques;, In Aurum, A.; Jeffery, R.; Wohlin, C.; Handzic, M. (Eds): Managing Software Engineering Knowledge; Springer-Verlag; Berlin 2003, pp. 199--230Google ScholarCross Ref
- Wohlin, C.; Petersson, H.; Aurum, A.: Combining Data from reading Experiments in Software Inspections; In Juristo, N.; Moreno, A. M.: Lecture Notes on Empirical Software Engineering, World Scientific Publishing Co. Pte. Ltd, Singapore, 2000. pp. 85--132 Google ScholarDigital Library
Index Terms
- Accumulation and presentation of empirical evidence: problems and challenges
Recommendations
Accumulation and presentation of empirical evidence: problems and challenges
REBSE '05: Proceedings of the 2005 workshop on Realising evidence-based software engineeringUnderstanding 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 ...
Software Process Tailoring: An Empirical Investigation
A well-defined software process is critical for success in software projects. Software process tailoring refers to the activity of tuning a standardized process to meet the needs of a specific project. We conducted two case studies that address the ...
International workshop on realising evidence-based software engineering
ICSE '05: Proceedings of the 27th international conference on Software engineeringThis workshop is concerned with defining the procedures that are needed to establish a sound empirical foundation for the practices of Software Engineering. Our goal is to begin building a community that will review, analyse, codify and promulgate ...
Comments