Share on Facebook Tweet on Twitter Share on LinkedIn Share by email
Let's go to the whiteboard: how and why software developers use drawings

Mauro Cherubini, Gina Venolia, Rob DeLine, and Andrew J. Ko

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.

Details

Publication typeInproceedings
Published inCHI '07: Proceedings of the SIGCHI conference on Human factors in computing systems
URLhttp://doi.acm.org/10.1145/1240624.1240714
Pages557–566
ISBN978-1-59593-593-9
AddressNew York, NY, USA
PublisherAssociation for Computing Machinery, Inc.
> Publications > Let's go to the whiteboard: how and why software developers use drawings