SUMLOW: early design‐stage sketching of UML diagrams on an E‐whiteboard

Chen, Qi; Grundy, John; Hosking, John

doi:10.1002/spe.856

Cited by 25 publications

(18 citation statements)

References 22 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Plimmer and Grundy's [28] discussion of beautification issues in computer-supported sketch-based design tools has illustrated different ways of supporting beautification, as well as userinterface design, by implementing FreeForm [27] and SUMLOW [7] for testing and evaluation purposes. Plimmer and Grundy further identified issues associated with sketch-time beautification (beautifying sketch content as the user draws) and delayed, user controlled beautification (when sketched content is beautified as required), and identified the system requirements to support each approach to beautification.…”

Section: Introductionmentioning

confidence: 99%

“…Plimmer and Grundy further identified issues associated with sketch-time beautification (beautifying sketch content as the user draws) and delayed, user controlled beautification (when sketched content is beautified as required), and identified the system requirements to support each approach to beautification. SUMLOW [7] maintains two visualizations of the UML model ( Figure 1). FreeForm [27] takes a different approach for user interface design: the sketch is retained as is, but a formal visual basic form can be generated from the sketch ( Figure 2).…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Levels of formality in diagram presentation

Yeung

Plimmer

Lobb

et al. 2007

Proceedings of the 19th Australasian Conference on Computer-Human Interaction: Entertaining User Interfaces

View full text Add to dashboard Cite

The incremental beautification of hand-drawn diagrams is a process that is poorly understood. Thus implementation of beautification techniques in computer-based sketch tools is ad hoc, with most only supporting the ends of the spectrum: handdrawn and fully formalized. Hand-drawn diagrams are more effective for early design and review but users are more satisfied with formal designs. This suggests that there may be applications for intermediate levels of formality. By understanding the attributes of visual formality it is possible to beautify a diagram progressively, thereby achieving visually consistent intermediate levels of formality. Here we present a taxonomy of the attributes of visual formality and the implementation of this taxonomy into a sketch tool.

show abstract

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Levels of formality in diagram presentation

Yeung

Plimmer

Lobb

et al. 2007

Proceedings of the 19th Australasian Conference on Computer-Human Interaction: Entertaining User Interfaces

View full text Add to dashboard Cite

show abstract

“…[14,15]). The key idea is that sketch recognition algorithms will convert the produced sketches into semi-formal models.…”

Section: Related Workmentioning

confidence: 99%

FlexiSketch: A Mobile Sketching Tool for Software Modeling

Wüest

Seyff

Glinz

2013

Lecture Notes of the Institute for Computer Sciences, Social Informatics and Telecommunications Engineering

View full text Add to dashboard Cite

Although most software engineers have access to various modeling tools, they often use paper and pencil to sketch ideas and to support modeling activities. This is particularly true when they are working in the field, for example gathering requirements from stakeholders. Sketches documented on paper very often need to be re-modeled in order to allow further processing -an error-prone and timeconsuming task. The aim of our work is to better integrate these early sketching and modeling activities into the overall software engineering process. We have prototyped FlexiSketch, a mobile application that supports freeform, flexible, in-situ modeling and allows software engineers to annotate their models. Apart from the application and the underlying conceptual solution we also present the results of initial experiments. Those suggest that the tool supports freeform sketching similar to paper and pencil, and that practitioners would be willing to use a tool like FlexiSketch in their daily work. Abstract. Although most software engineers have access to various modeling tools, they often use paper and pencil to sketch ideas and to support modeling activities. This is particularly true when they are working in the field, for example gathering requirements from stakeholders. Sketches documented on paper very often need to be re-modeled in order to allow further processing -an error-prone and time-consuming task. The aim of our work is to better integrate these early sketching and modeling activities into the overall software engineering process. We have prototyped FlexiSketch, a mobile application that supports freeform, flexible, in-situ modeling and allows software engineers to annotate their models. Apart from the application and the underlying conceptual solution we also present the results of initial experiments. Those suggest that the tool supports freeform sketching similar to paper and pencil, and that practitioners would be willing to use a tool like FlexiSketch in their daily work.

show abstract

“…SUMLOW [4], and Tahuti [10]. These tools use predefined libraries and thus only support certain languages.…”

Section: Related Workmentioning

confidence: 99%

“…[4,10]). However, such tools rely on predefined notations, so that the user needs to know the underlying modeling language and is restricted to its vocabulary.…”

Section: Introductionmentioning

confidence: 99%

Flexible Sketch-Based Requirements Modeling

Wüest

Glinz

2011

Requirements Engineering: Foundation for Software Quality

View full text Add to dashboard Cite

[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. [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.

show abstract

SUMLOW: early design‐stage sketching of UML diagrams on an E‐whiteboard

Cited by 25 publications

References 22 publications

Levels of formality in diagram presentation

Levels of formality in diagram presentation

FlexiSketch: A Mobile Sketching Tool for Software Modeling

Flexible Sketch-Based Requirements Modeling

Contact Info

Product

Resources

About