Author:
Junko Shirogane
Affiliation:
Tokyo Woman’s Christian University, Japan
Keyword(s):
User Interface, Scenario, Usability.
Related
Ontology
Subjects/Areas/Topics:
Requirements Elicitation and Specification
;
Software Engineering
;
Software Engineering Methods and Techniques
Abstract:
Scenarios, which represent operation flows of a software package, are often described in requirements elicitation phase by a natural language. Stakeholders that do not have knowledge of software development are said that they can easily understand and describe scenarios. However, defining appropriate granularities of input and output items and individual operations and describing scenarios without mistakes and missing are difficult. Actual task flows are not always appropriate for computer operation flows. In addition, even if the actual task flows in business are strictly represented in scenarios, software may not be usable. it is difficult to describe appropriate operation flows considering usability in scenarios. When a new software package is developed, stakeholders may survey existing software packages similar to the software package that they require. In this method, to support for describing appropriate scenarios, stakeholders try to use the existing software packages, and sce
narios are generated using the operation histories. Scenarios are customized considering the
actual task flows in business, limitations of input and output orders, and usability, and stakeholders can obtain the required scenarios.
(More)