2010
DOI: 10.1007/978-3-642-13881-2_7
|View full text |Cite
|
Sign up to set email alerts
|

Automatic Quality Assessment of Source Code Comments: The JavadocMiner

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
66
0
1

Year Published

2011
2011
2020
2020

Publication Types

Select...
3
2
1

Relationship

1
5

Authors

Journals

citations
Cited by 69 publications
(67 citation statements)
references
References 6 publications
0
66
0
1
Order By: Relevance
“…This paradigm shift leads to situations where the major documentation, such as software requirements specifications or design and implementation decisions, are only available in form of source code comments. Therefore, the quality of this documentation becomes increasingly important for developers attempting to perform the various software engineering and maintenance tasks [4].…”
Section: Software Engineering Backgroundmentioning
confidence: 99%
See 2 more Smart Citations
“…This paradigm shift leads to situations where the major documentation, such as software requirements specifications or design and implementation decisions, are only available in form of source code comments. Therefore, the quality of this documentation becomes increasingly important for developers attempting to perform the various software engineering and maintenance tasks [4].…”
Section: Software Engineering Backgroundmentioning
confidence: 99%
“…The goal of our JavadocMiner tool [4] is to enable users to automatically assess the quality of source code comments. The JavadocMiner is also capable of providing users with recommendations on how a Javadoc comment may be improved based Fig.…”
Section: Quality Analysis Of Source Code Commentsmentioning
confidence: 99%
See 1 more Smart Citation
“…Siy et al similarly found that a non-trivial portion of the issues that arise during industrial code inspection concern the quality of documentation [57]. Recently, there has been preliminary work examining both the completeness of comments and the consistency of comment updates with respect to future defects [32,41,55]. In all cases, low-quality and inconsistently updated comments correlated with higher defect density.…”
Section: Ensuring Documentation Completeness and Consistencymentioning
confidence: 99%
“…[4,15,20,23,30,31,45,47,53,71]) and to ensure long-term system understandability and evolvability (e.g. [11,12,13,41,55,58,59]). Despite these advancements, developers still struggle to handle the volume of maintenance tasks that arise in practice [31].…”
Section: Introductionmentioning
confidence: 99%