Abstract

Eliciting requirements is one of the key aspects of the software development life cycle. Incorrect determination of the requirements can lead to the failure of the projects. Traditional waterfall method does not accommodate changing requirements easily while agile methodology welcomes the changing requirements even at the later phases of the development life cycle. The aim of the research is to improve the agile requirement elicitation process to ensure quality product is developed that aligns to the organizational strategy and its high value initiatives. Requirement elicitation process within agile projects should consider organisational actor’s strategic dependency and rationale to ensure alignment with organisational strategy. We propose to improve the requirement elicitation process by combining i*organizational models with standard Agile-Scrum methodology through a real-life health service provider scenario. The aim of our methodology is to ensure the social aspects of the organizational actor’s strategic dependency and rationale are considered. We argue the requirement process could be significantly improved by combining these two aspects; Agile-Scrum methodology will address the requirements through user stories, vision document, epics and i*organizational model will include the social aspects of the organization to reduce the gap between the project goal and organization goal.

Highlights

  • One of the critical aspects of the software development process is collecting, managing and understanding the requirements

  • The aim of this paper is to illustrate a methodology to enhance the quality of agile requirement elicitation process

  • As this paper focuses on improving the requirement elicitation process and for this agile is combined with the i* organizational framework which is based on the concept of “intentional actor”

Read more

Summary

Introduction

One of the critical aspects of the software development process is collecting, managing and understanding the requirements. It states the “what” and “why” of the system. Requirement elicitation is one of the most important phases of the software development life cycle because project’s initiation is largely dependent on it (Rida et al, 2016). There are many examples where the project failed due to the poor requirement elicitation. Requirement engineering poses a big challenge to the software industry. To cope up with fast evolving software industry the requirements need to be understood to satisfy the customers and make the project a success

Objectives
Methods
Findings
Discussion
Conclusion
Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call