Follow that sketch: Lifecycles of diagrams and sketches in software development

Walny, Jagoda; Haber, Jonathan; Dörk, Marian; Sillito, Jonathan; Carpendale, Sheelagh

doi:10.1109/vissof.2011.6069462

Cited by 27 publications

(31 citation statements)

References 18 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Walny et al [43] analyzed eight workflows of software developers in an academic setting. They report on a variety of transitions that sketches and diagrams undergo.…”

Section: Related Workmentioning

confidence: 99%

“…Our study complements a number of existing studies on the use of sketches and diagrams in software development (see Section 4.2), which analyzed the above aspects only in parts and often focused on an academic environment [43], a single company [6,21], open source projects [7,45], or were limited to a small group of participants [25,45]. Based on our findings, we point at the need for tool support to better integrate sketches and diagrams into the software development process.…”

Section: Introductionmentioning

confidence: 98%

See 1 more Smart Citation

Sketches and diagrams in practice

Baltes

Diehl

2014

Proceedings of the 22nd ACM SIGSOFT International Symposium on Foundations of Software Engineering

View full text Add to dashboard Cite

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 different countries and on projects from a wide range of application areas. Most questions in the survey were related to the last sketch or diagram that the participants had created. Contrary to our expectations and previous work, the majority of sketches and diagrams contained at least some UML elements. However, most of them were informal. The most common purposes for creating sketches and diagrams were designing, explaining, and understanding, but analyzing requirements was also named often. More than half of the sketches and diagrams were created on analog media like paper or whiteboards and have been revised after creation. Most of them were used for more than a week and were archived. We 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.

show abstract

“…Walny et al [43] analyzed eight workflows of software developers in an academic setting. They report on a variety of transitions that sketches and diagrams undergo.…”

Section: Related Workmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 98%

Sketches and diagrams in practice

Baltes

Diehl

2014

Proceedings of the 22nd ACM SIGSOFT International Symposium on Foundations of Software Engineering

View full text Add to dashboard Cite

show abstract

“…Sketches are used throughout the lifetime of a project, expanding to include different facets and migrating to different media along the way [34]. Diagrams are used to form and retain early concepts [35].…”

Section: Programmer Information Needsmentioning

confidence: 99%

Programmer information needs after memory failure

Parnin

Rugaber

2012

2012 20th IEEE International Conference on Program Comprehension (ICPC)

View full text Add to dashboard Cite

Despite its vast capacity and associative powers, the human brain does not deal well with interruptions. Particularly in situations where information density is high, such as during a programming task, recovering from an interruption requires extensive time and effort. Although modern program development environments have begun to recognize this problem, none of these tools take into account the brain's structure and limitations. In this paper, we present a conceptual framework for understanding the strengths and weaknesses of human memory, particularly with respect to it ability to deal with work interruptions. The framework explains empirical results obtained from experiments in which programmers were interrupted while working. Based on the framework, we discuss programmer information needs that development tools must satisfy and suggest several memory aids such tools could provide. We also describe our prototype implementation of these memory aids.

show abstract

“…Software developers use sketches frequently in different phases of the software development process to depict and convey different views and concepts of the system under development [20]. We approach this by using such rather informal drawings as means for navigation and understanding of code bases by integrating them into the IDE and connecting them to code artifacts (figure 1).…”

Section: Introductionmentioning

confidence: 99%

CodeGraffiti: Using hand-drawn sketches connected to code bases in navigation tasks

Lichtschlag

Spychalski

Bochers

2014

2014 IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC)

View full text Add to dashboard Cite

Current IDEs excel at text manipulation, but offer little support for sketching and capturing informal visual artifacts that developers create during their work on the code base. Such artifacts promise to help the examination of existing source bases and the orientation therein when linked up to corresponding code fragments. In this paper, we present a design and prototype how to use linked sketches to assist the the developer in orientating in the code base. Our evaluation with 32 users shows that testers adopt the navigation through linked sketches and refer to the spatial documentation significantly more.

show abstract

Follow that sketch: Lifecycles of diagrams and sketches in software development

Cited by 27 publications

References 18 publications

Sketches and diagrams in practice

Sketches and diagrams in practice

Programmer information needs after memory failure

CodeGraffiti: Using hand-drawn sketches connected to code bases in navigation tasks

Contact Info

Product

Resources

About