Welcome!
To use the personalized features of this site, please log in or register.
If you have forgotten your username or password, we can help.
|
 |
Towards Using Reo for Compliance-Aware Business Process Modeling
| |
|
| Communications in Computer and Information Science |
Leveraging Applications of Formal Methods, Verification and Validation Third International Symposium, ISoLA 2008, Porto Sani, Greece, October 13-15, 2008. Proceedings
|
| 10.1007/978-3-540-88479-8_9 |
| Tiziana Margaria and Bernhard Steffen |
Towards Using Reo for Compliance-Aware Business Process Modeling
Farhad Arbab3 , Natallia Kokash3 and Sun Meng3 
| (3) |
CWI, Kruislaan 413, Amsterdam, The Netherlands |
Abstract
Business process modeling and implementation of process supporting infrastructures are two challenging tasks that are not
fully aligned. On the one hand, languages such as Business Process Modeling Notation (BPMN) exist to capture business processes
at the level of domain analysis. On the other hand, programming paradigms and technologies such as Service-Oriented Computing
(SOC) and web services have emerged to simplify the development of distributed web systems that underly business processes.
BPMN is the most recognized language for specifying process workflows at the early design steps. However, it is rather declarative
and may lead to the executable models which are incomplete or semantically erroneous. Therefore, an approach for expressing
and analyzing BPMN models in a formal setting is required. In this paper we describe how BPMN diagrams can be represented
by means of a semantically precise channel-based coordination language called Reo which admits formal analysis using model
checking and bisimulation techniques. Moreover, since additional requirements may come from various regulatory/legislative
documents, we discuss the opportunities offered by Reo and its mathematical abstractions for expressing process-related constraints
such as Quality of Service (QoS) or time-aware conditions on process states.
Fulltext Preview (Small, Large)
 References secured to subscribers.
|
|
|
|
|
|