Pub Date : 1900-01-01DOI: 10.4018/978-1-60566-288-6.CH012
Combi Carlo, G. Pozzi
Time is a very important dimension of any aspect in human life, affecting also information and information management. As such, time must be dealt with in a suitable way, considering all its facets. The related literature already considered temporal information management from a pure database point of view: temporal aspects (also known as temporalities) of stored information cannot be neglected and the adoption of a suitable database management system (Temporal Database Management System TDBMS) could be helpful. Recently, research of the temporal data management area started to consider business processes, extending and enriching models, techniques, and architectures to suitably manage temporal aspects. According to this scenario, the authors discuss here some of the main advantages achievable in managing temporal aspects and consider temporalities in process models, in exception definition, in the architecture of a Workflow Management System (WfMS), and in the scheduling of tasks and their assignment to agents.
{"title":"Temporalities for Workflow Management Systems","authors":"Combi Carlo, G. Pozzi","doi":"10.4018/978-1-60566-288-6.CH012","DOIUrl":"https://doi.org/10.4018/978-1-60566-288-6.CH012","url":null,"abstract":"Time is a very important dimension of any aspect in human life, affecting also information and information management. As such, time must be dealt with in a suitable way, considering all its facets. The related literature already considered temporal information management from a pure database point of view: temporal aspects (also known as temporalities) of stored information cannot be neglected and the adoption of a suitable database management system (Temporal Database Management System TDBMS) could be helpful. Recently, research of the temporal data management area started to consider business processes, extending and enriching models, techniques, and architectures to suitably manage temporal aspects. According to this scenario, the authors discuss here some of the main advantages achievable in managing temporal aspects and consider temporalities in process models, in exception definition, in the architecture of a Workflow Management System (WfMS), and in the scheduling of tasks and their assignment to agents.","PeriodicalId":206618,"journal":{"name":"Handbook of Research on Business Process Modeling","volume":"29 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"117341343","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1900-01-01DOI: 10.4018/978-1-60566-288-6.CH010
C. Cappiello, B. Pernici
This chapter illustrates the concept of repairable processes and self-healing functionalities and discusses about their design requirements. Self-healing processes are able to monitor themselves, to diagnose the causes of a failure and to recover from the failure, where a failure can be either the inability to provide a given service, or a loss in the service quality. Defining the process as a composition of services, the aim of this chapter is also to provide guidelines for designing services in such a way that they can be easily recovered during their execution. Repair mechanisms are thoroughly described by distinguishing between mechanisms applicable at design time and at run time.
{"title":"Design of Repairable Processes","authors":"C. Cappiello, B. Pernici","doi":"10.4018/978-1-60566-288-6.CH010","DOIUrl":"https://doi.org/10.4018/978-1-60566-288-6.CH010","url":null,"abstract":"This chapter illustrates the concept of repairable processes and self-healing functionalities and discusses about their design requirements. Self-healing processes are able to monitor themselves, to diagnose the causes of a failure and to recover from the failure, where a failure can be either the inability to provide a given service, or a loss in the service quality. Defining the process as a composition of services, the aim of this chapter is also to provide guidelines for designing services in such a way that they can be easily recovered during their execution. Repair mechanisms are thoroughly described by distinguishing between mechanisms applicable at design time and at run time.","PeriodicalId":206618,"journal":{"name":"Handbook of Research on Business Process Modeling","volume":"3 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115486865","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1900-01-01DOI: 10.4018/978-1-60566-288-6.CH014
D. Karastoyanova, Tammo van Lessen, F. Leymann, Zhilei Ma, Joerg Nitzche, B. Wetzstein
Even though process orientation/BPM is a widely accepted paradigm with heavy impact on industry and research the available technology does not support the business professionals’ tasks in an appropriate manner that is in a way allowing processes modeling using concepts from the business domain. This results in a gap between the business people expertise and the IT knowledge required. The current trend in bridging this gap is to utilize technologies developed for the Semantic Web, for example ontologies, while maintaining reusability and flexibility of processes. In this chapter the authors present an overview of existing technologies, supporting the BPM lifecycle, and focus on potential benefits Semantic Web technologies can bring to BPM. The authors will show how these technologies help automate the transition between the inherently separate/detached business professionals’ level and the IT level without the burden of additional knowledge acquisition on behalf of the business professionals. As background information they briefly discuss existing process modeling notations like the Business Process Modeling Notation (BPMN) as well as the execution centric Business Process Execution Language (BPEL), Tammo van Lessen University of Stuttgart, Germany
{"title":"Semantic Business Process Management","authors":"D. Karastoyanova, Tammo van Lessen, F. Leymann, Zhilei Ma, Joerg Nitzche, B. Wetzstein","doi":"10.4018/978-1-60566-288-6.CH014","DOIUrl":"https://doi.org/10.4018/978-1-60566-288-6.CH014","url":null,"abstract":"Even though process orientation/BPM is a widely accepted paradigm with heavy impact on industry and research the available technology does not support the business professionals’ tasks in an appropriate manner that is in a way allowing processes modeling using concepts from the business domain. This results in a gap between the business people expertise and the IT knowledge required. The current trend in bridging this gap is to utilize technologies developed for the Semantic Web, for example ontologies, while maintaining reusability and flexibility of processes. In this chapter the authors present an overview of existing technologies, supporting the BPM lifecycle, and focus on potential benefits Semantic Web technologies can bring to BPM. The authors will show how these technologies help automate the transition between the inherently separate/detached business professionals’ level and the IT level without the burden of additional knowledge acquisition on behalf of the business professionals. As background information they briefly discuss existing process modeling notations like the Business Process Modeling Notation (BPMN) as well as the execution centric Business Process Execution Language (BPEL), Tammo van Lessen University of Stuttgart, Germany","PeriodicalId":206618,"journal":{"name":"Handbook of Research on Business Process Modeling","volume":"4 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125337654","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1900-01-01DOI: 10.4018/978-1-60566-288-6.CH004
M. Kloppmann, Dieter König, Simon Moser
AbstrAct This chapter introduces a set of languages intended to model and run business processes. The Business Process Modeling Notation 1.1 (BPMN) is a notation used to graphically depict business processes. BPMN is able to express choreographies, i.e. the cooperation of separate, auto no mous business processes to jointly achieve a larger scenario. Since BPMN is only a notation, there is no specification for a meta-model that allows rendering BPMN choreographies into an executable form. This chapter describes how the Service Component Architecture (SCA) and the Web Services Business Process Execution Language (WS-BPEL) help to close that gap. BPMN, SCA and WS-BPEL can jointly be used and combined to model, deploy and execute business process choreographies. We will also integrate the related BPEL4People specification, since BPMN allows human 'user tasks', but WS-BPEL focuses only on automated business process. The authors argue that, based on these specifications, the dichotomy between modeling and execution can be addressed efficiently. In this chapter, we will show that a key aspect of the future of Business Process Management is to combine graphical modeling (via BPMN) with a precise specification of an executable business process (via WS-BPEL and related standards).
{"title":"The Dichotomy of Modeling and Execution","authors":"M. Kloppmann, Dieter König, Simon Moser","doi":"10.4018/978-1-60566-288-6.CH004","DOIUrl":"https://doi.org/10.4018/978-1-60566-288-6.CH004","url":null,"abstract":"AbstrAct This chapter introduces a set of languages intended to model and run business processes. The Business Process Modeling Notation 1.1 (BPMN) is a notation used to graphically depict business processes. BPMN is able to express choreographies, i.e. the cooperation of separate, auto no mous business processes to jointly achieve a larger scenario. Since BPMN is only a notation, there is no specification for a meta-model that allows rendering BPMN choreographies into an executable form. This chapter describes how the Service Component Architecture (SCA) and the Web Services Business Process Execution Language (WS-BPEL) help to close that gap. BPMN, SCA and WS-BPEL can jointly be used and combined to model, deploy and execute business process choreographies. We will also integrate the related BPEL4People specification, since BPMN allows human 'user tasks', but WS-BPEL focuses only on automated business process. The authors argue that, based on these specifications, the dichotomy between modeling and execution can be addressed efficiently. In this chapter, we will show that a key aspect of the future of Business Process Management is to combine graphical modeling (via BPMN) with a precise specification of an executable business process (via WS-BPEL and related standards).","PeriodicalId":206618,"journal":{"name":"Handbook of Research on Business Process Modeling","volume":"65 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114965214","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1900-01-01DOI: 10.4018/978-1-60566-288-6.ch006
E. Kindler
AbstrAct There are many different notations and formalisms for modelling business processes and workflows. These notations and formalisms have been introduced with different purposes and objectives. Later, influenced by other notations, comparisons with other tools, or by standardization efforts, these notations have been extended in order to increase expressiveness and to be more competitive. This resulted in an increasing number of notations and formalisms for modelling business processes and in an increase of the different modelling constructs provided by modelling notations, which makes it difficult to compare modelling notations and to make transformations between them. One of the reasons is that, in each notation , the new concepts are introduced in a different way by extending the already existing constructs. In this chapter, the authors go the opposite direction: showing that it is possible to add most of the typical extensions on top of any existing notation or formalism—without changing the formalism itself. Basically, they introduce blocks with some additional attributes defining their initiation and termination behaviour. This serves two purposes: First, it gives a clearer understanding of the basic constructs and how they can be combined with more advanced constructs. Second, it will help combining different modelling notations with each other. Note that, though they introduce a notation for blocks in this chapter, they are not so much interested in promoting this notation here. The notation should just prove that it is possible to separate different issues of a modelling notation, and this way making its concepts clearer and the interchange of models easier. A fully-fledged block notation with a clear and simple interface to existing formalisms is yet to be developed.
{"title":"Modelling Constructs","authors":"E. Kindler","doi":"10.4018/978-1-60566-288-6.ch006","DOIUrl":"https://doi.org/10.4018/978-1-60566-288-6.ch006","url":null,"abstract":"AbstrAct There are many different notations and formalisms for modelling business processes and workflows. These notations and formalisms have been introduced with different purposes and objectives. Later, influenced by other notations, comparisons with other tools, or by standardization efforts, these notations have been extended in order to increase expressiveness and to be more competitive. This resulted in an increasing number of notations and formalisms for modelling business processes and in an increase of the different modelling constructs provided by modelling notations, which makes it difficult to compare modelling notations and to make transformations between them. One of the reasons is that, in each notation , the new concepts are introduced in a different way by extending the already existing constructs. In this chapter, the authors go the opposite direction: showing that it is possible to add most of the typical extensions on top of any existing notation or formalism—without changing the formalism itself. Basically, they introduce blocks with some additional attributes defining their initiation and termination behaviour. This serves two purposes: First, it gives a clearer understanding of the basic constructs and how they can be combined with more advanced constructs. Second, it will help combining different modelling notations with each other. Note that, though they introduce a notation for blocks in this chapter, they are not so much interested in promoting this notation here. The notation should just prove that it is possible to separate different issues of a modelling notation, and this way making its concepts clearer and the interchange of models easier. A fully-fledged block notation with a clear and simple interface to existing formalisms is yet to be developed.","PeriodicalId":206618,"journal":{"name":"Handbook of Research on Business Process Modeling","volume":"986 ","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"120870229","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1900-01-01DOI: 10.4018/978-1-60566-288-6.CH013
K. Ploesser, N. Russell
This chapter discusses the challenges associated with integrating work performed by human agents into automated workflows. It briefly recounts the evolution of business process support systems and concludes that although the support for people integration continues to evolve in these offerings, in broad terms it has not advanced markedly since their inception several decades ago. Nevertheless, people are an integral part of business processes and integration of human work deserves special consideration during process design and deployment. To this end, the chapter explores the requirements associated with modelling human integration and examines the support for people integration offered by WS-BPEL, which (together with its WS-BPEL4People and WS-HumanTask extensions) currently represents the state of the art when defining and implementing business processes in a service-oriented environment. In order to do this, it utilises a common framework for language assessment, the workflow re-source patterns, both to illustrate the capabilities of WS-BPEL and to identify future technical opportunities.
{"title":"The People Integration Challenge","authors":"K. Ploesser, N. Russell","doi":"10.4018/978-1-60566-288-6.CH013","DOIUrl":"https://doi.org/10.4018/978-1-60566-288-6.CH013","url":null,"abstract":"This chapter discusses the challenges associated with integrating work performed by human agents into automated workflows. It briefly recounts the evolution of business process support systems and concludes that although the support for people integration continues to evolve in these offerings, in broad terms it has not advanced markedly since their inception several decades ago. Nevertheless, people are an integral part of business processes and integration of human work deserves special consideration during process design and deployment. To this end, the chapter explores the requirements associated with modelling human integration and examines the support for people integration offered by WS-BPEL, which (together with its WS-BPEL4People and WS-HumanTask extensions) currently represents the state of the art when defining and implementing business processes in a service-oriented environment. In order to do this, it utilises a common framework for language assessment, the workflow re-source patterns, both to illustrate the capabilities of WS-BPEL and to identify future technical opportunities.","PeriodicalId":206618,"journal":{"name":"Handbook of Research on Business Process Modeling","volume":"8 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134509912","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1900-01-01DOI: 10.4018/978-1-60566-288-6.CH016
H. Mourão, P. Antunes
In this chapter the authors propose a solution to handle unexpected exceptions in WfMS. They characterize these events deeply and recognize that some of them require immediate reaction and users can not plan their response in advance. Current approaches that handle unexpected exceptions are categorized by their resilience property and it is identified that supporting unstructured activities becomes critical to react to these events. Their proposed system is able to change its behaviour from supporting structured activities to supporting unstructured activities and back to its original mode. They also describe how the system was implemented and we discuss a concrete scenario where it was tested.
{"title":"Using WfMS to Support Unstructured Activities","authors":"H. Mourão, P. Antunes","doi":"10.4018/978-1-60566-288-6.CH016","DOIUrl":"https://doi.org/10.4018/978-1-60566-288-6.CH016","url":null,"abstract":"In this chapter the authors propose a solution to handle unexpected exceptions in WfMS. They characterize these events deeply and recognize that some of them require immediate reaction and users can not plan their response in advance. Current approaches that handle unexpected exceptions are categorized by their resilience property and it is identified that supporting unstructured activities becomes critical to react to these events. Their proposed system is able to change its behaviour from supporting structured activities to supporting unstructured activities and back to its original mode. They also describe how the system was implemented and we discuss a concrete scenario where it was tested.","PeriodicalId":206618,"journal":{"name":"Handbook of Research on Business Process Modeling","volume":"25 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122396646","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1900-01-01DOI: 10.4018/978-1-60566-288-6.CH020
Guido Governatori, S. Sadiq
It is a typical scenario that many organisations have their business processes specified independently of their business obligations (which includes contractual obligations to business partners, as well as obligations a business has to fulfil against regulations and industry standards). This is because of the lack of guidelines and tools that facilitate derivation of processes from contracts but also because of the traditional mindset of treating contracts separately from business processes. This chapter will provide a solution to one specific problem that arises from this situation, namely the lack of mechanisms to check whether business processes are compliant with business contracts. The chapter begins by defining the space for business process compliance and the eco-system for ensuring that process are compliant. The key point is that compliance is a relationship between two sets of specifications: the specifications for executing a business process and the specifications regulating a business. The central part of the chapter focuses on a logic based formalism for describing both the semantics of normative specifications and the semantics of compliance checking procedures.
{"title":"The Journey to Business Process Compliance","authors":"Guido Governatori, S. Sadiq","doi":"10.4018/978-1-60566-288-6.CH020","DOIUrl":"https://doi.org/10.4018/978-1-60566-288-6.CH020","url":null,"abstract":"It is a typical scenario that many organisations have their business processes specified independently of their business obligations (which includes contractual obligations to business partners, as well as obligations a business has to fulfil against regulations and industry standards). This is because of the lack of guidelines and tools that facilitate derivation of processes from contracts but also because of the traditional mindset of treating contracts separately from business processes. This chapter will provide a solution to one specific problem that arises from this situation, namely the lack of mechanisms to check whether business processes are compliant with business contracts. The chapter begins by defining the space for business process compliance and the eco-system for ensuring that process are compliant. The key point is that compliance is a relationship between two sets of specifications: the specifications for executing a business process and the specifications regulating a business. The central part of the chapter focuses on a logic based formalism for describing both the semantics of normative specifications and the semantics of compliance checking procedures.","PeriodicalId":206618,"journal":{"name":"Handbook of Research on Business Process Modeling","volume":"2 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127762962","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1900-01-01DOI: 10.4018/978-1-60566-288-6.CH005
C. Ouyang, M. Adams, A. Hofstede
Due to the absence of commonly accepted conceptual and formal foundations for workflow management, and more generally Business Process Management (BPM), a plethora of approaches to process modelling and execution exists both in academia and in industry. The introduction of workflow patterns provided a deep and language independent understanding of modelling issues and requirements encountered in business process specification. They provide a comparative insight into various approaches to process specification and serve as guidance for language and tool development. YAWL (Yet Another Workflow Language) is a novel and formally defined workflow language based on workflow patterns and Petri nets, thus leveraging off both practical and theoretical insights in the field of BPM. This chapter provides an overview of this language and its corresponding open source support environment.
由于工作流管理和更普遍的业务流程管理(BPM)缺乏普遍接受的概念和正式基础，学术界和工业界都存在过多的流程建模和执行方法。工作流模式的引入提供了对业务流程规范中遇到的建模问题和需求的深入且独立于语言的理解。它们提供了对过程规范的各种方法的比较见解，并作为语言和工具开发的指导。YAWL (Yet Another Workflow Language)是一种新颖的、正式定义的工作流语言，它基于工作流模式和Petri网，从而充分利用了BPM领域的实践和理论见解。本章概述了这种语言及其相应的开源支持环境。
{"title":"Yet Another Workflow Language","authors":"C. Ouyang, M. Adams, A. Hofstede","doi":"10.4018/978-1-60566-288-6.CH005","DOIUrl":"https://doi.org/10.4018/978-1-60566-288-6.CH005","url":null,"abstract":"Due to the absence of commonly accepted conceptual and formal foundations for workflow management, and more generally Business Process Management (BPM), a plethora of approaches to process modelling and execution exists both in academia and in industry. The introduction of workflow patterns provided a deep and language independent understanding of modelling issues and requirements encountered in business process specification. They provide a comparative insight into various approaches to process specification and serve as guidance for language and tool development. YAWL (Yet Another Workflow Language) is a novel and formally defined workflow language based on workflow patterns and Petri nets, thus leveraging off both practical and theoretical insights in the field of BPM. This chapter provides an overview of this language and its corresponding open source support environment.","PeriodicalId":206618,"journal":{"name":"Handbook of Research on Business Process Modeling","volume":"26 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114742971","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1900-01-01DOI: 10.4018/978-1-60566-288-6.CH024
Laura Sánchez-González, Andrea Delgado, F. Ruiz, Félix García, M. Piattini
AbstrAct The underlying premise of process management is that the quality of products and services is largely determined by the quality of the processes used to develop, deliver and support them. A concept which has been closely related to process quality over the last few years is the maturity of the process and it is important to highlight the current proposal of Business Process Maturity Model (BPMM), which is based on the principles, architecture and practices of CMM and CMMI for Software and describes the essential practices for the development, preparation, deployment, operations and support of product and service offers from determining customer needs. When maturity models are in place, it is important not to forget the important role that measurement can play, being essential in organizations which intend to reach a high level in the maturity in their processes. This is demonstrated by observing the degree of importance that measurement activities have in maturity models. This chapter tackles the Business Process Maturity Model and the role that business measurement plays in the context of this model. In 533 Measurement and Maturity of Business Processes addition, a set of representative business process measures aligned with the characteristics of BPMM are introduced which can guide organizations to support the measurement of their business processes depending on their maturity.
{"title":"Measurement and Maturity of Business Processes","authors":"Laura Sánchez-González, Andrea Delgado, F. Ruiz, Félix García, M. Piattini","doi":"10.4018/978-1-60566-288-6.CH024","DOIUrl":"https://doi.org/10.4018/978-1-60566-288-6.CH024","url":null,"abstract":"AbstrAct The underlying premise of process management is that the quality of products and services is largely determined by the quality of the processes used to develop, deliver and support them. A concept which has been closely related to process quality over the last few years is the maturity of the process and it is important to highlight the current proposal of Business Process Maturity Model (BPMM), which is based on the principles, architecture and practices of CMM and CMMI for Software and describes the essential practices for the development, preparation, deployment, operations and support of product and service offers from determining customer needs. When maturity models are in place, it is important not to forget the important role that measurement can play, being essential in organizations which intend to reach a high level in the maturity in their processes. This is demonstrated by observing the degree of importance that measurement activities have in maturity models. This chapter tackles the Business Process Maturity Model and the role that business measurement plays in the context of this model. In 533 Measurement and Maturity of Business Processes addition, a set of representative business process measures aligned with the characteristics of BPMM are introduced which can guide organizations to support the measurement of their business processes depending on their maturity.","PeriodicalId":206618,"journal":{"name":"Handbook of Research on Business Process Modeling","volume":"23 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"120962897","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
京公网安备 11010802042870号
京ICP备2023020795号-1
扫码关注我们
求助内容：
应助结果提醒方式：