Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
people:minostro [2008/06/17 19:41] – minostro | people:minostro [2012/01/27 00:17] (current) – minostro | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | | | ||
+ | | **Milton Inostroza** | ||
+ | | //Master Student// | ||
+ | | [[http:// | ||
+ | | [[http:// | ||
+ | | [[http:// | ||
+ | |||
+ | ===== About Me ===== | ||
+ | I'm a second year Master student at the [[http:// | ||
+ | |||
+ | ===== Research Interests ===== | ||
+ | * Aspect-Oriented Programming | ||
+ | * Modularity | ||
+ | |||
+ | ===== Short Research Description===== | ||
+ | (from the abstract of my thesis proposal) | ||
+ | |||
+ | Aspect-Oriented Programming (AOP) successfully modularizes crosscutting concerns such as logging, profiling, security among others. However, AOP fails to provide modular reasoning and separate evolution of aspects and base code. In current aspect languages, modular reasoning is hampered because base code has no way to know which properties and invariants aspects rely upon, and because aspects, through their pointcuts, carry explicit references to the base code. This compromises separate evolution of aspects and base code because slight changes in either base or aspect code can break unwittingly strong assumptions made by programmers. | ||
+ | |||
+ | In the AOP community, several proposals try to address these problems without success. In this thesis, we introduce Join Point Interfaces (JPIs): a novel abstraction layer between aspects and base code. JPIs support, by design, modular reasoning and independent evolution by supporting a modular type-checking algorithm. We provide strong guarantees that any program that typechecks is free of uncaught checked exceptions at runtime. This in contrast to existing solutions that cannot provide such guarantees in all cases. In addition, we plan to implement JPIs as an extension of the abc compiler for AspectJ and migrate several applications to assess the impact of JPIs in real software products. | ||
+ | |||
+ | ===== Publications ===== | ||
+ | |||
+ | <note important> | ||
+ | //The following documents are included by the contributing authors as a means to ensure timely dissemination of scholarly and technical work on a non-commercial basis. Copyright and all rights therein are maintained by the authors or by other copyright holders, notwithstanding that they have offered their works here electronically. It is understood that all persons copying this information will adhere to the terms and constraints invoked by each author' | ||
+ | // | ||
+ | </ | ||
+ | |||
+ | < | ||
+ | < | ||
+ | <div id=" | ||
+ | </ | ||
+ | |||