Potato workflow management system
Organizational model overview
V1.0
Project Name: Potato Workflow Management System
Schedule: wind rolling
Writtenman: wind rolling
Writing time: 2004.8.18
QQ: 9131144 E-mail: Workflow@163.com
table of Contents
Directory. 2
1. Introduction. 3
1.1. Writing the purpose ... 3
1.2. Background ... 3
1.3. Definition ... 3
2. Design instructions. 4
2.1. Type Description ... 4
2.2. Function Description ... 4
1 Introduction
1.1. Writing
I have always wanted to write a workflow management system (including organizational model, process engine, process definition), and finally filed a pen today. From graduation, I have been touched in this direction, I have been more than four years. I have a variety of customers, I have done a different industry project, and I always have a regret in my heart. Unfortunately, there is a sense of accomplishment in my heart. It is unsatisfactory for what I have made. Things don't have to give customers a convenience, sometimes I feel that it doesn't reduce customers' workload. Instead, the workload of the customer has also increased. And it feels the difference in scalable from the system itself. The reason why this will be the lack of a flexible workflow management system. In order to make up for the regret in your heart, we determine our own idle time to develop a workflow management system.
1.2. Background
Under the tide of e-government, more and more government, enterprises, and institutions have joined them. It is the tide and the tide and the tide. After the tide will leave some "failure" project. The failures here include: 1, the failure of the project (software) itself; 2, the project is not used or used (of course, including those political academic projects, face engineering).
1.3. Definition
Regarding the definition of workflows, different organizations have different definitions, and it is generally the same. It is a group of people who participate in people (probably people, systems, machines, etc.) in order to complete a business process (if the issuance of documents, admission, reference, etc.) is experienced. Here I discussed here is mainly for e-government in China's national conditions, because the author only is more familiar with this, and does not dare to comment on other workflows (industrial control, etc.). (Different workflow systems should be different for different industries.
In the workflow management system, we must first consider the organization model. Because the workflow management system should be based on the organizational model, the person defined in the organization model is the main part of the process.
2. Design instructions
The main implementation technology of the program is: Struts Hibernate Spring
2.1. Type Description
The physical type in the organizational model mainly includes the following five categories:
1, personnel
2, department (organizational unit)
3, group (working group, group)
4, role
5, position (such as administrative position)
The relationship between each entity:
Personnel --------- Department N ----- 1
Personnel --------- Group N ----- N
Personnel --------- Role N ----- N
Personnel --------- Director 1 ----- 1
Department --------- Department 1 ----- N
Group --------- Group N ----- N
Group --------- Role N ---- N
Description:
1. Originally designed as a character ------- character n - n, and then thought about it, there is no need. The reasons are as follows: A, this is designed to be too complicated.
b, if the role contains the role, the end user is also complex; it cannot be convenient for users.
2, the role should be divided into two. One is a global role, one is a partial role. The first role is useful throughout the system. The second role is constrained by a certain range (department), which may have different permissions for different departments.
3,
2.2. Function Description
A, increase, delete, modification, query
b, the addition, deletion, modification, query
C, increase, delete, modification, query
D, group increase, delete, modify, query
e, increase, delete, modify, query
