This workshop is dedicated to applying UML to model Aspect-Oriented Systems and Aspect-Oriented approaches to modeling with UML. Suggested issues are: How can we apply UML artifacts to AOSD? Are the existing notations and modeling techniques of UML sufficient to model aspects, or do we need to extend UML to support AOSD? Is UML the appropriate modeling language on which to base modeling for AOSD? Is UML capable of expressing "Core" components and "Aspectual" components as well as associations linking them together? If we have to extend the UML, are the extension mechanisms provided by UML adequate? What could then be a UML profile for AOSD? On the contrary, would it be possible to rely only on a restricted subset of the UML for AOSD? What would be this subset?

We are interested in submissions on all topics related to aspect-oriented software development with UML, including, but not limited to:

• Extending or "tailoring" UML to fit the needs of AOSD systems
• Architectural descriptions using UML and AOSD
• Aspect-oriented behavioral modeling with UML
• Is a UML profile the best way to encapsulate extensions to the UML for AOSD?
• UML templates for AOSD.
• Modeling intra-object and inter-object crosscutting concerns
• Verification and validation of aspect-oriented models
• Using existing UML tools in AOSD life-cycles
• Methodological issues related to the application of the UML in AOSD
• Tool support for modeling AOSD artifacts with the UML
• How can we relate the UML, AOSD, and the IEEE recommended practice on architectural modeling (which promotes a multi-dimensional view of a system under construction)
• Composition of aspect-oriented models

Position papers & Workshop Agenda