2016 42th Euromicro Conference on Software Engineering and Advanced Applications (SEAA) (2016)
Aug. 31, 2016 to Sept. 2, 2016
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/SEAA.2016.50
[Context] Problems in Requirements Engineering (RE) can lead to serious consequences during the software development lifecycle. [Goal] The goal of this paper is to propose empirically-based guidelines that can be used by different types of organisations according to their size (small, medium or large) and process model (agile or plan-driven) to help them in preventing such problems. [Method] We analysed data from a survey on RE problems answered by 228 organisations in 10 different countries. [Results] We identified the most critical RE problems, their causes and mitigation actions, organizing this information by clusters of size and process model. Finally, we analysed the causes and mitigation actions of the critical problems of each cluster to get further insights into how to prevent them. [Conclusions] Based on our results, we suggest preliminary guidelines for preventing critical RE problems in response to context characteristics of the companies.
Guidelines, Requirements engineering, Analytical models, Business, Software, Data models, Industries
P. Mafra, M. Kalinowski, D. M. Fernandez, M. Felderer and S. Wagner, "Towards Guidelines for Preventing Critical Requirements Engineering Problems," 2016 42th Euromicro Conference on Software Engineering and Advanced Applications (SEAA), Limassol, Cyprus, 2016, pp. 25-29.