Student or educator? Sign up with your school email and get 6 months of Pro free.
CoChat

The DOI matches its Crossref record, with a small difference in title or year; 86 of the 89 references it cites were found in a registry or an index; 6 of the 106 sources its claims cite were checked for support.

Detecting Developers' Task Switches and Types

Open access
Meyer, Andre N., Satterfield, Chris, Zuger, Manuela, Kevic, Katja, Murphy, Gail C., Zimmermann, Thomas, Fritz, Thomas · 2022 · IEEE Transactions on Software Engineering

Abstract

Developers work on a broad variety of tasks during their workdays and constantly switch between them. While these task switches can be beneficial, they can also incur a high cognitive burden on developers, since they have to continuously remember and rebuild the task context–the artifacts and applications relevant to the task. Researchers have therefore proposed to capture task context more explicitly and use it to provide better task support, such as task switch reduction or task resumption support. Yet, these approaches generally require the developer tomanuallyidentify task switches. Automatic approaches for predicting task switches have so far been limited in their accuracy, scope, evaluation, and the time discrepancy between predicted and actual task switches. In our work, we examine the use ofautomaticallycollected computer interaction data for detecting developers’ task switches as well as task types. In two field studies–a 4h observational study and a multi-day study with experience sampling–we collected data from a total of 25 professional developers. Our study results show that we are able to use temporal and semantic features from developers’ computer interaction data to detect task switches and types in the field with high accuracy of 84 percent and 61 percent respectively, and within a short time window of less than 1.6 minutes on average from the actual task switch. We discuss our findings and their practical value for a wide range of applications in real work settings.

Overview

CoChat Summary

TL;DR

The paper studies whether developers’ task switches and task types can be automatically detected from computer interaction data. Using two field studies with 25 professional developers, the authors report 84% accuracy for task-switch detection and 61% accuracy for task-type detection, with task switches detected on average within 1.6 minutes of the actual switch.

Key findings

  • Task-switch detection reached 84% averaged accuracy with individual models (precision 62%, recall 35%, kappa 0.34); the general model reached 73% accuracy (precision 46%, recall 55%, kappa 0.27).
  • The average task-switch prediction error was 2.79 application-switches, which the paper translates to 4.46 minutes before/after the actual switch using the average application-segment length of 1.6 minutes.
  • For task-type detection, individual models outperformed the general model: 61% accuracy for individual models versus 50% for the general model; for all task types combined, the table reports 59% precision / 61% recall for individual models and 44% precision / 50% recall for general models.
  • Feature importance was highest for user input features for task switches (45.8%) and task types (47.6% for all features); lexical features were weakest, contributing 8.2% for switches and 0% for task types.

Methods

  • Two field studies with professional software developers: a 4-hour observational study with 12 participants and a multi-day experience-sampling study with 13 participants; the paper states 25 professional developers in total.
  • Data sources included observed or self-reported ground truth plus automatically tracked computer interaction data from a monitoring tool; the paper extracted 109 temporal and semantic features overall and used 84 features for task-switch detection and 25 features for task-type detection.
  • Main analysis used RandomForest classifiers with 500 estimators, evaluated with 10-fold cross-validation for individual models and a leave-one-participant-out style general model; task-switch data were additionally handled with SMOTE due to class imbalance, while task-type detection used penalized classification.

Limitations

  • The paper states that task-switch detection is limited to application-switch granularity, so it cannot detect switches within an application and misses very short switches; it also notes an average delay of 1.6 minutes due to this granularity.
  • The paper states that self-reports may be inaccurate or burdensome, and that the study relied only on computer interaction data, which limits visibility into cases with no computer input; it explicitly notes this as a limitation.
  • Evident from the text: the observational study covered only one workday per participant, and the generalizability of the results is constrained by the sample sizes and recruitment from a small number of companies; the paper itself notes this as a threat to external validity.

Model-written summary. Check it against the paper before relying on it.

Integrity signals

Registry

Crossref · 10.1109/tse.2020.2984086

Cites

86 of 86 references verified0 citation errors · 0 not checkable

Statistics

Nothing to recompute.

Verification

Claims the paper makes

6 Valid · 2 Not valid · 51 Not checked · 104 Own results and interpretations

79 more claims

Create a free account to see all 163 claims and to verify the 7 references still open.

See all claims — free account
  • Probably not a substantial claim. 51
  • It may state two separate claims as one. 46
  • The quote only partly states this claim. 1

Create a free account to see these claims.

Self-check

Percentages, sums and reported differences re-computed from the paper’s own numbers.

Each contradiction between two passages listed here was confirmed by an independent check.

1 of 1

Citations

Cites

Show all 89 references

Research works printed but not linked: 2

  1. Bruegge, 2004, Object-Oriented Software Engineering Using UML, Patterns and Java-(Required), 2004
  2. 10.1023/A:I0I0933404324 · doi:10.1023/a:i0i0933404324

Cited by

See all 14

Metadata

Authors
Meyer, A. N., Satterfield, C., Zuger, M., Kevic, K., Murphy, G. C., Zimmermann, T., & Fritz, T.
Affiliations
  • University of British Columbia (CA)
  • Microsoft (United States) (US)
  • University of Zurich (CH)
Venue
IEEE Transactions on Software Engineering
Published
2022-01-01
Volume
48
Issue
1
Pages
225-240
ISSN
  • 0098-5589 (ISSN-L)
  • 1939-3520
  • 2326-3881
OpenAlex
W3017224552
Cited by
14
References
89
Citations by year
2026: 5 · 2025: 5 · 2024: 1 · 2023: 1
FWCI
0.71
Type
journal article
Language
en
Open access
Locations
  • IEEE Transactions on Software Engineering (publishedVersion, cc-by)
  • Zurich Open Repository and Archive (University of Zurich) (acceptedVersion, cc-by)
  • Zurich Open Repository and Archive (University of Zurich) (submittedVersion, cc-by)
  • Zurich Open Repository and Archive (University of Zurich)
Topics
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Research
  • Social Sciences › Decision Sciences › Information Systems and Management › Personal Information Management and User Behavior
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
Keywords
task type, task context, cognitive burden, temporal features, semantic features, professional developers

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.

The claim verdicts this report counts are experimental: their accuracy is not yet measured.

A language model drew the claims from the paper on 2026-10-10, under version 3 of the claim definition (model deepseek-v4.1-flash, prompt extract-v3).

A second model labelled each claim on 2026-10-10 (model jev-1.13-20260917, definition revision gold-guideline-v0.2).

Cited sources are checked with a language model’s help (gpt-6-sol).

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

How to cite

Cite CoChat for the checks on this page, and the paper for its own findings.

This page
CoChat. (2026). Citation check: Detecting Developers' Task Switches and Types. https://app.cochat.ai/papers/10.1109/tse.2020.2984086
The paper
Meyer, A. N., Satterfield, C., Zuger, M., Kevic, K., Murphy, G. C., Zimmermann, T., & Fritz, T. (2022). Detecting Developers' Task Switches and Types. IEEE Transactions on Software Engineering. https://doi.org/10.1109/tse.2020.2984086

Data sources

Bibliographic data: Semantic Scholar, OpenAlex, Crossref.

Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).

Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.