Stop Words for Processing Software Engineering Documents: Do they Matter?

Yaohou Fan, Chetan Arora, Christoph Treude
3/18/2023
cs.SEcs.CL

No confident code implementation found for this paper.

Abstract

Stop words, which are considered non-predictive, are often eliminated in natural language processing tasks. However, the definition of uninformative vocabulary is vague, so most algorithms use general knowledge-based stop lists to remove stop words. There is an ongoing debate among academics about the usefulness of stop word elimination, especially in domain-specific settings. In this work, we investigate the usefulness of stop word removal in a software engineering context. To do this, we replicate and experiment with three software engineering research tools from related work. Additionally, we construct a corpus of software engineering domain-related text from 10,000 Stack Overflow questions and identify 200 domain-specific stop words using traditional information-theoretic methods. Our results show that the use of domain-specific stop words significantly improved the performance of research tools compared to the use of a general stop list and that 17 out of 19 evaluation measures showed better performance. Online appendix: https://zenodo.org/record/7865748

View on arXivView PDF

Code Implementations

No confident code match yet

We couldn't find an author-owned or strongly-evidenced community implementation for this paper. Any repos shown below are weak matches — verify before relying on them.

No code implementations found yet.

Know of an implementation? Let us know in the comments below!

Similar Papers

Cite this paper

@article{fan2023stop,
  title  = {Stop Words for Processing Software Engineering Documents: Do they Matter?},
  author = {Yaohou Fan and Chetan Arora and Christoph Treude},
  year   = {2023},
  eprint = {2303.10439},
  archivePrefix = {arXiv},
  url    = {http://arxiv.org/abs/2303.10439v2}
}

Add a badge to your README

Shows whether official code is linked for this paper.

Code of Paper badge
[![Code of Paper](https://codeofpaper.com/badge/2303.10439.svg)](https://codeofpaper.com/paper/2303.10439)

Discussion