%0 Conference Proceedings
%T Verbal Use Case Specifications for Informal Requirements Elicitation
%+ Technion - Israel Institute of Technology [Haifa]
%A Kantorowitz, Eliezer
%Z Part 2: Building Bridges: Non-formal Modeling (ECCE 2011)
%< avec comité de lecture
%( Lecture Notes in Computer Science
%B 7th Workshop on Human-Computer Interaction and Visualization (HCIV)
%C Rostock, Germany
%Y Achim Ebert
%Y Gerrit C. Veer
%Y Gitta Domik
%Y Nahum D. Gershon
%Y Inga Scheler
%I Springer Berlin Heidelberg
%3 Building Bridges: HCI, Visualization, and Non-formalModeling
%V LNCS-8345
%P 165-174
%8 2011-08-23
%D 2011
%R 10.1007/978-3-642-54894-9_12
%K Satisfactory specifications
%K Computer Supported Cooperative Work
%K CSCW
%K UML
%K Use case
%K Software specifications
%K Software requirements
%K Requirements elicitation
%K Human Factors
%K Verification
%K non-ambiguous
%K natural language
%K correct specifications
%K verbal specifications
%K formal specifications
%K behavioral study
%Z Computer Science [cs]Conference papers
%X 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.
%G English
%Z TC 13
%Z WG 13.7
%2 https://hal.science/hal-01414703/document
%2 https://hal.science/hal-01414703/file/325006_1_En_12_Chapter.pdf
%L hal-01414703
%U https://hal.science/hal-01414703
%~ IFIP-LNCS
%~ IFIP
%~ IFIP-AICT
%~ IFIP-TC13
%~ IFIP-HCIV
%~ IFIP-WG13-7
%~ IFIP-LNCS-8345