Evidence in Requirements Engineering: A Systematic Literature Review Protocol

Requirements Engineering (RE) is recognized as one of the critical phases in software development. RE has its own journals and conferences where lots of work has been published. As the area is maturing, increasingly large numbers of empirically supported studies have been reported in RE. There is a need to synthesize evidence based RE literature. We plan to systematically investigate evidence based RE studies to see and report state of the art in evidence based RE reported research. This paper aims at providing a systematic literature review (SLR) protocol to describe a process for synthesizing the empirically supported work in the area of RE that will eventually present a state of the art of the field. This SLR intends to not only summarize the empirical data regarding RE but will also be helpful for various practitioners in this field to find out areas of RE rich in terms of tools, techniques, frameworks, models and guidelines to aid in their work. It will also facilitate RE researchers to identify knowledge gaps to recognize needs and chances for future research directions in this field. Keywords-systematic literature review; requirements engineering; evidence-based software engineering.

[1]  Roel Wieringa,et al.  Requirements engineering paper classification and evaluation criteria: a proposal and a discussion , 2005, Requirements Engineering.

[2]  Neil Potter,et al.  In Search of Excellent Requirements , 2002 .

[3]  Per Runeson,et al.  Checklists for Software Engineering Case Study Research , 2007, First International Symposium on Empirical Software Engineering and Measurement (ESEM 2007).

[4]  P. Kidwell,et al.  The mythical man-month: Essays on software engineering , 1996, IEEE Annals of the History of Computing.

[5]  Pearl Brereton,et al.  An Evaluation of Quality Checklist Proposals - A participant-observer case study , 2009, EASE.

[6]  Franz Lehner,et al.  Requirements Engineering as a Success Factor in Software Projects , 2001, IEEE Softw..

[7]  Pearl Brereton,et al.  Performing systematic literature reviews in software engineering , 2006, ICSE.

[8]  Kai Petersen,et al.  Systematic Mapping Studies in Software Engineering , 2008, EASE.

[9]  Thomas E. Bell,et al.  Software requirements: Are they really a problem? , 1976, ICSE '76.

[10]  Tore Dybå,et al.  Strength of evidence in systematic reviews in software engineering , 2008, ESEM '08.

[11]  Per Runeson,et al.  Can we evaluate the quality of software engineering experiments? , 2010, ESEM '10.

[12]  T.C. Lethbridge,et al.  Guide to the Software Engineering Body of Knowledge (SWEBOK) and the Software Engineering Education Knowledge (SEEK) - a preliminary mapping , 2001, 10th International Workshop on Software Technology and Engineering Practice.

[13]  Douglas T. Ross,et al.  Structured Analysis for Requirements Definition , 1977, IEEE Transactions on Software Engineering.

[14]  Cheng Zhang,et al.  Preliminary Reporting Guidelines for Experience Papers , 2009, EASE.

[15]  Pearl Brereton,et al.  Systematic literature reviews in software engineering - A systematic literature review , 2009, Inf. Softw. Technol..