Two-way traceability and conflict debugging for AspectLTL programs

Shahar Maoz*, Yaniv Sa'ar

*Corresponding author for this work

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

Abstract

Tracing program actions back to the concerns that have caused them and blaming specific code artifacts for concern interference are known challenges of AOP and related advanced modularity paradigms. In this work we address these challenges in the context of AspectLTL, a temporallogic based language for the specification and implementation of crosscutting concerns, which has a composition and synthesis-based weaving process whose output is a correct-by-construction executable artifact. When a specification is realizable, we provide two-way traceability information that links each allowed or forbidden transition in the generated program with the aspects that have justified its presence or elimination. When a specification is unrealizable, we provide an interactive game proof that demonstrates conflicts that should be fixed. The techniques are implemented and demonstrated using running examples.

Original languageEnglish
Title of host publicationAOSD'12 - Proceedings of the 11th Annual International Conference on Aspect Oriented Software Development
Pages35-46
Number of pages12
DOIs
StatePublished - 2012
Externally publishedYes
Event11th Annual International Conference on Aspect Oriented Software Development, AOSD'12 - Potsdam, Germany
Duration: 25 Mar 201230 Mar 2012

Publication series

NameAOSD'12 - Proceedings of the 11th Annual International Conference on Aspect Oriented Software Development

Conference

Conference11th Annual International Conference on Aspect Oriented Software Development, AOSD'12
Country/TerritoryGermany
CityPotsdam
Period25/03/1230/03/12

Keywords

  • Aspect-oriented programming
  • Linear temporal logic
  • Synthesis

Fingerprint

Dive into the research topics of 'Two-way traceability and conflict debugging for AspectLTL programs'. Together they form a unique fingerprint.

Cite this