Source: Echinagov Huang Zhi
First define, "Process" of this article refers to business processes. In general, the relationship between business processes and information systems is defined: First, the information system must meet certain business process requirements; second, information technology can be used to help and promote improved processes. Realizing these two-layer relationship can be said to be a more ideal goal of information system construction.
Regarding the first layer of relationship, there is generally no objection; however, it is said that information technology has touched the sensitive nerves of e-government related aspects of the "reaction force" of the process. After all, the "process" of e-government applications is about policies, reflecting laws, regulations, and is not similar. Therefore, in order to turn policies, regulations into information systems, "process" designers and IT people often lead to the aforementioned draft, not tireless, hate these "processes" can mechanically turn into program code. If the process changes, most of the "can not change the unchanged" avoidance attitude. So there is such a pass in the industry: at a certain point in time by the two parties in a formal document, a "one knife two-break" - design according to the "process" before this time, and after this point "process "Change does not pay attention. The subtext of this approach is: Your demand is not fixed, how do I do it? So you can often see this phenomenon: Yesterday, IT staff is still unwilling to understand and research demand; today, I started to bury the car, and the changes in demand - including the change of the process - do not ask, smashed .
The practice of picking out the demand cutouts is not a big mistake. On the contrary, it is a usual practice of demand management, which is an embodiment of the information system engineering. But our attitude towards the "process" change (which is the change of demand) determines the actual effect of us to take this practice. If we do nothing to do for business processes and information technology, we just cater to the existing processes, which will fall into the quagmis that can be dealt with. This situation has not been seen: According to the information system designed in a process, it has been encountered "policy risks" in the "process change" in the "process change" in accordance with the information system designed, and even yet implemented. It should be a saying: "There is no change in the plan."
Indeed, "Process Change" is the common "policy risk" common to e-government projects at present. Today's e-government construction is no longer ink, closed the door. Under the banner of demand, the banner of the people of the people, the "process" does not want to unchange the same, and there is a tendency to become more frequent. Politically, this "policy risk" is reflecting the process of political system reform and the transformation of government functions. It is worthy of welcome and hug.
In this situation, we need to re-examine the attitude of "process" and "process changes". For the main body of the government department, in order to improve administrative efficacy, improve services, certain changes in the "process" (of course, sometimes it may have to endure the pain), is the general trend.
Once this attitude is held, we can discover: in fact, there are many mature technical products and management ideas to support the variability of the process: in technology, there are various middleware and platform products, allow us For the "flow" in the application system, the development of the information system is a "live" system; in management ideas, there is an iterative process idea, guiding us in the "process risk" System construction is performed. Boldly learn and use these new technologies and management ideas, allowing e-government construction to put energy into the process of adjustment, optimization, not just the implementation of the process.
