2019
DOI: 10.1007/978-3-030-21290-2_29
|View full text |Cite
|
Sign up to set email alerts
|

Generation and Transformation of Compliant Process Collaboration Models to BPMN

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Year Published

2020
2020
2021
2021

Publication Types

Select...
1
1

Relationship

1
1

Authors

Journals

citations
Cited by 2 publications
(3 citation statements)
references
References 18 publications
0
3
0
Order By: Relevance
“…Finally, the Compliance Management Service serves as a pluggable middleware that may be used to integrate other process execution engines. For testing the framework, we edited choreography and collaboration models in BPMN 2.0 using Signavio 4 and exported them to the C3Pro framework as XML files. Examples are extended with GCR, which are then decomposed into derived assertions using Alg.…”
Section: Implementation and Discussionmentioning
confidence: 99%
See 1 more Smart Citation
“…Finally, the Compliance Management Service serves as a pluggable middleware that may be used to integrate other process execution engines. For testing the framework, we edited choreography and collaboration models in BPMN 2.0 using Signavio 4 and exported them to the C3Pro framework as XML files. Examples are extended with GCR, which are then decomposed into derived assertions using Alg.…”
Section: Implementation and Discussionmentioning
confidence: 99%
“…The interactions of a single partner are described in a public model. The public model thus serves as public (restricted) view on the private model of the partner which "describes the internal logic of a partner including its private activities and interactions" [4]. In this paper, we assume that the choreography y is sound, i.e., structural and behavioral compatibility between public models and consistency between public and private models are given [7].…”
Section: Fundamentals and Transitivity Theoremmentioning
confidence: 99%
“…In contrast, compliance checking for collaborative processes is still sparse in the literature. Few works like [2], [3] that address the compliance checking of collaborative processes still lack full support to address the different phases of the process life cycles, i.e., control, data, time, and resource perspectives at both designs and run time [1]. Considering this, we justify the need to support the automated compliance checking of collaborative processes with varied regulatory requirements at all phases of the process life cycle at both design and runtime.…”
Section: Introductionmentioning
confidence: 99%