Proceedings of the 5th ACM International Conference on Distributed Event-Based System 2011
DOI: 10.1145/2002259.2002270
|View full text |Cite
|
Sign up to set email alerts
|

Business artifacts with guard-stage-milestone lifecycles

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
18
0

Year Published

2013
2013
2021
2021

Publication Types

Select...
5
3

Relationship

0
8

Authors

Journals

citations
Cited by 140 publications
(28 citation statements)
references
References 11 publications
0
18
0
Order By: Relevance
“…In [12], [13]. Works in [14] have introduced the Business Entities and Business Entity Definition Language (BEDL), an XML-based language, for modeling Business Artifact processes.…”
Section: Prototypingmentioning
confidence: 99%
“…In [12], [13]. Works in [14] have introduced the Business Entities and Business Entity Definition Language (BEDL), an XML-based language, for modeling Business Artifact processes.…”
Section: Prototypingmentioning
confidence: 99%
“…In this section, we will review and analyze typical examples of such attempts, choosing the ones that have included relatively formal definitions of the process model. More specifically, we consider the following examples of non-traditional process modeling techniques: (a) declarative process modeling that includes the notion of state [20], (b) artifact-centered process modeling [21], [22], (c) data-driven process modeling [23] and (d) state-oriented process modeling [24].…”
Section: Existing Non-workflow Business Process Modeling Techniquesmentioning
confidence: 99%
“…Firstly, we give a short overview of the state of the art in CM/ACM field (Section 2.1), and explain the main ideas of * Our way of defining data-centric process modeling substantially differs from other suggestion for nonworkflow process modeling, e.g. as artifact-based process modeling [22], data-driven process modeling [23], declarative process modeling [20], or state-oriented process modeling [24]. These works will be considered in Section 3. agile business process development (Section 2.2).…”
Section: Introductionmentioning
confidence: 99%
“…Hence, the languages are well suited to structured processes with little variation. On the other hand, the so-called declarative paradigm, including languages such as Declare [28], Multi-Perspective-Declare (MP-Declare) [8], DCR graphs [22], GSM [23] and the Declarative Process Intermediate Language (DPIL) [31,44], focuses on describing the process by restrictions (so-called constraints) over the behaviour, which must be satisfied throughout the whole process execution. Thus, they do not model the control flow explicitly.…”
Section: Introductionmentioning
confidence: 99%