-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathIWoR19_Experiment.html
156 lines (128 loc) · 5.43 KB
/
IWoR19_Experiment.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
<!DOCTYPE html>
<html lang="en">
<head>
<title>Refactoring Empirical Study</title>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css">
<link rel="stylesheet" href="https://www.w3schools.com/w3css/4/w3.css">
<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js"></script>
<script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/js/bootstrap.min.js"></script>
<style>
div.box{
text.align: center;
}
.button {
background-color: #555555;;
border: none;
color: white;
padding: 15px 32px;
text-align: center;
text-decoration: none;
display: inline-block;
font-size: 16px;
margin: 4px 2px;
cursor: pointer;
border-radius: 8px;
}
/* Add a gray background color and some padding to the footer */
footer {
background-color: #f2f2f2;
padding: 25px;
}
</style>
</head>
<body>
<nav class="navbar navbar-inverse">
<div class="container-fluid">
<div class="navbar-header">
<button type="button" class="navbar-toggle" data-toggle="collapse" data-target="#myNavbar">
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</button>
</div>
<div class="collapse navbar-collapse" id="myNavbar">
<ul class="nav navbar-nav">
<li class="active"><a href="IWoR19_Index.html">Home</a></li>
</ul>
</div>
</div>
</nav>
<div class="jumbotron">
<div class="container text-center">
<h1>Can Refactoring be Self-Affirmed?</h1>
</div>
</div>
<h2>Research Questions and Findings</h2>
<blockquote><strong>RQ1: What patterns do developers use to describe their
refactoring activities?</strong></blockquote><p>Developers tend to use a variety of textual
patterns to document their refactoring activities, such as "refactor", "move", "extract", "reorganize", and "fix". These patterns could provide either (1) a generic description/
motivation of the refactoring activity such as "optimize the code design", "improving code readability", and "fix long method", or (2) a specific refactoring
operation name following Fowler's names such as "extract method", "extract class", and "extract interface".</p>
<div style="text-align: center" >
<img src="./Images/pattern.PNG" height="900" width="900"></div>
</div>
</div>
</div>
<hr>
<blockquote><strong>RQ2: What are the quality issues that drive developers to
refactor?</strong></blockquote><p>Our findings indicate that developers frequently state their intention behind the application of refactorings. They address quality issues that can be
related to : (1) internal quality attributes, (2) external quality attributes, or (3) code smells. Furthermore,
developers occasionally mention their refactoring strategy or operation performed with regard of addressing
the quality issue.</p>
<div class="container">
<div class="row">
<div class="col-sm-4">
<div class="panel panel-primary">
<div class="panel-heading">Internal Quality Attributes
</div>
<div class="panel-body"><img src="./Images/internalQA-wordcloud.png" class="img-responsive" style="width:100%" alt="Image"></div>
<div class="panel-footer"></div>
</div>
</div>
<div class="col-sm-4">
<div class="panel panel-danger">
<div class="panel-heading">External Quality Attributes
</div>
<div class="panel-body"><img src="./Images/externalQA-wordcloud.png" class="img-responsive" style="width:100%" alt="Image"></div>
<div class="panel-footer"></div>
</div>
</div>
<div class="col-sm-4">
<div class="panel panel-success">
<div class="panel-heading">Code Smell
</div>
<div class="panel-body"><img src="./Images/codesmell-wordcloud.png" class="img-responsive" style="width:100%" alt="Image"></div>
<div class="panel-footer"></div>
</div>
</div>
</div>
</div><br>
<hr>
<blockquote><strong>RQ3: What are the top-10 patterns developers use to
describe quality issues in their commits?</strong></blockquote><p>Our findings indicate that while there are no
patterns that are restricted to a specific quality issue, developers occasionally do link the refactoring of a
quality issue with a specific operation e.g., associating the correction of a feature envy by the operation move method.</p>
<div class="container">
<div class="row">
<div class="col-sm-6">
<div class="panel panel-danger">
<div class="panel-heading">Top-10 Popular Patterns</div>
<div class="panel-body"><img src="./Images/topkeyword-wordcloud_4.PNG" class="img-responsive" style="width:100%" alt="Image"></div>
<div class="panel-footer"></div>
</div>
</div>
</div>
</div>
<br>
<hr>
<blockquote><strong>RQ4: Do Commits containing the label Refactor indicate
more refactoring activity than those without the label?</strong></blockquote><p>Our findings confirm that developers do not exclusively rely on the pattern "refactor" to
describe refactoring activities. However, we found that developers do document their refactoring activities in commit messages with a variety of patterns that we identified in this study.</p>
<div style="text-align: center" >
<img src="./Images/RQ4.PNG" height="800" width="900"></div>
<footer class="container-fluid text-center">
</footer>
</body>
</html>