AN EFFECTIVE APPROACH FOR ELICITING REQUIREMENTS AND ENSURING TRACEABILITY: A CASE STUDY OF AUTOMATED TELLER MACHINE
DOI:
https://doi.org/10.15282/ijsecs.11.1.2025.1.0133Keywords:
Requirement Elicitation, Requirements, Techniques, Traceability, Functional, Non-functionalAbstract
Requirements elicitation plays a great role in the successful completion of a software project. Elicitation is a productive effort to extract project-associated information from the stakeholders. To gather complete, concise, and clear requirements, the concept of requirements elicitation allows for various analyses and techniques. Requirement elicitation is significant due to the lack of efficiency in accurately articulating their demands for the intended system. Therefore, requirements engineers realize the need to perform elicitation to ensure that the requirements produced are easily accessible, usable, and applicable according to the client’s demands. A software project can be considered successful if it satisfies all the client's requirements. In certain situations, changes in requirements from the client side may arise during the development of the intended software. This research focuses on the challenges of this context, mentioned as follows: many stakeholders are unable to clearly express their needs for the intended system, and the client-side requirements may change often. In this case, traceability plays a vital role in making the necessary changes in the components of the corresponding requirements. Therefore, the impact of any change can be easily visible & the changes can be applied correspondingly. After all, a project’s success can be achieved by ensuring traceability among the components used in eliciting requirements. So, this research proposes an effective approach for eliciting functional and non-functional requirements and ensuring traceability among the corresponding components used in eliciting requirements. In addition, a tool has been designed to ensure traceability among functional requirements, non-functional requirements, and other corresponding components. If any change request arises for any of the requirements, all the corresponding components associated with that requirement can be traced with the help of this tool. Overall, this proposed approach has been applied successfully to a case study of an Automated Teller Machine using this tool.
Downloads
References
[1] P. Zave, “Classification of research efforts in requirements engineering,” ACM Computing Surveys, vol. 29, no. 4, pp. 315–321, 1997. https://doi.org/10.1145/267580.267581
[2] T. Shah and S. Patel, “A novel approach for specifying functional and non-functional requirements using RDS (Requirement Description Schema),” Procedia Computer Science, vol. 79, pp. 852-860, 2016. https://doi.org/10.1016/j.procs.2016.03.083
[3] A. Jarzebowicz and P. Weichbroth, “A qualitative study on non-functional requirements in agile software development,” IEEE Access, vol. 9, pp. 40458-40475, 2021. https://doi.org/10.1109/ACCESS.2021.3064424
[4] J. D. Summers, S. Joshi, and B. Morkos, “Requirements evolution: Relating functional and non-functional requirement change on student project success,” in Proceedings of the ASME International Design Engineering Technical Conferences and Computers and Information in Engineering Conference (IDETC/CIE), Buffalo, NY, USA, 2014, Paper DETC2014-35023. https://doi.org/10.1115/DETC2014-35023
[5] “User stories: An agile introduction,” Agile Modeling. [Online]. Available: https://agilemodeling.com/artifacts/userstory.htm. [Accessed: Dec. 20, 2024].
[6] D. E. Avison and G. Fitzgerald, Information Systems Development: Methodologies, Techniques and Tools, 4th ed. Berkshire, U.K.: McGraw-Hill Education, 2006.
[7] H. F. Hofmann and F. Lehner, “Requirements engineering as a success factor in software projects,” IEEE Software, vol. 18, no. 4, pp. 58-66, 2001. https://doi.org/10.1109/MS.2001.936219
[8] P. Loucopoulos and V. Karakostas, System Requirements Engineering. London, U.K.: McGraw-Hill, 1995.
[9] E. Mumford, Effective Systems Design and Requirements Analysis: The ETHICS Approach. Basingstoke, U.K.: Macmillan, 1995.
[10] B. Nuseibeh and S. Easterbrook, “Requirements engineering: A roadmap,” in Proceedings of the Conference on the Future of Software Engineering (ICSE ’00), Limerick, Ireland, 2000, pp. 35-46. https://doi.org/10.1145/336512.336523
[11] A. Benfell, “Modeling functional requirements using tacit knowledge: A design science research methodology informed approach,” Requirements Engineering, vol. 26, no. 1, pp. 25-42, 2021. https://doi.org/10.1007/s00766-020-00330-4
[12] S. Kugele, W. Haberl, M. Tautschnig, and M. Wechs, “Optimizing automatic deployment using non-functional requirement annotations,” Communications in Computer and Information Science, vol. 17, pp. 400-414, 2008. https://doi.org/10.1007/978-3-540-88479-8_28
[13] M. A. Gondal, N. A. Qureshi, H. Mukhtar, and H. F. Ahmed, “An engineering approach to integrate non-functional requirements (NFR) to achieve high-quality software process,” in Proceedings of the 22nd International Conference on Enterprise Information Systems (ICEIS), Prague, Czech Republic, 2020, pp. 377-384. https://doi.org/10.5220/0009568503770384
[14] B. J. M. Abma and I. Kurtev, “Evaluation of requirements management tools with support for traceability-based change impact analysis,” M.S. thesis, University of Twente, Enschede, The Netherlands, 2009.
[15] B. Ramesh and M. Jarke, “Toward reference models for requirements traceability,” IEEE Transactions on Software Engineering, vol. 27, no. 1, pp. 58-93, 2001. https://doi.org/10.1109/32.895989
[16] A. A. Attia and M. A.-K. Soliman, “A new methodology using QFD for tracing requirements in object-oriented software design process,” The Egyptian International Journal of Engineering Sciences and Technology, vol. 14, no. 3, pp. 288-303, 2011.
[17] D. Duarte, C. Farinha, M. M. da Silva, and A. R. da Silva, “Collaborative requirements elicitation with visualization techniques,” in Proceedings of the IEEE 21st International Workshop on Enabling Technologies: Infrastructure for Collaborative Enterprises (WETICE), Toulouse, France, 2012, pp. 343-348. https://doi.org/10.1109/WETICE.2012.14
[18] I. Sommerville, P. Sawyer, and S. Viller, “Viewpoints for requirements elicitation: A practical approach,” in Proceedings of the IEEE International Conference on Requirements Engineering, Colorado Springs, CO, USA, 1998, pp. 74-81. https://doi.org/10.1109/ICRE.1998.667811
[19] M. A. Abbasi, J. Jabeen, Y. Hafeez, D.-B. Batool, and N. Fareen, “Assessment of requirement elicitation tools and techniques by various parameters,” Software Engineering, vol. 3, no. 2, pp. 7-11, 2015. https://doi.org/10.11648/j.se.20150302.11
[20] F. Khursheed and M. Suaib, “A survey on importance of requirement traceability in software engineering,” International Journal of Engineering and Innovative Technology, vol. 5, no. 4, pp. 109-112, 2015.
[21] O. C. Z. Gotel and A. C. W. Finkelstein, “An analysis of the requirements traceability problem,” in Proceedings of the IEEE International Conference on Requirements Engineering, Colorado Springs, CO, USA, 1994, pp. 94-101. https://doi.org/10.1109/ICRE.1994.292398
[22] R. Torkar, T. Gorschek, R. Feldt, M. Svahnberg, U. A. Raja, and K. Kamran, “Requirements traceability: A systematic review and industry case study,” International Journal of Software Engineering and Knowledge Engineering, vol. 22, no. 3, pp. 385-433, 2012. https://doi.org/10.1142/S021819401250009X
[23] P. Rempel and P. Mäder, “Preventing defects: The impact of requirements traceability completeness on software quality,” IEEE Transactions on Software Engineering, vol. 43, no. 8, pp. 777-797, 2017. https://doi.org/10.1109/TSE.2016.2622264
[24] E. Scharifi, A. Danilenko, U. Weidig, and K. Steinhoff, “Influence of plastic deformation gradients at room temperature on precipitation kinetics and mechanical properties of high-strength aluminum alloys,” International Journal of Engineering Research and Applications, vol. 9, no. 6, pp. 42-48, 2019. https://doi.org/10.9790/9622-0906024248
[25] S. Tiwari and S. S. Rathore, “A methodology for the selection of requirement elicitation techniques,” arXiv preprint arXiv:1709.08481, 2017. https://doi.org/10.48550/arXiv.1709.08481
[26] M. F. Bashir and M. A. Qadir, “Traceability techniques: A critical study,” in Proceedings of the 10th IEEE International Multitopic Conference (INMIC), Islamabad, Pakistan, 2006, pp. 265-268. https://doi.org/10.1109/INMIC.2006.358175
[27] S. Ibrahim, N. B. Idris, M. Munro, and A. Deraman, “A requirements traceability to support change impact analysis,” Asian Journal of Information Technology, vol. 4, no. 4, pp. 345-355, 2005.
[28] M. Lindvall and K. Sandahl, “Traceability aspects of impact analysis in object-oriented systems,” Journal of Software Maintenance: Research and Practice, vol. 10, no. 1, pp. 37-57, 1998. https://doi.org/10.1002/(SICI)1096-908X(199801/02)10:1%3C37::AID-SMR163%3E3.0.CO;2-R DBLP
[29] H. Dar, M. I. Lali, H. Ashraf, M. Ramzan, T. Amjad, and B. Shahzad, “A systematic study on software requirements elicitation techniques and its challenges in mobile application development,” IEEE Access, vol. 6, pp. 63859-63867, 2018. https://doi.org/10.1109/ACCESS.2018.2874981
[30] E. Serna M. and A. Serna A., “A model for documenting requirements elicitation,” Ingeniería, vol. 28, no. 2, Art. no. e19411, 2023. https://doi.org/10.14483/23448393.19411
[31] F. Shahbeklu, Requirement Elicitation from Diverse Sources for Software Projects: A Literature Review and Interview Study, M.S. thesis, Blekinge Institute of Technology, Karlskrona, Sweden, 2024.
[32] “What is ATM-Definition, uses and ATM full meaning,” Paytm. [Online]. Available: https://paytm.com/blog/atm/what-is-atm-full-form-definition-uses/. [Accessed: Dec. 21, 2024].
Downloads
Published
Issue
Section
License
Copyright (c) 2025 The Author(s)
This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.
