What is Business Process Modeling?

BPM (Business Process Modeling) is the core method and tool of business process management. Taking mainstream management software in the market: UFIDA and Kingdee as examples, business process modeling includes process node modeling, process content modeling, and process permission modeling.

BPM

(Business Process Modeling)

Modeling BPM

Business Process Modeling (BPM) is a way of expressing business processes. It is an important basis for process analysis and reorganization. This expression has greatly optimized the software development and operation efficiency, and has also led to the use of BPM technology by traditional ERP software vendors such as UFIDA, Kingdee, and the like, which made new BPM software applications shine.

Under the premise of cross-organizational business process reorganization, the main purpose of process modeling is to provide an effective cross-organizational process model and assist related personnel in cross-process analysis and optimization. At present, there are a large number of process modeling technologies that can support the reorganization of business processes, but at the same time it also causes confusion for related personnel: Faced with so many technologies, it is difficult for them to choose a suitable technology or tool. At the same time, most of the current researches on process modeling techniques focus on the proposition and application of modeling techniques. The lack of collation and classification of existing techniques and the horizontal comparison between techniques has deepened the complexity of modeling technique selection. .

The BPM system administrator uses a graphical monitoring console to maintain and track the status of the engine process. The powerful and easy-to-use flowchart-based modeling and monitoring are also widely evaluated as the most important reason for product competitiveness. The process console interfaces with the engine using a management language. The real-time engine persists the process state to the database, and the console meets the database directly instead of communicating with the management language. The runtime engine persists the process state to the database, and the console meets the database directly instead of using a management language to specifically execute the process's requests. The monitoring construct also supports Business Activity Monitoring (BAM) or dashboard-style business monitoring.

The development process on this platform is as follows:

1. Generate an initial BPMN model from a WS-CDL choreography. Skip this step if the process is not derived from an orchestration.

2. Design the BPMN model

3. Generate BPEL from BPMN model

4. Develop the necessary people and systems (internal and external) interfaces

5. Deploy BPEL code and its necessary interfaces to the engine

6. Use management and monitoring interfaces to track running processes.

The overall picture of this architecture (inspired by the reference model of WFMC, the most mature of many BPM standards organizations) is similar to that of many integration vendors (such as IBM, BEA, Oracle, Tibco, SeeBeyond, and Vitria) Provided platform. What makes this architecture special is its standard choice. BPEL,

BPM standard in an ideal system Figure 2

Both BPMN and WS-CDL are included because they are the best solutions for execution, design and orchestration, respectively, and the three most important parts of BPM.

(As shown in Figure 2, the future may include emerging standards BPQL-for monitoring, BPSM and BPDM-for metamodel modeling, BPRI-for runtime interfaces, BPXL-for BPEL extensions). In fact, many vendors support or are implementing support for BPEL. But BPMN has very little support (most vendors provide their own solutions), and WS-CDL has almost no support. BPEL is not enough. This system is ideal and requires practical implementation.