Answers are grounded in this paper and cite their sources.
The Requirement Engineering (RE) is a systemic and integrated process of eliciting, elaborating, negotiating, prioritizing, specifying, validating and managing the requirements of a system. The detailed and agreed requirements are documented and specified to serve as the basis for further system development activities. The software industry has moved from traditional software development method to service oriented software development. While many researchers and practitioners have observed issues and challenges in Requirement Engineering phase specific to a software method, very little attention has been given to investigate diversity of issues and challenges of RE in different software development methods under one umbrella. This paper tries to review significant issues and challenges of RE from traditional software development method to recent service oriented software development method. The study unveils that there is a wide scope for developing new approaches and techniques in requirement engineering to resolve problems observed in various SE methods. The review discussion reveals the need of standardization and automation of RE process especially for Service oriented software development.
No takes yet. Share an insight, caveat, or question.
Shah et al. (2014) studied this question.
Synapse has enriched 10 related papers. Consider them for comparative context: