200 likes | 346 Views
March 14, 2005 Chicago, IL http://dawis.informatik.uni-essen.de/events/AOM_AOSD2005/. Aspect-Oriented Modeling Workshop. Authors Pablo A. Amaya Barbosa Hubert Baumeister José Conejero Armin B. Cremers Carlos F. González Contreras Tzilla Elrad Robert France Geri Georg Aniruddha Gokhale
E N D
March 14, 2005 Chicago, IL http://dawis.informatik.uni-essen.de/events/AOM_AOSD2005/ Aspect-Oriented Modeling Workshop
Authors Pablo A. Amaya Barbosa Hubert Baumeister José Conejero Armin B. Cremers Carlos F. González Contreras Tzilla Elrad Robert France Geri Georg Aniruddha Gokhale Jeff Gray Yan Han Gregor Kiczales Alexander Knapp Günter Kniesel Nora Koch Mark Mahoney Juan Hernández Raghu Reddy Juan M. Murillo Rodriguez Roberto Rodríguez Maria Tkatchenko Gefei Zhang Introduction to Participants International Representation: Canada, China, Germany, Spain, and USA
Program Committee: Faisal Akkawi Mehmet Aksit Atef Bader Siobhán Clarke Sudipto Ghosh Robert France Stefan Hanenberg Ana Moreira Organizing Committee: Omar Aldawud Tzilla Elrad Jeff Gray Mohamed Kandé Jörg Kienzle Dominik Stein Introduction to Participants International Representation: Canada, Ireland, Portugal, Switzerland, Germany, Netherlands, and USA
Let’s Introduce Ourselves • Your name and affiliation • Research interests • Briefly • Any position you would like to state • Your goals in attending this workshop • Questions to be discussed
Workshop Background and Stated Goals • Focus topics of workshop: • Aspect-Oriented Modeling • Defining requirements on Aspect-Oriented Modeling • Verification and validation of aspect-oriented models • Composition of aspect-oriented models • Modeling of aspects at different stages of software development (requirements engineering, software architecture, design, implementation), e.g., what are the main elements at each individual stage and what are the aspects that crosscut? • Application of AOM to modeling notations that are not tied to the UML (e.g., domain-specific modeling languages, or Matlab models, etc.) • Aspect-Oriented UML • Identification of UML elements that can be used to model aspects • Identification of UML elements that can NOT be used to model aspects • UML profiles for AOSD • Aspect-oriented support in UML 2.0 • Extensions to UML for supporting AOSD • AOSD Method and Tool Support • Aspect-oriented software development methods • Using existing UML tools in AOSD life-cycles • New tools and extensions to existing tools to support aspect-oriented modeling • Aspect-Oriented Modeling Case Studies • Detailed examples that demonstrate how a certain concern can be modeled during software development throughout the different development stages • Results: • Pre-conference papers on website • Post-workshop web site • Presentations and Breakout summary • Photos: Stick around for the group photo before first break at 10:30am
Breakout Discussion Groups • For 3.5 hours, 3 groups discuss focused issues related to the workshop and report back to all participants • The size of each group should be similar • To reach consensus on the discussion topic areas: • Each workshop participant will suggest several issues to be discussed and write them on post-it notes • Related issues will be grouped together • Each group should have a scribe and presenter (perhaps the same person) • Try to stay focused and don’t get sidetracked on peripheral discussions (e.g., spending an hour defining the meaning of a specific word)
Summary • Heavyweight • M. Tkatchenko, G. Kiczales («Meta-Model Extension») • Lightweight • J. Conejero, J. Hernández, R. Rodríguez («Profile») • G. Zhang, H. Baumeister, N. Koch, A. Knapp («Sub-States») • Who cares! • Y. Han, G. Kniesel, A. Cremers («New Meta-Model») • Statechart • M. Mahoney, T. Elrad («Event Re-Interpretation») • Automated SoC • A. Gokhale, J. Gray («Tool») CoSMIC (C-SAW) • Dependability (Property based composition) • R. Reddy, R. France, G. Georg («Dependabilities») • Extending MDA Model • P. Amaya, C. González, J. Murillo («MDA»)
J. Conejero, J. Hernández, R. Rodríguez («Profile»)UML Profile Definition for Dealing with the Notification Aspect in Distributed Environments • Use of AOP to support Corba’s notification aspect • Event notification is scattered across all corba objects • UML profile • This separation can be carried at the implementation level • Can we cross-cut at the method level and not the class level. For example maybe a subset of the class methods crosscut and the whole.
M. Tkatchenko, G. Kiczales («Meta-Model Extension»)Uniform Support for Modeling Crosscutting Structure • AOSD as a mean for Connecting UML diagrams. • Change the uml meta-model to use the JPM • Build a cross-by-list to support the cross-cut structure • Questions • Obliviousness in models
Y. Han, G. Kniesel, A. Cremers («New Meta-Model»)Towards Visual AspectJ by a Meta Model and Modeling Notation • UML with Aspects • Lightweight extensions • Weak • Heavyweight extensions • Expensive, break tools • Proposal • Develop AspectJ metamodel • Simple Java Metamodel • A process to get us to a more general solution, but giving the state of the research this approach is believed to be more realistic • Do we design or program first?
G. Zhang, H. Baumeister, N. Koch, A. Knapp («Sub-States»)Aspect-Oriented Modeling of Access Control in Web Applications • UML based web engineering • State based
M. Mahoney, T. Elrad («Event Re-Interpretation»)Modeling Platform Specific Attributes of a System as Crosscutting Concerns using Aspect-Oriented Statecharts and Virtual Finite State Machines • Extend statechart model to support crosscutting concerns • A framework to weave core and aspect statechart by reinterpreting events
A. Gokhale, J. Gray («Tool»)An Integrated Aspect-Oriented Model-Driven Development Toolsuite for Distributed Real-Time and Embedded Systems • Automated SoC approach
R. Reddy, R. France, G. Georg («Dependabilities»)An Aspect Oriented Approach to Analyzing Dependability Features
G-1 • UML Extension Mechanisms • Lightweight • Profiles (stereotypes, tagged values, ..) • Simple extensions to UML • Heavyweight • Extending UML meta-model • Standardization issues • Notation and semantics
G-2 • Lifecycle issues • Refactoring • Reverse engineering • Early aspects • Traceability across the life cycle • How to model SW architecture with aspects • MDA
G3 • Tools • State based modeling • Verifications of models • Conflict management • Visualization of aspects