Science lab repository requirements elicitation based on text analytics
Requirements elicitation is an important task before any development of system repository can be conducted. Typically, traditional methods such as interview, questionnaire and observation are made to gauge the users‟ needs. However, the users may not be able to spell out specifically of their nee...
Saved in:
| Main Authors: | , , , |
|---|---|
| Format: | Conference or Workshop Item |
| Language: | English English |
| Published: |
2019
|
| Subjects: | |
| Online Access: | http://irep.iium.edu.my/79740/13/79740_Science%20Lab%20Repository%20Requirements_new.pdf http://irep.iium.edu.my/79740/2/79740_Science%20Lab%20Repository%20Requirements%20Elicitation_scopus.pdf http://irep.iium.edu.my/79740/ https://aaec.uitm.edu.my/scds2019/ |
| Tags: |
Add Tag
No Tags, Be the first to tag this record!
|
| Summary: | Requirements elicitation is an important task before any development of
system repository can be conducted. Typically, traditional methods such as interview,
questionnaire and observation are made to gauge the users‟ needs. However, the users
may not be able to spell out specifically of their need especially if there is no available
system to compare resulting to outrageous demands and unrealistic expectations to the
repository developer. An alternative approach to gauge the user needs from users‟
reviews of the on-the-shelf software may be a good starting point. In this paper we
attempt to extract requirements from the users‟ independent reviews gathered from the
internet using text analytics approach. The keywords are visualized based on its
relevance and importance to the user. Then, it is used as a benchmark for the user to
alter to their specific repository needs. From the experimental results, it is observed that
there are functions that are very much needed by the user and yet there are also
functions that are not used at all. Hence, this proposed approach may give insight to the
user and developer about the actual needs of the respective system. It is envisaged that
such approach can be a guide to the novice user and the developer in order to shorten
the time to agree on the development of the repository system. |
|---|