Endre søk
RefereraExporteraLink to record
Permanent link

Direct link
Referera
Referensformat
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Annet format
Fler format
Språk
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Annet språk
Fler språk
Utmatningsformat
  • html
  • text
  • asciidoc
  • rtf
On the analysis of CMMN expressiveness: revisiting workflow patterns
Univ Quebec, LATECE Lab, Montreal, PQ, Canada..
Univ Quebec, LATECE Lab, Montreal, PQ, Canada..
Univ Quebec, LATECE Lab, Montreal, PQ, Canada..
Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
Vise andre og tillknytning
2016 (engelsk)Inngår i: 2016 IEEE 20TH INTERNATIONAL ENTERPRISE DISTRIBUTED OBJECT COMPUTING WORKSHOP (EDOCW), 2016, s. 54-61Konferansepaper, Publicerat paper (Fagfellevurdert)
Abstract [en]

Traditional business process modeling languages use an imperative style to specify all possible execution flows, leaving little flexibility to process operators. Such languages are appropriate for low-complexity, high-volume, mostly automated processes. However, they are inadequate for case management, which involves low-volume, high-complexity, knowledge-intensive work processes of today's knowledge workers. OMG's Case Management Model and Notation (CMMN), which uses a declarative style to specify constraints placed at a process execution, aims at addressing this need. To the extent that typical case management situations do include at least some measure of imperative control, it is legitimate to ask whether an analyst working exclusively in CMMN can comfortably model the range of behaviors s/he is likely to encounter. This paper aims at answering this question by trying to express the extensive collection of Workflow Patterns in CMMN. Unsurprisingly, our study shows that the workflow patterns fall into three categories: 1) the ones that are handled by CMMN basic constructs, 2) those that rely on CMMN's engine capabilities and 3) the ones that cannot be handled by current CMMN specification. A CMMN tool builder can propose patterns of the second category as companion modeling idioms, which can be translated behind the scenes into standard CMMN. The third category is problematic, however, since its support in CMMN tools will break model interoperability.

sted, utgiver, år, opplag, sider
2016. s. 54-61
Serie
IEEE International Enterprise Distributed Object Computing Conference Workshops, ISSN 2325-6583
HSV kategori
Identifikatorer
URN: urn:nbn:se:bth-13504ISI: 000386577000030ISBN: 978-1-4673-9933-3 (tryckt)OAI: oai:DiVA.org:bth-13504DiVA, id: diva2:1049628
Konferanse
IEEE 20th International Enterprise Distributed Object Computing Workshop (EDOCW), SEP 05-09, 2016, Vienna, AUSTRIA
Tilgjengelig fra: 2016-11-25 Laget: 2016-11-25 Sist oppdatert: 2018-01-13bibliografisk kontrollert

Open Access i DiVA

Fulltekst mangler i DiVA

Personposter BETA

Gonzalez-Huerta, Javier

Søk i DiVA

Av forfatter/redaktør
Gonzalez-Huerta, Javier
Av organisasjonen

Søk utenfor DiVA

GoogleGoogle Scholar

isbn
urn-nbn

Altmetric

isbn
urn-nbn
Totalt: 114 treff
RefereraExporteraLink to record
Permanent link

Direct link
Referera
Referensformat
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Annet format
Fler format
Språk
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Annet språk
Fler språk
Utmatningsformat
  • html
  • text
  • asciidoc
  • rtf