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
Requirement Elicitation plays a great role in the successful completion of a software project. Elicitation is a productive effort to extricate project-associated information from the stakeholders. To gather complete, concise, and clear requirements, the concept of requirement elicitation allows various analytics and techniques. Requirement elicitation is significant due to the lack of efficiency in accurately articulating their demands towards the intended system. Therefore, requirement engineers realize the need to perform elicitation to ensure that the requirements produced are easily accessible, useable, and applicable according to the client’s demands. A software project can be considered successful if it satisfies all the requirements of the client. 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 toward 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 to any of the requirements, all the corresponding components associated with that requirement can be traced with the help of this tool. In overall, this proposed approach has been applied successfully to a case study of an Automated Teller Machine using this tool.
References
[1] P. Zave, “Classification of Research Efforts in Requirements Engineering,” 1997.
[2] T. Shah and S. Patel, “A Novel Approach for Specifying Functional and Non-functional Requirements Using RDS (Requirement Description Schema),” Procedia Comput. Sci., vol. 79, pp. 852–860, 2016, doi: 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, doi: 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,” Proc. ASME Des. Eng. Tech. Conf., vol. 3, 2014, doi: 10.1115/DETC2014-35023.
[5] “User Stories: An Agile Introduction.” https://agilemodeling.com/artifacts/userstory.htm (accessed Dec. 20, 2024).
[6] D. Avison and G. Fitzgerald, “Information systems development: methodologies, techniques & tools,” Inf. Syst. Ser., p. 645, 2006, Accessed: Dec. 20, 2024. [Online]. Available: https://books.google.com/books/about/Information_Systems_Development.html?id=xk9dPwAACAAJ
[7] H. F. Hofmann and F. Lehner, “Requirements engineering as a success factor in software projects,” IEEE Softw., vol. 18, no. 4, pp. 58–66, Jul. 2001, doi: 10.1109/MS.2001.936219.
[8] “Loucopoulos, P. and Karakostas, V. (1995) System Requirements Engineering. McGraw Hill, London. - References - Scientific Research Publishing.” https://www.scirp.org/reference/referencespapers?referenceid=3428127 (accessed Dec. 20, 2024).
[9] E. Mumford, “Effective systems design and requirements analysis : the ETHICS approach,” p. 188, 1995.
[10] “Nuseibeh, B. and Easterbrook, S. (2000) Requirements Engineering A Roadmap. Proceedings of the Conference on the Future of Software Engineering, 35-46. - References - Scientific Research Publishing.” https://www.scirp.org/reference/referencespapers?referenceid=1706167 (accessed Dec. 20, 2024).
[11] A. Benfell, “Modeling functional requirements using tacit knowledge: a design science research methodology informed approach,” Requir. Eng., vol. 26, no. 1, pp. 25–42, 2021, doi: 10.1007/s00766-020-00330-4.
[12] S. Kugele, W. Haberl, M. Tautschnig, and M. Wechs, “Optimizing automatic deployment using non-functional requirement annotations,” Commun. Comput. Inf. Sci., vol. 17 CCIS, pp. 400–414, 2008, doi: 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,” ICEIS 2020 - Proc. 22nd Int. Conf. Enterp. Inf. Syst., vol. 2, no. Iceis, pp. 377–384, 2020, doi: 10.5220/0009568503770384.
[14] B. J. M. Abma and I. Kurtev, “Evaluation of requirements management tools with support for traceability-based change impact analysis,” 2009.
[15] B. Ramesh and M. Jarke, “Towards Reference Models for,” Source, vol. 1, no. 1, pp. 1–54, 1999, [Online]. Available: http://www.springerlink.com/index/6q31q7556n440211.pdf%5Cnhttp://scholar.google.com/scholar?hl=en&btnG=Search&q=intitle:TOWARDS+REFERENCE+MODELS+FOR+REQUIREMENTS+TRACEABILITY#2%5Cnhttp://scholar.google.com/scholar?hl=en&btnG=Search&q=intitle:Towards+Refer
[16] A. A. Attia and M. A. Soliman, “EIJEST A NEW MEHODOLOGY USING QFD FOR TRACING REQUIREMENTS IN,” vol. 14, no. 3, pp. 288–303, 2011.
[17] “D. Duarte, C. Farinha, M. M. da silva, and A.R. da silva, ‘Collaborative Requirement Elicitation with visualization Techniques,’ IEEE, pp. 343 - 348 2012.”.
[18] I. Sommerville, P. Sawyer, and S. Viller, “Viewpoints for requirements elicitation: A practical approach,” Proc. IEEE Int. Conf. Requir. Eng., pp. 74–81, 1998, doi: 10.1109/ICRE.1998.667811.
[19] M. Ahmed Abbasi, J. Jabeen, Y. Hafeez, D.-B. Batool, and N. Fareen, “Assessment of Requirement Elicitation Tools and Techniques by Various Parameters,” Softw. Eng., vol. 3, no. 2, pp. 7–11, 2015, doi: 10.11648/j.se.20150302.11.
[20] F. Khursheed and M. Suaib, “A Survey on Importance of Requirement Traceability in Software Engineering,” Int. J. Eng. Innov. Technol., vol. 5, no. 4, pp. 109–112, 2015, doi: 10.17605/OSF.IO/ZPVSK.
[21] O. C. Z. Gotel and A. C. W. Finkelstein, “Analysis of the requirements traceability problem,” Proc. Int. Conf. Requir. Eng., pp. 94–101, 1994, doi: 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,” Int. J. Softw. Eng. Knowl. Eng., vol. 22, no. 3, pp. 385–433, 2012, doi: 10.1142/S021819401250009X.
[23] P. Rempel and P. Mader, “Preventing defects: The impact of requirements traceability completeness on software quality,” IEEE Trans. Softw. Eng., vol. 43, no. 8, pp. 777–797, Aug. 2017, doi: 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,” J. Eng. Res. Appl., vol. 9, no. 1, pp. 24–29, 2019, doi: 10.9790/9622.
[25] S. Tiwari and S. S. Rathore, “A Methodology for the Selection of Requirement Elicitation Techniques,” 2017, [Online]. Available: http://arxiv.org/abs/1709.08481
[26] M. F. Bashir and M. A. Qadir, “Proceedings, 10th IEEE International Multitopic Conference, INMIC 2006 : 2006, 23-24 December, 2006, Islāmābād, Pakistan.,” p. 506, 2006.
[27] K. Lumpur, F. Technology, and I. System, “A REQUIREMENTS TRACEABILITY TO SUPPORT CHANGE IMPACT ANALYSIS Suhaimi Ibrahim , Norbik Bashah Idris Centre For Advanced Software Engineering , Malcolm Munro Department of Computer Science , University of Durham , United Kingdom Aziz Deraman,” pp. 1–12.
[28] “M. Lindvall and K. Sandahl, 1998. ‘Traceability Aspects of Impacts Analysis in Object-Oriented System’, Journal of Software Maintenance Research And Practice, vol. 10, pp. 37-57.”.
[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, doi: 10.1109/ACCESS.2018.2874981.
[30] E. S. M, “Ingeniería Un modelo para documentar la elicitación de requisites,” no. 2, pp. 1–24, 2023.
[31] I. Study and F. Shahbeklu, “Requirement Elicitation from Diverse Sources for Software Projects,” no. May, 2024.
[32] “What is ATM - Definition, Uses and ATM Full Meaning.” 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.
