Natural language is the main presentation means in industrial requirements documents. In such documents, system behavior is mostly specified in the form of scenarios, with every scenario written as a sequence of sentences in natural language. The scenarios are often incomplete: For the authors of requirements documents some facts are so obvious that they forget to mention them; this surely causes problems for the requirements analyst. In our previous work we developed an approach to translate textual scenarios to message sequence charts (MSCs). In order that the produced MSCs can be used for further development, they must be validated: i.e., for each MSC we have to say whether it really represents a possible system behavior, and whether the textual scenario was correctly interpreted. In the presented paper we suggest an approach to visualize different interpretations for the same scenario. For visualized scenarios, the user can decide, which of them represent allowed system behavior. This allows, in turn, to generalize exemplary scenarios to universal specifications. Applicability of the presented approach was confirmed in a case study. 1. A Scenario Can Have Several Interpretations At the beginning of every software project, some kind of requirements document is usually written. The majority of these documents are written in natural language, as the survey by Mich et al. shows . This results in requirements documents are imprecise, incomplete, and inconsistent. From the linguistic point of view, document authors may introduce three defect types, without perceiving the
To submit an update or takedown request for this paper, please submit an Update/Correction/Removal Request.