Enhancing Software Feature Extraction Results Using Sentiment Analysis to Aid Requirements Reuse

Indra Kharisma Raharjana,Via Aprillya,Army Justitia,Badrus Zaman,Shukor Sanim Mohd Fauzi

doi:10.3390/computers10030036

Indra Kharisma Raharjana, Via Aprillya + Show 3 more

Open Access

https://doi.org/10.3390/computers10030036

Copy DOI

Abstract

Recently, feature extraction from user reviews has been used for requirements reuse to improve the software development process. However, research has yet to use sentiment analysis in the extraction for it to be well understood. The aim of this study is to improve software feature extraction results by using sentiment analysis. Our study’s novelty focuses on the correlation between feature extraction from user reviews and results of sentiment analysis for requirement reuse. This study can inform system analysis in the requirements elicitation process. Our proposal uses user reviews for the software feature extraction and incorporates sentiment analysis and similarity measures in the process. Experimental results show that the extracted features used to expand existing requirements may come from positive and negative sentiments. However, extracted features with positive sentiment overall have better values than negative sentiments, namely 90% compared to 63% for the relevance value, 74–47% for prompting new features, and 55–26% for verbatim reuse as new requirements.

Highlights

Requirement elicitation is the process of searching and acquiring stakeholders’ interests in a software development [1,2,3]
The comparison results show that the software feature produced by POS chunking has the best F-measure value compared to other approaches, which indicates the effectiveness of the POS tag pattern (See Figure 2)
We used POS chunking as the software feature extraction method in this study

Summary

Introduction

Requirement elicitation is the process of searching and acquiring stakeholders’ interests in a software development [1,2,3]. Techniques that are commonly used in requirement elicitation are open/closed interviews, scenarios, use cases, observations, questionnaires, brainstorming, prototyping, focus group discussions, and joint application development (JAD) workshops [6]. It is widely recognized among researchers and industry practitioners that software projects are very prone to failure when the requirements elicitation process is not carried out properly [7,8]. In the software development life cycle (SDLC), this undertaking is challenging because it involves socio-technical characteristics and changing requirements [9,10], and because there may be problems of ambiguity and tacit knowledge transfer [11,12] Such problems, if found too late, can lead to high rework costs because they necessitate modifications in other processes [4,13]

Methods

Results

Discussion

Conclusion