Released Illinois Data Set Refactoring Composition Patterns (transaction-pattern-descriptions.csv)
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

 
View only
 
 
Still loading...
ABCDEFGHIJKLMNOPQR
1
TRANSACTION_PATTERN_IDENTIFIERNUMBER_OF_TRANSACTIONSFUNCTION1FUNCTION2TRANSACTION_PATTERN_DESCRIPTION
2
455preparationThe programmer extracted an expression into a local variable to add a corresponding parameter to the method signature inferred by an upcoming Extract Method refactoring.
3
67no-configurationThe programmer extracted at least one local variable and later renamed it.
4
206backtrackingAt least a pair of Inline and Extract Local Variable refactorings canceled each other.
5
202related-entitiesThe programmer first extracted a local variable, say v, and then extracted another expression containing v into a local variable.
6
201related-entitiesThe programmer extracted an expression into a local variable, and then inlined a local variable used in the previously extracted expression.
7
373related-entitiesThe programmer renamed a local variable and its surrounding method.
8
372related-entitiesThe programmer renamed a method and then one of its parameters.
9
372related-entitiesThe programmer renamed a method and a local variable holding its return value.
10
371related-entitiesThe programmer renamed a method and a local variable with similar names.
11
371related-entitiesThe programmer renamed two methods with similar names.
12
478related-entitiesThe programmer renamed a field and a local variable used in the same class.
13
475related-entitiesThe programmer renamed a field and a local variable with similar names.
14
472related-entitiesThe programmer renamed a local variable and one of its fields.
15
472related-entitiesThe programmer renamed a field and its corresponding constructor parameter.
16
1275preparationThe programmer extracted a local variable to include it in the inferred signature of an upcoming Extract Method refactoring.
17
1275cleanupThe programmer extracted a method and then inlined one of its arguments that was used only once.
18
1274preparationcleanupThe programmer first extracted a local variable to include it in the signature of an upcoming Extract Method refactoring. Second, he performed an Extract Method refactoring with a selection that excluded the previously extracted local variable. Finally, the programmer inlined the previously extracted local variable.
19
1273cleanupThe programmer first performed an Extract Method refactoring. The Extract Method refactoring added a return statement, which returned a local variable that was used once. Finally, the programmer inlined the local variable of the return statement.
20
1272cleanupThe programmer extracted a method. The refactoring tool stored the return value of the extracted method in a local variable, which was used just once. The programmer inlined the local variable that stored the return value of the extracted method.
21
1403cleanupThe programmer extracted a method and then inlined one if its arguments.
22
1403cleanupThe programmer extracted a method and then inlined the variable that it returned.
23
1403cleanupThe programmer extracted a method and then inlined the variable that held the return value of the extracted method.
24
1385related-entitiesThe extracted constant and local variable appeared in the same statement.
25
1383related-entitiesThe programmer first extracted a constant. Then, he extracted an expression containing the constant into a local variable.
26
1382backtrackingThe programmer extracted an expression into a local variable, undid it, and then extracted the expression into a constant.
27
1002backtrackingThe programmer first extracted an expression into a method. Then, he undid it and applied the Extract Constant refactoring on the same expression.
28
1332related-entitiesThe promoted local variable and the inlined local variable appeared in the same statement.
29
1331backtrackingThe programmer performed inline local variable, undid it, and finally converted it to a field.
30
1331backtrackingThe programmer converted a local variable to a field, undid it, and finally inlined the local variable.
31
712related-entitiesThe programmer renamed a type and encapsulated some of its fields.
32
531related-entitiesThe extracted local variable and changed method appeared in the same statement.
33
36unrelatedThe refactorings are unrelated.
34
66unrelatedThe refactorings are applied to pieces of code in close proximity, but, they are otherwise unrelated.
35
691preparationrelated-entitiesThe programmer extracted local variables to control the method signature inferred by an upcoming Extract Method refactoring. Then, he renamed the extracted method and used the Change Method Signature refactoring to change the type of one of its parameters from int to String.
36
771unrelatedThe transaction was big and difficult to follow.
37
811single-entityThe programmer performed the following two changes. First, the programmer extracted a constant and then pulled it up. Second, the programmer extracted a method and then pulled it up.
38
821unrelatedThe Encapsulate Field and Pull Up refactoring operated on different fields and thus were not related.
39
901single-entityThe programmer pushed down two fields and performed the Encapsulate Field refactoring on them.
40
911singly-entityThe programmer pushed down two fields into a subclass and extracted a method in the subclass. It isn't clear how these refactorings are related.
41
941singly-entityThe programmer moved and renamed a type and encapsulated a field of it. He also extracted a method in a class and pushed down fields of its superclass, but, these two refactorings don't seem related.
42
961related-entitiesThe programmer changed the type of a method parameter and pushed down a field of the same class. The new method parameter and the field had same types and names.
43
991unrelatedThere is no clear relation between the refactorings in the single instance of this pattern.
44
1201related-entitiesThe Extract Method and Pull Up refactorings in the single instance of this pattern are not related, but, the Pull Up refactorings operate on fields of the same class.
45
1491related-entitiesThe programmer performed Rename and Extract Superclass refactorings on the same type.
46
1901unrelatedThe refactorings in the single instance of this pattern seem unrelated.
47
2091single-entityThe programmer pushed down a method and then moved the resulting two methods from the subclasses.
48
2441unrelatedThe two refactorings don't seem related.
49
301single-entityThe programmer extracted a method manually and then pull it up.
50
331single-entityThe programmer pulled up a method from a class and then renamed the class.
51
1191no-configurationThe programmer pulled up two methods of the same class one by one.
52
1681related-entitiesThe programmer moved a class and then pulled up 4 of its members.
Loading...
 
 
 
Sheet1