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
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.
Integrity signals
Registry
Cites
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.
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
Hutchins, E. (1995) · doi:10.7551/mitpress/1881.001.0001 · Cited by 10,801
Why a Diagram is (Sometimes) Worth Ten Thousand Words
Larkin, J. H., & Simon, H. A. (1987) · Cognitive Science · doi:10.1016/s0364-0213(87)80026-5 · Cited by 3,733
Clark, H. H., & Schaefer, E. F. (1989) · Cognitive Science · doi:10.1207/s15516709cog1302_7 · Cited by 1,699
Hearing gesture: how our hands help us think
(2004) · Choice Reviews Online · doi:10.5860/choice.41-4463 · Cited by 1,140
Maintaining mental models: a study of developer work habits
LaToza, T. D., Venolia, G., & DeLine, R. (2006) · Proceedings of the 28th international conference on Software engineering · doi:10.1145/1134285.1134355 · Cited by 628
Self-citationA Principled Taxonomy of Software Visualization
Price, B. A., Baecker, R. M., & Small, I. S. (1993) · Journal of Visual Languages & Computing · doi:10.1006/jvlc.1993.1015 · Cited by 476
Bellotti, V., & Bly, S. (1996) · Proceedings of the 1996 ACM conference on Computer supported cooperative work · doi:10.1145/240080.240256 · Cited by 456
Burris, B. H., & Henderson, K. (2001) · Contemporary Sociology · doi:10.2307/2654335 · Cited by 427
People, organizations, and process improvement
Perry, D. E., Staudenmayer, N. A., & Votta, L. G. (1994) · IEEE Software · doi:10.1109/52.300082 · Cited by 401
The information-seeking practices of engineers: searching for documents as well as for people
Hertzum, M., & Pejtersen, A. M. (2000) · Information Processing & Management · doi:10.1016/s0306-4573(00)00011-x · Cited by 355
Research works printed but not linked: 4
- 10.1145/1083106.1083109 · doi:10.1145/1083106.1083109
- 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.
- 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.
- 10.5555/521215 · doi:10.5555/521215
Cited by
Resumption strategies for interrupted programming tasks
Parnin, C., & Rugaber, S. (2011) · Software Quality Journal · doi:10.1007/s11219-010-9104-9 · Cited by 103
Past and future of software architectural decisions – A systematic mapping study
Tofan, D., Galster, M., Avgeriou, P., & Schuitema, W. (2014) · Information and Software Technology · doi:10.1016/j.infsof.2014.03.009 · Cited by 77
Manual refactoring changes with automated refactoring validation
Ge, X., & Murphy-Hill, E. (2014) · Proceedings of the 36th International Conference on Software Engineering · doi:10.1145/2568225.2568280 · Cited by 55
Razzaq, A., Buckley, J., Lai, Q., Yu, T., & Botterweck, G. (2025) · ACM Computing Surveys · doi:10.1145/3687299 · Cited by 36
Ten simple rules for helping newcomers become contributors to open projects
Sholler, D., Steinmacher, I., Ford, D., Averick, M., Hoye, M., & Wilson, G. (2019) · PLOS Computational Biology · doi:10.1371/journal.pcbi.1007296 · Cited by 35
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.