Activities and Practices of Requirements Engineering in Agile Software Environments
DOI:
https://doi.org/10.59992/IJCI.2023.v2n4p2Keywords:
Requirements Engineering, Requirements Elicitation, Requirements Documentation, Requirements Validation, Agile RequirementsAbstract
Requirements are one of the important factors for software success. However, Requirements Engineering (RE) activities, in the Waterfall process model, are done sequentially in the analysis phase, which makes it difficult when RE practitioners think and reason about them in Agile Software Development (ASD) process model. RE practitioners need to find the established RE activities conventions in the ASD process model, especially with an increase of software companies, which transform to the ASD process model, in order to foster their transition to the new model. The objective of this study is to provide RE activities in ASD to allow RE practitioners to utilize the appropriate activity for specific ASD methodology. RE activities in ASD are handled repetitively and on a small scale, which makes them embedded in the development life cycle. This paper focuses on highlighting them in different ASD methodologies and discusses the practices that resolve the traditional Waterfall model issues. Although the ASD model has resolved some traditional RE issues, it introduced other issues, such as a consequence of trying to achieve an adequate balance between agility and stability. In addition, there is a lack of practices that target non-functional requirements.
References
[1] R. S. Pressman, Software engineering : a practitioner’s approach, 7th ed., New York: McGraw-Hill, 2010.
[2] "VersionOne 12th Annual State of Agile Report," VersionOne, 2018.
[3] I. Inayat, S. S. Salim, S. Marczak, M. Daneva and S. Shamshirband, "A Systematic Literature Review on Agile Requirements Engineering Practices and Challenges," Computers in Human Behavior, vol. 51, pp. 915-929, 2015.
[4] K. Beck, M. Beedle, A. v. Bennekum, A. Cockburn, W. Cunningham, M. Fowler, J. Grenning, J. Highsmith, A. Hunt, R. Jeffries, J. Kern, B. Marick, R. C. Martin, S. Mellor, K. Schwaber, J. Sutherland and D. Thomas, "Manifesto for Agile Software Development," 2001. [Online]. Available: http://agilemanifesto.org/. [Accessed 16 January 2019].
[5] E. Hull, K. Jackson and J. Dick, Requirements Engineering, 3rd ed., London: Springer-Verlag, 2011.
[6] C. Pacheco, I. García and M. Reyes, "Requirements Elicitation Techniques: A Systematic Literature Review Based on The Maturity of The Techniques," IET Software, vol. 12, no. 4, pp. 365-378, 2018.
[7] K. Wiegers and J. Beatty, Software Requirements, 3rd ed., Redmond, Washington: Microsoft Press, 2013.
[8] I. Sommerville, Software Engineering, 9th ed., New York: Addison-Wesley, 2011.
[9] E.-M. Schön, J. Thomaschewski and M. J. Escalona, "Agile Requirements Engineering: A Systematic Literature Review," Computer Standards & Interfaces, vol. 49, pp. 79-91, 2017.
[10] O. Liskin, , K. Schneider, F. Fagerholm and J. Münch, "Understanding the Role of Requirements Artifacts in Kanban," in Proceedings Proceedings of the 7th International Workshop on Cooperative and Human Aspects of Software Engineering, 2014.
[11] K. S. Rubin, Essential Scrum A Practical Guide to The Most Popular Agile Process, Pearson Education, Inc, 2013.
[12] N. R. Darwish and S. Megahed, "Requirements Engineering in Scrum Framework," International Journal of Computer Applications, vol. 149, no. 8, pp. 24-29, 2016.
[13] V. N. Vithana, "Scrum Requirements Engineering Practices and Challenges in Offshore Software Development," International Journal of Computer Applications, vol. 116, no. 22, pp. 43-49, 2015.
[14] M. Al-Zewairi, M. Biltawi and W. Etaiwi, "Agile Software Development Methodologies: Survey of Surveys," Journal of Computer and Communications, vol. 5, no. 5, pp. 74-97, 2017.
[15] D. Wells, "Extreme Programming: A gentle introduction," 8 10 2013. [Online]. Available: http://www.extremeprogramming.org/map/project.html. [Accessed 23 12 2018].
[16] N. Baruah, "Requirement Management in Agile Software Environment," in The 2015 International Conference on Soft Computing and Software Engineering, 2015.
[17] M. Poppendieck and T. Poppendieck, Lean Software Development: An Agile Toolkit, Addison Wesley, 2003.
[18] H. Lei, F. Ganjeizadeh, P. K. Jayachandran and P. Ozcan, "A Statistical Analysis of The Effects of Scrum And Kanban on Software Development Projects," Robotics and Computer-Integrated Manufacturing, vol. 43, pp. 59-67, 2017.
[19] M. O. Ahmad, D. Dennehy, K. Conboy and M. Oivo, "Kanban in Software Engineering: A Systematic Mapping Study," The Journal of Systems and Software, vol. 137, pp. 96-113, 2018.
[20] M. Hammarberg and J. Sundén, Kanban in Action, Shelter Island: Manning Publications Co., 2014.
[21] M. Rehkopf, "Kanban vs. Scrum," [Online]. Available: https://www.atlassian.com/agile/kanban/kanban-vs-scrum. [Accessed 09 02 2019].
