Evolution of Requirements Engineering in Agile Methodology – Literature Review Manuscript Received: 31 March 2024, Accepted: 29 April 2024, Published: 15 September 2024, ORCiD: 0009-0007-7230-1696, https://doi.org/10.33093/jetap.2024.6.2.9
Main Article Content
Abstract
Requirements Agile approaches have transformed engineering. This paper shows how RE in Agile software development has evolved from documentation-heavy to collaborative, adaptable, and customer-focused. Agile was born in the mid-1990s when the industry realized it needed to respond to changing client needs and market volatility. This evolution includes iterative development, client interaction, and emphasizing communication above documentation, as discussed in the paper. By comparing conventional and Agile RE approaches, we demonstrate the benefits of adapting to change, working with customers, and delivering functional software faster. This analysis provides a persuasive description of Agile RE implementation methodologies and resources through a detailed literature review and real-world experiences. User stories and backlog refinement are notable techniques. The research finishes by exploring how these techniques affect team dynamics, project success, and customer satisfaction. RE's Agile difficulties and opportunities are also examined. The findings illuminate RE methods' successful adaptation to Agile projects' dynamic character. Software development is more responsive and effective due to this adaptation.
Article Details
This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License.
References
E. Schön, J. Sedeño, M. Mejías, J. Thomaschewski and M. Escalona, “A Metamodel for Agile
Requirements Engineering,” J. Comput. and Commun., vol. 7, pp. 1-22, 2013.
N. Saher, F. Baharom and R. Romli, “Guideline for the Selection of Requirement
Prioritization Techniques in Agile Software Development: Empirical Research,” Int. J.
Recent Technol. and Eng., vol. 8, no. 5, pp. 3381-3388, 2020.
“Agile Done Right Eliminates The Need for Classical Requirements Engineering,”
https://www.scrum.org/resources/blog/agile-done-right-eliminates-need-classical-
requirements-engineering.
November 2022]
A. Muhammad, A. Siddique, M. Mubassher, A. Aldweesh and Q. Naveed, “Prioritizing Non-
functional Requirements in Agile Process using Multi Criteria Decision Making Analysis,”
IEEE Access, vol. 11, pp. 24631-24654, 2023.
“Classical Project Management vs Agile Project Management,” https://www.visual-
paradigm.com/scrum/classical-vs-agile-project-management/. [2023]
E. Schön, “A Framework for Modeling and Improving Agile Requirements Engineering,
Computer Languages and Systems Department University of Seville,” PhD Thesis, 2017.
V. Gaikwad and P. Joeg, “A Case Study in Requirements Engineering in Context of Agile,”
Int. J. Appl. Eng. Res., vol. 12, no. 8, pp. 1697-1702, 2017.
T. Hirotaka and I. Nonaka, “The New Product Development Game,” Harvard Busine. Rev.,
pp. 137-146, 1986.
K. Schwaber, “SCRUM Development Process,” in J. Sutherland, C. Casanave, J. Miller, P. Patel
and G. Hollowell, Business Object Design and Implementation, Springer, London, 1997.
K. Schwaber, “Agile Project Management with Scrum,” Microsoft Press, 2004.
K. Beck and C. Wilson, “Development of Affective Organizational Commitment: A Cross-
Sequential Examination of Change with Tenure,” J. Vocation. Behavior, vol. 56, pp. 114-136,
W. Laurie, R. Balasubramaniam, C. Alistair, L. Kalle and A. Pekka, “Agile Software
Development Methods: When and Why Do They Work?” in International Federation for
Information Processing Digital Library, Business Agility and Information Technology
Diffusion, 2005.
L. Williams, “What Agile Teams Think of Agile Principles,” Communications, vol. 55, pp. 71-
, 2012.
E. Schön, M. J. Escalona and T. Jörg, “Agile Values and Their Implementation in Practice,”
Int. J. Artif. Intellig. and Interac. Multimedia, vol. 3, no. 5, pp. 61-66, 2015.
I. Sacolick, “A Brief History of The Agile Methodology,” InfoWorld,
https://www.infoworld.com/article/3655646/a-brief-history-of-the-agile-
methodology.html. [8 April 2022]
M. D. Richter, J. D. Mason, M. W. Alford, I. F. Burns and H. A. Helton, “Software
Requirements Engineering Methodology,” Technical report, DTIC Document, 1976.
W. W. Royce, “Managing the Development of Large Software Systems,” in Proc. IEEE
WESCON, vol. 26, pp. 328-388, 1970.
L. Andrea De and A. Qusef, “Requirements Engineering in Agile Software Development,” J.
Emerg. Technol. in Web Intellig., vol. 2, no. 3, pp. 212-220, 2010.
F. Paetsch, A. Eberlein and F. Maurer, “Requirements Engineering and Agile Software
Development,” in Twelfth IEEE Int. Workshops on Enabling Technol.: Infrastruct. for Collab.
Enterpris., Linz, Austria, pp. 308–313, 2003.
T. Fatima and W. Mahmood, “Requirement Engineering in Agile,” IJ Educat. and Manage.
Eng., vol. 4, pp. 20-33, 2019.
A. Batool, Y. Motla, B. Hamid, S. Asghar, M. Riaz, M. Mukhtar and M. Ahmed, “Comparative
Study of Traditional Requirement Engineering and Agile Requirement Engineering,” in
th Int. Conf. Adv. Commun. Technol., pp. 1006-1014, 2013.
R. Tousif Ur, M. N. A. Khan and N. Riaz, “Analysis of Requirement Engineering Processes,
Tools/Techniques and Methodologies,” Int. J. Inform. Technol. and Comput. Sci., vol. 5, pp.
-48, 2013.
G. Umesauda, M. Murad and W. Mahmood, “Crowd-Based Requirement Engineering,” Int.
J. Educ. and Manage. Eng., vol. 8, no. 3, pp. 43-53, 2018.
D. Turk, R. France and B. Rumpe, “Assumptions Underlying Agile Software Development
Processes,” J. Database Manage., vol. 16, no. 4, pp. 62-87, 2005.
A. Rasheed, B. Zafar, T. Shehryar, N. A. Aslam, M. Sajid, N. Ali, S. H. Dar and S. Khalid,
“Requirement Engineering Challenges in Agile Software Development,” Math. Probl. in
Eng., vol. 2021, pp. 696695, 2021.
A. Sillitti and G. Succi, “Requirements Engineering for Agile Methods,” Engineering and
Managing Software Requirements, pp. 309-326, Springer, 2005.
T. Memmel, F. Gundelsweiler and H. Reiterer, “Agile Human-Centered Software
Engineering,” in 21st British HCI Group Annual Conf. People and Comput., Lancaster, UK,
-7 September 2007.
K. Kautz, “Participatory Design Activities and Agile Software Development,” in Int. Working
Conf. IFIP WG, vol. 318, pp. 303–316, Springer, 2010.
M. Fernández, D. Penzenstadler, B. Kuhrmann, M. Broy, “A Meta Model for Artefact-
Orientation: Fundamentals and Lessons Learned in Requirements Engineering,” in D. C.
Petriu, N. Rouquette, Ø. Haugen, Model Driven Engineering Languages and Systems,
MODELS 2010, Lecture Notes in Comput. Sci., vol. 6395, Springer, Berlin.
M. Maguire, “Using Human Factors Standards to Support User Experience and Agile
Design,” in Int. Conf. UAHCI 2013, Las Vegas, USA, 2013.
J. M. Rivero, J. Grigera, G. Rossi, E. Robles Luna, F. Montero and M. Gaedke, “Mockup-
Driven Development: Providing agile support for Model-Driven Web Engineering,” Inform.
and Softw.Technol., vol. 56, no. 6, pp. 670-687, 2014.
E. M. Schön, J. Thomaschewski and M. J. Escalona, “Identifying Agile Requirements
Engineering Patterns in Industry by Means of Empirical Research,” in 22nd Europ. Conf.
Patt. Langua. of Progr., 2017.
E. M. Schön, T. Jörg and M. J. Escalona, “Agile Requirements Engineering: A Systematic
Literature Review,” Comput. Standar. & Interf., vol. 49, pp. 79-91, 2017.
E. Kheirkhah and A. Deraman, “Requirements Engineering in End-User Computing: A
review,” in 2008 Int. Symp. on Inform. Technol., Kuala Lumpur, Malaysia, pp. 1-8, 2008.
A. Gupta, G. Poels and P. Bera, “Using Conceptual Models in Agile Software Development:
A Possible Solution to Requirements Engineering Challenges in Agile Projects,” IEEE
Access, vol. 10, pp. 119745-119766, 2022.
A. Hamzah, M. Omar and R. Romli. “The State of The Art of Agile Kanban Method:
Challenges and Opportunities,” Independ. J. Manage. & Product., vol. 12, no. 8, pp. 2535-
, 2021.