Integration of business process modeling and Web services: a survey

2013 ◽  
Vol 8 (2) ◽  
pp. 105-128 ◽  
Author(s):  
Katarina Grolinger ◽  
Miriam A. M. Capretz ◽  
Americo Cunha ◽  
Said Tazi
2010 ◽  
pp. 1627-1638
Author(s):  
Dimitris Folinas ◽  
Tania Pavlou ◽  
Bill Karakostas ◽  
Vicky Manthou

Among different approaches in business processes modelling procedure are those in virtual and dynamic organizational environments. In this paper, a conceptual framework for modelling business processes in Virtual Organizations is suggested, by introducing Web Services technology. Web Services can be the business enabler for the new organizational form, which is particularly well suited to meet the demands arising from today’s turbulent changes in the firms’ environment. The proposed framework consists of several steps in a bottom-up approach, aiming to support the modelling and coordination of the complex and shared business processes in the examined environment.


Author(s):  
Dimitris Folinas ◽  
Tania Pavlou ◽  
Bill Karakostas ◽  
Vicky Manthou

Among different approaches in business processes modelling procedure are those in virtual and dynamic organizational environments. In this paper, a conceptual framework for modelling business processes in Virtual Organizations is suggested, by introducing Web Services technology. Web Services can be the business enabler for the new organizational form, which is particularly well suited to meet the demands arising from today’s turbulent changes in the firms’ environment. The proposed framework consists of several steps in a bottom-up approach, aiming to support the modelling and coordination of the complex and shared business processes in the examined environment.


Author(s):  
Brian H. Cameron

Business process modeling (BPM) is a topic that is generating much interest in the information technology (IT) industry today. Business analysts, process designers, system architects, software engineers, and systems consultants must understand the foundational concepts behind BPM and evolving modeling standards and technologies that have the potential to dramatically change the nature of phases of the systems development life cycle (SDLC). Pareto’s 80/20 rule, as applied to the SDLC, is in the process of being drastically altered. In the past, approximately 20 % of the SDLC was spent on analysis and design activities with the remaining 80 % spent on systems development and implementation (Weske, Goesmann, Holten, & Striemer, 1999). Today, with the introduction of the Business Process Management Initiative (BPMI), Web services, and the services-oriented architecture (SOA), the enterprise SDLC paradigm is poised for a dramatic shift. In this new paradigm, approximately 80 % of the SDLC is spent on analysis and design activities with the remaining 20 % spent of systems development and implementation. Once referred to as workflow and process automation, business process modeling (BPM) has evolved into a suite of interrelated components providing significant business value. Emerging BPM technologies will be the primary vehicle by which current application portfolios transition to service-oriented architectures and Web services (Aversano, & Canfora, 2002). Business Process Management Initiative’s Business Process Modeling Notation (BPMN) subgroup is currently finalizing a standardized notation for business process modeling. Although the notation is still in working draft format, system architects and designers should consider incorporating the concepts of BPM into their current and future systems analysis and design procedures.


Author(s):  
B. Cameron

Business process modeling (BPM) is a topic that is generating much interest in the information technology industry today. Business analysts, process designers, system architects, software engineers, and systems consultants must understand the foundational concepts behind BPM and evolving modeling standards and technologies that have the potential to dramatically change the nature of phases of the systems development life cycle (SDLC). Pareto’s 80/20 rule, as applied to the SDLC, is in the process of being drastically altered. In the past, approximately 20% of the SDLC was spent on analysis and design activities with the remaining 80% spent on systems development and implementation (Weske, Goesmann, Holten, & Striemer, 1999). Today, with the introduction of the Business Process Management Initiative (BPMI), Web services, and the services-oriented architecture (SOA), the enterprise SDLC paradigm is poised for a dramatic shift. In this new paradigm, approximately 80% of the SDLC is spent on analysis and design activities with the remaining 20% spent on systems development and implementation. Once referred to as process or workflow automation, BPM has evolved into a suite of interrelated components for systems analysis, design, and development. Emerging BPM standards and technologies will be the primary vehicles by which current systems portfolios transition to Web services and service-oriented architectures (Aversano, & Canfora, 2002). The Business Process Management Initiative’s business process modeling notation (BPMN) subgroup is currently finalizing a standardized notation for business process modeling. Although the notation is still in working-draft format, system architects and designers should consider incorporating the concepts of BPM into their current and future systems analysis and design procedures.


Author(s):  
Brian H. Cameron

Business process modeling (BPM) is a topic that is generating much interest in the information technology (IT) industry today. Business analysts, process designers, system architects, software engineers, and systems consultants must understand the foundational concepts behind BPM and evolving modeling standards and technologies that have the potential to dramatically change the nature of phases of the systems development life cycle (SDLC). Pareto’s 80/20 rule, as applied to the SDLC, is in the process of being drastically altered. In the past, approximately 20 % of the SDLC was spent on analysis and design activities with the remaining 80 % spent on systems development and implementation (Weske, Goesmann, Holten, & Striemer, 1999). Today, with the introduction of the Business Process Management Initiative (BPMI), Web services, and the services-oriented architecture (SOA), the enterprise SDLC paradigm is poised for a dramatic shift. In this new paradigm, approximately 80 % of the SDLC is spent on analysis and design activities with the remaining 20 % spent of systems development and implementation. Once referred to as workflow and process automation, business process modeling (BPM) has evolved into a suite of interrelated components providing significant business value. Emerging BPM technologies will be the primary vehicle by which current application portfolios transition to service-oriented architectures and Web services (Aversano, & Canfora, 2002). Business Process Management Initiative’s Business Process Modeling Notation (BPMN) subgroup is currently finalizing a standardized notation for business process modeling. Although the notation is still in working draft format, system architects and designers should consider incorporating the concepts of BPM into their current and future systems analysis and design procedures.


Author(s):  
Lai Xu ◽  
Paul de Vrieze

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.


Sign in / Sign up

Export Citation Format

Share Document