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.

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.

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.

Among different BPR strategies and methodologies, one common feature is to capture existing processes and represent new processes adequately. Business process modeling plays a crucial role on such effort. This paper proposes a generic structure for modeling business processes in order to capture essential concepts of business process and represent them structurally. The generic structure possesses two main features suitable for business process modeling: one is that it can represent a business process in various concerns and multiple layers of abstraction, and the other is that it lowers the barriers between process representation and model analysis by embedding verification and validation with the model. The generic modeling method is illustrated by an order fulfillment process in supply chain networks.

From knowledge management point of view, business process models and ontologies are two essential knowledge artifacts for organizations that consume similar information sources. In this study, the PROMPTUM method for integrated process modeling and ontology development that adheres to well-established practices is presented. The method is intended to guide practitioners who develop both ontologies and business process models in the same or similar domains.

The method is supported by a recently developed toolset, which supports the modeling of relations between the ontologies and the labels within the process model collections. This study introduces the method and its companion toolset. An explanatory study, that includes two case studies, is designed and conducted to reveal and validate the benefits of using the method. Then, a follow-up semi-structured interview identifies the perceived benefits of the method.

Application of the method revealed several benefits including the improvements observed in the consistency and completeness of the process models and ontologies. The method is bringing the best practices in two domains together and guiding the use of labels within process model collections in ontology development and ontology resources in business process modeling.

The proposed method with its tool support is a pioneer in enabling to manage the labels and terms within the labels in process model collections consistently with ontology resources. Establishing these relations enables the definition and management of process model elements as resources in domain ontologies. Once the PROMPTUM method is utilized, a related resource is managed as a single resource representing the same real-world object in both artifacts. An explanatory study has shown that improvement in consistency and completeness of process models and ontologies is possible with integrated process modeling and ontology development.

Business process models, while primarily intended for process documentation, communication, and improvement, are often also used as input for developing process-oriented software systems (Ouyang et al., 2009). Ensuring correctness, handling complexity, and improving reusability and maintainability of business process models are important for all these goals. The purpose of this paper is to propose an aspect-oriented business process modeling and correctness controlling method based on Petri nets to satisfy these goals.

The aspect-oriented paradigm provides a proper mechanism to modularization, and thus reduces the complexity of models, and also improves reusability and maintainability. However, weaving aspects into base processes may bring in mistakes or errors. To ensure correctness of modeling, this paper presents a formal approach to modeling aspect-oriented business processes and a method to ensure modeling correctness. Petri net is used as the process modeling language and its analysis techniques are applied to analyze the correctness of modeling. Two types of correctness, specifically, aspect-aspect correctness and base-aspect correctness are analyzed. A real banking process model is studied systematically in the case study to evaluate the approach and the performance assessments are conducted to show the cost and effect of the approach.

Designing aspect-oriented business process models help organizations reusing the model elements to reduce redundancy of their model repository, improving their maintainability, and supporting them to adapt to the changes of business requirements with flexible modeling. It is important to stress that the correctness of business process modeling is important in ensuring the quality of the models, especially in the safety-critical business domains, such as financial business domain.

In this paper, separation of concerns is used to separate the cross-cutting activities and core activities in accordance with the different functions of these activities, and an approach to modeling aspect-oriented business processes is proposed. First, the cross-cutting activities are encapsulated as aspects, while core business activities are modeled as base processes. Then, according to the correctness requirements of business process models, based on the weaving mechanisms of aspect-oriented approach, weaving correctness is defined. Weaving correctness controlling methods between multi-aspects and between aspects and base processes are designed. Errors or mistakes of aspect-oriented business process modeling are prevented during the procedure of modeling to ensure error-free business process modeling.

The purpose of this chapter is to introduce the concept of public business models and develop a theory for the process of developing and managing public business models.

This research synthesizes insights from various fields into a set of theoretical ideas that lay out what public business models are, to what extent they differ from commercial/industrial business models, and how they are developed and managed by public entrepreneurs.

Developing and managing a business model is an entrepreneurial task that has been missing from the public entrepreneurship literature. Public entrepreneurs perform these tasks using public and private resources, leveraging public institutional systems, and developing capabilities that differ in several dimensions from private entrepreneurs due to the nature of public goods and existence of quasi-markets where public business models are developed and used.

This chapter opens new avenues for research in public entrepreneurship by suggesting that (1) public business models form the foundation of public entrepreneurship, (2) public business models differ from commercial business models not in their functionality but rather in their scope and design, and (3) public business models co-evolve with public institutions to maintain their legitimacy and value creation potential.

This chapter equips public entrepreneurs with new insights into enterprising behaviors and the dynamism of value creation and capture in public ventures.

The current study represents the first attempt to directly incorporate the notion of business models into the public entrepreneurship literature.

An issue of managing a business (unit) as a whole successfully is perceived to belong to the fundamental issues within strategic management. This paper proposes that a business unit can be managed successfully in short and longer term in its focal contexts as a set of three recursive, competence-based, and process-based systems. Many elements of Stafford Beer's (1985) viable system model along the key competence-based theoretical bases are applied to this system design task. The outcome is an ideal, recursive template for advancing competence-based business management (CBBM) and its conceptual modeling. It is assumed that it is possible to design a business unit as a viable system that is capable of sustaining a separate existence at only three levels of hierarchy, as part of single or multi-business firms. Business-process models and their redesign processes are chosen as the 2nd-order, focal system which produces a business unit's competitiveness and solves longitudinal CBBM problems. One level of recursion down includes a unit's value creating, capturing, releveraging, and respective processes that enable to solve cross-sectional problems. One level of recursion up includes a unit's existential foresights and their crafting processes that solve existential problems. Recursivity is designed inside each system in terms of three kinds of subsystems for (a) primary value releveraging, process-model redesign, and business-foresight crafting, (b) the management of varieties in releveraging, modeling, and foreseeing, and (c) the monitoring and probing of all three systems. Systemic competences are incorporated inside respective systems. Such competences possess three flexibilities of absorption, attenuation, and amplification. At each level of recursion, a competence-based process is a unit of conceptual modeling of CBBM. A business unit is defined as a set of its purposeful processes. No thing or one is left outside them. Viability is ensured by real-time interaction and the 1st-, 2nd-, and 3rd-order feedback loops between three systems. Overall, the suggested, recursive, 3-system template is intended to serve future, compatible modeling efforts among interested, pioneering firms, professional CBBM modelers, scholars, and alike. Its novelty is produced by choosing and designing the CBBM modeling as the 2nd-order system-in-focus with its two recursions, by designing and using systemic, competence-based processes as the units of conceptualization, and by choosing and drawing the figures to illustrate the 3-system template in the ways that allow also business managers comprehend and apply the suggested template in practice.

An enterprise application can be quickly built up by service composition. Business process composition is the essence of service composition. To build up such service‐oriented enterprise application, the developer needs an integrated design tool. The purpose of this paper is to present and integrated business‐process driven design for service‐oriented enterprise applications.

In the approach, there are three phases: business environment modeling, business process modeling, and script compiling. Business environment modeling adopts a new modeling technique which combines both the advantages of use case diagram and sequence diagram in UML. Business process modeling builds a concrete model according to business environment modeling. The mapping algorithms from business environment model to business process model are also given. At script compiling phase, the business process model is compiled into several deployable files. And then the paper presents a demonstration which shows how to apply our approach to developing a supply chain management system for the retail industry.

The analysis shows that the approach can meet the requirement of service‐composition. The approach can help business expert freely express their business requirement at business environment modeling phase; and help IT expert quickly design service‐oriented enterprise application according to business environment model at business process modeling phase.

This paper proposes a novel integrated approach to model and implement business‐process driven service composition, and presents an integrated tool based Eclipse to implement this approach.

The purpose of this paper is to describe and analyze the benefits of the application of a requirements engineering framework to assist Enterprise Resource Planning (ERP) development. This framework combines the technology-driven and the process-driven approaches for requirements analysis and implementation. Specific business process modeling methods enhance the framework and assist the formulation of the functional specifications of the ERP system and the management of requirements.

A case study strategy was chosen as the most appropriate method to answer the research question and test the theoretical propositions. The case study’s unit of analysis is a Greek manufacturing company and its ERP implementation project. A requirements engineering framework enhanced with business process modeling methods was applied and the results were evaluated using metrics for ERP implementation success. Data were collected using multiple sources of evidences, including interviews with various stakeholders, structured questionnaires, direct observations, vendors’ functionality papers and company’s documentation.

This study proves that the configuration of ERP’s reference models together with the adjustments of organization’s processes, provided through a structured requirements engineering framework can lead to reliable functional specifications, a smooth transition to an ERP system and, eventually, to successful ERP implementation, concerning its alignment with requirements.

A single case study is conducted in a typical manufacturing company, providing opportunities for further research in other industries, testing in parallel well-defined requirements and other success factors for ERP implementation.

The paper fulfils the identified needs for applied methodologies and frameworks for requirements engineering which can assist successful ERP implementations.