Maps of lessons learnt in requirements engineering: a research preview

Authors:
Ibtehal Noorwali;Nazim H. Madhavji
Affiliations:
University of Western Ontario, London, Canada;University of Western Ontario, London, Canada
Venue:
REFSQ'13 Proceedings of the 19th international conference on Requirements Engineering: Foundation for Software Quality
Year:
2013

Citing 8
Cited 0

Requirements Engineering: Processes and Techniques

Requirements Engineering: Processes and Techniques
Lessons learned from 25 years of process improvement: the rise and fall of the NASA software engineering laboratory

Proceedings of the 24th International Conference on Software Engineering
Building an Experience Base for Software Engineering: A Report on the First CeBASE eWorkshop

PROFES '01 Proceedings of the Third International Conference on Product Focused Software Process Improvement
ERP Requirements Engineering Practice: Lessons Learned

IEEE Software
A view of 20th and 21st century software engineering

Proceedings of the 28th international conference on Software engineering
Understanding the Product Life Cycle: Four Key Requirements Engineering Techniques

IEEE Software
Stakeholders in Global Requirements Engineering: Lessons Learned from Practice

IEEE Software
Requirements reuse at Danfoss

RE '12 Proceedings of the 2012 IEEE 20th International Requirements Engineering Conference (RE)

Quantified Score

Hi-index	0.00

Visualization

Abstract

[Context and Motivation] "Those who cannot remember the past are condemned to repeat it" --- George Santayana. From the survey we conducted of requirements engineering (RE) practitioners, over 70% seldom use RE lessons in the RE process, though 85% of these would use such lessons if readily available. Our observation, however, is that, RE lessons are scattered, mainly implicitly, in the literature and practice, which, obviously, does not help the situation. [Problem/Question] Approximately 90% of the survey participants stated that not utilising RE lessons has significant negative impact on product quality, productivity, project delays and cost overruns. [Principal Ideas] We propose "maps" (or profiles) of RE lessons which, once populated, would highlight weak (dark) and strong (bright) areas of RE (and hence RE theories). Such maps would thus be: (a) a driver for research to "light up" the darker areas of RE and (b) a guide for practice to benefit from the brighter areas. [Contribution] The key contribution of this work is the concept of "maps" of RE lessons.