@proceedings {2017:benchflow:bpmds,
	title = {Performance Comparison Between BPMN 2.0 Workflow Management Systems Versions},
	year = {2017},
	month = {June},
	publisher = {Springer},
	address = {Essen, Germany},
	abstract = {Software has become a rapidly evolving artifact and Workflow Management Systems (WfMSs) are not an exception. WfMSs{\textquoteright} changes may impact key performance indicators or resource consumption levels may change among different versions. Thus, users considering a WfMS upgrade need to evaluate the extent of such changes for frequently issued workload.  Deriving such information requires running performance experiments with appropriate workloads. 
In this paper, we propose a novel method for deriving a structurally representative workload from a given business process collection, which we later use to evaluate the performance and resource consumption over four versions of two open-source WfMSs, for different numbers of simulated users. In our case study scenario the results reveal relevant variations in the WfMSs{\textquoteright} performance and resource consumption, indicating a decrease in performance for newer versions.},
	keywords = {BenchFlow, BPMN, Performance Regression, Performance Testing, workflow engine, Workflow Management Systems},
	author = {Vincenzo Ferme and Marigianna Skouradaki and Ana Ivanchikj and Cesare Pautasso and Frank Leymann}
}
@conference {benchflow:2017:bpm,
	title = {On the Performance Overhead of BPMN Modeling Practices},
	booktitle = {15th International Conference on Business Process Management (BPM2017)},
	year = {2017},
	month = {September},
	pages = {216--232},
	publisher = {Springer},
	organization = {Springer},
	address = {Barcelona, Spain},
	abstract = {Business process models can serve different purposes, from discussion and analysis among stakeholders, to simulation and execution. 
While work has been done on deriving modeling guidelines to improve understandability, it remains to be determined how different modeling practices impact the execution of the models. 
In this paper we observe how semantically equivalent, but syntactically different, models behave in order to assess the performance impact of different modeling practices. 
To do so, we propose a methodology for systematically deriving semantically equivalent models by applying a set of model transformation rules and for precisely measuring their execution performance. 
We apply the methodology on three scenarios to systematically explore the performance variability of 16 different versions of parallel, exclusive, and inclusive control flows. 
Our experiments with two open-source business process management systems measure the execution duration of each model{\textquoteright}s instances. 
The results reveal statistically different execution performance when applying different modeling practices without total ordering of performance ranks.
},
	keywords = {BenchFlow, BPMN, performance},
	doi = {10.1007/978-3-319-65000-5_13},
	author = {Ana Ivanchikj and Vincenzo Ferme and Cesare Pautasso}
}
@conference {restalk:2016:europlop,
	title = {A Pattern Language for RESTful Conversations},
	booktitle = {Proceedings of the 21st European Conference on Pattern Languages of Programs (EuroPLoP)},
	year = {2016},
	month = {July},
	pages = {4:1{\textendash}4:22},
	publisher = {ACM},
	organization = {ACM},
	address = {Kloster Irsee, Germany},
	abstract = {As a good user interface design is important for the success of an app, so is a good API for the success of a Web service. Within the RESTful Web services community there is a need for a systematic approach in knowledge sharing, for which patterns are particularly suitable. Using a RESTful service to achieve a certain goal often requires multiple client-server interactions, i.e., to have a conversation. While patterns of such RESTful conversations can be uncovered from existing APIs{\textquoteright} usage scenarios, or the service engineering literature, they have never been gathered in a pattern language, nor properly visualized with a Domain Specific Modeling Language (DSML). These patterns provide valuable input for API designers, as well as API consumers, by establishing a common vocabulary to describe recurring conversations. To do so, this paper uses RESTalk, a DSML, to model the basic RESTful conversation patterns structured around the life cycle of a resource (create, discover, read, edit, delete, protect) by showing the corresponding sequences of HTTP request-response interactions. We show how the resulting pattern language can be applied to individual resources, or also collections of resources.},
	keywords = {conversation composition, conversation patterns, pattern language, RESTalk, RESTful conversation, RESTful web services},
	isbn = {978-1-4503-4074-8},
	doi = {10.1145/3011784.3011788},
	url = {http://doi.acm.org/10.1145/3011784.3011788},
	author = {Cesare Pautasso and Ana Ivanchikj and Silvia Schreier}
}
