Linking sketches and diagrams to source code artifacts
Open accessAbstract
Recent studies have shown that sketches and diagrams play an important role in the daily work of software developers. If these visual artifacts are archived, they are often detached from the source code they document, because there is no ad- equate tool support to assist developers in capturing, archiving, and retrieving sketches related to certain source code artifacts. This paper presents SketchLink, a tool that aims at increasing the value of sketches and diagrams created during software development by supporting developers in these tasks. Our prototype implementation provides a web application that employs the camera of smartphones and tablets to capture analog sketches, but can also be used on desktop computers to upload, for instance, computer-generated diagrams. We also implemented a plugin for a Java IDE that embeds the links in Javadoc comments and visualizes them in situ in the source code editor as graphical icons.
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
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.
Claims other papers make about this one
Each is checked against this paper’s own text: does it say what the citing paper says it does?
Whyline builds a path just-in-time to bridge the gap between two topologies: from GUI output to its relevant source code, and SketchLink links sketches to code.
“Whyline [20] builds a path just-in-time to bridge the gap between two topologies: from GUI output to its relevant source code, and SketchLink [3] links sketches to code.”
From Foraging and navigations, fundamentally: developers' predictions of value and cost (2016) · cites this paper as [3]
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Cites
Ko, A. J., Myers, B. A., Coblenz, M. J., & Aung, H. H. (2006) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2006.116 · Cited by 685 · see citing works
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 · see citing works
How software engineers use documentation: the state of the practice
Lethbridge, T. C., Singer, J., & Forward, A. (2003) · IEEE Software · doi:10.1109/ms.2003.1241364 · Cited by 340 · see citing works
An examination of software engineering work practices
Singer, J., Lethbridge, T. C., Vinson, N. G., & Anquetil, N. (2010) · doi:10.1145/1925805.1925815 · Cited by 298 · see citing works
The relevance of software documentation, tools and technologies: a survey
Forward, A., & Lethbridge, T. C. (2002) · Proceedings of the 2002 ACM symposium on Document engineering · doi:10.1145/585058.585065 · Cited by 268 · see citing works
Cherubini, M., Venolia, G. D., DeLine, R., & Ko, A. J. (2007) · CHI Conference on Human Factors in Computing Systems · doi:10.1145/1240624.1240714 · Cited by 262 · see citing works
Identifying Refactorings from Source-Code Changes
Weißgerber, P., & Diehl, S. (2006) · IEEE/ACM International Conference on Automated Software Engineering (ASE) · doi:10.1109/ase.2006.41 · Cited by 192 · see citing works
Self-citationHammond, T., & Davis, R. (2006) · ACM SIGGRAPH Conference (SIGGRAPH) · doi:10.1145/1185657.1185786 · Cited by 172 · see citing works
Tool support for cooperative object-oriented design
Damm, C. H., Hansen, K., & Thomsen, M. (2000) · ACM SIGCHI Conference on Human Factors in Computing Systems (CHI) · doi:10.1145/332040.332488 · Cited by 134 · see citing works
How designers design and program interactive behaviors
Myers, B. A., Park, S. Y., Nakano, Y., Mueller, G., & Ko, A. J. (2008) · IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC) · doi:10.1109/vlhcc.2008.4639081 · Cited by 131 · see citing works
Visual Thinking In Action: Visualizations As Used On Whiteboards
Walny, J., Carpendale, S., Riche, N. H., Venolia, G. D., & Fawcett, P. (2011) · IEEE Transactions on Visualization and Computer Graphics · doi:10.1109/tvcg.2011.251 · Cited by 91 · see citing works
An e-whiteboard application to support early design-stage sketching of UML diagrams
Chen, Q., Grundy, J., & Hosking, J. (2004) · doi:10.1109/hcc.2003.1260232 · Cited by 85 · see citing works
Sketches and diagrams in practice
Baltes, S., & Diehl, S. (2014) · ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) · doi:10.1145/2635868.2635891 · Cited by 82 · see citing works
Self-citationOn the use of software design models in software development practice: An empirical investigation
Gorschek, T., Tempero, E. D., & Angelis, L. (2014) · Journal of Systems and Software · doi:10.1016/j.jss.2014.03.082 · Cited by 77 · see citing works
Notation and representation in collaborative object-oriented design
Dekel, U., & Herbsleb, J. D. (2007) · Conference on Object-Oriented Programming Systems, Languages, and Applications · doi:10.1145/1297027.1297047 · Cited by 58 · see citing works
Software design sketching with calico
Mangano, N., Baker, A., Dempsey, M., Navarro, E. O., & van der Hoek, A. (2010) · IEEE/ACM International Conference on Automated Software Engineering (ASE) · doi:10.1145/1858996.1859003 · Cited by 53 · see citing works
Branham, S. M., Golovchinsky, G., Carter, S., & Biehl, J. T. (2010) · CHI Conference on Human Factors in Computing Systems · doi:10.1145/1753326.1753338 · Cited by 52 · see citing works
Follow that sketch: Lifecycles of diagrams and sketches in software development
Walny, J., Haber, J., Dörk, M., Sillito, J., & Carpendale, S. (2011) · IEEE Working Conference on Software Visualization (VISSOFT) · doi:10.1109/vissof.2011.6069462 · Cited by 41 · see citing works
Petre, M., & van der Hoek, A. (2013) · Chapman & Hall/CRC eBooks · doi:10.1201/b15530 · Cited by 33 · see citing works
Bridging the gap between real printouts and digital whiteboard
Brandl, P., Haller, M., Oberngruber, J., et al. (2008) · Working Conference on Advanced Visual Interfaces (AVI) · doi:10.1145/1385569.1385577 · Cited by 20 · see citing works
How can diagramming tools help support programming activities?
Lee, S., Murphy, G. C., Fritz, T., & Allen, M. (2008) · IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC) · doi:10.1109/vlhcc.2008.4639095 · Cited by 17 · see citing works
Enhancing UML sketch tools with digital pens and paper
Dachselt, R., Frisch, M., & Decker, E. (2008) · doi:10.1145/1409720.1409756 · Cited by 11 · see citing works
Flagged first, then by citations
Research works printed but not linked: 2
- [11][11] T. Hammond and R. Davis. Tahuti: A Geometrical Sketch Recognition System for UML Class Diagrams. In SIGGRAPH'06 Courses . ACM, 2006. -
- [18][18] M. Petre. UML in Practice. In ICSE'13 . IEEE, 2013. -
Cited by
Sorted by citations
Foraging and navigations, fundamentally: developers' predictions of value and cost
Piorkowski, D., Henley, A. Z., Nabi, T., Fleming, S. D., Scaffidi, C., & Burnett, M. (2016) · Proceedings of the 2016 24th ACM SIGSOFT International Symposium on Foundations of Software Engineering · doi:10.1145/2950290.2950302 · Cited by 38 · see citing works
- Authors
- Baltes, S., Schmitz, P., & Diehl, S.
- Affiliations
- Universität Trier (DE)
- Venue
- Proceedings of the 22nd ACM SIGSOFT International Symposium on Foundations of Software Engineering
- Publisher
- ACM
- Published
- 2014-11-11
- Pages
- 743-746
- OpenAlex
- W2000591416
- Cited by
- 26
- References
- 22
- Citations by year
- 2026: 1 · 2025: 1 · 2023: 3 · 2021: 3 · 2020: 5 · 2019: 3 · 2018: 3 · 2017: 2 · 2016: 3 · 2015: 2
- FWCI
- 1.99
- Type
- conference paper
- Language
- en
- Open access
- green
- arxiv.org
- Locations
- ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) (publishedVersion)
- arXiv (Cornell University) (submittedVersion)
- arXiv (Cornell University)
- Topics
- Physical Sciences › Computer Science › Information Systems › Software Engineering Research
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Physical Sciences › Computer Science › Software › Model-Driven Software Engineering Techniques
- Keywords
- sketches, diagrams, visual artifacts, Javadoc, software documentation, visual programming
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
