This document proposes an architecture for enabling reusable and adaptive modeling, provisioning, and execution of BPEL processes. The architecture supports collaborative, dynamic, and complex systems through reusable process fragments and abstract activities that can be flexibly modeled and executed. It consists of a modeling environment to create and manage process models using fragments, and a runtime environment containing an execution engine, integration layer, and persistence layer to instantiate and execute processes by injecting fragments at runtime. The architecture was evaluated through a use case of modeling and executing payment processes across different transportation systems.

1. ENABLING REUSABLE AND ADAPTIVE
MODELING,
PROVISIONING & EXECUTION OF BPEL
PROCESSES
Done by Ahmad Taweel
1

2. Outline
Introduction
 Motivation
 Life cycle
 Architecture
 Evaluation & Implementation
 Conclusion
2

3. Introduction
 The service oriented computing paradigm
 Development & operation of complex distributed systems
 Application in different areas of the system
 Collaborative, Dynamic, and Complex (CDC) systems
was proposed
 Adapting with respect to different triggers
 Modeling, Provisioning and Execution aspects
3

4. Outline
 Introduction
Motivation
 Life cycle
 Architecture
 Evaluation & Implementation
 Conclusion
4

5. Motivation
 Collective Adaptive Systems (CAS) as a type of
CDC systems, CAS consists of
 Heterogeneous entities
 High influence on the behavior of the system
 Modeling, execution, and adaptation of CAS entities
and their interactions
5

6. Outline
 Introduction
 Motivation
Life cycle
 Architecture
 Evaluation & Implementation
 Conclusion
6

7. Life cycle of the process in the CDC
system
CDC system life cycle
7

8. Outline
 Introduction
 Motivation
 Life cycle
Architecture
 Evaluation & Implementation
 Conclusion
8

9. Architecture
Modeling
Environment
Runtime
Environment
9

10. Modeling
Environment
Process
Modeler
Fragment
Repository
10

11.  Process Modeler
 Create process models
 Manage processes
 Support operations on running process instance
 Injection of fragments
 Support the reusability
 Fragment Repository
 Storage of process fragments
 Retrieval of process fragments
11

12. Runtime
Environment
CDC
Execution
Engine
Integration
Layer
Workflow
Engine API
Runtime Layer
Persistence
Layer
12

13.  The Integration Layer:
 Exposes the engine-internal functionality
 Provides the communication features
 The Workflow Engine API: as an intermediate layer
 The Runtime Layer: provides the core functionality
 Instantiate and execute a process model
 Re-executing parts of a running process instance
 Realize the Injection Framework
 The Persistence Layer: provides database
13

14. Outline
 Introduction
 Motivation
 Life cycle
 Architecture
Evaluation & Implementation
 Conclusion
14

15. Urban Mobility
System
Passenger
Trip Booking
System
Transportation
Mean
Systems
Payment
Gateway 15

16.  Payment Gateway
 Concrete
 Different payment methods
 Abstract the definition of the payment process
 Abstract activity
 conductPayment
16

17. Activity Executed
Activity Executing
Activity Skipped
17

18. Outline
 Introduction
 Motivation
 Life cycle
 Architecture
 Evaluation & Implementation
Conclusion
18

19. Conclusion (1/2)
 Collaborative, Dynamic, and Complex (CDC)
systems
 Application based on complex services
 Abstract activities at the design level
• Flexibility at modeling level
• Reusability across designed models
19

20. Conclusion (2/2)
 Modeling and Runtime environments
 Deployment of reusable and adaptive processes
 Execution of reusable and adaptive processes
 Abstract constructs in executable process models
 Specify process fragment
20

21. Thank You
21