A Review of Requirement Engineering Issues and Challenges in Various Software Development Methods

Abstract

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.

A Systematic Review of Software Security Issues Associated With Agile Software Development

“…[17] Poor quality of requirement has increased the development and sustainment cost. [22] 5. Engineers do not pay enough attention to develop documentation and it has created the life cycle problems in the working environment.…”

“…Requirements inconsistency has created an impact in lot of organizations [21]. Shah and Patel [22] reviewed the requirement engineering issues and challenges in various software development methods. Poor quality of requirement has increased the development and sustainment DOI: 10.9790/0661-1804056467 www.iosrjournals.org 66 | Page cost which also has resulted in the delayed schedule.…”

A Requirements Definition Framework for the Robotic Systems Domain - An Exploratory Study

“…Most research projects focus on a RE phase singly (e.g. elicitation or validation) and there has been little work on interconnection of requirement models and combining RE phases [24] mainly in the robotic domain [19]. Well defined approaches are required to interrelate RE goals, scenarios, data, functions, state-based behavior and constraints.…”

“…Conflicting and Ambiguous Requirements: The different stakeholders' opinions, objectives, needs may have different meanings and may conflicts with vague words. When eliciting the requirements; the terminology, keywords and domain knowledge should be properly notified [24]. Simply stated, the business of robotics research consists in "requirements that allow robots to function autonomously in unstructured, dynamic, partially observable, and uncertain environments" [27].…”

The Impact of Visualizing Traceability Links for Evolving Requirements in Software Maintenance– A Controlled Experiment

“…Even with the modern tools it is highly difficult to trace requirements to design and architecture [10]. Peng Liang et al identify management of requirements in an evolving system to be a research challenge.…”