Sketches and diagrams in practice

@article{Baltes2015SketchesAD,
  title={Sketches and diagrams in practice},
  author={Sebastian Baltes and Stephan Diehl},
  journal={Proceedings of the 22nd ACM SIGSOFT International Symposium on Foundations of Software Engineering},
  year={2015}
}
  • Sebastian Baltes, S. Diehl
  • Published 11 November 2014
  • Computer Science
  • Proceedings of the 22nd ACM SIGSOFT International Symposium on Foundations of Software Engineering
Sketches and diagrams play an important role in the daily work of software developers. In this paper, we investigate the use of sketches and diagrams in software engineering practice. To this end, we used both quantitative and qualitative methods. We present the results of an exploratory study in three companies and an online survey with 394 participants. Our participants included software developers, software architects, project managers, consultants, as well as researchers. They worked in… 

Figures and Tables from this paper

Sketches and diagrams in practice
TLDR
It was found that the majority of participants related their sketches to methods, classes, or packages, but not to source code artifacts with a lower level of abstraction.
Linking sketches and diagrams to source code artifacts
TLDR
SketchLink is presented, a tool that aims at increasing the value of sketches and diagrams created during software development by supporting developers in these tasks by embedding the links in Javadoc comments and visualizing them in situ in the source code editor as graphical icons.
Using sketch recognition for capturing developer's mental models
TLDR
A preliminary approach that consists in automatically capture information from the sketches using image processing and pattern recognition to verify that simply capturing sketches can provide useful information for later use and then improve the modeling process efficiency.
Towards Employing Informal Sketches and Diagrams in Software Development
TLDR
This work hypothesize about understandability and helpfulness of these sketches and their deeper inclusion into software development process and is leveraging the fact that it has a collection of such sketches affiliated to a commercial software system.
Round-Trip Sketches: Supporting the Lifecycle of Software Development Sketches from Analog to Digital and Back
TLDR
The conceptual design and a prototype of LivelySketches are presented, a tool that supports the "round-trip" lifecycle of sketches from analog to digital and back and includes capturing both analog and digital sketches as well as relevant context information.
Sketching and Conceptions of Software Design
  • D. Socha, J. Tenenberg
  • Computer Science
    2015 IEEE/ACM 8th International Workshop on Cooperative and Human Aspects of Software Engineering
  • 2015
TLDR
A study of sketching and design within a software organization in which hundreds of hours of video of development activity in situ were captured and analyzed is described to question how researcher conceptions of software design affect the way in which design is empirically studied.
Improving Model Usability and Utility by Layered Diagrams
  • Harald Störrle
  • Computer Science
    2018 IEEE/ACM 10th International Workshop on Modelling in Software Engineering (MiSE)
  • 2018
TLDR
Whether layered diagrams are a useful addition to the software engineers repertoire is understood, and they are easy to comprehend and apply by modelers, and allow richer models.
Design Workspaces: Preserving and Recovering Meaning in Groups of Sketches - eScholarship
This thesis presents a prototype sketching tool designed to address the problem of reusing sketches. Our goal is to help designers preserve, understand, and communicate meaning that is represented in
Examining truthfulness of informal diagrams more than a year after their creation
TLDR
This work proposed an approach for measuring truthfulness of such informal diagrams, and conducted a mini-experiment on sample diagrams (aged 13–21 months) to measure their truthfulness.
Characterizing the Development and Usage of Diagrams in Embedded Software Systems
TLDR
The conceptual model, which characterizes the attributes of a diagram development and usage, will help to express the meaning of terms used by domain experts to discuss the problems and find the relationships between these attributes.
...
1
2
3
4
5
...

References

SHOWING 1-10 OF 50 REFERENCES
Sketches and diagrams in practice
TLDR
It was found that the majority of participants related their sketches to methods, classes, or packages, but not to source code artifacts with a lower level of abstraction.
Sketching and Drawing in the Design of Open Source Software
TLDR
This study focuses on the diagramming practices used in the design of Open Source Software, where the norm is highly distributed group work and shows that although contributors understand the advantages of using diagrams for design-related activities, diagrams are infrequently used.
Follow that sketch: Lifecycles of diagrams and sketches in software development
TLDR
Through a series of interviews with computer science researchers who develop software, the purpose, contexts, and media in which they created and re-created sketches and diagrams were probed, and the ways in which these informal visualizations evolved over time were analyzed.
Let's go to the whiteboard: how and why software developers use drawings
TLDR
Findings from semi-structured interviews that have been validated with a structured survey show that most of the diagrams had a transient nature because of the high cost of changing whiteboard sketches to electronic renderings.
Notation and representation in collaborative object-oriented design: an observational study
TLDR
Observational studies of collaborative design exercises found that teams intentionally improviserepresentations and organize design information in responseto ad-hoc needs, which arise from the evolution of the design, and which are difficult to meet with fixed standard notations.
Software Design and Architecture The once and future focus of software engineering
TLDR
Directions for design research are outlined, including: (a) drawing lessons, inspiration, and techniques from design fields outside of computer science, (b) emphasizing the design of application "character" (functionality and style) as well as the application's structure, and (c) expanding the notion of software to encompass the designof additional kinds of intangible complex artifacts.
Stories, Sketches, and Lists: Developers and Interaction Designers Interacting Through Artefacts
TLDR
This paper finds that both sketches and design stories have critical roles, and that these artefacts support creation and reflection, facilitate resolution of contradiction, and also work at a level of consciousness that is below the level of self-awareness.
Understanding how and why open source contributors use diagrams in the development of Ubuntu
TLDR
The study shows that diagrams are not actively used in many scenarios where they commonly would in co-located software development efforts, and presents design considerations for potential systems aimed at better supporting diagram use in OSS development.
How designers design and program interactive behaviors
TLDR
In a survey of 259 designers, 86% reported that the behavior is more difficult to prototype than the appearance, and designers want to explore multiple versions of behaviors, but today's tools make this difficult.
...
1
2
3
4
5
...