Bobmazelin Process Management System introduction and conceptual design (I)

I have been working in the Process Management System field for more than a year. Although the project is currently stuck, I still have hope for the process management field. this series of essays was developed by bobmazelin and his colleagues, who have accumulated experience in their work during this period. It is also an introduction to our process management system. If like-minded people share their own ideas at will, at the same time, we also need new vigor to promote the project again.

This is the first article in this series. I will introduce the general architecture of the system and some basic information. since this project is a commercial project, please forgive me for not disclosing the project name and other commercial materials.

What can the system do?

In one sentence, the customer can control each step in the process lifecycle through the system.

We understand the process lifecycle:

Understanding the process-> Design Process-> static analysis process-> Design Process-> deployment process-> process Version Control-> test process-> Design Process-> Execution Process-> monitoring process-> dynamic analysis process-> redesign process

Note: In some cases, this virtuous cycle mechanism is one of the core tasks of process management.

After realizing the process lifecycle, we also realized that the process in the process lifecycle is not just a process, it covers the resources, rules, and process itself in the process. we think about these three elements in the process lifecycle to form the overall architecture of the process system.

It is difficult for me to use a view to summarize the overall architecture of the process system. I use three views for presentation.

1. system elements: resources, rules, and processes. These three elements are the process system and line elements. Other views depend on them.

When the resource is at the bottom of the system, it indicates the data of the system. When the rule is in the middle, it describes logical business rules and relies on (use) resources. The process is at the top, call rules and manage resources. we can also see that resources should be the most stable element of the system. To change resources, we may need to adjust rules and processes. In this way, we can abstract the business meaning of resources as much as possible and try our best to reduce the impact of resources. although the rule is in the middle layer, it is well encapsulated. Its users (processes) do not need to pay attention to its internal structure, but only need to execute the rules. Therefore, the flexibility of the rules is crucial. the process is at the top level, and the process changes have the least impact. This is also required for process management.

2. Process lifecycle: provides a toolset for each step of the process lifecycle mentioned above to help users better manage the process.

Process Design components: necessary tools for identifying and designing resources, rules, and processes;

Static Process analysis component: ensures the correctness of the process "theory" before actual deployment by analyzing the static process structure, resource allocation methods, and rule correctness;

Deployment component: deploy resources, rules, and processes through HTTP, and deploy the process anytime and anywhere. The deployment method is simple;

Version Management: changes are inevitable. The automatic version control function ensures the restoration and query capabilities of historical design data;

Test process component: resources, rules, and processes can be tested without a page or form design, laying the foundation for fast and accurate execution of the process;

Execution Process component: diverse process execution interfaces: API, remoting, WebService, MSMQ, etc;

Monitoring process component: real-time monitoring and control process;

Process dynamic analysis component: analyzes historical data reports on demand, providing a good tool for process optimization.

The above lists the important component sets, but not the complete set. We can see that each function set is centered on the system elements.

3. System Structure: due to commercial technology, this view cannot be disclosed here. This view is more closely related to developers and is of no practical use from the user's perspective.

This series is mostly centered on the first two views, introducing the conceptual elements and the applications in process management.

Finally, please give me more comments. If not, please forgive me.