EBSE for Software Developers
Why is EBSE relevant to me?
An unfortunate characteristic of almost all software engineering practice is that it is informally based upon codifying experience rather than any systematic forms of study, further compounded by the need for individual expertise in order to employ this. This is not to suggest that experience, especially when codified well, is not of value, but as has been demonstrated in other disciplines, not all experience is of equal value, and there may be limitations to the applicability of techniques and practices that this does not reveal. There may also be social or commercial implications that may lead to a degree of 'hype' about particular practices.
The aim of EBSE is to provide a surer foundation for software development practices, by seeking, assessing and collating the empirical data about specific techniques. While the outcomes of systematic literature reviews still have to be assessed and interpreted in the light of specific needs, they do seek to be as unbiased and objective as possible.
What is available?
Systematic Literature Reviews have been undertaken on a number of topics that are relevant to developers. This page identifies these, based upon the SWEBOK (Software Engineering Body of Knowledge) classifications. The set is inevitably incomplete since EBSE is a relatively new development in itself, and the topics chosen by researchers have to date been partly based upon their own interests, and also the likelihood of finding sufficient primary studies to be able to undertake some form of review and analysis that will be meaningful.
For each of the main SWEBOK headings we list known reviews, together with details of the authors, where published, the number of primary studies included in the review, and the period covered by the review.