Analyze this! 145 questions for data scientists in software engineering
Open accessThe DOI matches its Crossref record; 6 of the 6 references it cites were found in a registry or an index.
Abstract
In this paper, we present the results from two surveys related to data science applied to software engineering. The first survey solicited questions that software engineers would like data scientists to investigate about software, about software processes and practices, and about software engineers. Our analyses resulted in a list of 145 questions grouped into 12 categories. The second survey asked a different pool of software engineers to rate these 145 questions and identify the most important ones to work on first. Respondents favored questions that focus on how customers typically use their applications. We also saw opposition to questions that assess the performance of individual employees or compare them with one another. Our categorization and catalog of 145 questions can help researchers, practitioners, and educators to more easily focus their efforts on topics that are important to the software industry.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Five misunderstandings about case-study research
Flyvbjerg, B. (2006) · Qualitative Inquiry · doi:10.1177/1077800405284363 · Cited by 14,266
Information Needs in Collocated Software Development Teams
Ko, A. J., DeLine, R., & Venolia, G. (2007) · 29th International Conference on Software Engineering (ICSE'07) · doi:10.1109/icse.2007.45 · Cited by 499 · cited 1×
“Please list up to five questions you would like them to answer.”
BackgroundA Model for Technology Transfer in Practice
Gorschek, T., Garre, P., Larsson, S., & Wohlin, C. (2006) · IEEE Software · doi:10.1109/ms.2006.147 · Cited by 350 · cited 1×
“Numerous studies have reviewed the performance of such partnerships to describe the impact of research and glean the attributes that make for successful technology transfer [39,40].”
BackgroundNovice software developers, all over again
Begel, A., & Simon, B. (2008) · Proceedings of the Fourth international Workshop on Computing Education Research · doi:10.1145/1404520.1404522 · Cited by 266
Self-citationConducting on-line surveys in software engineering
Punter, T., Ciolkowski, M., Freimut, B., & John, I. (2003) · 2003 International Symposium on Empirical Software Engineering, 2003. ISESE 2003. Proceedings. · doi:10.1109/isese.2003.1237967 · Cited by 193
Using information fragments to answer the questions developers ask
Fritz, T., & Murphy, G. C. (2010) · Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 1 · doi:10.1145/1806799.1806828 · Cited by 163
Cited by
Practitioners' expectations on automated fault localization
Kochhar, P. S., Xia, X., Lo, D., & Li, S. (2016) · Proceedings of the 25th International Symposium on Software Testing and Analysis · doi:10.1145/2931037.2931051 · Cited by 346
Storey, M.-A., Zagalsky, A., Filho, F. F., Singer, L., & German, D. M. (2017) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2016.2584053 · Cited by 221
“as answering technical questions is one of the most important developer information needs [37], [38] and resources such as Stack Overflow are designed to be reached through Search tools.”
MethodData scientists in software teams: State of the art and challenges
Kim, M., Zimmermann, T., DeLine, R., & Begel, A. (2018) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2017.2754374 · Cited by 199
Self-citationCode review quality: how developers see it
Kononenko, O., Baysal, O., & Godfrey, M. W. (2016) · Proceedings of the 38th International Conference on Software Engineering · doi:10.1145/2884781.2884840 · Cited by 183
Ensemble Methods for App Review Classification: An Approach for Software Evolution (N)
Guzman, E., El-Haliby, M., & Bruegge, B. (2015) · 2015 30th IEEE/ACM International Conference on Automated Software Engineering (ASE) · doi:10.1109/ase.2015.88 · Cited by 143
Metadata
- Authors
- Begel, A., & Zimmermann, T.
- Venue
- Proceedings of the 36th International Conference on Software Engineering
- Publisher
- ACM
- Published
- 2014-05-31
- Pages
- 12-23
- ISSN
- 0270-5257 (ISSN-L)
- OpenAlex
- W2163004671
- Cited by
- 212
- References
- 6
- FWCI
- 21.66
- Type
- conference paper
- Language
- en
- Open access
- bronze
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
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.