![]() |
|
|||||||||
|
Workshop Results: Poster![]() (click to enlarge) Workshop ProgramNow Available
Early aspects are crosscutting concerns in the early life cycle phases of software development, including the requirements engineering, domain analysis and architecture design activities. In previous editions of this workshop, held in conjunction with AOSD 2002-2005 and OOPSLA 2004, we looked at different techniques, tools and languages that support early aspects (visit http://www.early-aspects.net/ for more information). This time we are going to discuss the results of early aspects techniques, tools and languages applied to the same system: the famous Java Pet Store application. Looking at the same concrete example shall provide basis for comparison and promote collaborations and cross-fertilization of ideas to improve the various techniques, tools and languages. For complete information, visit the Call For Papers. Background: Why Early Aspects?Early aspects cannot be localized and tend to be scattered over multiple early life cycle modules. This reduces the modularity of the artifacts in the early life cycle. Conventional aspect-oriented software development approaches have mainly focused on identifying aspects at the programming level and less attention has been taken on the impact of crosscutting concerns at the early phases of the software process. The early software development phases actually set the early design decisions and have a large impact on the whole system. Therefore, coping with aspects at the early life cycle phases as such is a primary issue.Main Theme: The Devil is In the DetailsAs the world of Early Aspects grows, more and more EA techniques arise. At previous EA workshops we have noticed that there are many similar techniques, and many highly related terms. However, because of subtle differences in what is meant by each term, and in the underlying assumptions of each technique, it is difficult to move forward with EA research with a confident understanding of what has gone before. In this workshop we will provide a basis for exposure of EA techniques, and provide a unique opportunity for observation and comparison of both the application of those techniques, and the techniques themselves.Workshop GoalsThis case study exercise will be highly participatory, instructive, and fruitful. It will afford participants an intimate and immediate practical understanding of the approaches in EA today. Study topic participants may even gather enough data to report on preliminary results or hypotheses in an independent publication. This means that the workshop not only becomes a place for convergence of ideas, but also for conducting of new and uniquely possible research.
|