Match!

A systematic review of requirements change management

Published on Jan 1, 2018in Information & Software Technology2.921
· DOI :10.1016/j.infsof.2017.09.004
Shalinka Jayatilleke2
Estimated H-index: 2
(La Trobe University),
Richard Lai13
Estimated H-index: 13
(La Trobe University)
Sources
Abstract
ContextSoftware requirements are often not set in concrete at the start of a software development project; and requirements changes become necessary and sometimes inevitable due to changes in customer requirements and changes in business rules and operating environments; hence, requirements development, which includes requirements changes, is a part of a software process. Previous work has shown that failing to manage software requirements changes well is a main contributor to project failure. Given the importance of the subject, there's a plethora of research work that discuss the management of requirements change in various directions, ways and means. An examination of these works suggests that there's a room for improvement. ObjectiveIn this paper, we present a systematic review of research in Requirements Change Management (RCM) as reported in the literature. MethodWe use a systematic review method to answer four key research questions related to requirements change management. The questions are: (1) What are the causes of requirements changes? (2) What processes are used for requirements change management? (3) What techniques are used for requirements change management? and (4) How do organizations make decisions regarding requirements changes? These questions are aimed at studying the various directions in the field of requirements change management and at providing suggestions for future research work. ResultsThe four questions were answered; and the strengths and weaknesses of existing techniques for RCM were identified. ConclusionsThis paper has provided information about the current state-of-the-art techniques and practices for RCM and the research gaps in existing work. Benefits, risks and difficulties associated with RCM are also made available to software practitioners who will be in a position of making better decisions on activities related to RCM. Better decisions will lead to better planning which will increase the chance of project success.
  • References (175)
  • Citations (8)
📖 Papers frequently viewed together
2012
5 Authors (Muneera Bano, ..., Muhammad Usman)
20 Citations
22 Citations
2001
1 Author (Ralph R. Young)
118 Citations
78% of Scinapse members use related papers. After signing in, all features are FREE.
References175
Newest
2 CitationsSource
Sep 12, 2016 in RE (IEEE International Conference on Requirements Engineering)
#1Waqar Hussain (AUT: Auckland University of Technology)H-Index: 5
#2Didar Zowghi (UTS: University of Technology, Sydney)H-Index: 26
Last. Kelly Blincoe (University of Auckland)H-Index: 12
view all 5 authors...
Software has always been considered as malleable. Changes to software requirements are inevitable during the development process. Despite many software engineering advances over several decades, requirements changes are a source of project risk, particularly when businesses and technologies are evolving rapidly. Although effectively managing requirements changes is a critical aspect of software engineering, conceptions of requirements change in the literature and approaches to their management i...
8 CitationsSource
Sep 1, 2016 in INFOCOM (International Conference on Computer Communications)
#1Sunil Kumar Khatri (Amity University)H-Index: 7
#2Sanjana Malhotra (Amity University)H-Index: 1
Last. Prashant Johri (Galgotias University)H-Index: 4
view all 3 authors...
Software Projects are developed with the prior requirements and should be capable to complete on time under a fixed budget but it gets late to delivered, gets over-budget and even not able to meet user expectations. In agile approach, the estimation of software depends on expert opinion or on any historical data which is used as the input to previous methods like planning poker. The accuracy in estimation is the primary goal of any development but various factors related to environment and techn...
4 CitationsSource
#1Samina Rajper (Shah Abdul Latif University)H-Index: 1
#2Zubair A. Shaikh (Shah Abdul Latif University)H-Index: 3
Objectives: The present study is undertaken to survey the Software development cost estimation techniques. This study will provide guidelines and for researchers and practitioners of software engineering. Methods/Analysis: The study was undertaken by planning, conducting and reporting the literature review (LR) for the years 1991-2016. Findings: The study revealed that several SDCE models have been introduced. The reason for the evolution of software cost estimation models may be the changing na...
1 CitationsSource
Aug 1, 2016 in ICSE (International Conference on Software Engineering)
#1Jessada Tomyim (PSU: Prince of Songkla University)H-Index: 1
#2Amnart Pohthong (PSU: Prince of Songkla University)H-Index: 4
User requirements for software development are getting more complicated and are changing all the time. Not only should the requirements engineering process be well-organized but requirements change management should also be effective, especially for complex systems. However, the software engineering methodology employed can also make requirements change difficult to manage. Object-oriented software engineering using unified modeling language (UML) describes software systems by providing multiple...
14 CitationsSource
#1Naveed Ali (La Trobe University)H-Index: 3
#2Richard Lai (La Trobe University)H-Index: 13
Context: Requirements change is an inevitable software development activity and can occur due to changes in user requirements, increased understanding of the stakeholders' needs, customer organizational re-structure, and availability of new technologies. Timely management of these changes is vital to successful software development, which can be achieved through a rigorous requirements change management (RCM) process. RCM is not straight forward in collocated software development; and with the p...
13 CitationsSource
#1Saurabh Bilgaiyan (KIIT: KIIT University)H-Index: 5
#2Samaresh Mishra (KIIT: KIIT University)H-Index: 3
Last. Madhabananda Das (KIIT: KIIT University)H-Index: 5
view all 3 authors...
For a successful software project, accurate prediction of its overall effort and cost estimation is a very much essential task. Software projects have evolved through a number of development models over the last few decades. Hence, to cover an accurate measurement of the effort and cost for different software projects based on different development models having new and innovative phases of software development, is a crucial task to be done. An accurate prediction always leads to a successful so...
11 CitationsSource
#1Petteri KaresmaH-Index: 1
1 Citations
#1Irum Inayat (Information Technology University)H-Index: 7
#2Siti Salwah Salim (Information Technology University)H-Index: 12
Last. Shahaboddin Shamshirband (IAU: Islamic Azad University)H-Index: 38
view all 5 authors...
We mapped out 17 requirements engineering practices adopted by agile practitioners so far.Identified 5 challenges of traditional requirements engineering overcome by adopting agile requirements engineering.Found 8 challenges posed by following agile requirements engineering.Findings suggest that research context needs attention in terms of more empirical.The empirical results can help to analyse impact of adopting agile requirements engineering. Unlike traditional software development methods, a...
135 CitationsSource
#1Ruchika Malhotra (DCE: Delhi Technological University)H-Index: 20
#2Megha Khanna (DU: University of Delhi)H-Index: 6
Change in a software is crucial to incorporate defect correction and continuous evolution of requirements and technology. Thus, development of quality models to predict the change proneness attribute of a software is important to effectively utilize and plan the finite resources during maintenance and testing phase of a software. In the current scenario, a variety of techniques like the statistical techniques, the Machine Learning (ML) techniques and the Search-based techniques (SBT) are availab...
6 CitationsSource
Cited By8
Newest
Source
#1Arif Ali Khan (NUAA: Nanjing University of Aeronautics and Astronautics)H-Index: 10
#2Muhammad Azeem Akbar (NUAA: Nanjing University of Aeronautics and Astronautics)H-Index: 4
Last. Muhammad Azeem Akbar (NUAA: Nanjing University of Aeronautics and Astronautics)
view all 2 authors...
2 CitationsSource
#2Everton Guimaraes (PSU: Pennsylvania State University)
Last. Hyggo AlmeidaH-Index: 10
view all 7 authors...
Source
#1Muhammad Azeem Akbar (NUAA: Nanjing University of Aeronautics and Astronautics)H-Index: 4
#1Muhammad Azeem Akbar (NUAA: Nanjing University of Aeronautics and Astronautics)
Last. Syed Furqan Qadri (SZU: Shenzhen University)
view all 6 authors...
Source
#1Muhammad Azeem Akbar (NUAA: Nanjing University of Aeronautics and Astronautics)
Last. Sajjad MahmoodH-Index: 9
view all 4 authors...
Source
#1Woogon Shim (Ajou University)
Agile and lean are now the mainstream tenets of software development. This development methodology is attracting attention because it can develop software that operates quickly despite uncertain situations and limited information (requirements), and it can adaptively develop while checking feedback both frequently and regularly. The key is to welcome change without resistance, which is not limited to development but also requires changes in requirement management. However, there is a lack of pra...
Source
#1Muhammad Umair (CUI: COMSATS Institute of Information Technology)H-Index: 6
#2Munam Ali Shah (CUI: COMSATS Institute of Information Technology)H-Index: 12
Last. Muhammad Hamza Sarwar (CUI: COMSATS Institute of Information Technology)
view all 3 authors...
Global Software Development (GSD) is gaining fame every day, we need to understand the GSD environment to make project management more effective and successful. There are many difficulties and challenging activities in GSD environment and one of them is Requirement Change Management (RCM) process. Previous research shows that RCM process is very vague and cannot be used properly in GSD context due to numerous reasons. To address these issue, this study investigates the barriers of RCM Process in...
Source
#1Hasan Salim Alkaf (UPM: King Fahd University of Petroleum and Minerals)H-Index: 1
#2Jameleddine Hassine (UPM: King Fahd University of Petroleum and Minerals)H-Index: 9
Last. Daniel Amyot (U of O: University of Ottawa)H-Index: 30
view all 4 authors...
Abstract Requirements and their models often evolve to reflect changing needs, technologies, and regulations. The decision to implement proposed changes to requirements models relies on means to capture and analyze the potential impact of such changes. The User Requirements Notation (URN) is a standardized requirements modeling language that incorporates two complementary views based on Use Case Maps (UCM), for expressing scenarios and processes bound to architectural components, and on the Goal...
1 CitationsSource
#1Muhammad Azeem Akbar (Chongqing University)H-Index: 4
#2Jun Sang (Chongqing University)H-Index: 5
Last. Shahid Hussain (CUI: COMSATS Institute of Information Technology)H-Index: 5
view all 4 authors...
Source
#1Sajid Anwer (Griffith University)H-Index: 1
#2Lian Wen (Griffith University)H-Index: 7
Last. Zhe Wang (Griffith University)H-Index: 1
view all 3 authors...
Requirement Change is one of the most challenging tasks in software development lifecycle, particularly in the complex context of Global Software Development (GSD). During the last decade, many studies are carried out to address these problems, however, careful examination of these works suggests that there's a potential research gap. This paper has performed a Systematic Literature Review (SLR) to identify the most significant/commonly studied challenges of requirement change management process...
2 CitationsSource