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

Détails

ID Serval
serval:BIB_79254E66CC7B
Type
Actes de conférence (partie): contribution originale à la littérature scientifique, publiée à l'occasion de conférences scientifiques, dans un ouvrage de compte-rendu (proceedings), ou dans l'édition spéciale d'un journal reconnu (conference proceedings).
Collection
Publications
Titre
Let's go to the whiteboard : how and why software developers use drawings
Titre de la conférence
Proceedings of the SIGCHI conference on Human factors in computing systems - CHI '07
Auteur⸱e⸱s
Cherubini M., Venolia G., DeLine R., Ko A. J.
Editeur
Association for Computing Machinery (ACM)
Adresse
San Jose, CA, USA
ISBN
978-1-59593-593-9
Statut éditorial
Publié
Date de publication
2007
Pages
557-566
Langue
anglais
Résumé
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.
Mots-clé
Software visualization, diagrams, exploratory/field study
Web of science
Création de la notice
29/11/2016 15:45
Dernière modification de la notice
20/08/2019 14:35
Données d'usage