The Changing Nature of Business Process Modeling

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):  
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):  
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.


1995 ◽  
Vol 04 (02n03) ◽  
pp. 145-164 ◽  
Author(s):  
VOLKER GRUHN

Most of today’s approaches to business process engineering (also called business process management) start from an activity-centered perspective. They describe activities to be carried out within a business process and their relationships, but they usually pay little attention to the objects manipulated within processes. In this article, we discuss an approach to business process modeling, model analysis, and business process enaction (also called workflow management) which is based on data modeling, activity modeling, and organization modeling. In fact, the ℒeu approach to business process management considers data models (describing types of objects to be manipulated in a business process and their relationships), activity models (describing activities to be carried out in a business process), and organization models (describing organizational entities involved in a business process) as separate, but equally important, facets of business processes.


2010 ◽  
Vol 450 ◽  
pp. 413-416
Author(s):  
Yong Ping Hao ◽  
Xiao Lei Xu ◽  
Wei Ping Shao ◽  
Peng Fei Zeng

Through the analysis of the execution and dispatching principle of the Petri net, the business process management mode based on Petri net is proposed. We merge the place node and the transition node, and reside the token in the node. The only token in process instances and the sub-token in parallel process are introduced, which can avoid conflicts caused by multi-tokens. The business process model for the drawings design and approval is established, and it is verified by the workflow modeling system.


Author(s):  
Jan Mendling

This chapter provides an overview of business process management and business process modeling. We approach business process management by giving a historical classification of seminal work, and define it by the help of the business process management life cycle. Business process models play an important role in this life cycle, in particular, if information systems are used for executing processes. We deduct a definition for business process modeling based on a discussion of modeling from a general information systems point of view. In the following, we detail business process modeling techniques, in particular, modeling languages and modeling procedures for business process modeling. Finally, we discuss some future trends with a focus on the business process execution language for Web services (BPEL), and conclude the chapter with a summary. The chapter aims to cover business process modeling in a comprehensive way such that academics and practitioners can use it as a reference for identifying more specialized works.


Author(s):  
Gang He ◽  
Gang Xue ◽  
Kui Yu ◽  
Shaowen Yao

Business process modeling is that make use of graphics, formulas, tables and text to describe the characteristics of business process, and answer why to do, what to do, how to do. Business process modeling is the foundation of business process management. Implementation of business process management can improve the process and enhance competitiveness. In this chapter, the authors attempt to find current business process modeling methods’ advantages and disadvantages by analyzing their feature and comparison of based on series important evaluation criteria. The goal is that it provides a reference to business process modeling methods in practice.


Author(s):  
Jan Mendling

This chapter provides an overview of business process management and business process modeling. We approach business process management by giving a historical classification of seminal work, and define it by the help of the business process management life cycle. Business process models play an important role in this life cycle, in particular, if information systems are used for executing processes. We deduct a definition for business process modeling based on a discussion of modeling from a general information systems point of view. In the following, we detail business process modeling techniques, in particular, modeling languages and modeling procedures for business process modeling. Finally, we discuss some future trends with a focus on the business process execution language for Web services (BPEL), and conclude the chapter with a summary. The chapter aims to cover business process modeling in a comprehensive way such that academics and practitioners can use it as a reference for identifying more specialized works.


2018 ◽  
Vol 7 ◽  
pp. 166
Author(s):  
Marino Luiz Eyerkaufer ◽  
Ana Carolina Sedlacek

O Business Process Management (BPM), denominado no Brasil de gestão de processos de trabalho é considerado um modelo direcionador a estratégia organizacional que combina processos, pessoas e tecnologia para conectar estratégias de negócio ao foco do cliente. A gestão de processos de riscos e desastres, por sua vez, carece de colaboração intersetorial e comunitária, para o qual a coordenação demanda de uma governança otimizada a fim de promover essa integração entre mecanismos e instituições. O objetivo do presente trabalho é apresentar a gestão e modelagem de processos colaborativos de trabalho para a governança em riscos e desastres a nível local, para o qual apresenta-se em seu desenvolvimento, processos de trabalho na visão do Business Process Modeling Notation (BPMN), utilizando para sua modelagem o Software Bizagi Modeler. Para isso, uma análise de cenário local foi utilizada, no caso, a cidade de Ibirama (SC). Conclui-se ao final do estudo que os desafios para desenvolver processos de trabalho em gestão de riscos e desastres pode ter dimensões muito próximas das dificuldades atuais de coordenação encontradas ao nível local, o que reforça a importância de desenvolver os processos de trabalho que favorecem ao alinhamento organizacional e a definição clara dos papeis e responsabilidades de cada um dos envolvidos em cada processo, favorecendo à sua governança. 


Sign in / Sign up

Export Citation Format

Share Document