Title:	SCENARIO CREATION METHOD TO ELICIT REQUIREMENTS BY STAKEHOLDERS
Author(s):	Junko Shirogane
ISBN:	978-989-8533-62-3
Editors:	Miguel Baptista Nunes, Pedro Isaías and Philip Powell
Year:	2017
Edition:	Single
Keywords:	Operation History, Scenario, Requirements
Type:	Full Paper
First Page:	69
Last Page:	76
Language:	English
Cover:
Full Contents:	click to dowload
Paper Abstract:	Typically software developers create use case diagrams and scenarios after stakeholders identify their requirements. However, stakeholders often have difficulty identifying their actual requirements. Consequently, the generated diagrams and scenarios may not reflect stakeholders’ requirements. The previous paper proposed a support method to create use case diagrams from the operation histories of applications. When developing a new application, similar applications often exist. Thus, our method records the operation histories when stakeholders try to use similar applications. Then the use case diagrams are generated from the recorded operation histories and customized. Because stakeholders only operate similar applications, use case diagrams that appropriately reflect stakeholders’ requirements can be easily obtained. Herein our method is expanded to create scenarios in a use case. When generating use case diagrams, the operation histories are divided into use cases. Because operation histories record the input and selection of widgets in windows, the input and selection sequences are constructed as event sequences in scenarios. Event sentences are often represented in a natural language. Thus, each event is represented in a natural language sentence using label names of widgets. The sequences of event sentences are generated as scenarios. Although there are several types of scenarios such as main scenario, alternative scenario, and exception scenario, all are generated as individual scenarios.
	Go Back