Tools
Main.Tools History
Hide minor edits - Show changes to output
08-10-2013 21:03
by -
Changed lines 21-28 from:
*[[https://bitbucket.org/gustavoasoares/jdolly | https://bitbucket.org/gustavoasoares/jdolly]]
to:
*[[https://bitbucket.org/gustavoasoares/jdolly | https://bitbucket.org/gustavoasoares/jdolly]]
[+Colligens+]
A Software Product Line (SPL) is a set of products developed from reusable assets. These products share a common platform and we can customize them for specific customers. In an SPL, developers use the concept of features. They are the semantic units by which we can differentiate products. In C programming, we can implement features by mapping them to preprocessor directives, such as #ifdef and#endif. In this context, although there are tools to deal with C preprocessors and SPLs, they are not integrated, which hinders their usage in product line development. In this paper, we propose a tool that provides an integrated environment based on the Eclipse platform to support the development of preprocessor-based SPLs in C. Thus, developers can create feature models, analyze SPL statistics, and generate SPL products automatically after checking for the absence of invalid products.
More Information:
*[[https://sites.google.com/a/ic.ufal.br/colligens/ | Colligens Website]]
[+Colligens+]
A Software Product Line (SPL) is a set of products developed from reusable assets. These products share a common platform and we can customize them for specific customers. In an SPL, developers use the concept of features. They are the semantic units by which we can differentiate products. In C programming, we can implement features by mapping them to preprocessor directives, such as #ifdef and#endif. In this context, although there are tools to deal with C preprocessors and SPLs, they are not integrated, which hinders their usage in product line development. In this paper, we propose a tool that provides an integrated environment based on the Eclipse platform to support the development of preprocessor-based SPLs in C. Thus, developers can create feature models, analyze SPL statistics, and generate SPL products automatically after checking for the absence of invalid products.
More Information:
*[[https://sites.google.com/a/ic.ufal.br/colligens/ | Colligens Website]]
07-10-2013 17:07
by -
Changed line 7 from:
*[[http://www.dsc.ufcg.edu.br/~spg/safira.html | Safira]]
to:
*[[http://www.dsc.ufcg.edu.br/~spg/safira.html | Safira Home Page]]
07-10-2013 17:05
by -
Added lines 1-8:
[+Safira+]
Safira is a change impact analyzer tool. It analyzes two versions of a program (original and modified) and yields the set of methods impacted by the change. Safira decomposes a coarse-grained transformation into smaller transformations. For each small-grained transformation, it identifies the set of impacted methods using laws that formalize their impact. Moreover, it also identifies the methods that exercise an impacted method directly or indirectly.
More Information:
*[[http://www.dsc.ufcg.edu.br/~spg/safira.html | Safira]]
Safira is a change impact analyzer tool. It analyzes two versions of a program (original and modified) and yields the set of methods impacted by the change. Safira decomposes a coarse-grained transformation into smaller transformations. For each small-grained transformation, it identifies the set of impacted methods using laws that formalize their impact. Moreover, it also identifies the methods that exercise an impacted method directly or indirectly.
More Information:
*[[http://www.dsc.ufcg.edu.br/~spg/safira.html | Safira]]
Changed line 21 from:
*[[https://bitbucket.org/gustavoasoares/jdolly | https://bitbucket.org/gustavoasoares/jdolly]]
to:
*[[https://bitbucket.org/gustavoasoares/jdolly | https://bitbucket.org/gustavoasoares/jdolly]]
04-10-2013 12:36
by -
Changed line 10 from:
JDolly is a Java program generator useful for performing the test input generation. It generates Java programs from a Java metamodel specification. It contains a subset of the Java metamodel specified in Alloy, a formal specification language. It employs the Alloy Analyzer, a tool for the analysis of Alloy models, to generate solutions for this metamodel. Each solution is translated into a Java program. In JDolly, the user can specify the maximum number (scope) of packages, classes, fields, and methods for the generated programs. The tool exhaustively generates programs for a given scope. In this way, it may generate input programs capable of revealing bugs that developers were unaware of. Furthermore, JDolly can be parameterized with specific constraints. For example, when testing a refactoring that pulls up a method to a superclass, the input programs must contain at least a subclass declaring a method that is subject to be pulled up. We can specify these constraints in Alloy.
to:
JDolly is a Java program generator useful for performing the test input generation. It generates Java programs from a Java metamodel specification. It contains a subset of the Java metamodel specified in Alloy, a formal specification language. It employs the Alloy Analyzer, a tool for the analysis of Alloy models, to generate solutions for this metamodel. Each solution is translated into a Java program. In JDolly, the user can specify the maximum number (scope) of packages, classes, fields, and methods for the generated programs. The tool exhaustively generates programs for a given scope.
04-10-2013 12:35
by -
Changed lines 6-14 from:
*[[http://www.dsc.ufcg.edu.br/~spg/saferefactor/ | Safe Refactor Home Page]]
to:
*[[http://www.dsc.ufcg.edu.br/~spg/saferefactor/ | Safe Refactor Home Page]]
[+JDolly+]
JDolly is a Java program generator useful for performing the test input generation. It generates Java programs from a Java metamodel specification. It contains a subset of the Java metamodel specified in Alloy, a formal specification language. It employs the Alloy Analyzer, a tool for the analysis of Alloy models, to generate solutions for this metamodel. Each solution is translated into a Java program. In JDolly, the user can specify the maximum number (scope) of packages, classes, fields, and methods for the generated programs. The tool exhaustively generates programs for a given scope. In this way, it may generate input programs capable of revealing bugs that developers were unaware of. Furthermore, JDolly can be parameterized with specific constraints. For example, when testing a refactoring that pulls up a method to a superclass, the input programs must contain at least a subclass declaring a method that is subject to be pulled up. We can specify these constraints in Alloy.
*[[https://bitbucket.org/gustavoasoares/jdolly | https://bitbucket.org/gustavoasoares/jdolly]]
[+JDolly+]
JDolly is a Java program generator useful for performing the test input generation. It generates Java programs from a Java metamodel specification. It contains a subset of the Java metamodel specified in Alloy, a formal specification language. It employs the Alloy Analyzer, a tool for the analysis of Alloy models, to generate solutions for this metamodel. Each solution is translated into a Java program. In JDolly, the user can specify the maximum number (scope) of packages, classes, fields, and methods for the generated programs. The tool exhaustively generates programs for a given scope. In this way, it may generate input programs capable of revealing bugs that developers were unaware of. Furthermore, JDolly can be parameterized with specific constraints. For example, when testing a refactoring that pulls up a method to a superclass, the input programs must contain at least a subclass declaring a method that is subject to be pulled up. We can specify these constraints in Alloy.
*[[https://bitbucket.org/gustavoasoares/jdolly | https://bitbucket.org/gustavoasoares/jdolly]]
17-02-2010 12:15
by -
Changed line 6 from:
*[[http://www.dsc.ufcg.edu.br/~spg/safeRefactor/ | Safe Refactor Home Page]]
to:
*[[http://www.dsc.ufcg.edu.br/~spg/saferefactor/ | Safe Refactor Home Page]]
02-09-2009 10:33
by -
Changed lines 1-5 from:
Program refactorings in IDEs are commonly implemented in an ad hoc way, since checking correctness with respect to a formal semantics is prohibitive. These tools may perform erroneous transformations, not preserving behavior.
Safe
to:
[+Safe Refactor+]
Program refactorings in IDEs are commonly implemented in an ad hoc way, since checking correctness with respect to a formal semantics is prohibitive. These tools may perform erroneous transformations, not preserving behavior. Safe Refactor is an Eclipse Plugin for verifying the safety of Eclipse refactorings on sequential Java Program. It is based on our technique for generating tests in order to find behavioral changes in automated refactored programs transformed by well-known tools, such as Eclipse, JBuilder, IntelliJ or Netbeans
More Information:
02-09-2009 02:03
by -
Changed line 6 from:
*[[http://www.dsc.ufcg.edu.br/~spg/safeRefactor/ | Safe Refactor Project Home Page]]
to:
*[[http://www.dsc.ufcg.edu.br/~spg/safeRefactor/ | Safe Refactor Home Page]]
02-09-2009 02:03
by -
Changed lines 5-7 from:
[[http://www.dsc.ufcg.edu.br/~spg/safeRefactor/ | Safe Refactor Project Home Page]]
to:
''''+Related links+''''
*[[http://www.dsc.ufcg.edu.br/~spg/safeRefactor/ | Safe Refactor Project Home Page]]
*[[http://www.dsc.ufcg.edu.br/~spg/safeRefactor/ | Safe Refactor Project Home Page]]
02-09-2009 02:01
by -
Changed line 1 from:
to:
#'''[++Safe Refactor++]'''
Changed lines 3-7 from:
Safe Refactor is an Eclipse Plugin for verifying the safety of Eclipse refactorings on sequential Java Program. It is based on our technique for generating tests in order to find behavioral changes in automated refactored programs transformed by well-known tools, such as Eclipse, JBuilder, IntelliJ or Netbeans
to:
Safe Refactor is an Eclipse Plugin for verifying the safety of Eclipse refactorings on sequential Java Program. It is based on our technique for generating tests in order to find behavioral changes in automated refactored programs transformed by well-known tools, such as Eclipse, JBuilder, IntelliJ or Netbeans
*Related links
[[http://www.dsc.ufcg.edu.br/~spg/safeRefactor/ | Safe Refactor Project Home Page]]
*Related links
[[http://www.dsc.ufcg.edu.br/~spg/safeRefactor/ | Safe Refactor Project Home Page]]
02-09-2009 01:54
by -
Changed lines 1-2 from:
[+Safe Refactor+]
to:
*'''[+Safe Refactor+]'''
Changed lines 3-4 from:
Safe Refactor is an Eclipse Plugin for verifying the safety of Eclipse refactorings on sequential Java Program. \\
It is based on our technique for generating tests in order to find behavioral changes in automated refactored programs transformed by well-known tools, such as Eclipse, JBuilder, IntelliJ or Netbeans
It is based on our technique for generating tests in order to find behavioral changes in automated refactored programs transformed by well-known tools, such as Eclipse, JBuilder, IntelliJ or Netbeans
to:
Safe Refactor is an Eclipse Plugin for verifying the safety of Eclipse refactorings on sequential Java Program. It is based on our technique for generating tests in order to find behavioral changes in automated refactored programs transformed by well-known tools, such as Eclipse, JBuilder, IntelliJ or Netbeans
02-09-2009 01:53
by -
Added lines 1-5:
[+Safe Refactor+]
Program refactorings in IDEs are commonly implemented in an ad hoc way, since checking correctness with respect to a formal semantics is prohibitive. These tools may perform erroneous transformations, not preserving behavior.\\
Safe Refactor is an Eclipse Plugin for verifying the safety of Eclipse refactorings on sequential Java Program. \\
It is based on our technique for generating tests in order to find behavioral changes in automated refactored programs transformed by well-known tools, such as Eclipse, JBuilder, IntelliJ or Netbeans
Program refactorings in IDEs are commonly implemented in an ad hoc way, since checking correctness with respect to a formal semantics is prohibitive. These tools may perform erroneous transformations, not preserving behavior.\\
Safe Refactor is an Eclipse Plugin for verifying the safety of Eclipse refactorings on sequential Java Program. \\
It is based on our technique for generating tests in order to find behavioral changes in automated refactored programs transformed by well-known tools, such as Eclipse, JBuilder, IntelliJ or Netbeans
