Sketches of thought: a study of the role of sketching in design problem-solving and its implications for the computational theory of the mind
MetaEdit+: A Fully Configurable Multi-User and Multi-Tool CASE and CAME Environment
CAiSE ;96 Proceedings of the 8th International Conference on Advances Information System Engineering
SketchREAD: a multi-domain sketch recognition engine
Proceedings of the 17th annual ACM symposium on User interface software and technology
Let's go to the whiteboard: how and why software developers use drawings
Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
Supporting Generic Sketching-Based Input of Diagrams in a Domain-Specific Visual Language Meta-Tool
ICSE '07 Proceedings of the 29th international conference on Software Engineering
SUMLOW: early design-stage sketching of UML diagrams on an E-whiteboard
Software—Practice & Experience
A toolkit approach to sketched diagram recognition
BCS-HCI '07 Proceedings of the 21st British HCI Group Annual Conference on People and Computers: HCI...but not as we know it - Volume 1
SketchML a representation language for novel sketch recognition approach
Proceedings of the 2nd International Conference on PErvasive Technologies Related to Assistive Environments
Very Lightweight Requirements Modeling
RE '10 Proceedings of the 2010 18th IEEE International Requirements Engineering Conference
| Hi-index | 0.00 |
[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.