Levels of Independence in AspectOriented Modeling

1
Levels of Independence in Aspect-Oriented
Modeling

• Workshop on Model-driven Approaches to Middleware
  Applications DevelopmentJune 17, 2003
• Jeff Gray, Yuehua Lin, Jing Zhanggray (at)
  cis.uab.eduhttp//www.gray-area.org

This research is funded by DARPA/IXO, under the
PCES program.
2
Shameless Plug for CFPs

• Workshop on Domain-Specific Visual Languages
• September 22, 2003 (GPCE Conference - Erfurt,
  Germany)
• Papers due         30 June
• http//www.cis.uab.edu/info/GPCE-DSVL3/
• 3rd OOPSLA Workshop on Domain-Specific
  Modeling(Domain-Driven Development Track)
• October 26, 2003 (OOPSLA - Anaheim, CA)
• Papers due         15 August
• http//www.cis.uab.edu/info/OOPSLA2003-DSM

3
Shameless Plug for CFPs

• Aspect-Oriented Modeling Workshop
• October 20-24, 2003
• UML Conference (San Francisco, CA)
• Papers due         25 August
• http//www.cs.iit.edu/oaldawud/AOM/index.htm

4
Types of Transformation Translation

• Horizontal transformation
• Transformation within the same representation
  level of abstraction
• e.g., MDA PIM-gtPSM, model weaving (VEST, C-SAW),
  code refactoring
• Vertical translation
• Typically, translation, or synthesis, between
  layers of abstraction
• e.g., MIC interpreters, CASE-tool scripting and
  reverse engineering, PSM-gtPSI

Current Focus Vertical transformation higher
level models transform existing code base
(rather than synthesize new code orconfiguration
information)
5
Motivating Problem Crossccuting Constraints in
Real-Time/Embedded Models
Changeability???

• Base models become constrained to capture a
  particular design

A
B
F
c
d
e
B
B
c
d
e
c
d
e
6

• Small changes in requirements entail large
  changes in the structure and configuration

Sussman, 1999 Gerald Jay Sussman, Robust
Design through Diversity, DARPA Amorphous
Computing Workshop, 1999..
7
Motivation

• Problems
• Difficult to specify and manage cross-cutting
  concerns (e.g., constraints) in model-based
  systems
• Lack of tool support for automatically weaving
  constraints into models
• New Lack of a core weaving engine that is
  independent of modeling environments.

8
Previous Work (Solution)
9
Two levels of weaving
Aspect Model Weaving
Aspect Code Weaving/ Program Transformation
10
Levels of Independence in Model Weaving

• Domain independence
• GME meta-models and weaver strategies determine
  domain of discourse
• Platform independence
• GME interpreters and weaver strategies map to
  platform specific synthesis
• Tool independence (new)
• Separation of core weaving engine with
  tool-specific adapters

11
Tool Independence

• Requires an exposed API for accessing internal
  model data structures
• Tool-specific adapters written for each new
  supported tool

Rose
GME
Cadena
MetaEdit
12
Adaptive Core Weaving Engine
13
Not unlike AspectJ AJDT
AJDT
14
More Info

• Representative Publications
• Comm. of the ACM, October 2001, Handling
  Crosscutting Constraints in Domain-Specific
  Modeling
• GPCE 2003 (forthcoming), An Approach for
  Supporting Aspect-Oriented Domain Modeling
• AOSD Book Chapter (forthcoming), Two-Level
  Weaving to Support Evolution of Model-Based
  Software
• Demo
• Prepared to give a very brief demo of
• GME
• Example weaving of processor assignment
  constraints into an avionics system model

15
Demo

• Very brief intro to GME
• Entire course on this, so very superficial demo
• Weaving of constraints into GME models
• Ill have to talk fast

16
Model Integrated Computing (MIC)

• Grew out of over 14 years of research on
  computer-
• based systems in aerospace, instrumentation,
• manufacturing and robotics.
• Common challenges
• Software and environment are inextricably
• combined
• Need for adaptability to changing environment
• and end-user needs
• Complex, heterogeneous applications
• Stringent reliability and dependability
  requirements

17
Domain-Specific Modeling at ISISModel
Integrated Computing

• The Generic Modeling Environment (GME) is a
  domain-specific modeling tool (gt20-person years)
• It can be utilized in many different domains by
  providing a meta-level paradigm description
• Paradigm describes all of the entities of the
  domain, as well as valid relationships
• Freely available
• http//www.isis.vanderbilt.edu
• See November 2001 issue of IEEE Computer

18
Meta-Modeling Framework
META-MODEL
Meta-Model of Stateflow using UML/OCL as
meta-modeling language.
DOMAIN-MODEL
Model instance of Stateflow

19
Model Integrated Computing
20
GME
21
MICApplications