Reference Hub15
A Methodological Approach for Mining the User Requirements Using Apriori Algorithm

A Methodological Approach for Mining the User Requirements Using Apriori Algorithm

Anuja Soni, Anand Saxena, Parul Bajaj
Copyright: © 2020 |Volume: 22 |Issue: 4 |Pages: 30
ISSN: 1548-7717|EISSN: 1548-7725|EISBN13: 9781799804802|DOI: 10.4018/JCIT.2020100101
Cite Article Cite Article

MLA

Soni, Anuja, et al. "A Methodological Approach for Mining the User Requirements Using Apriori Algorithm." JCIT vol.22, no.4 2020: pp.1-30. http://doi.org/10.4018/JCIT.2020100101

APA

Soni, A., Saxena, A., & Bajaj, P. (2020). A Methodological Approach for Mining the User Requirements Using Apriori Algorithm. Journal of Cases on Information Technology (JCIT), 22(4), 1-30. http://doi.org/10.4018/JCIT.2020100101

Chicago

Soni, Anuja, Anand Saxena, and Parul Bajaj. "A Methodological Approach for Mining the User Requirements Using Apriori Algorithm," Journal of Cases on Information Technology (JCIT) 22, no.4: 1-30. http://doi.org/10.4018/JCIT.2020100101

Export Reference

Mendeley
Favorite Full-Issue Download

Abstract

Users of enterprise software are multiple, and their requirements are diverse. Often their specifications are masked by mundane details and at times are vague too. Acknowledging these complexities in requirements engineering, the paper proposes a multistage methodological approach based on Apriori algorithm, a data mining technique. It extracts useful information from the given data on the criteria of mutual association and sufficient frequency. The user requirements captured through interviews and brainstorming are pre-processed for eliminating unnecessary stop words and developing a uniform structure of small stories. Mutual association and occurrence of the requirements are represented through association rules and rule metrics, for example, ‘Lift', ‘Support', and ‘Confidence'. The requirements having strong and moderate association are placed in ‘Top Priority List'; those with nominal, weak, or nil association are placed in ‘Low Priority List'. Gap analysis is employed to validate the defined requirements with respect to stakeholders' expectations. The complete and correct lists of requirements significantly influence the client satisfaction, software development process, and its eventual success.