DOCSLIB.ORG

Open-Source Workflow Evaluation an Evaluation of the Activiti BPM Platform

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Open-Source Workflow Evaluation an Evaluation of the Activiti BPM Platform Mid Sweden University The Department of Information Technology and Media (ITM) Author: Mikael Nilsson E-mail address: [email protected] Study programme: M. Sc. In engineering – computer engineering, 240 ECTS Examiner: Tingting Zhang, [email protected] Tutors: Anders Trollås, Cybercom Group, [email protected] Fredrik Håkansson, Mid Sweden University, [email protected] Scope: 29901 words inclusive of appendices Date: 2012-06-29 M.Sc. Thesis within Computer Engineering AV, 30 ECTS Open-source Workflow Evaluation An evaluation of the Activiti BPM Platform Mikael Nilsson Open-source Workflow Evaluation - An evaluation of the Activiti BPM Platform Abstract Mikael Nilsson 2012-06-29 Abstract The aim of this thesis is to evaluate the newly released open-source business process management platform Activiti. The platform is evalu- ated in the first instance by implementing the control-flow patterns which will be used at a later stage as a comparison with other platforms that have already been evaluated. Activiti comes with a web application called Activiti Explorer which is a graphical user interface between the process engine and the user. As all the desired features commissioned by the Cybercom Group were not available in the Activiti Explorer its source-code was extended. These extended features included support for several companies per installation and the ability to customize the layout of the components in user task forms. The report is concluded with a comparison between Activiti, jBPM, OpenWFE and Enhydra shark with regards to the control-flow patterns. Keywords: Open-source, Workflow, BPM, BPMN 2.0, Activiti, Work- flow patterns, Control-flow patterns ii Open-source Workflow Evaluation - An evaluation of the Activiti BPM Platform Acknowledgements Mikael Nilsson 2012-06-29 Acknowledgements Thanks to... Anders Trollås, my tutor from Cybercom Group, for your help, guidance and support during this thesis. Fredrik Håkansson, my tutor from Mid Sweden University, for your help, reviews and valuable advice for my report. iii Open-source Workflow Evaluation - An evaluation of the Activiti BPM Platform Table of Contents Mikael Nilsson 2012-06-29 Table of Contents Abstract ............................................................................................................. ii Acknowledgements ....................................................................................... iii Terminology .....................................................................................................ix 1 Introduction ............................................................................................ 1 1.1 Background and problem motivation ...................................... 4 1.2 Overall aim and verifiable goals ............................................... 5 1.3 Scope ............................................................................................. 6 1.4 Outline .......................................................................................... 6 1.5 Contributions ............................................................................... 7 2 Theory ...................................................................................................... 8 2.1 BPMN 2.0 ...................................................................................... 8 2.2 Activiti Designer .......................................................................... 8 2.3 Workflow Patterns ...................................................................... 9 2.4 Control-flow patterns ................................................................. 9 2.4.1 Basic Control Flow Patterns ............................................ 9 2.4.2 Advanced Branching and Synchronization Patterns 10 2.4.3 Multiple Instance Patterns ............................................ 11 2.4.4 State-based Patterns ....................................................... 11 2.4.5 Cancellation and Force Completion Patterns ............. 12 2.4.6 Iteration Patterns ............................................................ 12 2.4.7 Termination Patterns ..................................................... 12 2.4.8 Trigger Patterns .............................................................. 12 2.5 Activiti source code ................................................................... 13 2.6 Activiti Explorer ........................................................................ 13 2.6.1 Spring Framework .......................................................... 13 2.6.2 Vaadin .............................................................................. 14 2.6.3 Activiti Process Engine .................................................. 16 iv Open-source Workflow Evaluation - An evaluation of the Activiti BPM Platform Table of Contents Mikael Nilsson 2012-06-29 3 Methodology ........................................................................................ 18 3.1 Literature studies ....................................................................... 18 3.2 Workflow patterns initiative.................................................... 18 3.3 Workflow patterns evaluation ................................................. 18 3.3.1 Implementing the patterns ............................................ 18 3.4 Product comparison .................................................................. 19 3.5 Building the extended version of Activiti Explorer ............. 19 4 Implementation ................................................................................... 21 4.1 Control-flow patterns ............................................................... 21 4.1.1 Pattern 1 – Sequence....................................................... 21 4.1.2 Pattern 2 – Parallel split ................................................. 21 4.1.3 Pattern 3 – Synchronization .......................................... 22 4.1.4 Pattern 4 - Exclusive Choice .......................................... 22 4.1.5 Pattern 5 - Simple Merge ............................................... 23 4.1.6 Pattern 6 - Multi-Choice ................................................ 23 4.1.7 Pattern 7 - Structured Synchronizing Merge .............. 24 4.1.8 Pattern 8 - Multi-Merge ................................................. 24 4.1.9 Pattern 9 - Structured Discriminator ........................... 25 4.1.10 Pattern 10 – Arbitrary Cycles ........................................ 25 4.1.11 Pattern 11 - Implicit Termination ................................. 25 4.1.12 Pattern 12 - Multiple Instances without Synchronization .............................................................. 26 4.1.13 Pattern 13 - Multiple Instances with a priori Design- Time Knowledge ............................................................ 26 4.1.14 Pattern 14 - Multiple Instances with a priori Run-Time Knowledge ...................................................................... 27 4.1.15 Pattern 15 - Multiple instances without a priori run- time knowledge .............................................................. 27 4.1.16 Pattern 16 - Deferred Choice ......................................... 27 4.1.17 Pattern 17 - Interleaved Parallel Routing .................... 28 4.1.18 Pattern 18 – Milestone .................................................... 28 4.1.19 Pattern 19 - Cancel Activity .......................................... 28 v Open-source Workflow Evaluation - An evaluation of the Activiti BPM Platform Table of Contents Mikael Nilsson 2012-06-29 4.1.20 Pattern 20 - Cancel Case ................................................ 29 4.1.21 Pattern 21 - Structured Loop ......................................... 29 4.1.22 Pattern 22 - Recursion .................................................... 30 4.1.23 Pattern 23 - Transient Trigger ....................................... 30 4.1.24 Pattern 24 - Persistent Trigger ...................................... 30 4.1.25 Pattern 25 - Cancel Region ............................................ 30 4.1.26 Pattern 26 - Cancel Multiple Instance Activity .......... 31 4.1.27 Pattern 27 - Complete Multiple Instance Activity ..... 31 4.1.28 Pattern 28 - Blocking Discriminator ............................. 32 4.1.29 Pattern 29 - Cancelling Discriminator ......................... 32 4.1.30 Pattern 30 - Structured Partial Join .............................. 32 4.1.31 Pattern 31 - Blocking Partial Join .................................. 32 4.1.32 Pattern 32 - Cancelling Partial Join .............................. 33 4.1.33 Pattern 33 - Generalized AND-Join ............................. 33 4.1.34 Pattern 34 - Static Partial Join for Multiple Instances 33 4.1.35 Pattern 35 - Cancelling Partial Join for Multiple Instances .......................................................................... 33 4.1.36 Pattern 36 - Dynamic Partial Join for Multiple Instances .......................................................................... 33 4.1.37 Pattern 37 - Acyclic Synchronizing Merge .................. 33 4.1.38 Pattern 38 - General Synchronizing Merge ................. 33 4.1.39 Pattern 39 - Critical Section ........................................... 33 4.1.40 Pattern 40 - Interleaved Routing .................................. 34 4.1.41 Pattern 41 - Thread Merge ............................................. 34 4.1.42 Pattern 42 - Thread Split ................................................ 34 4.1.43 Pattern 43 - Explicit Termination ................................. 34 4.2 Support for multiple companies
Load more

Recommended publications
  • A Language to Coordinate Collaborative Reuse
    The Journal of Systems and Software 131 (2017) 505–527 Contents lists available at ScienceDirect The Journal of Systems and Software journal homepage: www.elsevier.com/locate/jss CollabRDL: A language to coordinate collaborative reuse ∗ Edson M. Lucas a,b, , Toacy C. Oliveira a,d, Kleinner Farias c, Paulo S.C. Alencar d a PESC/COPPE, Federal University of Rio de Janeiro, Brazil b IPRJ/UERJ, Polytechnic Institute, State University of Rio de Janeiro, Brazil c PIPCA, University of Vale do Rio dos Sinos (Unisinos), Brazil d David Cheriton School of Computer Science, University of Waterloo, Canada a r t i c l e i n f o a b s t r a c t Article history: Coordinating software reuse activities is a complex problem when considering collaborative software de- Received 19 June 2015 velopment. This is mainly motivated due to the difficulty in specifying how the artifacts and the knowl- Revised 17 January 2017 edge produced in previous projects can be applied in future ones. In addition, modern software systems Accepted 31 January 2017 are developed in group working in separate geographical locations. Therefore, techniques to enrich collab- Available online 2 February 2017 oration on software development are important to improve quality and reduce costs. Unfortunately, the Keywords: current literature fails to address this problem by overlooking existing reuse techniques. There are many Software reuse reuse approaches proposed in academia and industry, including Framework Instantiation, Software Prod- Collaboration uct Line, Transformation Chains, and Staged Configuration. But, the current approaches do not support Framework the representation and implementation of collaborative instantiations that involve individual and group Language roles, the simultaneous performance of multiple activities, restrictions related to concurrency and syn- Reuse process chronization of activities, and allocation of activities to reuse actors as a coordination mechanism.
    [Show full text]
  • Open Source Power on BPM - a Comparison of Jboss Jbpm and Intalio BPMS
    Open Source Power on BPM - A Comparison of JBoss jBPM and Intalio BPMS Pin Nie, Riku Seppälä, Måns Hafrén T-86.5161 Special Course in Information Systems Integration Abstract. This paper presents a comparison of two open source products in Business Process Management: Intalio BPMS and JBoss jBPM. A framework for their comparison is constructed based on expert advice and a literature analysis. We implemented a simple process with both tools to gather experience of using the tools and combined this knowledge with information from official documentation, tutorials, research and any available third-party documentation. With this knowledge, the two tools were compared using the comparison framework. In the end, we score the two tools across the categories identified in the comparison framework and provide further discussion for future work. Keywords: BPMS, BPM, jBPM, Intalio, JBoss, Redhat, evaluation, comparison framework, open source 1 Introduction Business Process Management (BPM) is gaining increasing attention and consideration in organization and enterprise architecture as a bridge between information technology (IT) and business. BPM is a holistic management approach that promotes business effectiveness and flexibility on the basis of a set of standardized IT technologies and tools. The technology solutions that address the need for BPM are called Business Process Management Systems (or suites), or BPMS. There are various definitions for Business Process Management (Smith & Fingar, 2003; Hill et al., 2006). A recent and influential definition is given by Mathias Weske: “A business process management system is a generic software system that is driven by explicit process representations to coordinate the enactment of business process.” (Weske, 2007) However, most of the BPM tools and software employed today are expensive commercial products.
    [Show full text]
  • Digital Archive: Arrange, Assign & Sign!
    Digital Archive: Arrange, Assign & Sign! Patrícia Raquel Vieira Sousa Mestrado Integrado em Engenharia de Redes e Sistemas Informáticos Departamento de Ciência de Computadores 2016 Orientador Prof. Dr. Luís Filipe Coelho Antunes, Professor Auxiliar, FCUP Coorientador Eng. Pedro Vasconcelos Castro Lopes Faria, Consultor, HealthySystems Todas as correções determinadas pelo júri, e só essas, foram efetuadas. O Presidente do Júri, Porto, ______/______/_________ Patr´ıcia Raquel Vieira Sousa Digital archive: Arrange, Assign & Sign! Departamento de Ciˆencia de Computadores Faculdade de Ciˆencias da Universidade do Porto Junho de 2016 Patr´ıcia Raquel Vieira Sousa Digital archive: Arrange, Assign & Sign! Disserta¸c˜ao submetida `aFaculdade de Ciˆencias da Universidade do Porto como parte dos requisitos para a obten¸c˜ao do grau de Mestre em Engenharia de Redes em Sistemas Inform´aticos Orientador: Prof. Dr. Lu´ıs Filipe Coelho Antunes Co-orientador: Eng. Pedro Vasconcelos Castro Lopes Faria Departamento de Ciˆencia de Computadores Faculdade de Ciˆencias da Universidade do Porto Junho de 2016 To my parents and my love for all the support and patience... 3 Acknowledgments I want to thank my advisor Professor Lu´ıs Antunes for the support in all this time of work, for all suggestions that improved my thesis and for this opportunity. I also want to thank my co-advisor Pedro Faria for all dedication, support, patience and guidance that made all this work possible. Thanks for innovative ideas and the security knowledge transmitted during this thesis. I also want to thank Professor Manuel Eduardo Correia for the interest that has always shown for this thesis work and for all the support and ideas.
    [Show full text]
  • Alfresco Developer Series: Advanced Workflows
    ecmarchitect.com Alfresco Developer Series Advanced Workflows 2nd Edition February, 2012 Jeff Potts This work is licensed under the Creative Commons Attribution-ShareAlike 3.0 Unported License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/3.0/ or send a letter to Creative Commons, 444 Castro Street, Suite 900, Mountain View, California, 94041, USA. ecmarchitect.com Alfresco Developer Series Advanced Workflows 2nd Edition February, 2012 Jeff Potts About the Second Edition This tutorial was originally written in November of 2007. Since then, Alfresco has added the Share web client and the Activiti workflow engine, so, at first glance you could say that a lot has changed. On the other hand, if you've already worked through the Custom Content Types and Custom Actions tutorials, you'll already be comfortable with configuring the form service for Alfresco Share. And, although Activiti is an entirely new workflow engine, it was built by the same guys that built jBPM, after all, so it is similar enough in concept that people already familiar with building Alfresco workflows using jBPM should have a pretty easy transition moving to Activiti. The original version of this tutorial spent a little too long on details up front, which I tried to fix when this tutorial was used as the basis of the workflow chapter in the Alfresco Developer Guide. So, for this edition of the tutorial, I cut down on theory and moved into some Hello World examples as quickly as I could. I also did a little bit of rearranging to provide two distinct parts to the tutorial so that the first part covers everything you need to know, from concepts to deploying and running processes, with the focus being on the steps and tools using simple processes.
    [Show full text]
  • Flowable 5.23.0 User Guide
    Flowable 5.23.0 User Guide Table of Contents 1. Introduction 1.1. License 1.2. Download 1.3. Sources 1.4. Required software 1.4.1. JDK 7+ 1.4.2. IDE 1.5. Reporting problems 1.6. Experimental features 1.7. Internal implementation classes 2. Getting Started 2.1. What is Flowable? 2.2. Flowable and Activiti 2.3. Building a command-line application 2.3.1. Creating a process engine 2.3.2. Deploying a process definition 2.3.3. Starting a process instance 2.3.4. Sidetrack: transactionality 2.3.5. Querying and completing tasks 2.3.6. Writing a JavaDelegate 2.3.7. Working with historical data 2.3.8. Conclusion 2.4. Getting started with the Flowable REST API 2.4.1. Setting up the REST application 2.4.2. Deploying a process definition 2.4.3. Start a process instance 2.4.4. Task list and completing a task 3. Configuration 3.1. Creating a ProcessEngine 3.2. ProcessEngineConfiguration bean 3.3. Database configuration 3.4. JNDI Datasource Configuration 3.4.1. Configuration 3.4.2. JNDI properties 3.5. Supported databases 3.6. Creating the database tables 3.7. Database table names explained 3.8. Database upgrade 3.9. Job Executor (since version 6.0.0) 3.10. Job executor activation 3.11. Mail server configuration 3.12. History configuration 3.13. Exposing configuration beans in expressions and scripts 3.14. Deployment cache configuration 3.15. Logging 3.16. Mapped Diagnostic Contexts 3.17. Event handlers 3.17.1. Event listener implementation 3.17.2.
    [Show full text]
  • An Approach for Modeling and Transforming Contextually-Aware Software Engineering Workflows
    ICSEA 2014 : The Ninth International Conference on Software Engineering Advances An Approach for Modeling and Transforming Contextually-Aware Software Engineering Workflows Roy Oberhauser Computer Science Dept. Aalen University Aalen, Germany [email protected] Abstract—Software engineering environments (SEE) face rigid, and inflexible [6], and fail to adequately support the challenges for providing automated guidance for human- human, creative, and dynamics of SW development. Thus, centric software development workflows. Among the various such systems are ignored or abandoned by SW engineers. issues is the lack of a method to model software engineering To address this challenge for such human-centric SE (SE) workflows, as commonly used business process modeling processes, we created a PCSEE called the Context-aware notation is generalized and not conducive to context-aware Software Engineering Environment Event-driven Framework support for SEE, while available SE-specific process model (CoSEEEK) [7]. Beyond SE tool sensors and other notation, such as the Software & Systems Process Engineering contextual knowledge, it utilizes workflows to understand Metamodel, is not executable. The solution approach in this the process context. That includes knowing which activities a paper simplifies and validates the modeling of SE workflows SW engineer performed, which activity is likely currently via graphical modeling capabilities that extend the Software Engineering Workflow Language (SEWL). Model-based being worked on, which activity is next, and associates these transformation of workflow concepts to diverse workflow with SE concepts of project, teams, persons, roles, tools, and management systems (WfMS), as well semantic transformation artifacts via an ontology and reasoner. While various facets of SE concepts to a contextually-aware process-centered were investigated, including collaboration [8], quality software engineering environment - CoSEEEK, is supported.
    [Show full text]
  • Activiti Timer Boundary Event Example
    Activiti Timer Boundary Event Example CharacteristicRoilier Dietrich and variolates allied Chris her flax sobs: so anarthrouslywhich Constantine that Noach is nettled inwrap enough? very definably. Saturated and uneven Freddy still acidulated his Ciliata victoriously. Your profile picture is used as the logo for your personal space. Thanks for contributing an answer to Stack Overflow! Text: Enter descriptive text. So far, Alexandrya would look as expected. This language enables analysts to model their business. If you press two active signal boundary events catching the same signal event, of boundary events are triggered, even if anyone are district of warehouse process instances. The boundary definition. Can Digital Transformation happen without Process Automation? Execute any arbitrary expression! The example is an start events but were found. Alfresco Share with service i understand. Time event example activiti events, active while in boundary event listeners were all activities based on given listener and rest web service task and uses. Within the subprocess, a separate token is born which runs through the subprocess from the start to the end event, but the token of the parent process waits until the subprocess completes. So it looks like name due core is properly set, but why per the workflow immediately goes to remove next task instead have waiting press the discount date? But eventually continues after which is set of eclipse workspace to true. However, due to the broadcast semantics of the signal, it would also be propagated to all other process instances which have subscribed to the signal event. Compensation handlers are not contained in normal flow and are only executed when a compensation event is thrown.
    [Show full text]
  • Introduction to Flowable
    Introduction to Flowable Filip Hrisafov (@filiphr) Jose Antonio Alvarez (@jaam_eu) 1 Short Introduction Filip Hrisafov Jose Antonio Alvarez • Core Software • Head Solutions Architect at Flowable Architect at Flowable • Flowable core dev • Flowable core contributor • MapStruct project lead • 11 years experience in process management 29.01.2020 2 © 2020 Flowable AG. All rights reserved. Agenda & Goals • Explaining all that Flowable can do in 60 mins is … impossible • Short History • Open Standards (BPMN, CMMN, DMN) • A glimpse of what you can do • And hope to inspire you to look deeper! 29.01.2020 3 © 2020 Flowable AG. All rights reserved. Flowable Open Source Project Native BPMN, CMMN and DMN engines Speed, scalability and innovation process instances • High performance, high scale • Fastest engines available per second • Years of real world use • Lightweight FlowableFlowableA C 5.23 6.3 Community is key Long heritage of Open Source BPM • Credibility through engagement • Origins since 2010 in Activiti and jBPM & contributions • Established 2016 by Alfresco co-founder • Usage all over the world and Activiti team 2016 Flowable and in all kind 2010 Activiti jBPM of industries 29.01.2020 4 © 2020 Flowable AG. All rights reserved. Flowable Family Tree Implemented BPM on Red Hat R&D focus shifted to new microservice Drools architecture orchestration engine (Zeebe) jBPM 5 Camunda 7 Flowable 6 2010 2013 jBPM 3 Activiti Flowable 2009 2013 2016 Bonitasoft Effektif Activiti 5/6/7 Dropped jBPM and built own Lightweight BPMN, now rolled into Continues without architects but no core engine updates engine, but no longer a focus Signavio (not open source) 29.01.2020 5 Case and Business Process Management The heart of Digitalization Case management Manage complex business activities that require a mix of human and electronic actions, such as an incoming application, a submitted claim, a complaint, or incident management Business process management Coordinate or orchestrate the behaviour of people, systems, information, and things to produce business outcomes.
    [Show full text]
  • Diflow: a Distributed Workflow Management System
    DIFLOW: A DISTRIBUTED WORKFLOW MANAGEMENT SYSTEM by ANUJ SUNIL SHETYE (Under the Direction of Krzysztof J. Kochut) ABSTRACT Workflow systems are one of the key technologies enabling automation of business processes and, recently, scientific applications. Traditionally, control of the execution of workflow processes has been centralized, despite the fact that they have frequently involved and coordinated systems executing at distributed computing nodes. Today, there is a need for decentralized and distributed workflow management systems (WfMS). In this thesis, we present DIFLOW, a system for designing and executing workflow processes based on dynamic migration of workflow instances during runtime. The system allows a process designer to define process constraints, which are specified in terms of process variables and capabilities of the workflow’s processing nodes (performers). At runtime, workflow instances may migrate to computing nodes that satisfy the defined constraints. Process constraints in DIFLOW may capture functional or non-functional requirements of the process, which cannot be expressed using typical process definition languages, such as BPMN. In this thesis, we introduce a Constraint Definition Language (CDL) to describe constraints comprising of performer capabilities and domain specific variables for providing necessary migration meta-information. We also present a design and implementation of DIFLOW capable of scheduling and enacting workflow instances in a distributed environment. INDEX WORDS: Distributed Workflow Management System, BPMN 2.0, Activiti DIFLOW: A DISTRIBUTED WORKFLOW MANAGEMENT SYSTEM by ANUJ SUNIL SHETYE BE, University of Mumbai, India, 2010 A Thesis Submitted to the Graduate Faculty of The University of Georgia in Partial Fulfillment of the Requirements for the Degree MASTER OF SCIENCE ATHENS, GEORGIA 2014 © 2014 ANUJ SUNIL SHETYE All Rights Reserved DIFLOW: A DISTRIBUTED WORKFLOW MANAGEMENT SYSTEM by ANUJ SUNIL SHETYE Major Professor: Krzysztof J.
    [Show full text]
  • BPMN Conformance in Open Source Engines
    BPMN Conformance in Open Source Engines Matthias Geiger, Simon Harrer, Jorg¨ Lenhard, Mathias Casar, Andreas Vorndran and Guido Wirtz Distributed Systems Group University of Bamberg Bamberg, Germany fmatthias.geiger, simon.harrer, joerg.lenhard, [email protected] Abstract—Service-oriented systems are increasingly imple- when it comes to the construction of service orchestrations. mented in a process-based fashion. Multiple languages for More and more vendors are currently implementing the building process-based systems are available today, but the specification, resulting in a variety of freely available or Business Process Model and Notation (BPMN) is becoming 1 ubiquitous. With BPMN 2.0 released in 2011, execution seman- commercial modeling tools and engines . BPMN engines tics were introduced, supporting the definition of executable are able to consume and execute processes provided in the processes. Nowadays, more and more process engines directly correct format. Since BPMN standardizes the format and support the execution of BPMN processes. However, the BPMN semantics of processes, their execution behavior should not specification is lengthy and complex. As there are no official differ on different engines. However, this only works if all tests and no certification authority, it is very likely that engines a) implement only a subset of the language features and b) engines fully implement BPMN in the same manner with implement language features differently. In other words, we respect to semantics, which is an unrealistic assumption. If suspect that engines do not conform to the standard, despite the engines do not fully conform to the standard, i.e., if they fact that they claim support for it.
    [Show full text]
  • Opportunities for Business Process Semantization in Open-Source Process Execution Environments
    Proceedings of the Federated Conference on DOI: 10.15439/2015F250 Computer Science and Information Systems pp. 1307–1314 ACSIS, Vol. 5 Opportunities for Business Process Semantization in Open-source Process Execution Environments Krzysztof Kluza and Krzysztof Kaczor and Grzegorz J. Nalepa and Mateusz Sla´ zy˙ nski´ AGH University of Science and Technology al. A. Mickiewicza 30, 30-059 Krakow, Poland E-mail: {kluza,kk,gjn,mslaz}@agh.edu.pl Abstract—Business Process models help to visualize the pro- The paper is structured as follows. In Section II, we present cesses of an organization. There are open-source process execu- selected open-source process execution environments and their tion engines that provide the environments for enacting process general architecture. Section III gives an overview of business models. However, they lack semantization capabilities. In this paper, an overview of Business Process semantization techniques process semantization approaches, especially focusing on the is provided. Moreover, we discuss the common architecture of solution developed in the SUPER project and the SAP AG the selected open-source process execution environments (Activiti, company. Section IV analyzes the possibilities of process jBPM and Camunda) and provide the insights how they can be semantization in the open-source process execution environ- improved using semantization methods. We also present the use ments. The paper is concluded in Section V. of the introduced techniques in the Prosecco (Processes Semantics Collaboration for Companies) research project. II. OPEN-SOURCE PROCESS EXECUTION ENVIRONMENTS Index Terms —Business Process Model and Notation (BPMN), 3 4 Business Process Semantization, Business Process Management All three environments, Activiti [4], jBPM [5], and Ca- munda5 [6], are light-weight BPM suites with extensible I.
    [Show full text]
  • Evaluation of Business Process Management Systems
    Evaluation of business process management systems Daina Ardzevičiūtė doc. dr. Tomas Skersys Ernestas Kvedaras Department of Information Systems Department of Information Systems Kaunas, Lithuania Kaunas University of Technology Kaunas University of Technology e-mail:[email protected] Kaunas, Lithuania Kaunas, Lithuania e-mail: [email protected] e-mail: [email protected] Abstract—Nowadays, more and more industrial organizations are modeling their business processes and implementing business II. THE FRAMEWORK FOR EVALUATING BUSINESS PROCESS process management systems. Therefore, it is very important to MANAGEMENT SYSTEMS choose a suitable business process management system. The main Criteria identified during literary analysis were divided into purpose of this paper is to propose and verify the framework for six groups: evaluating business process management systems. This method covers the most important aspects of a business process • Business process modeling criteria – evaluate systems management systems from the design to the monitoring of the ability to model clear and complete processes and to business process. The main advantage of the proposed approach import and export them; is that it is independent from any specific domain and execution engine. The evaluation framework was tested by applying it to • Systems development criteria – evaluate business four different business process management systems: “Bonita process execution capabilities and user interface BPM”, “Camunda”, “jBPM“, “Activiti”. design; Keywords—Business
    [Show full text]