Header

UZH-Logo

Maintenance Infos

Flexible sketch-based requirements modeling


Wüest, Dustin; Glinz, Martin (2011). Flexible sketch-based requirements modeling. In: 17th International Working Conference on Requirements Engineering: Foundation for Software Quality, Essen, Germany, 28 March 2011 - 30 March 2011, 100-105.

Abstract

[Context and motivation] Requirements engineers and stakeholders like to create informal, sketchy models in order to communicate ideas and to make them persistent. They prefer pen and paper over current software modeling tools, because the former allow for any kind of sketches and do not break the creative flow. [Question/problem] To facilitate requirements management, engineers then need to manually transform the sketches into more formal models of requirements. This is a tedious, time-consuming task. Furthermore, there is a risk that the original intentions of the sketched models and informal annotations get lost in the transition. [Principal ideas/results] We present the idea for a seamless, tool-supported transition from informal, sketchy drafts to more formal models such as UML diagrams. Our approach uses an existing sketch recognizer together with a dynamic library of modeling symbols. This library can be augmented and modified by the user anytime during the sketching/modeling process. Thus, an engineer can start sketching without any restrictions, and can add both syntax and semantics later. Or the engineer can define a domain-specific modeling language with any degree of formality and adapt it on the fly. [Contribution] In this paper we describe how our approach combines the advantages of modeling with the freedom and ease of sketching in a way other modeling tools cannot provide.

Abstract

[Context and motivation] Requirements engineers and stakeholders like to create informal, sketchy models in order to communicate ideas and to make them persistent. They prefer pen and paper over current software modeling tools, because the former allow for any kind of sketches and do not break the creative flow. [Question/problem] To facilitate requirements management, engineers then need to manually transform the sketches into more formal models of requirements. This is a tedious, time-consuming task. Furthermore, there is a risk that the original intentions of the sketched models and informal annotations get lost in the transition. [Principal ideas/results] We present the idea for a seamless, tool-supported transition from informal, sketchy drafts to more formal models such as UML diagrams. Our approach uses an existing sketch recognizer together with a dynamic library of modeling symbols. This library can be augmented and modified by the user anytime during the sketching/modeling process. Thus, an engineer can start sketching without any restrictions, and can add both syntax and semantics later. Or the engineer can define a domain-specific modeling language with any degree of formality and adapt it on the fly. [Contribution] In this paper we describe how our approach combines the advantages of modeling with the freedom and ease of sketching in a way other modeling tools cannot provide.

Statistics

Citations

Dimensions.ai Metrics

Altmetrics

Downloads

246 downloads since deposited on 15 Feb 2012
19 downloads since 12 months
Detailed statistics

Additional indexing

Item Type:Conference or Workshop Item (Paper), refereed, original work
Communities & Collections:03 Faculty of Economics > Department of Informatics
Dewey Decimal Classification:000 Computer science, knowledge & systems
Language:English
Event End Date:30 March 2011
Deposited On:15 Feb 2012 16:25
Last Modified:21 Sep 2018 07:06
Publisher:Springer-Verlag
Series Name:Lecture Notes in Computer Science
Number:6606
ISSN:0302-9743
ISBN:978-3-642-19857-1
OA Status:Green
Publisher DOI:https://doi.org/10.1007/978-3-642-19858-8
Other Identification Number:merlin-id:3613

Download

Download PDF  'Flexible sketch-based requirements modeling'.
Preview
Filetype: PDF
Size: 86kB
View at publisher
Filetype: Other (Coversheet Pages conversion from application/pdf to application/pdf)