UML provides several notations to model the static and dynamic behavior of a software system. Separation of concerns is essential for software designers, and those concerns that have a crosscutting impact present many difficulties for software development. Since these difficulties are present throughout the development lifecycle, they must be addressed across its entirety. Once an initial decomposition of the problem identifies software components and the corresponding aspectual properties that cut through these components, we would like to be able to express and model this initial decomposition in a formal way, and carry it to the next phase of the development life cycle. The creation of UML models factored into separated concerns with rules or advice on how they interrelate can be applied even when the software ultimately created is not programmed in separate aspects or concerns. Thus, existing UML tools could be used for aspect oriented software development as well.

The goal of the workshop is to bring together the communities of aspect-oriented software development and UML to discuss the state of research and practice when handling various aspects of software at both programming and modeling levels, and to prepare together an agenda for future research in this new field.

Position papers & Workshop Agenda