IEEE International Conference on Computer Systems and Applications, 2006. 2006
DOI: 10.1109/aiccsa.2006.205164
|View full text |Cite
|
Sign up to set email alerts
|

Refactoring Tools and Complementary Techniques

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
6
0

Year Published

2010
2010
2021
2021

Publication Types

Select...
4
2

Relationship

0
6

Authors

Journals

citations
Cited by 6 publications
(6 citation statements)
references
References 2 publications
0
6
0
Order By: Relevance
“…Negatives. E1, E2, E5, and E6 indicated a problem in that the visualization overlaps the text (3,3,4,2). While most evaluators did not provide a reason for why this is a problem, E2 stated that having the colored petals beneath the black text and surrounded by a white background makes it noticeable and therefore affects the legibility.…”
Section: Discussionmentioning
confidence: 99%
See 2 more Smart Citations
“…Negatives. E1, E2, E5, and E6 indicated a problem in that the visualization overlaps the text (3,3,4,2). While most evaluators did not provide a reason for why this is a problem, E2 stated that having the colored petals beneath the black text and surrounded by a white background makes it noticeable and therefore affects the legibility.…”
Section: Discussionmentioning
confidence: 99%
“…E5 identified that the constantly changing petals could be quite distracting (3). E6 noted that, depending on position, the mouse rollover labels can obscure the problem that is being highlighted (4). E6 also observed that the darkness of some petals can obscure the text, which is yet another indication that it can be distracting for the visualization to overlay the text (1).…”
Section: Visibility Of Statementioning
confidence: 95%
See 1 more Smart Citation
“…Most automated refactorings might still need a certain level of user intervention to make the code more readable, and the developer still might need to know how the code base is affected due to the change [7,12].…”
Section: B Suggestions For Automated Refactoringsmentioning
confidence: 99%
“…Refactoring means to re-influence, something that already exists [1]. Whenever we make a change in the code, we are refactoring the software.…”
Section: Introductionmentioning
confidence: 99%