Academia.edu no longer supports Internet Explorer.
To browse Academia.edu and the wider internet faster and more securely, please take a few seconds to upgrade your browser.
The adoption of business processes to design business activities is becoming a reality to a significant number of companies. In addition, the Service-Oriented Architecture (SOA) is being used in diverse situations for the execution of business processes using computational resources. In this context, the need of business process automation appears with high relevance. In this work, we present a solution named BPA-SOA, which aims to automate SOA-based business processes, specified in BPMN, into WS-BPEL executable processes. In BPA-SOA, business and service information can be specified at the business level, translated into executable artifacts, deployed in execution-level resources and enforced at runtime. An illustrative scenario is presented to better illustrate and showcase the proposed solution.
Theory, Tools and Applications
The Business Process Execution Language for Web Services (BPEL) is an emerging standard for specifying the behaviour of Web services at different levels of details using business process modeling constructs. It represents a convergence between Web services and business process technology. This chapter introduces the main concepts and constructs of BPEL and illustrates them by means of a comprehensive example. In addition, the chapter reviews some perceived limitations of BPEL and discusses proposals to address perceived limitations of BPEL and discusses proposals to address these limitations. The chapter also considers the possibility of applying formal methods and Semantic Web technology to support the rigorous development of service-oriented processes using BPEL.
International Journal of Business Process Integration and Management, 2007
Service-Oriented Architectures (SOAs), an emerging paradigm for designing and implementing business collaborations within and across organisational boundaries, are currently of interest to both software vendors and scientists. In this paradigm, the functionality provided by business applications is encapsulated within web services: software components described at a semantic level, which can be invoked by application programs or by other services through a stack of internet standards including HTTP, XML, SOAP, ...
2011 30th International Conference of the Chilean Computer Science Society, 2011
Reducing the gap between the definition, modeling and management of business definition, modeling and management of business processes and the realization of the main processes functions through software services requires a methodological approach. Addressing such gap, this paper focuses on the interactions between the activities of a business process and the functionality provided by software services. It presents a meta-model to formally specify such interactions. The proposed meta-model is instantiated through a case study. Lessons learnt through the development of an example were used to define a graphic editor prototype, as an automated tool for managing interactions between business processes and software services. The proposed approach enables the alternative application of top-down and bottom-up analysis techniques for modeling processes and services, and assists developers with an integrated tool for modeling business processes and software services in a seamlessly combined way.
Proceedings of the 2007 conference of the center for advanced studies on Collaborative research - CASCON '07, 2007
The management of non-functional goals, or Service Level Agreements (SLA), in the development of business processes in a Service Oriented Architecture (SOA) often requires much manual and error-prone effort by all parties throughout the entire lifecycle of the processes. The formal specification of SLAs into development tools can simplify some of this effort. In particular, the runtime provisioning and monitoring of processes can be achieved by an autonomic system that adapts to changing conditions to maintain the SLA's goals. SOA supports partitioning a system into services that are running in a distributed execution environment. When coupled with an associated cost model, a process can be both executed and monitored in an optimal manner, based on a declarative, user-specified optimality function. * The views and opinions expressed in this paper solely reflect the personal views of the authors and do not necessarily represent the views, positions, strategies or opinions of IBM.
2011
Web services using XML provide information to applications through an application oriented interface, so that it can be parsed and processed easily rather than being formatted for display. Web services combine the advantages of the component-oriented methods and web techniques. An orchestration process presents different services which can be composed efficiently through a low in order to execute a business process. Application and business services can be freely designed to be processagnostic and reusable. Choreography describes multiparty collaboration and focuses on message exchange; each Web service involved in a choreography knows exactly when to execute its operations and with whom to interact. Choreography depends on the orchestration using the functional, resource dependencies among multiple services. Workflow services enable to interleave human interaction with connectivity to system and services within an end-to-end process flow. An orchestration process presents different services which can be composed efficiently through a flow in order to execute a business process. Business Process Execution Language (BPEL) defines a notation for specifying business process behavior based on Web services. BPEL for Web services is an XML-based language designed to enable tasksharing for a distributed computing or grid computing environment across multiple organizations using a combination of Web services. SOA allows the integration of existing systems, applications and users into a flexible architecture that can easily accommodate changing needs. BPEL Business Processes offer the possibility to aggregate web services and define the business logic between each of these service interactions that is BPEL orchestrates such web service interactions. Each service interaction can be regarded as a communication with a business partner. SOA allows the integration of existing systems, applications and users into a flexible architecture that can easily accommodate changing needs. Integrated design, reuse of existing IT investments and above all, industry standards are the elements needed to create a robust SOA.
2007
In process-driven, service-oriented architectures (SOA), process activities invoke services to perform the various tasks of the process. As the number of elements involved in ab usiness process architecture, such as processes, process activities, and services, grows, the complexity of process development also increases along with the number of the elements' relationships, interactions, and data exchanges -and quickly becomes hardly manageable. In addition, process-drivenSOA models address different stakeholders, such as business experts and technical experts, who require different kinds of information for their work. Finally,p rocess-drivenS OA models must deal with constant changes -b oth at the business level( e.g. business concept changes) and the technical level(e.g. technologies and platform changes). Separation of concerns is apromising approach to manage such development complexity.I nthis paper,w ep ropose av iew-based, model-drivena pproach with three major contributions: firstly,itcaptures different perspectivesofabusiness process model in separate, (semi-)formalized views; secondly,i ts eparatesd ifferent abstraction levels in ab usiness process architecture; thirdly,a ne xtensible model-drivena pproach to integrate the different viewmodels and abstraction levels is presented. Our approach is beneficial not only in reducing the process development complexity,but also in coping with dynamic changes at all abstraction levels.
Lecture Notes in Computer Science, 2011
Carrying out business processes by means of software services helps to close the business-systems gap, by introducing an intermediate layer between business process definition and software systems, thus permitting not only better independence, but also more traceability between them. Despite the fact that technologies have matured to support this new reality, there is a lack of methodologies and notations, although some have been proposed to guide service development with different visions of service design and implementation. Service modeling is the basis for, among other things, the automation of several development steps by means of the model-driven development paradigm. The SoaML standard is a major step towards service modeling in UML. In this paper we extend our Business Process Service Oriented Methodology (BPSOM) for service development from business processes by integrating two main aspects: service modeling using SoaML and QVT transformations to obtain SoaML service models from BPMN BP models.
OASIS Standard, 2007
The WS-BPEL 2.0 specification [WS-BPEL 2.0] provides a language for formally describing business processes and business interaction protocols. WS-BPEL was designed to extend the Web Services interaction model to support business transactions. The WS-BPEL Primer is a non-normative document intended to provide an easy to read explanation of the WS-BPEL 2.0 specification. The goal of this document is to help readers understand the concepts and major components of the WS-BPEL language. This document will also assist readers in recognizing appropriate scenarios for using WS-BPEL. This document describes several features of WS-BPEL using examples and extensive references to the normative specification.
Research and Development in E-Business through Service-Oriented Solutions
In this chapter, the authors explore fundamental links between business process management and Web services. The authors discuss how service technologies can extend traditional business process management into a cross-organizational environment (i.e., over Internet) to face the fast changing world. Particularly, the authors discuss the issues of business process modeling for service-oriented business process management.
Bridging People and Software through Process Technology, 2005
Semantic Web services: theory, tools, and applications, 2007
The Business Process Execution Language for Web Services (BPEL) is an emerging standard for specifying the behaviour of Web services at different levels of details using business process modeling constructs. It represents a convergence between Web services and business process technology. This chapter introduces the main concepts and constructs of BPEL and illustrates them by means of a comprehensive example. In addition, the chapter reviews some perceived limitations of BPEL and discusses proposals to ...
By the use of Web Service technologies and the Internet it is possible to lay the foundation for virtual value chains that cross enterprise boundaries. As the number of services and their interaction grow, it is evident that the flow of message exchange between services needs to be coordinated in a structured way. Executable process languages such as BPEL are proposed as an instrument for the coordination of services. Executable processes must be designed such that they solve technical coordination problems as well as provide a fundament for organizations to manage and monitor the progress of the business. In this paper we examine how the design of executable processes is affected by both technical and business issues. Furthermore, we examine a set of architectures that enable the use of executable processes to cater to both business and technical needs. We provide fundamental guidelines on how to apply the architectures.
Proceedings of the 2nd international conference on Service oriented computing - ICSOC '04, 2004
Composition of software services is a fundamental part in supporting enterprise business processes. Designed properly, executable processes can be used to closely support business processes by the integration of existing software services. In order to support business processes the design of the executable process must closely follow the business events and activities, as perceived by business actors. However, the design must also consider technical issues such as limitations in existing technology and systems. In this paper we examine how technical system constraints influence the realization of business processes. Based on this examination we present a set of realization types that describes the transformation from a business process into its realization as an executable process. We also propose design criteria that need to be adhered to in order to cater to both business and technical needs.
2009
This paper deals with the role of the concept of services in the area of Business Process Management and Reengineering. It describes the process of the Business Processes System Design which is a part of the Methodology for Business Processes Analysis and Design. The paper argues in support of thinking in terms of services as being much more useful and the general principle to be limited to the area of technology and software systems development only.
2010 2nd International Conference on Software Technology and Engineering, 2010
Business process modeling, simulation, deployment, execution and evaluation support have been improved in last years, through research efforts from both the academic field and industry. Organizations are now aware of the importance of explicitly defining the business processes of which their businesses are comprised realizing them by means of services. Service support helps to reduce the gap between the areas of Business and Information Technology (IT), thus easing the communication and understanding of business needs. Business Process Management (BPM), Service Oriented Computing (SOC) and Model Driven Development (MDD) paradigms are integrated, based on standards and tools which support them. MINERVA is a framework that aims to provide such an integrated solution. In this paper we present the MINERVA proposal for automating transformations from BPMN to SoaML models in order to automatically generate services from business processes.
The Dagstuhl seminar on emph{The Role of Business Processes in Service Oriented Architectures} (Seminar 06291) took place in July 2006 (16.07.2006-21.07.2006 to be precise). The seminar was attended by more than 40 experts from both academia and industry. Unlike most Dagstuhl seminars there was a high participation from industry (in particular from organizations developing software, e.g., IBM, SAP, Microsoft, Google, etc.). The focal point of the seminar was the marriage of business processes and service oriented architectures. This was reflected by the topics selected by the participants and their background. @InProceedings{leymann_et_al:DSP:2006:832, author = {Frank Leymann and Wolfgang Reisig and Satish R. Thatte and Wil van der Aalst}, title = {06291 Abstracts Collection -- The Role of Business Processes in Service-Oriented Architectures}, booktitle = {The Role of Business Processes in Service Oriented Architectures}, year = {2006}, editor = {Frank Leymann and Wolfgang Reisig an...
2010
The integration of Business Process Management (BPM), Service Oriented Computing (SOC) and Model Driven Development (MDD) paradigms to improve the development of services oriented solutions from business models is nowadays in the spotlight. Organizations wanting to remain competitive despite the constant changes in their business are paying more attention to their business processes and its base lifecycle. Business process modeling is also at the centre of software development efforts, as making those models explicitly constitutes the basis for services definition. Transformations between business process and services models allow the automatic generation of services from business processes in a repeatable and systematic way, easing the development process. In this paper we present MINERVA's tool support for service oriented development from business processes, including QVT transformations from BPMN to SoaML models to automatically generate service models from business process models.
EMISA Forum, 2006
Abstract: BPEL is gaining increasing attention as a potential standard for the definition of executable business processes based on web services. This paper gives an overview of standardization efforts in the area of business process execution, of the main concepts of BPEL, and of its support in practice.
IEEE Access
Enterprise Resource Planning (ERP) is a business process management system in which integrated applications are used to manage business processes in a shared data environment. ERP systems usually deal with the two types of business processes i.e. Exchange and Conversion. In the Exchange process, economic resource such as product exchanges to another economic resource like sales process. In a Conversion process, an enterprise consumes resources in order to produce new resources like the distribution process. Generally, the communication between ERP applications, based on Conversion and Exchange processes, is accomplished through web services. In this context, the implementation of web services in ERP systems is a complex task. To manage this, Business Process Model and Notation (BPMN) is frequently utilized to simplify the development of ERP applications. However, state-of-the-art BPMN approaches usually deal with the modelling of exchange processes without considering the conversion process. Furthermore, the model transformation solution to automatically generate web services from BPMN models is hard to find in the literature. Therefore, in this article, a novel framework is proposed that supports the modelling of both exchanges as well as conversion processes through BPMN. Particularly, a modeling approach is introduced to represent ERP processes through BPMN concepts. Subsequently, the rules are developed to convert source BPMN models into target SoaML (Service-oriented architecture Modeling Language) models. Finally, transformation rules are developed to generate fully functional executable Java web services from SoaML models. As a part of research, a complete open source BPMN to Web services transformation (B2W) tool is developed to automatically generate the web services from the high-level BPMN models. The proposed framework is validated through multiple case studies. The experimental results prove that the proposed framework accurately generates web services from BPMN models which eventually helps in developing the ERP systems with simplicity.
Services Transactions on Services Computing, 2016
When Service Oriented applications and services are modeled, the term Quality of Service (QoS) is used to refer to the collection of constraints and quality requirements for a service. It is important that QoS attributes are specified in early stages of the development process, and modeled in a way that can be recognized and understood by all stakeholders. Regarding Service Oriented Architecture (SOA) modeling, QoS usually includes security, performance and availability. There are many options to realize business processes with services, such as collaborations with partners, internal services, third parties services (SaaS) among others. In previous works we have proposed the automatic generation of services specified in the Service Architecture Modeling Language (SoaML) from business processes, and the associated code. As SoaML allows to model functional requirements only, we have extended our proposal to also take into account QoS modeling and generation from SoaML service models, enriching the specification of services with quality characteristics. We have also added a log facility to the generated WS client to register times regarding services execution, in order to evaluate the defined QoS.
Loading Preview
Sorry, preview is currently unavailable. You can download the paper by clicking the button above.