Overview
Foundations
Examples / Case Study
- PicWeb
- MDD4DRES
The Car Crash Crisis Management System
The associated paper is accepted for publication in the AOM special issue of the TAOSD journal. The final draft of the paper (submited to the editor) is available here: mosser-blay-france.pdf
Working Documents used as inputs
Approach overview
As Adore handles business processes, we base our case study on the CCCMS textual use cases, as defined in section 4.2 of the requirement document.
- First of all, we represent each textual use case main success scenario as an orchestration of services1).
- Then, we define each use case extension as an orchestration fragment, and express the composition rules which build the complete use case.
- We also realized 3 non-functional concerns as fragments, and use logical inference to weave them onto base scenario.
A demonstration (based on a sub-part of this case study) was accepted at AOSD'10. Associated material (including video screencasts) is available here: AOSD'10 Demonstration
Realization
We realize 2 CCCMS version. The first one only contains business-driven extensions (main success scenario & extensions). The second one include non-functional properties (security, persistence & log).
-
- User-given models: 12 processes, 24 fragments.
- Algorithms: 23 weave, 5 merge, 2422 atomic actions executed
-
- User-given models: 12 processes, 29 fragments (= 24+5).
- Algorithms: 86 weave, 38 merge, 10838 atomic actions executed (= 2422+8416)
Related Data
- CCCMS realization using ADORE, @Google Code
- Quantitative Analysis:
- Processed Data (both systems)
- Complete Set of metrics (business-only)
