AspectMaps: Extending Moose to visualize AOP software

Fabry, Johan; Kellens, Andy; Denier, Simon; Ducasse, Sté́phane

doi:10.1016/j.scico.2012.02.007

Cited by 7 publications

(3 citation statements)

References 18 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In the code editor, at each join point shadow, gutter markers are present that reveal information about the advice. AJDT also provides for a visualization of the source code, but this feature has been superseded by other aspectual visualizations, the most recent of which is AspectMaps [13,20]. AspectMaps is a visualization tool that shows where in the code aspects apply.…”

Section: Accepted Manuscriptmentioning

confidence: 99%

AspectJ code analysis and verification with GASR

Fabry

Roover

Noguera

et al. 2016

Journal of Systems and Software

Self Cite

View full text Add to dashboard Cite

• We argue for a general-purpose source code analysis tool that is aware of aspects.• We present the logic program querying tool GASR, the first such tool..• We discuss its implementation along with its library of logical predicates.• We show how it can automatically verify previously published aspectual assumptions. AbstractAspect-oriented programming languages extend existing languages with new features for supporting modularization of crosscutting concerns. These features however make existing source code analysis tools unable to reason over this code. Consequently, all code analysis efforts of aspect-oriented code that we are aware of have either built limited analysis tools or were performed manually. Given the significant complexity of building them or manual analysis, a lot of duplication of effort could have been avoided by using a general-purpose tool.To address this, in this paper we present Gasr: a source code analysis tool that reasons over AspectJ source code, which may contain metadata in the form of annotations. Gasr provides multiple kinds of analyses that are general enough such that they are reusable, tailorable and can reason over annotations. We demonstrate the use of Gasr in two ways: we first automate the recognition of previously identified aspectual source code assumptions. Second, we turn implicit assumptions into explicit assumptions through annotations and automate their verification. In both uses Gasr performs detection and verification of aspect assumptions on two well-known case studies that were manually investigated in earlier work. Gasr finds already known aspect assumptions and adds instances that had been previously overlooked.

show abstract

Section: Accepted Manuscriptmentioning

confidence: 99%

AspectJ code analysis and verification with GASR

Fabry

Roover

Noguera

et al. 2016

Journal of Systems and Software

Self Cite

View full text Add to dashboard Cite

show abstract

“…In the code editor, at each join point shadow, gutter markers are present that reveal information about the advice. AJDT also provides for a visualization of the source code, but this feature has been superseded by other aspectual visualizations, the most recent of which is AspectMaps [9], [16]. AspectMaps is a visualization tool that shows where in the code aspects apply.…”

Section: Related Workmentioning

confidence: 99%

Aspectual source code analysis with GASR

Fabry

Roover

Jonckers

2013

2013 IEEE 13th International Working Conference on Source Code Analysis and Manipulation (SCAM)

Self Cite

View full text Add to dashboard Cite

Abstract-To be able to modularize crosscutting concerns, aspects introduce new programming language features, often in a new language, with a specific syntax. These new features lead to new needs for source code analysis tools, resulting in the requirement for a general-purpose aspectual source code analysis tool. Ignoring this requirement has led to a nontrivial duplication of effort in the aspect-oriented software development community. This is because all code analysis efforts that we are aware of have either built ad-hoc analysis tools or were performed manually. In this paper we present GASR: a source code analysis tool in the tradition of logic program querying that reasons over ASPECTJ source code. By hooking into the IDE plugins for ASPECTJ, GASR provides a library of predicates that can be used to query aspectual source code. We demonstrate the use of GASR by automating the recognition of a number of previously identified aspectual source code assumptions. We then detect assumption instances on two well-known case studies that were manually investigated in the earlier work. In addition to finding the already known aspect assumptions, GASR encounters assumption instances that were overlooked before.

show abstract

“…Therefore, the separation of aspects of the system at the software architecture level can be done in order to achieve the traceability between architectural design and coding phase seamlessly. Recently, numerous studies, whose results show the beneficial effects of an architectural approach, have been presented (AOSD [2] sites).…”

Section: Introductionmentioning

confidence: 99%

An Aspect-oriented Software Architecture Description Language AO-ADL Based on XYZ

Cao¹,

Rong²,

Zhang³

2014

IJHIT

View full text Add to dashboard Cite

Aspect-Oriented Programming (AOP) can resolve the code tangling problem in Object-Oriented Programming (OOP) via using the technology of separation of concerns. Software architecture is becoming an important part in the phase of software design, it has the ability of helping designer to handle the structure and the complexity of large software systems, and Aspect-Oriented Software Development (AOSD) is a new paradigm proposed to manage the complexity by crosscutting concerns in the whole software life-cycle. In order to adequately specify aspect-oriented design, Aspect-Oriented Architecture Description Languages (AO-ADL) are needed. XYZ/ADL is an architecture description language which is based on temporal logic language XYZ/E. XYZ/ADL separates computation and communication into two different architecture elementscomponent and connector, but lacks some appropriate support to represent these crosscutting behaviors. So, XYZ/ADL must be extended to resolve the problem above by adding a kind of new elements-Aspect and modifying the former component and connector. At last, we illustrate them on an example of the Hotel Management System (HMS) via using AO-ADL.

show abstract

AspectMaps: Extending Moose to visualize AOP software

Cited by 7 publications

References 18 publications

AspectJ code analysis and verification with GASR

AspectJ code analysis and verification with GASR

Aspectual source code analysis with GASR

An Aspect-oriented Software Architecture Description Language AO-ADL Based on XYZ

Contact Info

Product

Resources

About