Using classification techniques for informal requirements in the requirements analysis-supporting system

Research output: Contribution to journalArticlepeer-review

55 Scopus citations

Abstract

In order to efficiently develop large-scale and complicated software, it is important for system engineers to correctly understand users' requirements. Most requirements in large-scale projects are collected from various stakeholders located in various regions, and they are generally written in natural language. Therefore, the initial collected requirements must be classified into various topics prior to analysis phases in order to be usable as input in several requirements analysis methods. If this classification process is manually done by analysts, it becomes a time-consuming task. To solve this problem, we propose a new bootstrapping method which can automatically classify requirements sentences into each topic category using only topic words as the representative of the analysts' views. The proposed method is verified through experiments using two requirements data sets: one written in English and the other in Korean. The significant performances were achieved in the experiments: the 84.28 and 87.91 F1 scores for the English and Korean data sets, respectively. As a result, the proposed method can provide an effective function for an Internet-based requirements analysis-supporting system so as to efficiently gather and analyze requirements from various and distributed stakeholders by using the Internet.

Original languageEnglish
Pages (from-to)1128-1140
Number of pages13
JournalInformation and Software Technology
Volume49
Issue number11-12
DOIs
StatePublished - Nov 2007
Externally publishedYes

Keywords

  • Internet-based application system
  • Requirements classification
  • Requirements engineering
  • Similarity measure

Fingerprint

Dive into the research topics of 'Using classification techniques for informal requirements in the requirements analysis-supporting system'. Together they form a unique fingerprint.

Cite this