The Service Oriented Architecture (SOA) paradigm supports the assembly of atomic services to create applications that implement complex business processes. Assembly is accomplished by service orchestrations defined by SOA architects. The ADORE framework allows SOA architects to model complex orchestrations of services by composing models of smaller orchestrations involving subsets of services. The smaller orchestrations are called orchestration fragments and encapsulates new concerns. Adore is then used to weave fragments into existing application models. This demonstration illustrates how the ADORE framework can be used to model a SOA, using the Car Crash Crisis Management System (common case study used in a special issue of the TAOSD journal) as leading example.

• TAOSD Special Issue on Aspect Oriented Modeling:
  • Special issue editor: Jörg Kienzle, McGill University, Montreal, Canada
  • Rationale: A common case study to compare AOM approaches.
  • Call For Paper (www, Requirements.pdf)
  • Associated ADORE Case study (Joint Work with Robert France, CSU)
• AOSD'10 Demo track:
  • Submitted description (Sébastien Mosser & Mireille Blay-Fornarino)
  • Adore Realization
  • Associated slides (forum demonstration track)

• Step 1 & 2: We use the Emacs mode to navigate into processes (orchestration & fragments). We also execute several model transformation on the modelled entities (e.g.,xml exportation, graph generation)
• Step 3: Based on a simple composition unit description, we use the engine to weave several fragment into a base orchestration.
• Step 4: We identify a shared join point in a composition unit, and then perform an order-independent merge of involved entities before weaving the merged result into the base orchestration.
• Step 5: ADORE is endogenous and can then be used to enhance enhancement. We demonstrate this functionality by weaving a fragment on another fragment before weaving the enhanced result into the base orchestration.
• Step 6: We use ADORE to build a complete use case. To illustrate ADORE capabilities about conflict detection, we manually trigger the conditionIncompletness detection rule on the resulting model.
• Step 7: We use the ADORE logical back-end to match pointcuts for non-functional concerns. The composition algorithm is then triggered and build associated models (intermediate entities and final result).

The following videos capture¹⁾ the demonstration, step by step. The english subtitle channel contains additional information for each steps. It should be activated by default in the DailyMotion player (if not, click Menu and then subtitles/en).