SOP electronic recording system and development method thereof

Abstract

The invention provides an SOP electronic recording system and a development method thereof. The SOP electronic recording system comprises a database and a work order recorder. The database is an XML database. The work order recorder is provided with a plurality of work order templates, and each work order template is stored in the database in an XML data format. Each work order template is used by a user to establish a work order record, and each work order record is stored in the database in an XML data format. As the data representation of the work order recorder during the operation of the work order templates and the persistent data representation in the database both adopt the consistent XML data format, based on the characteristics of XML data format files such as readability, self-interpretability, structure expandability, label customizability and the like, a user can compare a work order record presented by the work order recorder with a work order record stored in the database, so that system verification is facilitated; no data conversion or change is needed between the work order recorder and the database, and no redundant data exists in the database, so that the data reliability is improved.

Description

technical field [0001] The invention relates to the technical field of data processing, in particular to an SOP electronic record system and a development method thereof. Background technique [0002] Recording the implementation process (SOP) and results of production quality activities to ensure the authenticity, accuracy, completeness and traceability of the whole process information (data reliability) is a requirement in some industry regulatory regulations. In recent years, as the advantages of computerized systems are gradually recognized, electronic records are becoming an inevitable trend to replace paper records. However, the current electronic record system usually encounters the bottleneck of high development cost, long implementation period, and inflexibility and convenience of later expansion and change. [0003] The main reason is that the current electronic record system development is usually based on the classic three-tier architecture, which gives develope...

AI Technical Summary

Problems solved by technology

For example, the complete control of the middle business logic layer on the back-end data persistence layer can easily introduce the risk of developers interfering with data, but the system permission configuration cannot effectively control this; another example: the inherent data transformation between the three layers makes It is difficult for users to intuitively confirm that the data seen at the front end is the data stored at the back end, which makes developers and managers spend a lot of labor and time to implement the risk assessment, system verification and data reliability required by regulations Management responsibility such as sexual control

Images