Cited by 25Software Engineering ResearchSoftware Engineering Techniques and PracticesContext-Aware Activity Recognition Systems

Inference of development activities from interaction with uninstrumented applications

Bao, Lingfeng, Xing, Zhenchang, Xia, Xin, Lo, David, Hassan, Ahmed E.·2018·Empirical Software Engineering

Integrity signals

Registry

Crossref · 10.1007/s10664-017-9547-8

Cites

55 of 55 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Claims the paper makes

We couldn’t retrieve this paper’s full text, so its claims and self-check weren’t run. The registry and citation checks still apply.

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

  • That one approach was limited to specific development activities only and did not consider the whole range of non-development tasks.

    “Yet, their examination was limited to specific development activities only, and did not consider the whole range of non-development tasks that developers are working on, such as administrative or planning tasks.”

    From Detecting Developers' Task Switches and Types (2022) · cites this paper as [22]

  • Only one approach so far has looked at automatic classification of developers' activities on a task level.

    “To the best of our knowledge, there has been only one approach so far that looked at the automatic classification of developers' activities on a task level [22].”

    From Detecting Developers' Task Switches and Types (2022) · cites this paper as [22]

  • Bao et al. found that a Conditional Random Field is able to classify development activity with 73 percent accuracy.

    “An analysis of data collected from ten developers over a week shows that CRF is able to classify the activity with 73 percent accuracy.”

    From Detecting Developers' Task Switches and Types (2022) · cites this paper as [22]

  • The classifier can make predictions even on previously unseen applications, distinguishing it from previous work.

    “One important aspect of our approach that distinguishes our classifier from previous work (e.g., [15], [22], [47]) is its ability to make predictions even on previously unseen applications.”

    From Detecting Developers' Task Switches and Types (2022) · cites this paper as [22]

  • Only very little prior work exists on automatically detecting, characterizing and summarizing developers' tasks.

    “We have been able to find only very little work on automatically detecting, characterizing and summarizing (developers) tasks yet [22], [32], [33].”

    From Detecting Developers' Task Switches and Types (2022) · cites this paper as [22]

Cites

Flagged first, then by citations

2 of the 57 references couldn’t be matched to a known paper.

Cited by

Sorted by citations

Authors
Bao, L., Xing, Z., Xia, X., Lo, D., & Hassan, A. E.
Affiliations
  • Zhejiang University (CN)
  • Australian National University (AU)
  • Monash University (AU)
  • Singapore Management University (SG)
  • Queen's University (CA)
Corresponding author
Xia, Xin
Venue
Empirical Software Engineering
Published
2017-09-16
Volume
23
Issue
3
Pages
1313-1351
ISSN
  • 1382-3256 (ISSN-L)
  • 1573-7616
OpenAlex
W2755579216
Cited by
25
References
57
Citations by year
2022: 4 · 2021: 4 · 2020: 9 · 2019: 3 · 2018: 5
FWCI
8.67
Type
journal article
Language
en
Open access
closed
Locations
  • Empirical Software Engineering (publishedVersion)
  • Singapore Management University Institutional Knowledge (InK) (Singapore Management University) (submittedVersion)
  • ANU Open Research (Australian National University) (submittedVersion)
Topics
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Research
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
  • Physical Sciences › Computer Science › Computer Vision and Pattern Recognition › Context-Aware Activity Recognition Systems
Keywords
developer behavior, sequence labeling

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.

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