Watch here: Notations of Business Process Modeling. Simple introduction for any audience. Damrau shows how she uses business process modeling methodology BPM to meet the requirements of current and future content. This includes all task types whether they are a manual or system enabled. See here: Business Process Modeling.
Ready, here are 15 materials of different levels of depth for consultation and learning about process modeling in PDFs, e-books, videos, and slideshows! Enjoy this business process modeling tutorial! Your email address will not be published. Post Comment. Process Modeling.
Each material has different levels of complexity and is divided into 3 categories: Business process modeling tutorial in PDFs and e-books. Business process modeling tutorial via videos and tutorials. Business process modeling tutorial in slideshows. Business process modeling tutorial — PDF and e-books. There are 6 e-books in PDF on process modeling with access to links to download the materials.
An Introduction to Process Modeling An Introduction to Business Process Modeling — pages This PDF document is rather extensive, but covers in a way quite a full range of topics related to modeling processes, from motivation, through to tools, notations, and techniques, until process design. The Business Process Model The Business Process Model — 10 pages This tutorial deals with the UML notation covering flow elements, connection objects, artifacts and examples for you to understand easier.
Download here: The Business Process Model 4. They can also provide advanced functions that are specific for managing collections of process models, such as managing the consis- tency of public and private processes and extracting knowledge from ex- isting processes to better design new processes.
This paper, by analyzing existing business process model repositories, proposes a framework for repositories that assist in managing large collections of business process models. The framework consists of a management model and a reference architecture. The management model lists the functionality that can be provided by business process model repositories.
The reference architec- ture presents the components that provide this functionality and their interconnections. The framework provides a reference model for analysis and extension of existing repositories and design of new repositories. For example, the SAP reference model contains over business process models [15] and a col- lection of business process models for Dutch local government contains a similar number of business process models [7].
Typical issues arise, e. In addition to that, the availability of a large collection of processes opens up new possibilities, e. As a consequence, software tools have been developed to help perform such tasks. These tools have been built as extensions of general database and repos- itory systems. However, they have been specialized for storing business process models by using conceptual models, for example database schemas, that are pro- cess specific and by defining process specific interfaces.
The interface could, for M. Su Eds. Yan and P. In addition to exploiting the func- tionality that is commonly provided by repository and database management systems [4,14], BP Model Repositories provide functionality that is specific for repositories that contain business process models.
Examples of process-specific functionality include: functionality to assist with lifecycle management of busi- ness processes, functionality to help maintain consistency between the private view on business processes which is the view that organizations have internally on their business processes and the public view on business processes which is the view on those parts of business processes that companies want to make visible publicly , and functionality to assist with configuration management of business processes as they are composed of certain versions of sub-processes and tasks.
To provide an overview of the functionality that should be provided by BP Model Repositories, this paper analyzes and extends existing related works and provides a framework for BP Model Repositories. The contribution of this paper is as follows: it presents a framework for BP Model repositories, which consists of a management model and a reference architecture. The management model lists the functionality that can be provided by BP Model Repositories, while distinguishing between functionality that is provided by general repositories and database management systems [4,14] and functionality that is specific for repos- itories that contain business process models.
The reference architecture presents the components that provide this functionality and their interconnections. The framework serves as a guide for the development of BP Model Repositories. The remainder of the paper is organized as follows.
Section 2 introduces exist- ing BP Model Repositories. Section 4 presents a reference architecture for BP Model Repositories. Section 5 concludes the paper. Com- parisons of existing BP Model Repositories based on the framework are given in our internal report [19]. There are two basic approaches to built BP Model Repositories, i. Knowledge-based BP Model Repositories are repositories storing knowledge related to processes. The process variant repository PVR [10] provides a mechanism to monitor the executions of processes, and stores the execution traces as knowl- edge to improve processes.
Service-based BP Model Repositories are repositories storing processes that are defined in the context of services. The two main advantages of service-based BP Model Repositories are distribution and collaboration.
For example, OSIRIS Open Service Infrastructure for Reliable and Integrated process Support [16], combining the ideas of web services and hyperdatabases, to support peer-to-peer process execution by invoking services from distributed repositories. BP Model Repositories can be both knowledge-based and service-based at the same time. Also, BP Model Repositories vary with respect to the functions that they provide.
This section defines the possible forms of a BP Model Repository structure or interaction facility and the functions that a BP Model Repository can provide. We consider a BP Model Repository as a specialized repository.
Consequently, it should provide common database management services for data model cre- ation and adaption, data retrieval, enabling data views, integrity management, access management and state management. The functionality for general repositories, as it is summarized by Bernstein and Dayal [4] and by Sagawa [14], can be specialized and extended to develop repositories that are specific for storing and managing business process models.
We developed such an extension by taking the work of Bernstein and Dayal [4] and Sagawa [14] as a starting point and specializing and extending it, based on functionality that can be observed in existing BP Model Repositories, as described in Section 2. It consists of three parts: the process data model, the process function model and the process management model. It consists of the meta- model, the storage model and the index model.
The meta-model prescribes what information can be and must be stored in the BP Model Repository by defining the concepts that are used in the repository and the relations between those concepts. Each BP Model Repository potentially supports a large number of concepts. We classify those concepts by identifying the process aspects and the process types that are supported by a BP Model Repository. We distinguish the following process aspects. We distinguish the following process types.
If a reference process contains pre-defined configuration options, it is also called a config- urable reference process, e. A Framework for Business Process Model Repositories — A process instance I , or case, is an execution of a process for a customer, e. Table 1. For example, a BP Model Repository can store the information for ac- tivities and control-flow relations between those activities, but that information can be presented to the user in structured natural language, in a standardized graphical notation like EPC or BPMN, or in a proprietary graphical notation.
Grefen The storage model prescribes how the original information about the process must be technically provided to the BP Model Repository external data model and how it must be internally stored by the BP Model Repository internal data model. Other than that process related data, which is data that is used by, but not part of, the processes can be stored in the repository.
The index model prescribes the indices that are kept for process models, to allow both the user and the repository manager itself to quickly browse or search the collection of processes.
An index that is commonly used is a classification of process models in terms of the business functions for which they are available. For example, we can classify processes into processes for: sales, procurement, pro- duction, finance and support. We identify storage functions, retrieval functions and integration functions. The storage functions are the functions to create, update and delete processes or parts of processes, by creating, updating or deleting instances of the concepts that are defined in the process meta model.
In addition to that functions exist to import complete processes into the repository, using the interchange format from the external data model, and to export complete processes from the repository using that interchange format.
The retrieval functions can be used to obtain the required process according to some criteria. There are three methods for retrieving processes: navigate, query and search. Navigation is the method of manually scanning processes in a list, or by using a classification or some other index. Search provides the function to get processes that match criteria that are given as keywords. Queries and query languages can have a focus on one or more process aspects or process types. Awad distinguishes the following foci for process query languages [2]; languages that focus on retrieving elements of processes company specific or reference , languages that focus on retrieving elements of process instances and languages that focus on retrieving elements of process execution history.
The integration functions can be used to integrate a process repository with external tools. In the BP Model Repositories that we have studied, we have observed integrations with the following types of tools. When executing a business process a process instance is created and monitoring information is generated, e.
Within the set of BP Model Repositories that we studied, there was no strict separation with respect to what is considered internal functionality of the repos- itory and what is considered external functionality that can be integrated with the repository. For example, query tools have been proposed as external tools [2], but at the same time tools for establishing collaborations between organizations, based on their processes, have been proposed as internal parts of the reposi- tory [17].
We made the separation between internal and external functionality above, based on what we most frequently observed in the analyzed BP Model Repositories. The process specific management functions are: version management, config- uration management, lifecycle management and view management. Although version management, configuration management and view management are also general repository functions or even general database functions in the case of view management , these functions have been specialized to meet process spe- cific requirements [1,5,6,9,20].
The version management function enables multi- ple versions of the same process or activity to be maintained. The configuration management function makes it possible to maintain the relation between a version of a process and the versions of subprocesses and activities that it consists of. Grefen repository functions, specialized functionality is added to support requirements in the context of BP Model Repositories.
The lifecycle management function maintains the stage in its lifecycle that a process is currently in. For example, a process can be under design, validation and current. Depending on the stage that it is, some operations can be performed on it and others cannot.
For example, a new version cannot be created of a version that is under design, nor can a process that is still under validation be executed. The view management function makes it possible to create multiple views on a process. Although view management is a general database function, specialized functionality is added to support requirements in the context of BP Model Repositories.
For example, it is common to keep a private view on a process, which represents the process as it is performed inside an organization. At the same time a public view also called service can be provided of what the behavior of the process to the outside world will be like, therewith preserving company secrets of how services are internally implemented and not bothering clients with details that do not concern them.
To support the generation of the public view from the private view and to keep the two views consistent, BP Model Repository specific functionality is needed. The access man- agement function ensures that people only have access to the objects in the repository that they are authorized to view.
The integrity management function ensures that the repository cannot get into an inconsistent state. Transaction management ensures that multiple operations on a repository can be performed in a transactional manner i.
Optionally, multiple people can be allowed to check-out an object at the same time, in which case check-in manage- ment should ensure that changes that are made to the same object by multiple people are properly merged. Dispatch management makes it possible to asso- ciate a work-order with an object, such that it is forwarded to people in the order specified in the work-order along with notes about what these people have to do with the object.
0コメント