The type of evidence produced by empirical software engineers
REBSE '05 Proceedings of the 2005 workshop on Realising evidence-based software engineering
Two principles of end-user software engineering research
WEUSE I Proceedings of the first workshop on End-user software engineering
When Software Engineers Met Research Scientists: A Case Study
Empirical Software Engineering
On recommending meaningful names in source and UML
Proceedings of the 2nd International Workshop on Recommendation Systems for Software Engineering
Factors explaining external quality in 54 case studies of software development projects
EASE'09 Proceedings of the 13th international conference on Evaluation and Assessment in Software Engineering
| Hi-index | 0.00 |
In this paper, we argue that the gap between empirical software engineering and software engineering practice might be lessened if more attention were paid to two important aspects of evidence. The first is that evidence from case or field studies of actual software engineering practice is essential in order to understand and inform that practice. The second is that the nature of evidence should fit the purpose to which the evidence is going to be put. One type of evidence is not per se better than another. For example, the evidence required to persuade a manager to change an aspect of practice might be totally different in nature from that required to deepen the academic community's understanding of such practice.