Business Process Execution Language for Web Services

By Jan Mendling. EMISA FORUM, 2006

995 citations recorded by the source corpus.

View Paper: https://www.semanticscholar.org/paper/11c76b79edce7822ffd270f0b296bd0acd6c8821

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

Citations in the corpus

Non-intrusive monitoring and service adaptation for WS-BPEL (2008, methodology): “[13] refer to this technique as dynamic partner link assignment.”
Automated composition of Web services via planning in asynchronous domains (2005, background): “While novel and more powerful services can be obtained, in such setting, by suitably orchestrating existing ones, manually developing such orchestrations is highly demanding, time-consuming and error-prone.”
Dynamic QoS Management and Optimization in Service-Based Systems (2011, methodology): “This TeleAssistance (TA) system will be used as a running example throughout the rest of the paper, and its associated BPEL workflow is depicted in Fig.”
An approach for QoS-aware service composition based on genetic algorithms (2005, background): “INTRODUCTION The rapid di.usion of web services and of service oriented systems constitutes an important step towards a radical change in the software development process.”
QoS-aware middleware for Web services composition (2004, background): “Hence, it is possible to adapt the QoS-driven service selection mechanisms developed using statecharts, to (cid:2)t other alternative languages such as the Business Process Execution Language for Web Services (BPEL4WS) [2].”
Automated Planning and Acting (2016, background): “[22]), which proposes to plan and compose asynchronous software services represented as state transition systems.”
How Much Language Is Enough? Theoretical and Practical Use of the Business Process Modeling Notation (2008, methodology): “The development of BPMN was influenced by the demand for a graphical notation that complements the BPEL standard for executable business processes.”
A Survey of Automated Web Service Composition Methods (2004, unknown): “Some other initiatives such as Business Process Execution Language for Web Service (BPEL4WS) [2] and DAML-S ServiceModel, are focused on representing service compositions where flow of a process and bindings between services are known a priori.”
Swift: A language for distributed parallel scripting (2011, background): “BPEL [39] is a Web service-based standard that specifies how a set of Web services interact to form a larger, composite Web service.”
Service-oriented design and development methodology (2006, unknown): “These are defined using the Web services Business Process Execution Language (BPEL) [Andrews 2003].”
Process mining: a research agenda (2004, background): “the work on web services composition languages such as BPEL4WS and BPML [13,9].”
A Taxonomy of Workflow Management Systems for Grid Computing (2005, methodology): “Compared to other workflow languages, such as the Business Process Execution Language for Web Services (BPEL4WS) [14] , SCUFL allows implicit iteration over incoming data sets based on a specified strategy.”
A framework for QoS-aware binding and re-binding of composite web services (2008, methodology): “Let us consider a service–oriented system, or a composite service1 written using a workflow description l nguage such as BPEL4WS2 (Andrews et al., 2007).”