Impact of Non-functional Requirements on Requirements Evolution

Khatter, Kiran; Kalia, Arvind

doi:10.1109/icetet.2013.15

Cited by 10 publications

(4 citation statements)

References 30 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Kebutuhan non-fungsional adalah kriteria kualitas atau kinerja yang harus dipenuhi oleh sistem perangkat lunak (Xiang et al, 2015). Kebutuhan nonfungsional tersebut dianggap mampu mendukung keberhasilan pengembangan perangkat lunak (Ullah, Iqbal and Khan, 2011;Khatter and Kalia, 2013). Namun, kebutuhan non-fungsional sering diabaikan selama proses pengembangan perangkat lunak.…”

Section: Pendahuluanunclassified

Evaluasi Kombinasi Hipernin dan Sinonim untuk Klasifikasi Kebutuhan Non-Functional Berbasis ISO/IEC 25010

Hakim

Rochimah

Fatichah

2019

JTIIK

View full text Add to dashboard Cite

Kebutuhan non-fungsional dianggap mampu mendukung keberhasilan pengembangan perangkat lunak. Namun, kebutuhan non-fungsional sering diabaikan selama proses pengembangan perangkat lunak. Hal ini dikarenakan kebutuhan non-fungsional sering tercampur dengan kebutuhan fungsional. Disamping itu, standar kualitas yang beragam menyebabkan kebingungan dalam menentukan aspek kualitas. Pendekataan yang ada menggunakan ISO/IEC 9126 sebagai referensi untuk mengukur aspek kualitas. 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. Hal ini menimbulkan keraguan serius tentang validitas standar secara keseluruhan. Oleh karena itu, standar kualitas yang digunakan sebagai referensi untuk mengukur aspek kualitas pada penelitian ini adalah ISO/IEC 25010. Selain itu, penelitian ini juga mengusulkan suatu sistem untuk mengidentifikasi aspek kualitas kebutuhan non-fungsional dengan menggunakan 1 level hipernim dan 20 sinonim yang disebut skenario 1. Skenario ini akan dibandingkan dengan 2 level hipernim dan 9 sinonim pada masing-masing sinonim yang disebut skenario 2. Kedua skenario tersebut akan menghasilkan dua data latih berbeda. Kedua data latih tersebut akan dibandingkan menggunakan dua model pengujian yaitu berdasarkan ground truth pakar dan sistem dengan menggunakan metode klasifikasi KNN dan SVM. Hasil pengujian menunjukkan skenario 1 terbukti memberikan nilai lebih baik dibandingkan skenario 2 pada kedua model pengujian, dimana nilai precision dari ground truth pakar, KNN, dan SVM masing-masing 49.3%, 81.0%, dan 74.6%. Abstract Non-Functional requirements are considered capable of supporting the success of software development. However, non-functional requirements are often ignored during the software development process. This is because the quality aspects of non-functional requirements are often mixed with functional requirements. in addition, the number of diverse quality standards causes confusion in determining quality aspects. The existing approach uses ISO / IEC 9126 as a reference to measure quality aspects. ISO / IEC 9126 is an old standard released in 2001. Previous researchers revealed ambiguity in six sub-attributes on the hierarchical structure of ISO / IEC 9126. This raises serious doubts about the validity of the overall standard. Therefore, the quality standard used as a reference to measure the quality aspects of this study is ISO / IEC 25010. In addition, this study also proposes a system to identify aspects of the quality of non-functional requirements using 1 hypernym level and 20 synonyms called scenario 1. This scenario will be compared with 2 hypernym levels and 9 synonyms in each synonym called scenario 2. Both scenarios will produce two different training data. The two training data will be compared using two testing models ie based on expert ground truth and systems using the KNN and SVM classification methods. The test results showed scenario 1 is proven to provide a better value than scenario 2 in both testing models, where the precision values of expert ground truth, KNN, and SVM respectively 49.3%, 81.0%, and 74.6%.

show abstract

Section: Pendahuluanunclassified

Evaluasi Kombinasi Hipernin dan Sinonim untuk Klasifikasi Kebutuhan Non-Functional Berbasis ISO/IEC 25010

Hakim

Rochimah

Fatichah

2019

JTIIK

View full text Add to dashboard Cite

show abstract

“…Requirements originate from stakeholders in natural language [1]. Non-functional requirements (NFRs) are always associated with functional requirements (FRs) [2]. While FRs describe the functions, tasks or behavior that a system must support [3], NFRs represent the particular qualities the systems must have.…”

Section: Introductionmentioning

confidence: 99%

Multi-label Classifier to Deal with Misclassification in Non-functional Requirements

Sabir

Chrysoulas

Banissi

2020

Trends and Innovations in Information Systems and Technologies

View full text Add to dashboard Cite

Automatic classification of software requirements is an active research area; it can alleviate the tedious task of manual labeling and improves transparency in the requirements engineering process. Several attempts have been made towards the identification and classification by type of functional requirements (FRs) as well as non-functional requirements (NFRs). Previous work in this area suffers from misclassification. This study investigates issues with NFRs in particular the limitations of existing methods in the classification of NFRs. The goal of this work is to minimize misclassification and help stakeholders consider NFRs in early phases of development through automatically classifying requirements. In this study, we have proposed an improved requirement detection and classification technique. The following summarizes the proposed approach: A newly created labeled corpus. Textual semantics to augment user requirements by word2vec for automatically extracting features, and A convolution neural network-based multi-label requirement classifier that classifies NFRs into five classes: reliability, efficiency, portability, usability, and maintainability.

show abstract

“…A few research is found in the literature on the identification and measurement of software requirements based on international standards (Abran et al, 2013;Al-Sarayreh et al, 2013a;Meridji et al, 2013;Al-Sarayreh et al, 2013b;2014;Al-Sarayreh and Abran, 2010). Most of research studies target the identification and measurement of software requirements at late phase of the software development life cycle (Khatter and Kalia, 2013).…”

Section: Introductionmentioning

confidence: 99%

“…Software resources requirements are primary requirements in software development cycle, in which they guarantee software suitability and availability of resources for every task executed in such software products (Khatter and Kalia, 2013).…”

Section: Introductionmentioning

confidence: 99%

Towards a Reference Model of Software Resources Quality

Almakadmeh¹,

Meridji²,

Al-Sarayreh³

2018

Journal of Computer Science

View full text Add to dashboard Cite

International standards for software product quality classify software resources as a non-functional requirement for software product. Resources requirements based-standards describe required resources requirements related to software and hardware requirements, in which hardware resources requirements specify requirements relevant to hardware environment in which the software will operate. Whereas, software resources requirements specify sizing and timing requirements required by software product. This paper propose a reference model to identify and measure resources requirements of software product quality based on ISO international standards. The proposed reference model is experimented to present its applicability using the software specifications of an ATM machine to identify and measure the functional size of resources requirements independently from development technology. This measure take place at an early phase of the software development life cycle and used by software project managers as one of the primary inputs for the effort estimation process of software products.

show abstract

Impact of Non-functional Requirements on Requirements Evolution

Cited by 10 publications

References 30 publications

Evaluasi Kombinasi Hipernin dan Sinonim untuk Klasifikasi Kebutuhan Non-Functional Berbasis ISO/IEC 25010

Evaluasi Kombinasi Hipernin dan Sinonim untuk Klasifikasi Kebutuhan Non-Functional Berbasis ISO/IEC 25010

Multi-label Classifier to Deal with Misclassification in Non-functional Requirements

Towards a Reference Model of Software Resources Quality

Contact Info

Product

Resources

About