Match!

Review on Agile requirements engineering challenges

Published on Aug 1, 2016
· DOI :10.1109/ICCOINS.2016.7783267
Kaiss Elghariani1
Estimated H-index: 1
,
Nazri Kama7
Estimated H-index: 7
Abstract
The popularity of agile methodology has been increased since agile offers further collaboration. Requirements engineering (RE) is one of the software development process in agile approaches. The features of face to face communication is one of agile way which unlike to other traditional software methods. Software developers are using the definition agile way to improve the agile way of activities. Besides, the challenge of dealing with RE practices is not much is known in agile way or model. However, many literature works have been done in RE in agile approaches and challenges faced by teamwork. The aim of this paper is to fill the gap by presenting RE practices in agile methodology also the challenges of RE activities which are faced by agile team members. 80 systematic literature reviews are conducted and 22 research papers are identified. Moreover, the reviews discuss RE in agile methodology approaches. This paper has adopted a systematic literature review and has applied a certain inclusion and exclusion criteria to detect the research studies related to RE in agile methodology to achieve the aim of this research. This research determined most of agile requirements engineering activities, also challenges of requirements engineering in agile methodology. Therefore, the research findings can be a reference to all researchers who are interested in this research area because the paper's findings clarify that RE in agile methodology need to have further attention by researchers and more practical results are needed to gain understandable information about RE practices in Agile methodology.
  • References (30)
  • Citations (9)
📖 Papers frequently viewed together
2015
4 Authors (Irum Inayat, ..., Siti Salwah Salim)
9 Citations
135 Citations
16 Citations
78% of Scinapse members use related papers. After signing in, all features are FREE.
References30
Newest
#1Buturab Rizvi (Athabasca University)H-Index: 1
#2Ebrahim Bagheri (RyeU: Ryerson University)H-Index: 18
Last. Dragan Gasevic (Edin.: University of Edinburgh)H-Index: 38
view all 3 authors...
The combination of Agile methods and distributed software development via remote teams represents an emerging approach to address the challenges such as late feedback, slow project timelines, and high cost, typically associated with software development projects. However, when projects are implemented using an Agile model with distributed human resources, there are a number of challenges that need to be considered and mitigated. The objectives of our work are multifold. First, we would like to u...
11 CitationsSource
#1Neil A. Ernst (UBC: University of British Columbia)H-Index: 20
#2Alexander Borgida (RU: Rutgers University)H-Index: 41
Last. J. Mylopolous (University of Trento)H-Index: 78
view all 4 authors...
Innovative companies need an agile approach towards product and service requirements, to rapidly respond to and exploit changing conditions. The agile approach to requirements must nonetheless be systematic, especially with respect to accommodating legal and non-functional requirements. This paper examines how to support lightweight, agile requirements processes which can still be systematically modeled, analyzed and changed. We propose a framework, RE-KOMBINE, which is based on a propositional ...
15 CitationsSource
#1Maya Daneva (UT: University of Twente)H-Index: 22
#2Egbert van der Veen (UT: University of Twente)H-Index: 4
Last. Roel Wieringa (UT: University of Twente)H-Index: 38
view all 9 authors...
The application of agile practices for requirements prioritization in distributed and outsourced projects is a relatively recent trend. Hence, not all of its facets are well-understood. This exploratory study sets out to uncover the concepts that practitioners in a large software organization use in the prioritization process and the practices that they deem good. We seek to provide a rich analysis and a deep understanding of three cases in an exploratory study that was carried out in a large an...
73 CitationsSource
Agile software development methods (ASD) and open source software development methods (OSSD) are two different approaches which were introduced in last decade and both of them have their fanatical advocators. Yet, it seems that relation and interface between ASD and OSSD is a fertile area and few rigorous studies have been done in this matter. Major goal of this study was assessment of the relation and integration of ASD and OSSD. Analyzing of collected data shows that ASD and OSSD are able to s...
8 Citations
#1Kent BeckH-Index: 24
#2Mike BeedleH-Index: 2
Last. Dave ThomasH-Index: 15
view all 17 authors...
1,397 Citations
#1Weam M. Farid (NSU: Nova Southeastern University)H-Index: 5
#2Frank J. Mitropoulos (NSU: Nova Southeastern University)H-Index: 6
There is consensus in the research community that agile software development methodologies, such as Scrum, are becoming more and more popular in delivering quality Functional Requirements (FRs). However, agile methodologies have not adequately modeled Non-Functional Requirements (NFRs) and their potential solutions (operationalizations) with FRs in early development phases-let alone having tools to support such initiatives. This research proposes NORMATIC, a Java-based simulation tool for modeli...
18 CitationsSource
#1Weam M. Farid (NSU: Nova Southeastern University)H-Index: 5
#2Frank J. Mitropoulos (NSU: Nova Southeastern University)H-Index: 6
Agile software development methodologies, such as Scrum, have gained tremendous popularity and proven successful in quickly delivering quality Functional Requirements (FRs). However, agile methodologies have not adequately modeled Non-Functional Requirements (NFRs) and their potential solutions (operationalizations) with FRs in early development phases. This research proposes three fundamental agile artifacts to model FRs, NFRs, and their potential solutions in a visual environment. First, FRs a...
14 CitationsSource
Jan 4, 2012 in HICSS (Hawaii International Conference on System Sciences)
#1Børge Haugset (SINTEF)H-Index: 8
#2Tor Stålhane (NTNU: Norwegian University of Science and Technology)H-Index: 13
This article describes how the use of automated acceptance test-driven development (ATDD) impacts requirements engineering in software development. We extend an existing framework of inherent risks in RE by adding knowledge from literature and a case study. We show how ATDD can be seen as a mix of the traditional RE focus on documentation and the agile focus on iterative communication. ATDD can mitigate some of the inherent risks in RE. It also carries with it the need for a proper domain and a ...
21 CitationsSource
#1Hasliza Md Sarkan (MIMOS)H-Index: 1
#2Tengku Puteri Suhilah Ahmad (MIMOS)H-Index: 1
Last. Azuraini Abu Bakar (MIMOS)H-Index: 2
view all 3 authors...
Today, Agile development has become popular due to the ability to deliver fast and hence reduce cost. It is expected that by 2012, Agile development method will be utilized in 80% of all software development projects. Since 2010, some of software projects in MIMOS have adopted agile methodology. Therefore, this paper will focus on how agile methodology applied in MIMOS has influenced the requirement process. The paper will discuss on the benefits and challenges that MIMOS faced using JIRA and Re...
9 CitationsSource
Aug 29, 2011 in RE (IEEE International Conference on Requirements Engineering)
#1Elizabeth Bjarnason (Lund University)H-Index: 11
#2Krzysztof Wnuk (Lund University)H-Index: 15
Last. Björn Regnell (Lund University)H-Index: 35
view all 3 authors...
Communication is essential for software development as its efficiency throughout the entire project life-cycle is a key factor in developing and releasing successful software products to the market. This paper reports on findings from an explanatory case study aiming at a deeper understanding of the causes and effects of communication gaps in a large-scale industrial set up. Based on an assumption of what causes gaps in communication of requirements and what effects such gaps have, a semi-struct...
68 CitationsSource
Cited By9
Newest
#1Woubshet Behutiye (University of Oulu)H-Index: 3
#2Pertti Karhapää (University of Oulu)H-Index: 2
Last. Markku Oivo (University of Oulu)H-Index: 15
view all 9 authors...
Abstract Context Quality requirements (QRs) describe the desired quality of software, and they play an important role in the success of software projects. In agile software development (ASD), QRs are often ill-defined and not well addressed due to the focus on quickly delivering functionality. Rapid software development (RSD) approaches (e.g., continuous delivery and continuous deployment), which shorten delivery times, are more prone to neglect QRs. Despite the significance of QRs in both ASD a...
2 CitationsSource
#1Hina Saeeda (Ocean University of China)H-Index: 1
view all 4 authors...
Source
#1Shreta Sharma (Jagannath University)H-Index: 1
#1S S SharmaH-Index: 2
Last. Saumya PandeyH-Index: 20
view all 2 authors...
Requirement documentation plays a substantial role in requirement engineering (RE) process. It is a procedure of forming the document, which is used to communicate functions, events and operations to many stakeholders in software development procedure. The documents similarly perform as a proof of all the processes and actions included in software development. The precise level of attention to clearly share requirements and the vital concepts makes software projects successful. The comprehensive...
Source
Jul 27, 2019 in INFOCOM (International Conference on Computer Communications)
#1Areebah Altaf (National University of Sciences and Technology)
#2Urooj Fatima (National University of Sciences and Technology)
Last. Maryum Hamdani (National University of Sciences and Technology)H-Index: 1
view all 5 authors...
Agile practices are considered as a major attraction for global software development (GSD) projects owing to its flexible nature. Beside the major benefits it offers to GSD, there are few challenges that hinders its implementation across the global software industry. This study contributes in constructing a systematic literature review for exploring the major factors impacting the agile adaptation at global level. We have identified and analyzed 28 research studies (2015-2019). These selected st...
Source
#1Anne Hess (Fraunhofer Society)H-Index: 3
#2Philipp Diebold (Fraunhofer Society)H-Index: 10
Last. Norbert Seyff (University of Applied Sciences and Arts Northwestern Switzerland FHNW)H-Index: 17
view all 3 authors...
Abstract For traditional software development processes, we have detailed empirical knowledge about role-specific information needs that have to be satisfied in requirements documents. Particularly, we gained detailed knowledge about priorities of a set of traditional requirements artifacts in a series of empirical studies from the viewpoint of software architects, usability engineers, and testers. However, little is known about such information needs from the viewpoint of agile team members. Mo...
3 CitationsSource
#1Karina Curcio (PUCPR: Pontifícia Universidade Católica do Paraná)H-Index: 2
#2Tiago Navarro (PUCPR: Pontifícia Universidade Católica do Paraná)
Last. Sheila Reinehr (PUCPR: Pontifícia Universidade Católica do Paraná)H-Index: 8
view all 4 authors...
SCRUM picture was replaced.Requirements modification statement was revised.References format was corrected. ContextRequirements engineering in agile software development is a relatively recent software engineering topic and it is not completely explored and understood. The understanding of how this process works on agile world needs a deeper analysis. ObjectiveThe goal of this paper is to map the subject area of requirements engineering in agile context to identify the main topics that have been...
Source
#1Rainer Telesko (University of Applied Sciences and Arts Northwestern Switzerland FHNW)
This chapter describes the research project Companion conducted at the University of Applied Sciences and Arts Northwestern Switzerland FHNW and its relationship to the research area Agile Requirements Engineering (ARE). ARE aims to establish requirements engineering practices, which are customized for agile development methodologies such like Scrum, XP, etc. Within the Companion project a Web App was developed to promote mental health of adolescents taking their first steps into working life. T...
Source
#1Anne HessH-Index: 3
#2Philipp DieboldH-Index: 10
Last. Norbert SeyffH-Index: 17
view all 3 authors...
We gained detailed empirical knowledge about rolespecific information needs that have to be satisfied in requirements documents in traditional software development processes. Motivated by the widespread use of agile development and existing challenges in industry regarding agile requirements engineering our current research aims at investigating whether agile teams could also benefit from results of our previous research. To support typical agile development characteristics like extensive collab...
4 CitationsSource
The enlargement for developing of software project in the IT Companies by habituated with traditional waterfall methodology, a software developers are facing much problem related to the software requirements. So with respect to that problems the software developers/teams deal with an Agile methodology to facilitate fully satisfaction of the customer related to the software requirements of the projects because of dynamic changing. Therefore in this paper we gathered the data related to the tradit...
1 CitationsSource