Planning and Design of Collaborative Application Support Platform
【 2.1 】 Platform construction principles
1. Unified planning and step-by-step implementation
The construction of informatization is not achieved overnight. We must adhere to the principle of unified planning and step-by-step implementation, and gradually improve it.
2. Design first, implement later
All project construction stages must first write design documents, which can only be implemented after being signed and confirmed by the user.
3. Unified standards and management
During the development process, this system strictly followed the national standards, industry standards, and the definition of e-government standards by the national e-government standardization group (such as using the J2EE platform). The system has an international standard software architecture and interface (XML), ensuring fast and smooth information exchange with other systems, achieving comprehensive utilization of resources, and unified management.
4. Information exchange and resource sharing
The focus of information construction is on collaboration. This system adopts a standard architecture and data interface to ensure good information interoperability, eliminate information silos, and in the future, it can achieve information and data exchange and resource sharing with relevant units and other government cooperation units.
5. Emphasize practicality, security, and confidentiality
By sharing information and resources, we can demonstrate the effectiveness of government cooperation. At the same time, we have carried out a three-dimensional and comprehensive security and confidentiality design from three levels: system, application, and usage, ensuring smooth government cooperation under the premise of security and confidentiality.
6. Professional, meticulous, and quick response
Professional, meticulous, and quick response are our attitudes towards users. Quality is life, and it requires the establishment of a sound quality management mechanism. Each engineering process has clear quality requirements to ensure the implementation of the system and after-sales service.
Platform design principles
1. System progressiveness principle
The system adopts the industry recognized advanced J2EE/EJB multi-level architecture, ensuring the mainstream of the system, which is also the factual standard for the construction of national e-government.
2. Principles of adaptability and flexibility of the system
The system can easily adapt to changes in the situation of XX department, including organizational structure, personnel and division of labor, office regulations, and other changes.
3. Cross platform principle
The system supports hardware platforms based on Windows NT/2000, AIX, OS/2, HP-UX, Solaris, Linux, and other operating platforms, and can smoothly migrate on various platforms without the need for development.
4. Principle of System Scalability
After the system is built, new application requirements can be seamlessly added to meet future business needs. This system has interfaces with other systems and can adopt standard and unified data structures to adapt to future development. The system can also be easily extended to all subordinate institutions, supporting a centralized approach or adopting a distributed approach.
5. The principle of system efficiency
The information volume of XX Hall is very large and increases significantly every year, so the system's information storage, management, and retrieval must consider this factor to ensure that the system has sufficient retrieval and processing speed, and can achieve a system response time of less than 3 seconds for local network response and less than 10 seconds for remote dialing when there are a large number of users (more than 5000 people).
6. Principles of System Stability
After the implementation of the system, there are many users and a wide range of involvement, so the stability of the system is crucial, and the system must have sufficient stability assurance.
7. Security principles of the system
How to ensure the security of information and user usage will be a very important technical key. Security issues can be comprehensively considered from the aspects of system architecture, security software, user authentication, application design, and system management, and designed and implemented at the three levels of system, application, and usage. The system should have multiple security measures to ensure the normal operation of the system: the security of system hardware, the security of system software, the security of network communication, the security of development tools, and the security of functional settings.
8. Standardization principle
Design strictly in accordance with the technical and regulatory requirements of the "Electronic Government Standardization Guidelines" of the "National Electronic Government Standardization Overall Group", and strictly follow the relevant national, provincial, and municipal standards in the system's entries and terminology; If there are no relevant standards during the development of XX administrative system software, the developer may develop their own open standards.
9. Principles of protecting and saving investment
Emphasis should be placed on the basic platform functions of the system, integrating data and applications between existing and future systems through platform services. At the same time, a custom design style should be fully adopted to minimize modifications to the system code caused by changes in business requirements, thereby prolonging the system's lifecycle and saving investment from system upgrades and renovations.
Platform Planning and Design
【 2.3.1 】 Platform Overview
【 2.3.1.1 】 Platform Function Overview
The application support platform should include the following systems or components: workflow system, system configuration management, content management system, full-text search engine, statistical report system, unified authentication and authorization system, security encryption system, email system, unified messaging platform, data exchange interface, and system deployment tools; Reserve functional modules for payment gateway, voice gateway, streaming media gateway, and wireless access gateway.
【 2.3.1.2 】 System (Basic) Structure
Platform (Basic) Architecture
The basic platform logically consists of a web server, security proxy server, application server, multi-channel message center, system integration adapter, email server, SMS server, and fax server.
【 2.3.1.3 】 System Technology
The XX Hall application support platform is based on advanced, reliable, and flexible J2EE standards, supporting Enterprise JavaBeans ? (EJBs ?) Component architecture, JavaServer Pages ? (JSP) ?) Technology and Java Servlet application programming interfaces (APIs). Fully based on Java's features, the collaborative government platform supports open standards, including JavaScript ? Technology, C++, COM, CORBA, XML, XSL, LDAP, WML, and WAP.
The platform supports the architecture design of J2EE technology, allowing customers to customize, expand, and modify e-government applications based on collaborative government platforms. For example, support for JSP allows customers to easily modify applications, while the connection of EJBs allows collaborative government platforms to quickly integrate with other systems. The use of easily accessible Java programming capabilities allows customers to reduce development costs and time.
Basic concepts of J2EE elements
Platform processing flow
Adopting the popular MVC mode, where the view is the display of data to the user, and the web view can be an HTML page, images, or other media. A model represents the data in the system, and a model can retrieve attributes related to a user profile. The controller is responsible for controlling the flow of the program and driving updates between the model and view. Specifically, attempts can be defined using JSP or HTML, models can be defined using Java objects (commonly referred to as Java beans), and controllers can be defined through the action classes of Java objects. The following is the processing flow of MVC architecture:
The processing flow of MVC architecture
System integration processing flow model
[2.3.2] Workflow system
The workflow system consists of three organic parts: workflow customization tools, workflow state machines (workflow engines), and work tasks (workflow instances). In practical work, it is very important to quickly implement customized management of processes and related elements. At the same time, workflow management needs to be able to be provided to various other systems based on this platform.
【 2.3.2.1 】 Standard compliant process state machine
A workflow state machine is a workflow engine that is used to parse the workflow models customized by workflow customization tools, initiate these process models, create a tangible task item, and then advance the status of the process according to the node customization order and various branch conditions, so that the work tasks can be pushed forward according to a certain pattern.
Due to the fact that the principles and design of workflow state machines are a very complete and rigorous system engineering, there are organizations such as the International Federation of Workflows (WFMC) that specialize in researching the practical application of workflows. WFMC has also proposed a reference model for workflow modeling. Therefore, the design of workflows should follow the reference model of WfMC and the workflow design guidelines recently released by the National E-Government Standards Group.
【 2.3.2.2 】 Visual Process Customization Tool
For the daily office work of a unit, it includes handling documents, affairs, meetings, and other aspects, and the handling methods of these tasks are all structured within the unit's management mechanism. As a software system, the process directly reflects these management mechanisms. So it achieved online file circulation approval.
In fact, with changes in management mechanisms or departmental organizational structures, the actual workflow undergoes changes. At this point, without a process tool, the direct consequence is that the developer needs to constantly modify the code. It is a significant loss for both users and developers. So, we need an intuitive and convenient process design tool. Enable individuals with simple computer knowledge to maintain their own processes according to the needs of the organization. Truly achieve the application system to meet the needs of users. As shown in the following figure:
【 2.3.2.3 】 Interface Customization Tool
Users have many operating habits, and through years of experience, developers can do a lot of work in various aspects such as system interface friendliness and aesthetics. But this does not cover the needs of all users. So it was decided to set up a "interface customization" function module in the system. Enable users to independently grasp the interface of the application system, making the interface more tailored to their needs. Moreover, the system will provide each employee with the function of defining "personalized interface settings". Enable different users of the same system to have their own personalized interface.
In addition, the backend provides interface style management, which only requires adding some compliant content in the system backend, such as system skins, layout, etc. Then various application systems can use this layout or layout to achieve interface customization.
[2.3.2.4] Work Task Management
A work task is an instance of instantiating a workflow model. The management of process instances is mainly designed to deal with emergency situations where the process cannot proceed according to the original process model due to unexpected reasons. In such cases, instance management can be used to forcibly terminate, force flow, suspend, and wake up the process for special handling.
The management of process instances can also provide basic application service functions for instance processing monitoring, statistics, and auditing.
【 2.3.2.5 】 Form Customization Tool
A form is an information carrier used in the process. In practical work, document processing forms such as "Office Note", "Document Circulation Form", "Expense Application Form", "Leave Application Form", etc. are used for the corresponding process of processing information.
The form customization tool is a graphical application software, and anyone with experience in drawing simple forms can create a form themselves after simple training.
[2.3.2.6] Workflow Application
On the basis of following the WFMC standard model, according to the actual needs of daily work, we need to implement some specific application functions in our process, and these applications can be directly reflected in all application systems using the process tool.
Conditional circulation
The approval flow of daily affairs may display different content, flow directions, and approvers based on various conditions, so the system has a built-in function for conditional flow. It can be set to change according to changes in fields or according to changes in flow direction.
Flat management
The process has both standardization and many individuality. As for the organizational structure of our unit, some departments may have departments while others do not, and some public institutions may have more complex organizational structures and management models. How to ensure that the same process can adapt to different departments, units, and personnel with different identities, and ensure corresponding control and management permissions for information (i.e. achieving flat management), is a key consideration for process tools. Our process tool can achieve this through simple condition settings.
Adapt to government documents
The WFMC standard has certain limitations compared to the handling of official documents by Chinese government agencies. On the basis of following this standard, we solve the setting of various special tasks such as "joint processing", "concurrent processing", and "separate processing", making the process setting more simplified and the function more powerful and applicable.
Process tracking
In the process of workflow execution, it is possible to track the processing process of the workflow. By tracking the entire process of the official document process, it is possible to understand the efficiency of the staff's work and effectively control and avoid the occurrence of adverse situations such as blockages in the management process. It should be possible to track the receiving time, processing time, and basic information of each step in the management process.
Urgent processing
You can set a time limit for each step in the official document process. If the step handler fails to process it within the specified time, the system will automatically issue a reminder notice. And all authorized personnel can send reminder notifications to all personnel currently in operation.
Supervision
Part of the supervision was achieved through urging. However, due to the huge amount of accumulated files in daily work, it is difficult to find files for supervision. Therefore, the system has set up a separate supervision module, which lists the files set by the user as supervision, monitors, consults, and urges them. This makes supervision easier and more convenient. And tasks can be assigned here.
Retention of modification traces
The modifications made by the processing personnel at each stage of the workflow execution process can be retained to ensure the seriousness, traceability, and non repudiation of the workflow execution process (especially the document processing process).
Main text lock
When the workflow reaches a certain stage (such as the process of affixing an electronic seal after the leader signs the document), the main body of the official document can be locked. After the main body is locked, no further modifications can be made to the main body in all subsequent processing steps.
Digital seal
When the workflow reaches the stamping stage, the digital seal stamping function can be performed. The digital seal is a graphic file encrypted by a special digital fingerprint, which is made and kept by the seal administrator.
Withdrawal processing
The workflow provides a recall function. If a user in one stage submits work to another person, as long as the other person has not yet opened the file, the recall operation can be performed.
Termination process
For some discontinued processes, if they have no actual value, they can be terminated. After the process is terminated, the task is deleted and the termination operation must be completed by the creator (i.e. the drafter) of the process. For processes that have been executed in intermediate stages of the process, they need to be returned to the drafting stage in order to be terminated.
【 2.3.3 】 System Configuration Management
All applications in the platform adopt a unified system configuration management, which implements various functions such as user management, permission allocation, data dictionary, application logic establishment, rule definition, version control, etc. Implement architecture on the same level
笔记
双语对照
排序
重点词汇
掌握这个方法，轻松get3500必备词！
重点词汇
统一规划 unified planning ; Unitary Plan
信息化建设 information construction ; Informatization Construction ; ERP ; MIS
项目建设 Project ; construction
统一标准 unified standard
统一管理 Unified management ; Integrated Water Resources Management
国家标准 national standard
行业标准 trade standard ; industry standard
电子政务 e-Government ; Electronic Government
软件体系结构 architecture ; software architecture ; softwarearchitecture
综合利用 comprehensive utilization ; integrated utilization ; multipurpose use ; multipurpose utilization of sth.