Student or educator? Sign up with your school email and get 6 months of Pro free.
Cited by 261

The DOI matches its Crossref record; 21 of the 21 references it cites were found in a registry or an index.

Let's go to the whiteboard: how and why software developers use drawings

Cherubini, Mauro, Venolia, Gina, DeLine, Rob, Ko, Amy J.·2007·Proceedings of the SIGCHI Conference on Human Factors in Computing Systems

Abstract

Software developers are rooted in the written form of their code, yet they often draw diagrams representing their code. Unfortunately, we still know little about how and why they create these diagrams, and so there is little research to inform the design of visual tools to support developers' work. This paper presents findings from semi-structured interviews that have been validated with a structured survey. Results show that most of the diagrams had a transient nature because of the high cost of changing whiteboard sketches to electronic renderings. Diagrams that documented design decisions were often externalized in these temporary drawings and then subsequently lost. Current visualization tools and the software development practices that we observed do not solve these issues, but these results suggest several directions for future research.

Overview

The claims and statistics of this paper haven’t been checked yet.

Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.

A few free checks a day · papers already verified open instantly · results are public

Integrity signals

Registry

Crossref · 10.1145/1240624.1240714

Cites

21 of 21 references verified0 citation errors · 0 not checkable

Statistics

Verification

Claims the paper makes

The claims and statistics of this paper haven’t been checked yet.

Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.

A few free checks a day · papers already verified open instantly · results are public

Self-check

Percentages, sums and reported differences re-computed from the paper’s own numbers.

The self-check needs the paper’s full text.

Citations

Cites

Show all 21 references

Research works printed but not linked: 4

  1. 10.1145/1083106.1083109 · doi:10.1145/1083106.1083109
  2. E. Do and M. D. Gross . Reasoning about cases with diagrams. In J. Vanegas and P. Chinowsky, editors , ASCE , pp. 314 -- 320 , 1996 . E. Do and M. D. Gross. Reasoning about cases with diagrams. In J. Vanegas and P. Chinowsky, editors, ASCE, pp. 314--320, 1996.
  3. J. Heiser , B. Tversky , and M. Silverman . Visual and spatial reasoning in design III , chapter Sketches for and from collaboration, pp. 69 -- 78 . 2004 . J. Heiser, B. Tversky, and M. Silverman. Visual and spatial reasoning in design III, chapter Sketches for and from collaboration, pp. 69--78. 2004.
  4. 10.5555/521215 · doi:10.5555/521215

Cited by

See all 261

Metadata

Authors
Cherubini, M., Venolia, G., DeLine, R., & Ko, A. J.
Venue
Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
Publisher
ACM
Published
2007-04-29
Pages
557-566
OpenAlex
W2110957405
Cited by
261
References
21
FWCI
10.18
Type
conference paper
Language
en
Open access
closed

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review

How to cite

Cite CoChat for the checks on this page, and the paper for its own findings.

This page
CoChat. (2026). Citation check: Let's go to the whiteboard: how and why software developers use drawings. https://app.cochat.ai/papers/10.1145/1240624.1240714
The paper
Cherubini, M., Venolia, G., DeLine, R., & Ko, A. J. (2007). Let's go to the whiteboard: how and why software developers use drawings. Proceedings of the SIGCHI Conference on Human Factors in Computing Systems. https://doi.org/10.1145/1240624.1240714

Data sources

Bibliographic data: Semantic Scholar, OpenAlex, Crossref.

Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).

Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.