Verbal Use Case Specifications for Informal Requirements Elicitation - Building Bridges: HCI, Visualization, and Non-formal Modeling Access content directly
Conference Papers Year : 2014

Verbal Use Case Specifications for Informal Requirements Elicitation


Constructing a software system from poor specifications may necessitate costly repairs. We introduce the notion “satisfactory specifications” for quality specifications that do not require costly repairs. Satisfactory specifications may be produced by a Computer Supported Collaborative Work (CSCW) team incorporating all the relevant experts and the stakeholders. It is suggested that the CSCW team develops use case specifications, where its expertise is especially useful. Specifying in a natural language understood by all team members facilitates needed intensive cooperation between different team members. Compared to specifications formulated in formal terminology, verbal formulations in domain language represent a textual visualization. Translating the verbal specifications into formal UML diagrams provides a further graphical visualization. It is suggested that each specification is provided with a separate example for each kind of the possible situations. These examples may clarify meaning of poorly formulated specifications, facilitate identifying faults in formal specifications and employed for software debugging.
Fichier principal
Vignette du fichier
325006_1_En_12_Chapter.pdf (156.16 Ko) Télécharger le fichier
Origin : Files produced by the author(s)

Dates and versions

hal-01414703 , version 1 (12-12-2016)





Eliezer Kantorowitz. Verbal Use Case Specifications for Informal Requirements Elicitation. 7th Workshop on Human-Computer Interaction and Visualization (HCIV), Aug 2011, Rostock, Germany. pp.165-174, ⟨10.1007/978-3-642-54894-9_12⟩. ⟨hal-01414703⟩
95 View
212 Download



Gmail Facebook X LinkedIn More