KLASIFIKASI KEBUTUHAN NON-FUNGSIONAL MENGGUNAKAN FSKNN BERBASIS ISO/IEC 25010
DOI:
https://doi.org/10.12962/j24068535.v17i2.a823Abstract
Aspek kualitas kebutuhan non-fungsional merupakan salah satu faktor penting yang berperan dalam kesuksesan pengembangan perangkat lunak. Namun, mengidentifikasi aspek kualitas kebutuhan non-fungsional merupakan hal yang sulit untuk dilakukan. Karena aspek kualitas kebutuhan non-fungsional sering ditemukan tercampur dengan kebutuhan fungsional. Oleh karena itu dibutuhkan suatu cara untuk dapat mengidentifikasi aspek kualitas kebutuhan non-fungsional. Penelitian yang ada mampu mengidentifikasi aspek kebutuhan non-fungsional dengan melakukan klasifikasi. Akan tetapi, standar kualitas yang digunakan sebagai rujukan untuk melabeli kalimat kebutuhan masih menggunakan standar ISO/IEC 9126. ISO/IEC 9126 merupakan standar lama yang dirilis pada tahun 2001. Peneliti sebelumnya mengungkapkan ambiguitas dalam enam sub-atribut pada struktur hirarkis ISO/IEC 9126. Oleh karena itu, standar kualitas yang digunakan untuk melabeli kalimat kebutuhan pada penelitian ini adalah ISO/IEC 25010. Sedangkan metode klasifikasi yang digunakan adalah FSKNN. Metode klasifikasi yang digunakan diuji dengan menggunakan nilai tetangga terdekat 10, 20 dan 30. Pada penelitian ini metode FSKNN berhasil memeroleh nilai tertinggi berdasarkan ground truth pakar yaitu precision sebesar 22.55 dan recall 27.64.
Downloads
References
S. Ullah, M. Iqbal, and A. M. Khan, “A survey on issues in non-functional requirements elicitation,” Proc. - Int. Conf. Comput. Networks Inf. Technol., pp. 333–340, 2011.
D. A. Ramadhani, S. Rochimah, and U. L. Yuhana, “Classification of Non-Functional Requirements Using Semantic-FSKNN Based ISO/IEC 9126,” TELKOMNIKA (Telecommunication Comput. Electron. Control., vol. 13, no. 4, p. 1456, 2015.
I. Sommerville, Software Engineering. 2010.
L. Chung and J. D. P. Leite, “On Non-Functional Requirements in Software Engineering,” Concept. Model. Found. …, pp. 363–379, 2009.
M. Rahimi, M. Mirakhorli, and J. Cleland-Huang, “Automated extraction and visualization of quality concerns from requirements specifications,” 2014 IEEE 22nd Int. Requir. Eng. Conf. RE 2014 - Proc., pp. 253–262, 2014.
A. Casamayor, D. Godoy, and M. Campo, “Identification of non-functional requirements in textual specifications: A semi-supervised learning approach,” Inf. Softw. Technol., vol. 52, no. 4, pp. 436–445, 2010.
A. Rashwan, O. Ormandjieva, and R. Witte, “Ontology-based classification of non-functional requirements in software specifications: A new corpus and SVM-based classifier,” Proc. - Int. Comput. Softw. Appl. Conf., no. ii, pp. 381–386, 2013.
J. Cleland-Huang, R. Settimi, X. Zou, and P. Sole, “The detection and classification of non-functional requirements with application to early aspects,” Proc. IEEE Int. Conf. Requir. Eng., pp. 36–45, 2006.
B. Behkamal, M. Kahani, and M. K. Akbari, “Customizing ISO 9126 quality model for evaluation of B2B applications,” Inf. Softw. Technol., vol. 51, no. 3, pp. 599–609, 2009.
W. Suharso and S. Rochimah, “Sistem Penambang.” 2012.
L. S. Jensen and T. Martinez, “Improving Text Classification by Using Conceptual and Contextual Features,” 2000.
H. Al-Kilidar, K. Cox, and B. Kitchenham, “The use and usefulness of the ISO/IEC 9126 quality standard,” 2005 Int. Symp. Empir. Softw. Eng. ISESE 2005, pp. 126–132, 2005.
R. E. Al-Qutaish, “Quality models in software engineering literature: an analytical and comparative study,” J. Am. Sci., vol. 6, no. 3, pp. 166–175, 2010.
F. Febrero, C. Calero, and M. Á. Moraga, “Software reliability modeling based on ISO/IEC SQuaRE,” Inf. Softw. Technol., vol. 70, pp. 18–29, 2016.
K. Gwet, “Self-care behaviors of Italian patients with heart failure,” Eur. J. Cardiovasc. Nurs., vol. 12, no. 1, p. S11, 2013.
Downloads
Published
Issue
Section
How to Cite
License
All papers should be submitted electronically. All submitted manuscripts must be original work that is not under submission at another journal or under consideration for publication in another form, such as a monograph or chapter of a book. Authors of submitted papers are obligated not to submit their paper for publication elsewhere until an editorial decision is rendered on their submission. Further, authors of accepted papers are prohibited from publishing the results in other publications that appear before the paper is published in JUTI unless they receive approval for doing so from the Editor-in-Chief.
JUTI open access articles are distributed under a Creative Commons Attribution-ShareAlike 4.0 International License. This license lets the audience to give appropriate credit, provide a link to the license, and indicate if changes were made and if they remix, transform, or build upon the material, they must distribute contributions under the same license as the original.











