Linking sketches and diagrams to source code artifacts

Baltes, Sebastian; Schmitz, Peter; Diehl, Stephan

doi:10.1145/2635868.2661672

Cited by 18 publications

(20 citation statements)

References 23 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…There are a few beginnings toward addressing the disjoint topologies challenge. For example, 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. Mining approaches like Chen and Grundy's [5] are also emerging to find relationships among disjoint topologies such as documentation and source code.…”

Section: Sometimes There Is No Pathmentioning

confidence: 99%

Foraging and navigations, fundamentally: developers' predictions of value and cost

Piorkowski

Henley

Nabi

et al. 2016

Proceedings of the 2016 24th ACM SIGSOFT International Symposium on Foundations of Software Engineering

View full text Add to dashboard Cite

Empirical studies have revealed that software developers spend 35%-50% of their time navigating through source code during development activities, yet fundamental questions remain: Are these percentages too high, or simply inherent in the nature of software development? Are there factors that somehow determine a lower bound on how effectively developers can navigate a given information space? Answering questions like these requires a theory that captures the core of developers' navigation decisions. Therefore, we use the central proposition of Information Foraging Theory to investigate developers' ability to predict the value and cost of their navigation decisions. Our results showed that over 50% of developers' navigation choices produced less value than they had predicted and nearly 40% cost more than they had predicted. We used those results to guide a literature analysis, to investigate the extent to which these challenges are met by current research efforts, revealing a new area of inquiry with a rich and crosscutting set of research challenges and open problems. CCS Concepts • Software and its engineering➝Software notations and tools • Software and its engineering➝Software creation and management

show abstract

Section: Sometimes There Is No Pathmentioning

confidence: 99%

Foraging and navigations, fundamentally: developers' predictions of value and cost

Piorkowski

Henley

Nabi

et al. 2016

Proceedings of the 2016 24th ACM SIGSOFT International Symposium on Foundations of Software Engineering

View full text Add to dashboard Cite

show abstract

“…A practical extension of this model would be to link external resources to the metadata. Similar thing was done by Baltes et al who designed SketchLink tool [5] for linking sketches documenting high-level design to code elements through SCAs. Their design included a service for uploading and managing images of sketches from mobile devices and web browsers.…”

Section: Related Workmentioning

confidence: 89%

“…Feature location tools from the recovering approach usually produce list of source code elements that are evaluated as relevant to the given feature [3]. Preserving approaches directly assign high-level information to source code elements with annotations [4], [5]. Although in both cases the retrievable data represent source code metadata (abbreviated: metadata), they are of different nature.…”

Section: A Motivationmentioning

confidence: 99%

See 1 more Smart Citation

Supporting Source Code Annotations with Metadata-Aware Development Environment

Juhár¹

2019

Proceedings of the 2019 Federated Conference on Computer Science and Information Systems

View full text Add to dashboard Cite

To augment source code with high-level metadata with the intent to facilitate program comprehension, a programmer can use annotations. There are several types of annotations: either those put directly in the code or external ones. Each type comes with a unique workflow and inherent limitations. In this paper, we present a tool providing uniform annotation process, which also adds custom metadata-awareness for an industrial IDE. We also report an experiment in which we sought whether the created annotating support helps programmers to annotate code with comments faster and more consistently. The experiment showed that with the tool the annotating consistency was significantly higher but also that the increase in annotating speed was not statistically significant.

show abstract

“…We conducted a formative user study and got valuable insights to improve the tool. In the future, we plan to extend LivelySketches to allow users to also link sketches to other relevant resources like documents, emails, or source code [32]. A linked sketch could then be used to navigate through linked artifacts.…”

Section: Discussionmentioning

confidence: 99%

Round-Trip Sketches: Supporting the Lifecycle of Software Development Sketches from Analog to Digital and Back

Baltes

Hollerich

Diehl

2017

2017 IEEE Working Conference on Software Visualization (VISSOFT)

Self Cite

View full text Add to dashboard Cite

Sketching is an important activity for understanding, designing, and communicating different aspects of software systems such as their requirements or architecture. Often, sketches start on paper or whiteboards, are revised, and may evolve into a digital version. Users may then print a revised sketch, change it on paper, and digitize it again. Existing tools focus on a paperless workflow, i.e., archiving analog documents, or rely on special hardware-they do not focus on integrating digital versions into the analog-focused workflow that many users follow. In this paper, we present the conceptual design and a prototype of LivelySketches, a tool that supports the "roundtrip" lifecycle of sketches from analog to digital and back. The proposed workflow includes capturing both analog and digital sketches as well as relevant context information. In addition, users can link sketches to other related sketches or documents. They may access the linked artifacts and captured information using digital as well as augmented analog versions of the sketches. We further present results from a formative user study with four students and outline possible directions for future work.

show abstract

Linking sketches and diagrams to source code artifacts

Cited by 18 publications

References 23 publications

Foraging and navigations, fundamentally: developers' predictions of value and cost

Foraging and navigations, fundamentally: developers' predictions of value and cost

Supporting Source Code Annotations with Metadata-Aware Development Environment

Round-Trip Sketches: Supporting the Lifecycle of Software Development Sketches from Analog to Digital and Back

Contact Info

Product

Resources

About