Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Del Myers

dblp:18/3828 · DBLP profile ↗
← Back
5ranked-venue papers
1as first author
0since 2021 · last 2010
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 5 · 1 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
3 papers
Software maintenance and evolution · 47% Empirical software engineering · 38% Program analysis · 16%
Human-computer interaction and pervasive computing
2 papers
User interface design and tools · 54% Collaborative and social computing · 46%

Topics — the 9 heaviest of 9, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Empirical software engineering
developer studies
0.222009
How Software Developers Use Tagging to Support Reminding and Refinding · IEEE Trans. Software Eng. 2009
TODO or to bug: exploring how task annotations play a role in the work practices of software developers · ICSE 2008
Program analysis
dynamic analysis
0.112010
Using dynamic analysis to create trace-focused user interfaces for IDEs · SIGSOFT FSE 2010
Software maintenance and evolution › program comprehension
software visualization
0.112010
Using dynamic analysis to create trace-focused user interfaces for IDEs · SIGSOFT FSE 2010
Software maintenance and evolution › software documentation
code annotation
0.112009
How Software Developers Use Tagging to Support Reminding and Refinding · IEEE Trans. Software Eng. 2009
Software maintenance and evolution › program comprehension
code navigation
0.112009
How Software Developers Use Tagging to Support Reminding and Refinding · IEEE Trans. Software Eng. 2009
Empirical software engineering › software project management
task management
0.112008
TODO or to bug: exploring how task annotations play a role in the work practices of software developers · ICSE 2008
User interface design and tools › programming environments
integrated development environment
0.012010
Using dynamic analysis to create trace-focused user interfaces for IDEs · SIGSOFT FSE 2010
Collaborative and social computing › social computing
social tagging
0.012009
How Software Developers Use Tagging to Support Reminding and Refinding · IEEE Trans. Software Eng. 2009
Software maintenance and evolution
software maintenance
0.012008
TODO or to bug: exploring how task annotations play a role in the work practices of software developers · ICSE 2008

Methods — techniques the papers use, named apart from their topics

dynamic analysis · 0.2survey · 0.1interviews · 0.1code analysis · 0.1
YearPublicationVenuePosition
2010 Using dynamic analysis to create trace-focused user interfaces for IDEs
abstract
This research demonstration presents the tool, Dynamic Interactive Views for Reverse Engineering (Diver). Diver supports software understanding through a trace focused user interface. The trace focused user interface is a method of re-organizing the user interface of integrated development environments so that developers can focus their attention on artifacts related to the run-time behaviour of the software that they are investigating. The tool combines concepts from research in software visualization, dynamic analysis, software reconnaissance, and task focused user interfaces.
Del Myers, Margaret-Anne D. Storey
SIGSOFT FSE1
2009 How Software Developers Use Tagging to Support Reminding and Refinding
abstract
Developers frequently add annotations to source code to help them remember pertinent information and mark locations of interest for future investigation. Finding and refinding these notes is a form of navigation that is integral to software maintenance. Although there is some tool support in modern development environments for authoring and navigating these comments, we have observed that these annotations often fail to remind and are sometimes difficult to find by the programmer. To address these shortcomings, we have designed a new approach for software navigation called tags for software engineering activities (TagSEA). TagSEA combines the notion of waypointing (a mechanism for marking locations in spatial navigation) with social tagging to support programmers in defining semantically rich annotations to source code comments. The tool provides support for creating, editing, navigating, and managing these annotations. We present the results from two empirical studies, where we observed and then analyzed how professional programmers used source code annotations to support their development activities over 24 months. Our findings indicate that the addition of semantic information to annotations can improve their value. We also provide suggestions on how annotation tools in general may be improved.
Margaret-Anne D. Storey, Jody Ryall, Janice Singer, Del Myers, Li-Te Cheng, Michael J. Muller
IEEE Trans. Software Eng.4
2008 TODO or to bug: exploring how task annotations play a role in the work practices of software developers
abstract
Software development is a highly collaborative activity that requires teams of developers to continually manage and coordinate their programming tasks. In this paper, we describe an empirical study that explored how task annotations embedded within the source code play a role in how software developers manage personal and team tasks. We present findings gathered by combining results from a survey of professional software developers, an analysis of code from open source projects, and interviews with software developers. Our findings help us describe how task annotations can be used to support a variety of activities fundamental to articulation work within software development. We describe how task management is negotiated between the more formal issue tracking systems and the informal annotations that programmers write within their source code. We report that annotations have different meanings and are dependent on individual, team and community use. We also present a number of issues related to managing annotations, which may have negative implications for maintenance. We conclude with insights into how these findings could be used to improve tool support and software process.
Margaret-Anne D. Storey, Jody Ryall, R. Ian Bull, Del Myers, Janice Singer
ICSE4
2008 A survey and evaluation of tool features for understanding reverse-engineered sequence diagrams
abstract
Abstract Sequence diagrams can be valuable aids to software understanding. However, they can be extremely large and hard to understand in spite of using modern tool support. Consequently, providing the right set of tool features is important if the tools are to help rather than hinder the user. This paper surveys research and commercial sequence diagram tools to determine the features they provide to support program understanding. Although there has been significant effort in developing these tools, many of them have not been evaluated using human subjects. To begin to address this gap, a preliminary study was performed with a specially designed sequence diagram tool that implements the features found during the survey. On the basis of an analysis of the study results, we discuss the features that were found to be useful and relate these to the tasks performed. It concludes by proposing how future tools can be improved to better support the exploration of large sequence diagrams. Copyright © 2008 Crown in the right of Canada. Published by John Wiley & Sons, Ltd.
Chris Bennett, Del Myers, Margaret-Anne D. Storey, Daniel M. Germán, D. Ouellet, Martin Salois, Philippe Charland
J. Softw. Maintenance Res. Pract.2
2007 How Programmers Can Turn Comments into Waypoints for Code Navigation
abstract
We have developed a new approach for software navigation called TagSEA (Tagging of Software Engineering Activities). TagSEA combines the notion of "waypointing" with "social tagging" to support programmers in defining navigational structures over a software system. In this paper we present the results from a case study series, conducted with professional programmers, that demonstrates how this tool supports navigation and under what circumstances. We conclude with insights into user-definable navigational structures, and how they can support software maintenance more effectively.
Margaret-Anne D. Storey, Li-Te Cheng, Janice Singer, Michael J. Muller, Del Myers, Jody Ryall
ICSM5