Let’s go to the whiteboard: How and why software developers use drawings

I am back from CHI2007, where I presented the work I did this summer at Microsoft Research, in Redmond (WA):

M. Cherubini, G. Venolia, R. deLine, and A. J. Ko. Let’s go to the whiteboard: How and why software developers use drawings. In Proceedings of the SIGCHI conference on Human factors in computing systems (CHI2007), pages 557 – 566, San Jose, CA, USA, April 28, May 3 2007. ACM Press. [pdf]

————-

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.

Letsgotothewhiteboard Cover

The slides of the presentation can be found here.

The PDF of the paper is available on the ACM digital library or here.

Tags: , ,

Leave a Reply