volume 30, issue 6, Pe1886 2017
DOI: 10.1002/smr.1886
View full text
|
Sign up to set email alerts
|
Share

Abstract: Existing techniques for detecting code smells (indicators of source code problems) do not consider the current context, which renders them unsuitable for developers who have a specific context, such as modules within their focus. Consequently, the developers must spend time identifying relevant smells. We propose a technique to prioritize code smells using the developers' context. Explicit data of the context are obtained using a list of issues extracted from an issue tracking system. We applied impact analys…

Expand abstract

Search citation statements

Order By: Relevance

Citation Types

0
9
0

Paper Sections

0
0
0
0
0

Publication Types

0
0
0
0

Relationship

0
0

Authors

Journals