46 research outputs found

    Emotional Awareness During Bug Fixes – A Pilot Study

    Get PDF
    This study examines the effects of a programmer\u27s emotional awareness on progress while fixing bugs. The goal of the study is to capitalize on emotional awareness to ultimately increase progress made during software development. This process could result in improved software maintenance

    Eye movements in code reading:relaxing the linear order

    Get PDF
    Abstract—Code reading is an important skill in programming. Inspired by the linearity that people exhibit while natural lan-guage text reading, we designed local and global gaze-based mea-sures to characterize linearity (left-to-right and top-to-bottom) in reading source code. Unlike natural language text, source code is executable and requires a specific reading approach. To validate these measures, we compared the eye movements of novice and expert programmers who were asked to read and comprehend short snippets of natural language text and Java programs. Our results show that novices read source code less linearly than natural language text. Moreover, experts read code less linearly than novices. These findings indicate that there are specific differences between reading natural language and source code, and suggest that non-linear reading skills increase with expertise. We discuss the implications for practitioners and educators. I

    Emotional Awareness During Bug Fixes – A Pilot Study

    Get PDF
    This study examines the effects of a programmer\u27s emotional awareness on progress while fixing bugs. The goal of the study is to capitalize on emotional awareness to ultimately increase progress made during software development. This process could result in improved software maintenance

    Deja Vu: semantics-aware recording and replay of high-speed eye tracking and interaction data to support cognitive studies of software engineering tasks—methodology and analyses

    Get PDF
    The paper introduces a fundamental technological problem with collecting high-speed eye tracking data while studying software engineering tasks in an integrated development environment. The use of eye trackers is quickly becoming an important means to study software developers and how they comprehend source code and locate bugs. High quality eye trackers can record upwards of 120 to 300 gaze points per second. However, it is not always possible to map each of these points to a line and column position in a source code file (in the presence of scrolling and file switching) in real time at data rates over 60 gaze points per second without data loss. Unfortunately, higher data rates are more desirable as they allow for finer granularity and more accurate study analyses. To alleviate this technological problem, a novel method for eye tracking data collection is presented. Instead of performing gaze analysis in real time, all telemetry (keystrokes, mouse movements, and eye tracker output) data during a study is recorded as it happens. Sessions are then replayed at a much slower speed allowing for ample time to map gaze point positions to the appropriate file, line, and column to perform additional analysis. A description of the method and corresponding tool, Deja Vu, is presented. An evaluation of the method and tool is conducted using three different eye trackers running at four different speeds (60 Hz, 120 Hz, 150 Hz, and 300 Hz). This timing evaluation is performed in Visual Studio, Eclipse, and Atom IDEs. Results show that Deja Vu can playback 100% of the data recordings, correctly mapping the gaze to corresponding elements, making it a well-founded and suitable post processing step for future eye tracking studies in software engineering. Finally, a proof of concept replication analysis of four tasks from two previous studies is performed. Due to using the Deja Vu approach, this replication resulted in richer collected data and improved on the number of distinct syntactic categories that gaze was mapped on in the code

    Eye gaze and interaction contexts for change tasks – Observations and potential

    Full text link
    The more we know about software developers’ detailed navigation behavior for change tasks, the better we are able to provide effective tool support. Currently, most empirical studies on developers performing change tasks are, however, limited to very small code snippets or limited by the granularity and detail of the data collected on developer’s navigation behavior. In our research, we extend this work by combining user interaction monitoring to gather interaction context – the code elements a developer selects and edits – with eye-tracking to gather more detailed and fine-granular gaze context-code elements a developer looked at. In a study with 12 professional and 10 student developers we gathered interaction and gaze contexts from participants working on three change tasks of an open source system. Based on an analysis of the data we found, amongst other results, that gaze context captures different aspects than interaction context and that developers only read small portions of code elements. We further explore the potential of the more detailed and fine-granular data by examining the use of the captured change task context to predict perceived task difficulty and to provide better and more fine-grained navigation recommendations. We discuss our findings and their implications for better tool support

    EMIP: The eye movements in programming dataset

    Get PDF
    A large dataset that contains the eye movements of N=216 programmers of different experience levels captured during two code comprehension tasks is presented. Data are grouped in terms of programming expertise (from none to high) and other demographic descriptors. Data were collected through an international collaborative effort that involved eleven research teams across eight countries on four continents. The same eye tracking apparatus and software was used for the data collection. The Eye Movements in Programming (EMIP) dataset is freely available for download. The varied metadata in the EMIP dataset provides fertile ground for the analysis of gaze behavior and may be used to make novel insights about code comprehension

    Corneal confocal microscopy detects a reduction in corneal endothelial cells and nerve fibres in patients with acute ischemic stroke

    Get PDF
    YesEndothelial dysfunction and damage underlie cerebrovascular disease and ischemic stroke. We undertook corneal confocal microscopy (CCM) to quantify corneal endothelial cell and nerve morphology in 146 patients with an acute ischemic stroke and 18 age-matched healthy control participants. Corneal endothelial cell density was lower (P<0.001) and endothelial cell area (P<0.001) and perimeter (P<0.001) were higher, whilst corneal nerve fbre density (P<0.001), corneal nerve branch density (P<0.001) and corneal nerve fbre length (P=0.001) were lower in patients with acute ischemic stroke compared to controls. Corneal endothelial cell density, cell area and cell perimeter correlated with corneal nerve fber density (P=0.033, P=0.014, P=0.011) and length (P=0.017, P=0.013, P=0.008), respectively. Multiple linear regression analysis showed a signifcant independent association between corneal endothelial cell density, area and perimeter with acute ischemic stroke and triglycerides. CCM is a rapid non-invasive ophthalmic imaging technique, which could be used to identify patients at risk of acute ischemic stroke.Qatar National Research Fund Grant BMRP2003865
    corecore