This document discusses the CHOReVOLUTION project, which aims to advance the state of the art in dynamic and secured service choreographies. The project has several research and innovation objectives: (1) developing modeling notations for choreographies, (2) automating synthesis of dynamic choreographies, (3) developing middleware to support heterogeneous entities, and (4) enabling secured choreographies across security domains. The objectives will be validated through industrial use cases in urban traffic coordination and smart mobility/tourism. The project will result in an integrated CHOReVOLUTION platform and development of an open source community around it.

1. CHOReVOLUTION
Technical Introduction
Massimo Tivoli
UDA
1st Review Meeting
Bruxelles,Feb. 11th, 2016

2. l We are in the Future Internet (FI) era
11 Feb. 2016 2
Setting the context (cont’d)
distributed computing environments
large number of available services
that can be composed
to meet user needs
Services will be increasingly active
software entities (peer-to-peer)

3. l Growth of innovative and revolutionary everyday-life scenarios within smart cities
11 Feb. 2016 3
Setting the context (cont’d)
the future smart mobility ecosystem scenario
A flexible, secure and distributed computing
environment is needed
different users
different environments different stakeholders
fully connected
fully connected
• Dynamism
• Heterogeneity
• New value added services
e.g., route guidance, speed advisory,
parking availability, POI suggestions

4. 11 Feb. 2016 4
Setting the context (cont’d)
l The ability to automatically compose and dynamically coordinate heterogeneous
computational resources abstracted as services is of paramount importance
dynamic evolution according to…
changing user preferences
changing environmental context
new business needs

5. 11 Feb. 2016 5
Setting the context
l Service composition approaches
l The trend is to build modern applications by reusing services
Orchestration (centralized) Choreography (fully distributed)
support for automation is needed
(time-to-market, correctness by construction, etc.)
CHOReVOLUTION is about aiding software producers to realize, deploy,
execute, and monitor choreography-based systems by reusing existing services
and things

6. CHOReOS core
Previous consortium experience:
EU FP7 CHOReOS project
CHOReOS IDRE overall structure
Choreography Modeler
Choreography Synthesis Processor
Choreography Middleware
Governance and V&V
Framework
Design- and Run-Time
Analysis Framework
Service Base &
Discovery
Choreography Goals &
Requirements
Specification
• As acknowledgedby the EU commission,CHOReOS results and related
experiments have been found promising
• Two recommendationsrelated to boostits application in industrial contexts
− Enhancing the maturity level of the core tools
− Enabling the production of dynamic and secured choreographies
11 Feb. 2016 4

7. 11 Feb. 2016 7
Towards CHOReVOLUTION
l Addressing the previous recommendations is a key driver of the
follow-up project
l Bringing the development and enactment of dynamic and
secured choreographies at the TRL required by industries
CHOReOS core
Choreography Modeler
Choreography Synthesis Processor
Choreography Middleware
Governance and V&V
Framework
Design- and Run-Time
Analysis Framework
Service Base &
Discovery
Choreography Goals &
Requirements
Specification

8. 11 Feb. 2016 8
CHOReVOLUTION approach at a glance
Services
Security
Domain
Services
Security
Domain
Things
CHOReVOLUTION
Synthesis
Cloud
Infrastructure
Choreography Model
Choreography
Modeler
Business
Goal
CHOReVOLUTION
Enactment
Engine
• Coordination and evolution (Coordination Delegates)
• Adaptation (Adapters)
• Security Filtering (Security Filters)
• Heterogeneous
Communication (Binding Components)
Choreography-enabling software artefacts

9. 11 Feb. 2016 9
CHOReVOLUTION R&I objectives
l They identify the challenges to be faced to realize dynamic and
secured choreographies via reuse and distributed coordination
of services and things
− OB1-4 concern Research actions
− OB5-7 concern Innovation actions

10. l Advance w.r.t. CHOReOS
− an integrated, yet flexible, modelling framework
− expressing several dimensions of choreography-based systems
11 Feb. 2016 10
OB1: modeling notations
BPMN2 Choreography Diagrams plus…
…additional and intermediate models
Service behaviour & identity
Service-role interface mappings
Choreography variations
• interface
• interaction protocol
• QoS & identity attributes
Security requirements
CDs, Adapters, Security Filters,
and BCs models
Choreography Enactment,
Deployment, and Execution
models variability points according
to specified context conditions
Synthesized models Specified modelsSpecified models
adaptation
dynamic evolution
security
service selection and reuse
automated reasoning (e.g., synthesis)

11. 11 Feb. 2016 11
OB2: automated synthesis of dynamic
choreographies (cont’d)
l Advance w.r.t. CHOReOS
− automated synthesis of an enhanced coordination logic addressing
choreography evolution (changes in the specification and/or context)
S Business Logic Layer
(Services)
Enhanced BPMN2
choreography spec.
(OB1 models)
Automated synthesis techniques
for the production of
choreography-enabling software
artefacts:
• CDs – distributed coord. & evolution
CD Protocol Coordination Layer (CDs)
S1 S2
Enhanced BPMN2
choreography spec.
(OB1 models)
CD1 CD2
What about
mismatching
interfaces?

12. 11 Feb. 2016 12
OB2: automated synthesis of dynamic
choreographies
l Advance w.r.t. CHOReOS
− automated synthesis of an enhanced coordination logic addressing
choreography evolution (changes in the specification and/or context)
− and protocol heterogeneity at the application level (mismatching interfaces)
S Business Logic Layer
(Services)
Enhanced BPMN2
choreography spec.
(OB1 models)
Automated synthesis techniques
for the production of
choreography-enabling software
artefacts:
• CDs – distributed coord. & evolution
• Adapters – mismatching interfaces adaptation
CD Protocol Coordination Layer (CDs)
S1 S2
Enhanced BPMN2
choreography spec.
(OB1 models)
CD1 CD2
A Protocol Adaptation Layer (Adapters)
A1 A2
What about
different styles of
interaction? E.g.,
SOAP vs REST

13. 11 Feb. 2016 13
OB3: middleware
l Advance w.r.t. CHOReOS
− targeting choreographies that integrate both business services and Things
− dealing with entities with greatly varying characteristics and employing different
styles of interaction (e.g., message passing vs event-based and data sharing)
− take into account also non-functional properties, related to QoS
S Business Logic Layer
(Services)
Enhanced BPMN2
choreography spec.
(OB1 models)
Production of other
choreography-enabling software
artefacts:
• BCs – dealing with heterogeneous
middleware-level protocols
CD Protocol Coordination Layer (CDs)
S1 S2
Enhanced BPMN2
choreography spec.
(OB1 models)
CD1 CD2
A Protocol Adaptation Layer (Adapters)
A1 A2
BC Middleware Layer (Binding Components)
BC1 BC2
What about
security?
E.g., different
authentication &
authorization
attributes

14. 11 Feb. 2016 14
OB4: secured choreographies
l Advance w.r.t. CHOReOS
− dealing different security domains governed by different authorities using
different identity attributes for their access control policies
− cross-boundaries authentication and authorization
Enhanced BPMN2
choreography spec.
(OB1 models)
Production of further
choreography-enabling software
artefacts:
• Security Filters – enforcing of
security-centric policies
S1 S2
Enhanced BPMN2
choreography spec.
(OB1 models)
S Business Logic Layer
(Services)
CD Protocol Coordination Layer (CDs)
A Protocol Adaptation Layer (Adapters)
BC Middleware Layer (Binding Components)
SF Protocol Security Layer
(Security Filters)
CD1 CD2
A1 A2
BC1 BC2
SF1 SF2

15. 11 Feb. 2016 15
OB5: validation through
industrial use cases (cont’d)
l Urban traffic coordination
− SOTA: traffic optimization based on road traffic data collection and
centralized analysis of the collected data
• suitable for long term traffic management, e.g., traffic prediction
• not suitable for dynamically adapting to emergent traffic situations, e.g.,
accidents blocking some routes
− beyond SOTA: cooperative traffic management systems able to coordinate
all components in a fully distributed way
− main subjects of validation
• traffic management choreography patterns
• security to protect the deployed elements
• heterogeneity, e.g., different styles of interaction

16. 11 Feb. 2016 16
OB5: validation through
industrial use cases
l Smart Mobility and Tourism
− SOTA: solutions to improve the travelling experience of people and their capabilities to access
and use various types of services when visiting our cities and regions
• planning of people mobility
• provision of real-time, updated information during travelling
− beyond SOTA: support for dynamic and context-aware travellers interaction with a number of
resources connected to the travel
• e.g., hotel information and booking, access to and payment for touristic sites, participation to
events, use of public services, etc.
− main subjects of validation (area of Porto Antico – Genova – Italy)
• provision of solutions for designing and executing domain-specific choreography patterns
• dynamic adaptation to the changing mobility and user environment
• security aspects to create a trusted environment
• enhancement of the user experience

17. 11 Feb. 2016 17
OB6: CHOReVOLUTION
Integrated Platform
l As a tool-box of integrated frontend
and backendsoftware components
l Frontend
− a CHOReVOLUTION-specific
customization ofthe Eclipse
platform
− an integrated Web application
l Backend
− a set of REST services/APIs
defining well-integrated
provided/required interfaces
− they agree on the I/O data to
be exchanged

18. 11 Feb. 2016 18
OB7: community of users and market take-up
l Enabling the take-up and further enhancement by third-party
developers
− CHOReVOLUTION as an open source project
− FISSi (http://www.ow2.org/bin/view/Future_Internet)
l Promote the growth of a community of users
− OSS best practices
− collaborative development tools
− communication and branding services
− releasing an early version of the platform

19. 11 Feb. 2016 19
WPs vs R&I objectives

20. Thank you