2006 Proceeding- Conference Chair:
- Robert Filman
AOSD 2006 is the fifth annual conference on Aspect-Oriented Software Development (AOSD). The conference is the flagship event for papers, presentations and demonstrations in state-of-the-art in AOSD research and practice. The conference, held in Bonn Germany, March 20-24, 2006, attracts researchers and practitioners in this area from all over the world as well as a large body of research students. This volume comprises of the papers of the research track of the conference.Aspect-oriented software development provides systematic support for identification, modularization, representation and composition of crosscutting concerns. Interest in AOSD tools, techniques and methodologies is growing significantly in both industry and academia. Researchers are continuously pushing the boundaries of established AOSD techniques and practices while practitioners are actively building on this research to develop tools and platforms targeted at industry. The program of AOSD 2006 reflects this continuous evolution in AOSD research and practice. The research papers track includes 20 papers, each reviewed by at least three referees and chosen from the 96 submissions at the program committee meeting. We believe the result is an exciting research program that highlights a transition towards empirical studies, metrics and testing methods for evaluation and validation of aspect-oriented systems. Papers on the software process, concern modeling and concern semantics during analysis and design reflect the growing interest in the emerging set of Early Aspects approaches. A number of papers also focus on new types of language constructs and join point models hence depicting the trends in evolution of aspect-oriented programming approaches. Others discuss aspect composition and interaction issues, which are critical for maintaining consistency of aspect compositions. The program thus provides a wide-ranging perspective from evolution of established aspect-oriented languages and concepts to development of new mechanisms for aspect modeling, evaluation and validation.Research track papers present mature scientific and engineering activities that have been vetted by a rigorous refereeing process. But the conference is by no means just the papers of the research track: there is considerable experience in applying AO technologies and a great number of emerging ideas. The conference features an industry track for practitioners as well as birds of a feature (BoF) sessions and demonstrations of new AOSD tools and techniques. A panel discussion, chaired by Kevin Sullivan of University of Virginia and involving leading researchers and practitioners, is devoted to important open problems for future research in AOSD. The nine workshops and seven tutorials reflect a similar breadth of topics ranging from discussions on aspects in teaching and early development stages to language implementation and evolution issues through to design and implementation of specific aspect-oriented programming platforms.A critical element to assuring the continuing evolution of a field is nurturing new talent. With this in mind, the conference also includes two events: the student extravaganza, a poster event where students can present their emerging thesis work to suggestions from experts in the field, and the one-day spring school, where students new to the field can learn about the issues and open problems.The conference program also includes two exciting keynote speeches from distinguish figures. Professor Carliss Baldwin of Harvard Business School provides insights into the financial and economical implications of new designs and artifacts. Dr. Richard Gabriel of Sun Microsystems Laboratories, winner of the ACM/AAAI Allen Newell Award, highlights how ultra large scale systems challenge our existing perceptions of abstraction, modularity and encapsulation.
Proceeding Downloads
Towards supporting on-demand virtual remodularization using program graphs
OOP style requires programmers to organize their code according to objects (or nouns, using natural language as a metaphor), causing a program's actions (verbs) to become scattered during implementation. We define an Action-Oriented Identifier Graph (...
Expressing different conceptual models of join point selections in aspect-oriented design
When specifying pointcuts, i.e. join point selections, in Aspect-Oriented Software Development, developers have in different situations different conceptual models in mind. Aspect-oriented programming languages are usually capable to support only a ...
Semantic-based weaving of scenarios
The notion of aspect looks promising for handling cross-cutting concerns earlier in the software life-cycle, up from programming to design, analysis and even requirements. Support for aspects is thus now raising interest also at the modeling level, ...
Adding open modules to AspectJ
AspectJ does not provide a mechanism to hide implementation details from advice. As a result, aspects are tightly coupled to the implementation of the code they advise, while the behaviour of the base code is impossible to determine without analysing ...
Explicitly distributed AOP using AWED
Distribution-related concerns, such as data replication, often crosscut the business code of a distributed application. Currently such crosscutting concerns are frequently realized on top of distributed frameworks, such as EJBs, and initial AO support ...
A join point for loops in AspectJ
The current AspectJ join points represent locations in the code that are the interface of the Java objects. However, not all the "things that happen" happen at the interfaces. In particular, loops are a key place that could be advised for ...
Relationship aspects
The relationships between objects in object-oriented programs are as important as the objects themselves. Unfortunately, most object-oriented programming languages provide little support for such relationships, leaving the task of implementing them ...
Reflections on aspects and configurable protocols
The goals of aspect oriented software development (AOSD) and frameworks for configurable protocols (CPs) are similar in many respects. AOSD allows the specification of cross-cutting concerns called aspects as separate modules that are woven with the ...
Doxpects: aspects supporting XML transformation interfaces
In the web services environment software development can involve writing both object-oriented programs and XML transformations. This can be seen in the popular Web Services architecture. In this architecture, crosscutting concerns are often manifest as ...
Composing design patterns: a scalability study of aspect-oriented programming
Pattern composition has been shown as a challenge to applying design patterns in real software systems. One of the main problems is that multiple design patterns in a system are not limited to affect only the application concerns. They also crosscut ...
Optimization aspects in network simulation
A primary goal of AOSD in the context of systems software has been to permit improved modularity without significantly degrading performance. Optimizations represent important crosscutting concerns in this context but also a significant challenge due to ...
Reusable aspect-oriented implementations of concurrency patterns and mechanisms
In this paper, we present a collection of well-known high-level concurrency patterns and mechanisms, coded in AspectJ. We discuss benefits of these implementations relative to plain Java implementations of the same concerns. We detect benefits from ...
Visualisation-based tool support for the development of aspect-oriented programs
The development of aspect-oriented software requires tool support to make the aspect-oriented structures explicit and to assist programmers in understanding the overall source code, including aspects. Tools exist to meet this need, but they struggle ...
Presenting crosscutting structure with active models
When modifying or debugging a software system, among other tasks, developers must often understand and manipulate source code that crosscuts the system's structure. These tasks are made more difficult by limitations of the two approaches currently used ...
Using aspects to support the software process: XP over Eclipse
Usually, aspects enhance a software product by being composed - or woven - into it. Here, on the other hand, we use aspects to support the software development process itself. The underlying system, i.e., the system to which the aspects are woven, is ...
State-based incremental testing of aspect-oriented programs
Taking aspects as incremental modifications to their base classes, this paper presents an incremental approach to testing whether or not aspect-oriented programs and their base classes conform to their respective behavior models. We exploit a rigorous ...
A framework and tool supports for generating test inputs of AspectJ programs
Aspect-oriented software development is gaining popularity with the wider adoption of languages such as AspectJ. To reduce the manual effort of testing aspects in AspectJ programs, we have developed a framework, called Aspectra, that automates ...
AO challenge - implementing the ACID properties for transactional objects
This paper presents a challenge case study to the aspect-oriented community: ensuring the ACID properties (atomicity, consistency, isolation and durability) for transactional objects. We define a set of ten base aspects, each one providing a well-...
Detecting and resolving ambiguities caused by inter-dependent introductions
AOP languages are continuously evolving, for example (1) pointcut languages are becoming increasingly powerful with respect to the expressiveness of the pointcut language itself, (2) new program properties can be used as a selection criterion in ...
Symmetric composition of musical concerns
Aspect-oriented programming (AOP) describes a range of techniques that enable the separation, organisation and composition of various programming concerns that cannot be adequately encapsulated using the principal decomposition mechanisms available to ...
Recommendations
Acceptance Rates
| Year | Submitted | Accepted | Rate |
|---|---|---|---|
| MODULARITY '14 | 60 | 21 | 35% |
| AOSD '12 | 79 | 20 | 25% |
| Overall | 139 | 41 | 29% |