Difference between revisions of "CarLogistics"
Bucchiarone (talk | contribs) |
Bucchiarone (talk | contribs) |
||
| Line 8: | Line 8: | ||
== Basic technology == | == Basic technology == | ||
| − | + | Adaptive and context-aware service-based systems are modeled by defining a set of entities. Each of them features its own business process and its provided services. | |
| − | + | Business processes are modeled as Adaptable Pervasive Flows (APFs) [1], an extension of traditional workflow language (e.g., BPEL) which makes them more suitable for | |
| + | adaptation and execution in dynamic environments. In addition to the classical workflow language constructs, APFs add the possibility to model abstract activities. An abstract activity is defined at design time in terms of the goal it needs to achieve and is dynamically refined at run-time into an executable process, considering the set of available services, the current execution context and its goal. | ||
| + | Each entity can provide a set of services to the other entities. We consider services to be stateful: they can ex- pose complex protocols (e.g., BPEL) combining traditional service actions (i. e., sending/receiving messages to/from services) with control flow structures (e.g. switch, while, pick). The application context is modeled as a set of context properties, each describing a particular aspect of an application domain. Every context property is modelled with a context property diagram, which is a state transition system capturing all possible property values and value changes. Each transition is labeled with a corresponding context event. A context property may evolve as an effect of service invocations, which corresponds to the normal behavior of the domain, but also as a result of volatile exogenous changes. | ||
== How to install == | == How to install == | ||
| Line 20: | Line 22: | ||
(i) run the CLS and simulate the execution and adaptation of each business process attached to each entity and | (i) run the CLS and simulate the execution and adaptation of each business process attached to each entity and | ||
| − | |||
(ii) view the different adaptation strategies supported by our framework and how they are used during the scenario execution. | (ii) view the different adaptation strategies supported by our framework and how they are used during the scenario execution. | ||
The goal of this demonstrator is to show the novel concepts and advantages of the CAptEvo Framework when applied to a real and complex pervasive system. | The goal of this demonstrator is to show the novel concepts and advantages of the CAptEvo Framework when applied to a real and complex pervasive system. | ||
| + | |||
| + | == Headline text == | ||
== Download == | == Download == | ||
Revision as of 12:32, 20 April 2012
This page gives a template for describing artifacts related to Service-Based Applications. Please create a page for each artifact according to this template
Possible artifacts could be: service interfaces, service-based process descriptions, service ontologies, formal specifications and models, QoS/SLA descriptions and data, service implementations, test suites, execution traces, monitoring data, etc.
Contents
Description
Brief description of the artifact and the goal of the artifact
Basic technology
Adaptive and context-aware service-based systems are modeled by defining a set of entities. Each of them features its own business process and its provided services.
Business processes are modeled as Adaptable Pervasive Flows (APFs) [1], an extension of traditional workflow language (e.g., BPEL) which makes them more suitable for
adaptation and execution in dynamic environments. In addition to the classical workflow language constructs, APFs add the possibility to model abstract activities. An abstract activity is defined at design time in terms of the goal it needs to achieve and is dynamically refined at run-time into an executable process, considering the set of available services, the current execution context and its goal.
Each entity can provide a set of services to the other entities. We consider services to be stateful: they can ex- pose complex protocols (e.g., BPEL) combining traditional service actions (i. e., sending/receiving messages to/from services) with control flow structures (e.g. switch, while, pick). The application context is modeled as a set of context properties, each describing a particular aspect of an application domain. Every context property is modelled with a context property diagram, which is a state transition system capturing all possible property values and value changes. Each transition is labeled with a corresponding context event. A context property may evolve as an effect of service invocations, which corresponds to the normal behavior of the domain, but also as a result of volatile exogenous changes.
How to install
If applicable, please give a clear procedure for installing the artifact
How to use
We have created a visualization environment enabling interaction between the framework and the user and simulating execution and adaptation of business processes in our case study. In particular, it can:
(i) run the CLS and simulate the execution and adaptation of each business process attached to each entity and (ii) view the different adaptation strategies supported by our framework and how they are used during the scenario execution.
The goal of this demonstrator is to show the novel concepts and advantages of the CAptEvo Framework when applied to a real and complex pervasive system.
Headline text
Download
All the artifacts of the Car Logistics Scenario (CLS) can be downloaded from: http://www.astroproject.org/downloads/artifacts.zip. The specification of the CLS we used to evaluate our approach is composed by 29 entities, 69 services and 40 context properties. Moreover to see the ASTRO-CAptEvo framework in action, one can download the complete demo and a video of a live demonstration from: http://www.astroproject.org/captevo.
Additional info
Link to papers or technical reports that could be useful to understand and use the artifact
