International Journal of Mathematical Sciences and Computing (IJMSC)
IJMSC Vol. 12, No. 2, 8 Jun. 2026
Cover page and Table of Contents: PDF (size: 1296KB)
Comparative Study of Functional vs. Non-Functional Requirement Defects in Practice
PDF (1296KB), PP.51-65
Views: 0 Downloads: 0
Author(s)
S. M. Ahsan Habib
1
Md. Shariful Islam
1
Md. Ashraful Islam
1
Jannatul Hoque Samy
1
Jubayer Ahamed
1
Index Terms
Functional Requirement, Non-Functional Requirement, Classification, Comparative Analysis, Decision Rules, Prioritization, Defect
Abstract
The success of a software system mostly depends on how effectively and carefully the requirements are understood, prioritized, and handled. Defects, cost escalation and project failure often occur because of misconception of requirements. While current requirement engineering methods have tried to solve these problems, still there are many that struggle to classify perfectly and prioritize needs. This is especially applied for non-functional requirements, where systematic validation remains as a notable gap in the process. This study suggests a structured FR/NFR Defect Decision Ontology Framework that combines ontology-based thinking including machine learning techniques. The framework is performed on a dataset consisting of 6,086 requirements (3,964 FRs and 2,122 NFRs). Defects are automatically identified by using ontology-driven rules, which leads to 458 defective occurrences. Evaluation has been done with a layered 80/20 train–test split with 10-fold cross-validation. FR/NFR classification, defect detection, defect type classification, and severity classification are four classification tasks which are performed by using models such as Naive Bayes, Support Vector Machine (SVM), Logistic Regression, and Random Forest. The result shows strong performance with the highest accuracy, 87.68% for FR/NFR classification, 97.29% for defect detection, 88.76% for defect type classification, and 82.02% for severity classification. The findings indicate that NFR defects are more complex and less traceable than FR defects. The framework will help to improve both accuracy and understandability that supports more effective requirement analysis and decision-making in software engineering.
Cite This Paper
S. M. Ahsan Habib, Md. Shariful Islam, Md. Ashraful Islam, Jannatul Hoque Samy, Jubayer Ahamed, "Comparative Study of Functional vs. Non-Functional Requirement Defects in Practice", International Journal of Mathematical Sciences and Computing(IJMSC), Vol.12, No.2, pp. 51-65, 2026. DOI: 10.5815/ijmsc.2026.02.04
Reference
[1]Ruslan Bahrii, Tetiana Skrypnyk, Bohdan Romanov, Elena Zaitseva, Houda El Bouhissi, and Volodymyr Lytvynenko. An approach to identifying functional and non-functional requirements in IT-project management using deep learning models. 2025.
[2]Umm-e-Habiba, Markus Haug, Justus Bogner, and Stefan Wagner. How mature is requirements engineering for AI-based systems? A systematic mapping study on practices, challenges, and future research directions. Requirements Engineering, 29(4):567–600, 2024.
[3]Kiramat Rahman, Anwar Ghani, Sanjay Misra, and Arif Ur Rahman. A deep learning framework for non-functional requirement classification. Scientific Reports, 14(1):3216, 2024.
[4]Abdur Rahman, Abu Nayem, and Saeed Siddik. Non-functional requirements classification using machine learning algorithms. International Journal of Intelligent Systems and Applications, 15(3):56–69, 2023.
[5]Cyrille Dongmo. A review of non-functional requirements analysis throughout the SDLC. Computers, 13(12):308, 2024.
[6]Muhammad Nouman, Muhammad Azam, Ashraf Mousa Saleh, Abdullah Alsaeedi, and Hayfa Yousef Abuaddous. A systematic review of non-functional requirements mapping into architectural styles. Bulletin of Electrical Engineering and Informatics, 12(2):1226–1236, 2023.
[7]Devendra Kumar, Anil Kumar, and Laxman Singh. Non-functional requirements elicitation in agile base models. Webology, 19(1):1992 2018, 2022.
[8]Misael C Júnior, Domenico Amalfitano, Lina Garcés, Anna Rita Fasolino, Stevão A Andrade, and Márcio Delamaro. Dynamic testing techniques of non-functional requirements in mobile apps: A systematic mapping study. ACM Computing Surveys (CSUR), 54(10s):1–38, 2022.
[9]Khan Mohammad Habibullah, Gregory Gay, and Jennifer Horkoff. Non-functional requirements for machine learning: Understanding current use and challenges among practitioners. Requirements Engineering, 28(2):283–316, 2023.
[10]Anderson Oliveira, João Correia, Wesley KG Assunção, Juliana Alves Pereira, Rafael de Mello, Daniel Coutinho, Caio Barbosa, Paulo Libório, and Alessandro Garcia. Understanding developers’ discussions and perceptions on non-functional requirements: The case of the spring ecosystem. Proceedings of the ACM on Software Engineering, 1(FSE):517–538, 2024.
[11]Maximilian A Köhl, Kevin Baum, Markus Langer, Daniel Oster, Timo Speith, and Dimitri Bohlender. Explainability as a non-functional requirement. In 2019 IEEE 27th international requirements engineering conference (RE), pages 363–368. IEEE, 2019.
[12]Larissa Chazette and Kurt Schneider. Explainability as a non-functional requirement: challenges and recommendations. Requirements Engineering, 25(4):493–514, 2020.
[13]Pablo Becker, Guido Tebes, Denis Peppino, and Luis Antonio Olsina Santos. Applying an improving strategy that embeds functional and non-functional requirements concepts. Journal of Computer Science & Technology, 19, 2019.
[14]Md Abdur Rahman, Md Ariful Haque, Md Nurul Ahad Tawhid, and MdSaeedSiddik. Classifying non-functional requirements using rnn variants for quality software development. In Proceedings of the 3rd ACM SIGSOFT International Workshop on Machine Learning Techniques for Software Quality Evaluation, pages 25–30, 2019.
[15]Vajeeha Mir Khatian, Qasim Ali Arain, Mamdouh Alenezi, Muhammad Owais Raza, Fariha Shaikh, and Isma Farah. Comparative analysis for predicting non-functional requirements using supervised machine learning. In 2021 1st International Conference on Artificial Intelligence and Data Analytics (CAIDA), pages 7–12. IEEE, 2021.
[16]László Tóth and László Vidács. Comparative study of the performance of various classifiers in labeling non-functional requirements. Information Technology and Control, 48(3):432–445, 2019.
[17]Cody Baker, Lin Deng, Suranjan Chakraborty, and Josh Dehlinger. Automatic multi-class non-functional software requirements classification using neural networks. In 2019 IEEE 43rd annual computer software and applications conference (COMPSAC), volume 2, pages 610–615. IEEE, 2019.
[18]Methinee Amorndettawin and Twittie Senivongse. Non-functional requirement patterns for agile software development. In Proceedings of the 20193rdInternational Conference on Software and e-Business, pages 66–74, 2019.
[19]LuizMarcioCysneirosandJulioCesarSampaiodoPradoLeite. Non-functional requirements orienting the development of socially responsible software. In International Conference on Business Process Modeling, DevelopmentandSupport, pages335–342.Springer,2020.
[20]Jennifer Horkoff, Fatma Başak Aydemir, Evellin Cardoso, Tong Li, Alejandro Maté, Elda Paja, Mattia Salnitri, Luca Piras, John Mylopoulos, and Paolo Giorgini. Goal-oriented requirements engineering: an extended systematic mapping study. Requirements engineering, 24(2):133–160, 2019.
[21]Lenis RWong,DavidSMauricio,GlenDRodriguez,etal. A systematic literature review about software requirements elicitation. Journal of Engineering Science and Technology, 12(2):296–317, 2017.
[22]Eva-Maria Schön, Jörg Thomaschewski, and María José Escalona. Agile requirements engineering: A systematic literature review. Computer standards & interfaces, 49:79–91, 2017.
[23]M Younas, DNA Jawawi, I Ghani, and R Kazmi. Non-functional requirements elicitation guideline for agile methods. Journal of Telecommunication, Electronic and Computer Engineering (JTEC), 9(3-4):137–142, 2017.
[24]Richard RMaitiandFrankJMitropoulos. Prioritizing non-functional requirements in agile software engineering. In Proceedings of the 2017 ACM Southeast Conference, pages 212–214, 2017.
[25]Aleksander Jarzębowicz and Paweł Weichbroth. A qualitative study on non-functional requirements in agile software development. IEEE Access, 9:40458–40475, 2021.
[26]Abdulhafeez Muhammad, Ansar Siddique, Muhammad Mubasher, Amjad Aldweesh, and Quadri Noorulhasan Naveed. Prioritizing non-functional requirements in agile process using multi criteria decision making analysis. IEEE Access, 11:24631–24654, 2023.
[27]Scarlet Rahy and Julian M Bass. Managing non-functional requirements in agile software development. IET software, 16(1):60–72, 2022.
[28]Jie Zou, Ling Xu, Mengning Yang, Xiaohong Zhang, and Dan Yang. Towardscomprehendingthenon-functional requirements through developers’ eyes: An exploration of stack overflow using topic analysis. Information and Software Technology, 84:19–32, 2017.
[29]Arshad Ahmad, Chong Feng, Kan Li, Syed Mohammad Asim, and Tingting Sun. Toward empirically investigating non-functional requirements of ios developers on stack overflow. IEEE Access, 7:61145–61169, 2019.
[30]David Ameller, Xavier Burgués, Dolors Costal, Carles Farré, and Xavier Franch. Non-functional requirements in model-driven development of service-oriented architectures. Science of computer programming, 168:18–37, 2018.
[31]Mohammad Gulam Lorgat and Hugo Paredes. Handling non-functional requirements in software architecture. Architecture, 30:31, 2021.
[32]Rafiq Ahmad Khan, Siffat Ullah Khan, Habib Ullah Khan, and Muhammad Ilyas. Systematic mapping study on security approaches in secure software engineering. Ieee Access, 9:19139–19160, 2021.