The impact of identifier style on effort and comprehension

Binkley, David; Davis, Marcia H.; Lawrie, Dawn; Maletic, Jonathan I.; Morrell, Christopher H.; Sharif, Bonita

doi:10.1007/s10664-012-9201-4

Cited by 128 publications

(76 citation statements)

References 34 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…For example, Sharif et al confirm that scan time and bug detection time are correlated [47]. Eyetracking has been used in studies of identifier style [49,8] and UML diagram layout [46,48], showing reduced comprehension when the code is not in an understandable format.…”

Section: Eye-tracking In Software Engineeringmentioning

confidence: 99%

Improving automated source code summarization via an eye-tracking study of programmers

Rodeghero

McMillan

McBurney

et al. 2014

Proceedings of the 36th International Conference on Software Engineering

169

106

View full text Add to dashboard Cite

Source Code Summarization is an emerging technology for automatically generating brief descriptions of code. Current summarization techniques work by selecting a subset of the statements and keywords from the code, and then including information from those statements and keywords in the summary. The quality of the summary depends heavily on the process of selecting the subset: a high-quality selection would contain the same statements and keywords that a programmer would choose. Unfortunately, little evidence exists about the statements and keywords that programmers view as important when they summarize source code. In this paper, we present an eye-tracking study of 10 professional Java programmers in which the programmers read Java methods and wrote English summaries of those methods. We apply the findings to build a novel summarization tool. Then, we evaluate this tool and provide evidence to support the development of source code summarization systems.

show abstract

Section: Eye-tracking In Software Engineeringmentioning

confidence: 99%

Improving automated source code summarization via an eye-tracking study of programmers

Rodeghero

McMillan

McBurney

et al. 2014

Proceedings of the 36th International Conference on Software Engineering

169

106

View full text Add to dashboard Cite

show abstract

“…One of the first eye-tracking studies in program comprehension was conducted by Crosby et al, who found that experts and novices differ in the way they looked at English and Pascal versions of an algorithm [11]. Since then, several researchers have used eye-tracking to evaluate the impact of developers' eye gaze on comprehension for different kinds of representations and visualizations such as 3D visualizations [37], UML diagrams [51,12], design pattern layout [39], programming languages [44], and identifier styles [40,8]. Researchers have also used eye-tracking to investigate developers' scan patterns for very small code snippets, finding that participants first read the entire code snippet to get an idea of the program [45].…”

Section: Biometric Sensingmentioning

confidence: 99%

Tracing software developers' eyes and interactions for change tasks

Kevic

Walters

Shaffer

et al. 2015

Proceedings of the 2015 10th Joint Meeting on Foundations of Software Engineering

Self Cite

View full text Add to dashboard Cite

What are software developers doing during a change task? While an answer to this question opens countless opportunities to support developers in their work, only little is known about developers' detailed navigation behavior for realistic change tasks. Most empirical studies on developers performing change tasks are limited to very small code snippets or are limited by the granularity or the detail of the data collected for the study. In our research, we try to overcome these limitations by combining user interaction monitoring with very fine granular eye-tracking data that is automatically linked to the underlying source code entities in the IDE.In a study with 12 professional and 10 student developers working on three change tasks from an open source system, we used our approach to investigate the detailed navigation of developers for realistic change tasks. The results of our study show, amongst others, that the eye-tracking data does indeed capture different aspects than user interaction data and that developers focus on only small parts of methods that are often related by data flow. We discuss our findings and their implications for better developer tool support.

show abstract

“…The approach of this proposal gives relevance to class names, and these determines the maintainability and legibility of software, between others [4,7,18,28,29,33,34]. Looking at the standard ISO/IEC FDIS 25010, maintainability includes the following quality attributes: modularity, reusability, analyzability, modifiability and testability.…”

Section: Resultsmentioning

confidence: 99%

“…For evaluating the proposed analysis technique, an application was implemented to getting the terms used in class name following the CamelCase coding style (predominant style due to its ease of writing and adoption [7,13]), storing terms in a Neo4j database (standard graph database in the industry [26]). The application was executed on twenty projects of the organizations Apache and Eclipse (see table 1).…”

Section: Resultsmentioning

confidence: 99%

Using Naming Patterns for Identifying Architectural Technical Debt

Carpio¹

2017

Adv. sci. technol. eng. syst. j.

View full text Add to dashboard Cite

The impact of identifier style on effort and comprehension

Cited by 128 publications

References 34 publications

Improving automated source code summarization via an eye-tracking study of programmers

Improving automated source code summarization via an eye-tracking study of programmers

Tracing software developers' eyes and interactions for change tasks

Using Naming Patterns for Identifying Architectural Technical Debt

Contact Info

Product

Resources

About