Detecting architecture instabilities with concern traces: An exploratory study

Figueiredo, Eduardo; Galvão, Ismênia; Khan, Safoora Shakil; Garcia, Alessandro; Sant’Anna, Cláudio; Pimentel, Afonso; Medeiros, Ana Luisa; Fernandes, Lyrene; Batista, Thaís; Ribeiro, Rita A.; Broek, Pim van den; Akşit, Mehmet; Zschaler, Steffen; Moreira, Ana

doi:10.1109/wicsa.2009.5290815

Cited by 11 publications

(11 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…3.1.1 in [10]) and run the experiments on the HealthWatcher [27] and MobileMedia [28] systems. We implemented analysis rules for all assumptions that can be sufficiently formalized, or approximated by a heuristic.…”

Section: Detecting Aspect Assumptions With Gasrmentioning

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)

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

Section: Detecting Aspect Assumptions With Gasrmentioning

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)

View full text Add to dashboard Cite

show abstract

“…Two modeling languages have been defined upon this meta-model: (i) AOPML [81] -an extension of the BPM notation to describe processes, improve modularity and make processes easier to understand and reuse [82]; and (ii) AOV-graph [83] -an extension of V-graph (a goal-oriented language used to model early aspects [84]) to represent the relationships among requirements. The AOVgraph has been used in empirical studies with the Health Watcher and Mobile Media benchmarks [85], [86], [87].…”

Section: E Early Aspectsmentioning

confidence: 99%

“…At this moment, MobileMedia encompasses eight subsequent releases that support the execution of studies of AO SPL maintainability. In addition, MobileMedia has already been successfully used in a number of assessments of AOSD [23], [86].…”

Section: B Assessment Of Aosd-br Research Impactmentioning

confidence: 99%

The AOSD Research Community in Brazil and Its Crosscutting Impact

Chávez

Kulesza

Soares

et al. 2011

2011 25th Brazilian Symposium on Software Engineering

Self Cite

View full text Add to dashboard Cite

In this paper, we present the birth, growth, and maturation of Aspect-Oriented Software Development (AOSD) research over the last years, with emphasis on the Brazilian AOSD community and its research contributions. These research contributions are illustrated from different perspectives: (i) an overview of the research work developed by our community in several prominent software engineering areas; (ii) a historical chronology of the community; and (iii) the growth, impact and quality of research outcomes.

show abstract

“…Data was collected for Version 10 of HealthWatcher [14]. [8,10] is an AspectJ application refactored and evolved from an initial object-oriented solution for the management of pictures in a mobile-phone context. It has been evolved to provide support for other types of media, using primarily static crosscutting to encapsulate the logic related to different types of media or target devices.…”

Section: Project Selectionmentioning

confidence: 99%

Aspect assumptions

Zschaler

Rashid

2011

Proceedings of the Tenth International Conference on Aspect-Oriented Software Development

Self Cite

View full text Add to dashboard Cite

Aspect developers constantly make a range of assumptions about the context in which their aspects will be deployed; ranging from assumptions about other aspects deployed to assumptions about semantic properties of the base and the joinpoints at which an aspect is woven. Although it has been acknowledged that such assumptions need to be made explicit to validate aspects in the face of evolution (both of aspects and the base) and reuse as well as to mitigate the fragile-pointcut problem, so far no study exists that identifies the types of assumptions aspect developers make. In this paper, we present a retrospective study of three medium-sized open-source AspectJ projects and assumptions identified in these. This leads to an initial classification of assumptions that can form the basis for further research into how best to support each type of assumption.

show abstract

Detecting architecture instabilities with concern traces: An exploratory study

Abstract: Abstract

Cited by 11 publications

References 13 publications

Aspectual source code analysis with GASR

Aspectual source code analysis with GASR

The AOSD Research Community in Brazil and Its Crosscutting Impact

Aspect assumptions

Contact Info

Product

Resources

About