Main

Research Areas And Projects

Main.ResearchAreasAndProjects History

Hide minor edits - Show changes to markup

18-02-2010 16:19 by rohit -
Changed line 6 from:

* '''Title''': A language to specify design rules for aspect oriented programming

to:

* '''Title''': A Language to Specify Design Rules for Aspect Oriented Programming

18-02-2010 16:18 by rohit -
Changed lines 1-2 from:

Past Projects

to:

Projects

* '''Title''': Making Program Refactoring Safer * '''Abstract''': Developers rely on compilation, test suite and tools to preserve observable behavior during refactoring. However, most of the refactoring tools do not implement all preconditions that guarantee the refactoring correctness, since formally identifying them is cost-prohibitive. Therefore, these tools may perform non-behavior preserving transformations. We aim at building a tool for improving safety during refactoring object oriented and aspect oriented refactorings.

Changed lines 8-9 from:

* '''Members''' Arthur Marques and Rohit Gheyi

to:
Deleted line 10:

* '''Members''' Diego Cavalcanti and Rohit Gheyi

23-10-2009 09:58 by rohit -
Deleted lines 0-5:

Current Projects

* '''Title''': * '''Abstract''': * '''Members'''

Changed line 9 from:

* '''Members''' Diego Tavares and Rohit Gheyi

to:

* '''Members''' Diego Cavalcanti and Rohit Gheyi

22-09-2009 15:29 by arthur -
Changed line 14 from:

* '''Abstract''': Symbolic execution defines program’s paths by their restrictions. Software’s tests can be developed according to values that satisfy those restrictions. However, some program’s restrictions can’t be solved by the current solvers. This project proposes different solvers that aim to mitigate this problem, solving complex restrictions.Therefore, tests can be improved according to this proposal.

to:

* '''Abstract''': Symbolic execution generates constraints according to program’s paths and their restrictions. One way to reduce the cost of testing is the assignment of values which satisfy constraints generated by symbolic execution of programs. However, some programs contain complex constraints that current constraint solvers do not support. This project proposes and evaluates three constraint solvers that aim to mitigate this problem, increasing the number of complex constraints solved. Therefore, tests coverage can be improved.

21-09-2009 23:21 by arthur -
Changed line 14 from:

* '''Abstract''': The purpose of this project was to propose restriction solvers that aids developers to generate case unit tests by solving restrictions generated by the symbolic execution program’s resolution.

to:

* '''Abstract''': Symbolic execution defines program’s paths by their restrictions. Software’s tests can be developed according to values that satisfy those restrictions. However, some program’s restrictions can’t be solved by the current solvers. This project proposes different solvers that aim to mitigate this problem, solving complex restrictions.Therefore, tests can be improved according to this proposal.

21-09-2009 23:10 by arthur -
Changed line 10 from:

* '''Abstract''': Despite Aspect Oriented Programming (AO) modularize program’s crosscutting concerns it can break class modularity in certain circumstances. In this case, classes must known what aspects interfere on its functionalities. It was observed that design rules can mitigate the coupling between aspects and classes. This project proposes a language to specify design rules and declare the dependences between classes and aspects. We’ve developed a tool to automatically check if the design rules are been followed.

to:

* '''Abstract''': Despite Aspect Oriented Programming modularize program’s crosscutting concerns it can break class modularity in certain circumstances. In this case, classes must known what aspects interfere on its functionalities. It was observed that design rules can mitigate the coupling between aspects and classes. This project proposes a language to specify design rules and declare the dependences between classes and aspects. We’ve developed a tool to automatically check if the design rules are been followed.

Added lines 12-15:

* '''Title''': Proposal and Analysis of Restriction Solvers * '''Abstract''': The purpose of this project was to propose restriction solvers that aids developers to generate case unit tests by solving restrictions generated by the symbolic execution program’s resolution. * '''Members''' Diego Tavares and Rohit Gheyi

21-09-2009 22:57 by arthur -
Changed lines 9-11 from:

* '''Title''': * '''Abstract''': * '''Members'''

to:

* '''Title''': A language to specify design rules for aspect oriented programming * '''Abstract''': Despite Aspect Oriented Programming (AO) modularize program’s crosscutting concerns it can break class modularity in certain circumstances. In this case, classes must known what aspects interfere on its functionalities. It was observed that design rules can mitigate the coupling between aspects and classes. This project proposes a language to specify design rules and declare the dependences between classes and aspects. We’ve developed a tool to automatically check if the design rules are been followed. * '''Members''' Arthur Marques and Rohit Gheyi

03-09-2009 18:21 by rohit -
Added lines 1-11:

Current Projects

* '''Title''': * '''Abstract''': * '''Members'''

Past Projects

* '''Title''': * '''Abstract''': * '''Members'''

Menu * Main * Members * Awards * Publications * Tools * Thesis * Internal Links * Contact

Blix theme adapted by David Gilbert, powered by PmWiki