scholarly journals Realizing Automatic Conversion of Service Models into Web Services towards Dynamic and Adaptive Business Process Management

2011 ◽  
Author(s):  
Teshome Bekele
Keyword(s):  
Web Services ◽  
Business Process ◽  
Business Process Management ◽  
Process Management ◽  
Service Models

Web services and business process management

2002 ◽  
Vol 41 (2) ◽  
pp. 198-211 ◽  
Author(s):  
F. Leymann ◽  
D. Roller ◽  
M.-T. Schmidt
Keyword(s):  
Web Services ◽  
Business Process ◽  
Business Process Management ◽  
Process Management

Enabling Technology: Ein J2EE-basiertes Business Process Management System zur Ausführung von BPEL- und Web Service-basierten Geschäftsprozessen (Enabling Technology: A J2EE based Business Process Management System for BPEL and Web services based business processes)

2004 ◽  
Vol 46 (4) ◽  
Author(s):  
Matthias Kloppmann ◽  
Dieter König ◽  
Frank Leymann ◽  
Gerhard Pfau ◽  
Dieter Roller
Keyword(s):  
Web Services ◽  
Business Process ◽  
Management System ◽  
Business Process Management ◽  
Process Management ◽  
Business Processes ◽  
Workflow Management ◽  
Workflow Management System ◽  
Enabling Technology ◽  
Business Process Execution

ZusammenfassungMithilfe von Web Services und BPEL (Business Process Execution Language for Web Services) können Geschäftsprozesse und deren Interaktion mit verschiedenen Partnern beschrieben werden. Zur Ausführung der Geschäftsprozesse finden Workflow Management Systeme Verwendung. Dieser Artikel beschäftigt sich, basierend auf den Grundlagen von Web Services und BPEL, mit der Implementierung eines Workflow Management Systems. Um den Anforderungen der Geschäftswelt zu genügen, muss ein Workflow Management System sowohl langlaufende, unterbrechbare als auch kurzlaufende Geschäftsprozesse mit ihren unterschiedlichen Quality-of-Service Eigenschaften unterstützen. Die Systeme müssen robust sein, sicher und hoch verfügbar. Der Artikel beschreibt die Implementierung eines J2EE-basierten Workflow Management System, das diesen Anforderungen entspricht. Dabei wird auf die Verwendung von Message Queuing Systemen und Datenbanken eingegangen, ebenso wie auf die Integration in einen Standard Application Server und die Verwendung dort zur Verfügung stehender Transaction Manager, EJB Container, People Directory und Deployment Infrastruktur.

The Changing Nature of Business Process Modeling

2009 ◽  
pp. 45-56
Author(s):  
Brian H. Cameron
Keyword(s):  
Web Services ◽  
Business Process ◽  
Process Modeling ◽  
Business Process Management ◽  
Process Management ◽  
Business Process Modeling ◽  
Systems Development ◽  
New Paradigm ◽  
Analysis And Design ◽  
Design Activities

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.

The Changing Nature of Business Process Modeling

2007 ◽  
pp. 119-137
Author(s):  
B. Cameron
Keyword(s):  
Web Services ◽  
Business Process ◽  
Process Modeling ◽  
Systems Analysis ◽  
Business Process Management ◽  
Process Management ◽  
Business Process Modeling ◽  
Systems Development ◽  
Analysis And Design ◽  
Design Activities

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.

Business process management: Where business processes and web services meet

2007 ◽  
Vol 61 (1) ◽  
pp. 1-5 ◽  
Author(s):  
Wil M.P. van der Aalst ◽  
Boualem Benatallah ◽  
Fabio Casati ◽  
Francisco Curbera ◽  
Eric Verbeek
Keyword(s):  
Web Services ◽  
Business Process ◽  
Business Process Management ◽  
Process Management ◽  
Business Processes

The Changing Nature of Business Process Modeling

2010 ◽  
pp. 42-53
Author(s):  
Brian H. Cameron
Keyword(s):  
Web Services ◽  
Business Process ◽  
Process Modeling ◽  
Business Process Management ◽  
Process Management ◽  
Business Process Modeling ◽  
Systems Development ◽  
New Paradigm ◽  
Analysis And Design ◽  
Design Activities

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.

Sign in / Sign up

Export Citation Format

Share Document