Sketches and Diagrams in Practice
arXiv:1706.09172 · doi:10.1145/2635868.2635891
Abstract
Sketches and diagrams play an important role in the daily work of software developers. In this paper, we investigate the use of sketches and diagrams in software engineering practice. To this end, we used both quantitative and qualitative methods. We present the results of an exploratory study in three companies and an online survey with 394 participants. Our participants included software developers, software architects, project managers, consultants, as well as researchers. They worked in different countries and on projects from a wide range of application areas. Most questions in the survey were related to the last sketch or diagram that the participants had created. Contrary to our expectations and previous work, the majority of sketches and diagrams contained at least some UML elements. However, most of them were informal. The most common purposes for creating sketches and diagrams were designing, explaining, and understanding, but analyzing requirements was also named often. More than half of the sketches and diagrams were created on analog media like paper or whiteboards and have been revised after creation. Most of them were used for more than a week and were archived. We found that the majority of participants related their sketches to methods, classes, or packages, but not to source code artifacts with a lower level of abstraction.
12 pages, 2 figures, Proceedings of the 22nd ACM SIGSOFT International Symposium on Foundations of Software Engineering (FSE 2014), ACM, 2014, pp. 530-541
References in corpus (1)
Cited by in corpus (6)
- Sketches and Diagrams in Practice
- Worse Than Spam: Issues In Sampling Software Developers
- Linking Sketches and Diagrams to Source Code Artifacts
- Navigate, Understand, Communicate: How Developers Locate Performance Bugs
- Draw This Object: A Study of Debugging Representations
- Empirical Research Plan: Effects of Sketching on Program Comprehension