Search results

The techniques for representing and analyzing business processes are referred to as business process modeling. Many business process modeling methods and their associated tools have been used to capture the characteristics of business processes. However, most methods view business processes from different perspectives and have different features and capabilities. Thus, an important research question is how process designers should select appropriate modeling methods for their BPR initiatives. In this paper, we propose a framework for selecting business process modeling methods based on modeling objectives. This framework can serve as the basis for evaluating modeling methods and generating selection procedures. A general selection procedure is also described. We use an expense claim process as an example to illustrate the application of the selection procedure.

This second part of the paper summarizes typical pitfalls as they can be observed in larger process modeling projects.

The identified pitfalls have been derived from a series of focus groups and semi‐structured interviews with business process analysts and managers of process management and modeling projects.

The article continues the discussion of the first part. It covers issues related to tools and related requirements (7‐10), the practice of modeling (11‐16), the way we design to‐be models (17‐19), and how we deal with success of modeling and maintenance issues (19‐21). Potential pitfalls related to strategy and governance (1‐3) and the involved stakeholders (4‐6) were discussed in the first part of this paper.

This paper is a personal viewpoint, and does not report on the outcomes of a structured qualitative research project.

The provided list of intotal 22 pitfalls increases the awareness for the main challenges related to process modeling and helps to identify common mistakes.

This paper is one of the very few contributions in the area of challenges related to process modeling.

This paper summarizes typical pitfalls as they can be observed in larger process modeling projects.

The identified pitfalls have been derived from a series of focus groups and semi‐structured interviews with business process analysts and managers of process management and modeling projects.

The paper provides a list of typical characteristics of unsuccessful process modeling. It covers six pitfalls related to strategy and governance (1‐3) and the involved stakeholders (4‐6). Further issues related to tools and related requirements (7‐10), the practice of modeling (11‐16), the way we design to‐be models (17‐19), and how we deal with success of modeling and maintenance issues (19‐21) will be discussed in the second part of this paper.

This paper is a personal viewpoint, and does not report on the outcomes of a structured qualitative research project.

The provided list of total 22 pitfalls increases the awareness for the main challenges related to process modeling and helps to identify common mistakes.

This paper is one of the very few contributions in the area of challenges related to process modeling.

One way to improve the quality of business and software processes is to make them compliant with standard. This paper seeks to explore the suitability of the BPMN and the teaching method for process modeling, which uses SEI CMMI‐SW standard as input and produces software process models as output.

The research approach consists of two parts. First, the students' responses during practical lectures of process modeling were gathered and studied. Then, the teaching process was modified and students' responses were studied again. The second part involves the survey about students' attitude towards BPMN usability and ease of use.

There are two key findings of the study. First, using the SEI CMMI‐SW standard in early phases of software process modeling is not very effective, because it overloads the students with abstract requirements, which are included in the standard. The more effective way is to use the standard in later phases of process modeling, in the phase of assessment and improvement of the process model. The second key finding is that there is a positive attitude among students towards BPMN usage for process modeling.

There is no evidence that this teaching approach can be generalized beyond the population of information science students and academic environment.

The improved teaching method for business and software process modeling can be used in similar environments (practical lectures of process modeling). Although there is no evidence, quality managers from organizations can also benefit from the lesson learned and avoid a less suitable process‐modeling approach.

The paper is useful to all roles in education and businesses, who deal with process models and standards (teachers, business and software analysts, quality managers, process designers).

Process models are a valuable tool in the design and configuration of enterprises. However, current modeling techniques have shortcomings that prevent them from fully supporting the analysis required to design an enterprise. This is especially true when considering the needs of modeling highly distributed and temporary multi‐company enterprises such as fractal or virtual enterprises. This paper presents a modeling scheme that supports a process‐centered approach to the analysis and design of both conventional and extended enterprises. Using a holon‐based approach to model the components of an enterprise, it allows for the development of integrated business rule, activity, resource, business process, and organizational views of the enterprise using the IDEF suite of modeling methods. The scheme is built around a central IDEF5 model of the enterprise from which the other views are extracted. The paper also describes the technique for developing an enterprise model using the scheme.

Process modeling is a complex organizational task that requires many iterations and communication between the business analysts and the domain specialists. The challenge of process modeling is exacerbated, when the process of modeling has to be performed in a cross‐organizational, distributed environment. This paper aims to suggest a three‐dimensional (3D) environment for collaborative process modeling, using virtual world technology.

The paper suggests a new collaborative process modeling approach based on virtual world technology. It describes the design of an innovative prototype collaborative process modeling approach, implemented as a 3D Business Process Modeling Notation (BPMN) modeling environment in Second Life. We use a case study to evaluate the suggested approach.

Based on a case study application, the paper shows that our approach increases user empowerment and adds significantly to the collaboration and consensual development of process models even when the relevant stakeholders are geographically dispersed.

The paper presents design work and a case study. More research is needed to more thoroughly evaluate the presented approach in a variety of real‐life process modeling settings.

The research outcomes as design artifacts are directly available and applicable by business process management professionals and can be used by business, system and process analysts in real‐world practice.

This research is the first reported attempt to develop a process modeling approach on the basis of virtual world technology. It describes a novel and innovative 3D BPMN modeling environment in Second Life.

Service‐oriented architecture is becoming increasingly important for healthcare delivery as it assures seamless integration internally between various teams and departments, and externally between healthcare organizations and their partners. In order to make healthcare more efficient and effective, we need to understand and evaluate its processes, and one way of achieving that is through process modeling. Modeling healthcare processes within a service‐oriented environment opens up new perspectives and raises challenging questions. The purpose of this paper is to investigate one of these questions, namely the suitability of web service orchestration and choreography, two closely related but fundamentally different methodologies for modeling web service‐based healthcare processes.

The authors use a case‐based approach that first developed a set of 12 features for modeling healthcare processes and then used the features to compare orchestration and choreography for modeling part of the scheduled workflow.

The findings show that neither methodology can, by itself, meet all healthcare modeling requirements in the context of the case study. The appropriate methodology must be selected after consideration of the specific modeling needs. The authors identified usability, capabilities, and evolution as three key considerations to assist with selection of a methodology for healthcare process modeling. Further, sometimes one method will not meet all modeling needs and hence the authors recommend combining the two methodologies in order to harness the benefits of modeling healthcare processes in a service‐oriented environment.

Although literature exists on process modeling of web services for healthcare, there are no criteria describing necessary features for micro‐level modeling, nor is there a comparison of the two leading service composition methodologies within the healthcare context. This paper provides some necessary formalization for process modeling in healthcare.

Business process (BP) reengineering is defined as reinventing BPs either structurally or technically to achieve dramatic improvements in performance. In any business process reengineering (BPR) project, process modeling is used to reason about problems found in existing (as-is) process and helps to design target (to-be) process. BP model notation is a widely accepted standard for process modeling. “Expressiveness” and “missing formal semantics” are two problems reported to its modeling practices. In existing studies, solutions to these problems are also proposed but still have certain limitations. The paper aims to discuss this issue.

In proposed methodology, a meta-model is formally defined that is composed of commonly used modeling elements and their well-formedness rules to check for syntactic and structural correctness of process models. Proposed solution also check semantics of process models and allows to compare as-is and to-be process models for gap identification which is another important aspect of BPR. To achieve the first goal, Z specification is used to provide formal specifications of modeling constructs and their rules and Z3 (an SMT solver) is used for comparisons and verifying properties.

Proposed method addresses both “expressiveness” and “missing formal semantics” of BPR models. The results of its evaluation clearly indicate that using formally specified meta-model, BPR model is syntactically and structurally correct. Moreover, formal modeling of BPs in Z3 helped to compare processes and to check control flow properties.

Although the proposed method is tested on an example that is widely used in BPR literature, the example is only covering modeling elements which are part of the proposed subset and are reported in literature as frequently used modeling elements. A separate detailed study is required to test it on more complex systems.

Specifying process models using Z specification and Z3 solver requires certain expertise.

The proposed method adds value to BPR body of knowledge as it proposes a method to ensure structural and syntactic correctness of models, highlighting the importance of verifying run time properties and providing a direction toward comparing process models for gap analysis.

The purpose of this paper is to conceptualize data quality (DQ) in the context of business process management and to propose a DQ oriented approach for business process modeling. The approach is based on key concepts and metrics from the data quality management domain and supports decision‐making in process re‐design projects on the basis of process models.

The paper applies a design oriented research approach, in the course of which a modeling method is developed as a design artifact. To do so, method engineering is used as a design technique. The artifact is theoretically founded and incorporates DQ considerations into process re‐design. Furthermore, the paper uses a case study to evaluate the suggested approach.

The paper shows that the DQ oriented process modeling approach facilitates and improves managerial decision‐making in the context of process re‐design. Data quality is considered as a success factor for business processes and is conceptualized using a rule‐based approach.

The paper presents design research and a case study. More research is needed to triangulate the findings and to allow generalizability of the results.

The paper supports decision‐makers in enterprises in taking a DQ perspective in business process re‐design initiatives.

The paper reports on integrating DQ considerations into business process management in general and into process modeling in particular, in order to provide more comprehensive decision‐making support in process re‐design projects. The paper represents one of the first contributions to literature regarding a contemporary phenomenon of high practical and scientific relevance.

The purpose of this paper is to introduce a multi-level framework for semantic modeling (MFSM) based on four signification levels: objects, classes of entities, instances and domains. In addition, four fundamental propositions of the signification process underpin these levels, namely, classification, decomposition, instantiation and contextualization.

The deductive approach guided the design of this modeling framework. The authors empirically validated the MFSM in two ways. First, the authors identified the signification processes used in articles that deal with semantic modeling. The authors then applied the MFSM to model the semantic context of the literature about lean manufacturing, a field of management science.

The MFSM presents a highly consistent approach about the signification process, integrates the semantic modeling literature in a new and comprehensive view; and permits the modeling of any semantic context, thus facilitating the development of knowledge organization systems based on semantic search.

The use of MFSM is manual and, thus, requires a considerable effort of the team that decides to model a semantic context. In this paper, the modeling was generated by specialists, and in the future should be applicated to lay users.

The MFSM opens up avenues to a new form of classification of documents, as well as for the development of tools based on the semantic search, and to investigate how users do their searches.

The MFSM can be used to model archives semantically in public or private settings. In future, it can be incorporated to search engines for more efficient searches of users.

The MFSM provides a new and comprehensive approach about the elementary levels and activities in the process of signification. In addition, this new framework presents a new form to model semantically any context classifying its objects.