A Scrum Model as a Tool for Track Changing Requirements
DOI:
https://doi.org/10.58916/jhas.v8i1.504Keywords:
Requirement engineering, traditional requirement engineering, agile, scrumAbstract
Over the years, the importance of requirements engineering in software development and its important role in collecting and documenting all customer requirements has become clear and evident. However, with the development of requirements engineering methodologies from traditional to modern ones, such as the agile methodology, it has become difficult to ascertain the validity of the important requirements for stakeholders and whether they must be implemented during the development process without the slightest doubt that they may be modified later or re-maintained. In this paper, focus has been placed on the importance of stakeholder vision and their view of the desired system through the application of the most important models of the agile methodology for the development and technology of Scrum to reach the largest coverage of their requirements with the least dependencies in the future.
Downloads
References
] Lucia, A.D. and A. Qusef, “Requirements engineering in agile software development”, Journal of emerging technologies in web intelligence, vol.2, no.3, pp.212-220, 2010.
A. Sillitti, M. Ceschi, B. Russo, and G. Succi, “Managing uncertainty in requirements: a survey in documentation-driven and agile companies”, Proc. 11 Th IEEE Int. Symposium on Software Metrics, pp. 10–17, 2005.
Carrizo, D., Dieste, O., & Juristo,N., “Systematizing requirements elicitation technique selection”. Information and Software Technology, no.56, pp.644–669,2014.
Chakraborty, S., Sarker, S., & Sarker, S, “An exploration into the process of requirements elicitation: A grounded approach”, Journal of the association for information systems, vol. 11, no.4, 2010.
Asma Batool, Yaser Hafeez *, Sohail Asghar , Muhammad A. Abbas and Muhammad S. Hassan, “A Scrum Framework for Requirement Engineering Practices”, Pakistan Academy of Sciences, vol.50, no.4, pp. 263–270,2013.
Abrahamsson, P., O. Salo, J. Ronkainen & J. Warsta, “Agile Software Development Methods: Review and Analysis”, VTT Electronics, VTT Publications, p. 107-478 ,2002.
K. Schwaber, “Agile project management with Scrum Redmond”, Wash.: Microsoft Press, 2004.
Xavier Franch1 , Norbert Seyff2 ,Marc Oriol1 ,Samuel Fricker 2 , Iris Groher3, Michael Vierhauser3 and Manuel Wimmer3, “Towards Integrating Data-Driven Requirements Engineering into the Software Development Process”, International Working Conference on Requirements Engineering: Foundation for Software Quality, 26th International Working Conference, p.135-142, March 24–27, 2020.
Nagy Ramadan Darwish, Salwa Megahed, “Requirements Engineering in Scrum Framework”, International Journal of Computer Applications, vol.149,no.8, September 2016.
Valpadasu Hema, Sravanthi Thota , S.Naresh Kumar , Ch Padmaja , C.Bala Rama Krishna, K Mahender, “Scrum: An Effective Software Development Agile Tool”. IOP Conference Series: Materials Science and Engineering, 2020.
Mark S. Rosenbaum, Mauricio Losada Otalora, Germa´n Contreras Ramı´rez, “How to create a realistic customer journey map”, Business Horizons, no.8, 2016.
Martin Fowler, Alan Cooper, and Marty Cagan, “user story mapping discover the whole story build the right product”, United States of America, O’Reilly Media,2014.
Dusan Savic, Alberto Rodrgues Da Siliva,Sinisa Vlajic, Sasad.Lazarevic,”Use Case Specification at Different Levels of Abstraction”, 18th International Conference on The Quality of Information and Communications Technology, 2012
” What is Use Case Diagram?”, Visual Paradigm,2022.[online]. Available: https://www.visual-paradigm.com/guide/uml-unified-modeling-language/what-is-use-case-diagram/[accessed:Dec.12.2022].
Downloads
Published
Issue
Section
How to Cite
