User Story Extraction from Online News for Software Requirements Elicitation: A Conceptual Model

To specify good requirements, system analysts need to understand the domain knowledge of the system. There are several techniques in requirements elicitation to improve domain knowledge understanding, such as user interviews, questioners, document analysis, and brainstorming. Most of these techniques require profound stakeholder involvement. However, not all software projects can do this task due to limited time or availability of stakeholders. In agile software development, the user story is the de facto standard used for capturing and writing functional requirements. The user story is an appropriate format and easy to understand for writing the results of requirements elicitation. This study purposes a conceptual model to extract user story from online news for improving domain knowledge understanding. The information in the online news contained lesson learned related to certain events. This information may improve the functionality of the software products. The user story consists of three aspects, namely: who, what, and why. Aspect of who represents the role or user, aspect of what shows the purpose or feature, while the aspect of why explains the reason. This format can summarize the lessons learned in the news. Our experimental results indicate that this conceptual model can extract user story from online news. The model manages to extract 105 user stories from 92 aspects of what/why candidate and 109 aspects of who candidate.