Stop Words for Processing Software Engineering Documents: Do they Matter?
Not on the map. Why?
Abstract (arXiv)
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
Key facts. No citing papers in the map yet (data through 7 Oct 2026). Builds on 5 of its 40 references that are in the map. First posted on arXiv 18 Mar 2023.
Builds on
5 of 40 references.
References · 5
- 2020Stopwords in Technical Language Processingcited by 29
- 2018Categorizing the Content of GitHub README Filescited by 18
- 2019TechNet: Technology Semantic Network Based on Patent Datacited by 14
- 2014Unsupervised Keyword Extraction from Polish Legal Textscited by 2
- 2018RACK: Code Search in the IDE using Crowdsourced Knowledgecited by 1
Built on by
Not cited yet.