A dynamic traceable data interaction method and system based on a DAG rule engine

Abstract

The application belongs to the field of simulation software and relates to a dynamic traceable data interaction method and system based on a DAG rule engine, which comprises the following steps: a CAE data model is constructed, and data operation is performed through the CAE data model; a DAG rule engine is constructed, and data operation is updated through the DAG rule engine; a data modification interface is called through a user interface, and updated data operation and display are performed; the method further comprises a data model part, a logic control part and an interface display part; and the method guarantees sustainable evolution of a project and improves maintainability, expandability and stability of simulation software.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of simulation software, and specifically discloses a dynamic traceable data interaction method and system based on a DAG rule engine. BACKGROUND

[0002] Currently, in the development and maintenance process of simulation software, many core challenges are faced: first, simulation software involves multiple types of data, with high data dimension and large quantity, and the data quantity increases exponentially with the complexity of the project, making the management difficulty increase dramatically;Multiple types of data can include calculation parameters, model information and topology structure, etc. Secondly, there is a dense association network relationship between data entities, and the association relationship is complex and dynamically changed, and the change of a single data may trigger a chain reaction, leading to the synchronous adjustment of other data, and improper maintenance may easily cause errors;The association network relationship can include dependency relationship, constraint condition and trigger mechanism, etc. Finally, data is directly mapped to the user interface, and the user interface changes frequently, and the interface update needs to be synchronized with the data, which causes great pressure on interface development and testing;User interface can include editing interface and visualization view, etc. The above problems of the prior art seriously restrict the maintainability, expandability and stability of simulation software, and a systematic solution is needed to ensure the sustainable evolution of the project.

[0003] Therefore, the present application provides a dynamic traceable data interaction method and system based on a DAG rule engine to provide a systematic solution, solve the problems of the prior art, ensure the sustainable evolution of the project, and improve the maintainability, expandability and stability of simulation software. SUMMARY

[0004] The purpose of the present application is to provide a dynamic traceable data interaction method and system based on a DAG rule engine, and the problem to be solved is: unified format storage basis, effective realization of the traceability of the complex association change and modification operation of data;The specific scheme is as follows:

[0005] A dynamic traceable data interaction method based on a DAG rule engine, comprising: constructing a CAE data model and performing data operation through the CAE data model;Construct a DAG rule engine and update the data operation by updating the DAG rule engine;Call the data modification interface through the user interface, and perform the update data operation and display.

[0006] Further, the CAE data model is constructed, and data operation is performed through the CAE data model, including: abstracting CAE simulation data into simulation concept semantics and simulation data, and taking the simulation data as a CAE data model; constructing a basic object tree for the simulation data in the CAE data model; the object tree is divided into multiple layers from top to bottom, the upper layer object includes multiple lower layer objects, and each object includes attribute parameters; through an increase, deletion, modification and query interface, an object or object combination in the basic object tree is represented in a nested manner to obtain a requirement object tree; through a visitor mode, object data in the requirement object tree is processed to realize various operations of data.

[0007] Further, the requirement object tree is further mapped into a document object, and the document object is accessed in a binary manner.

[0008] Further, the DAG rule engine is constructed, and data operation is updated through updating the DAG rule engine, including: determining an association change rule of object data based on an association change relationship between the object data; constructing an association change relationship graph between the object data based on the association change rule; the association change relationship graph is a directed acyclic graph for representing the association change relationship between the object data; when object data change in the requirement object tree is identified, associated data of the changed data is changed according to the association change relationship graph to update various operations of data; when the association change rule change is identified, a new association change relationship graph is generated based on the changed association change rule, and the rule change is performed according to the new association change relationship graph to update various operations of data.

[0009] Further, the data modification interface is called through a user interface to perform update data operation and display, including: sending a data modification instruction through the data modification interface, and storing the data modification instruction; generating changed data objects and / or changed association change rules based on the data modification instruction, and updating various operations of data; updating a user interface display based on a personalized operation (various operations) result of data.

[0010] The application further provides a dynamic traceable data interaction system based on a DAG rule engine, including a data model part, a logic control part and an interface display part; the data model part is used for performing data operation; the logic control part adopts an observer design mode and a callback method to automatically change the system internally to maintain the correctness of remaining data after data change; and the interface display part is used for interface display and / or personalized operation of simulation data in the data model.

[0011] Further, the data model part includes a CAE data model, data operation is carried out through the CAE data model;The logic control part includes a DAG rule engine, data operation is updated by updating the DAG rule engine;The interface display part includes a user interface and a data modification interface, interface display and / or personalized operation of simulation data in the data model are carried out by receiving data modification instructions sent by the data modification interface.

[0012] Further, the CAE data model includes a data abstraction unit, a basic object tree construction unit, a requirement object tree construction unit and a data operation unit;The data abstraction unit is used to abstract CAE simulation data into simulation concept semantics and simulation data, and the simulation data is used as a CAE data model;The basic object tree construction unit is used to construct a basic object tree for simulation data in the CAE data model;The object tree is divided into multiple layers from top to bottom, the upper layer object includes multiple lower layer objects, and each object includes attribute parameters;The requirement object tree construction unit is used to nest objects or object combinations in the basic object tree through the add, delete, modify and query interface, and obtain a requirement object tree;The data operation unit is used to process object data in the requirement object tree through the visitor mode, and realize personalized (multiple) operation of data.

[0013] Further, the DAG rule engine includes an associated change rule determination unit, an associated change relationship graph construction unit and a data update unit;The associated change rule determination unit is used to determine the associated change rule of object data based on the associated change relationship between object data;The associated change relationship graph construction unit is used to construct the associated change relationship graph between object data based on the associated change rule;The associated change relationship graph is a directed acyclic graph for representing the associated change relationship between object data;The data update unit is used to change the associated data of the changed data according to the associated change relationship graph when the object data change in the requirement object tree is identified, and update the multiple operations of data;When the associated change rule change is identified, a new associated change relationship graph is generated based on the changed associated change rule, and the multiple operations of data are updated according to the new associated change relationship graph.

[0014] The application has the following advantages and beneficial effects:

[0015] The application can effectively realize the traceability of complex associated change and modification operation of data on the basis of unified formatted storage by unifying data model structure, inducing data change rule, designing business rule engine based on directed acyclic graph and fusing the design concept of one-way data flow. BRIEF DESCRIPTION OF DRAWINGS

[0016] Figure 1 An exemplary schematic diagram of the associated change relationship provided by the present application is shown in the following figure.

[0017] Figure 2 An exemplary schematic diagram of the associated change relationship provided by the present application is shown in the following figure. DETAILED DESCRIPTION

[0018] For the purpose, technical solutions and advantages of the embodiments of the present application to be clearer, the technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. The components of the embodiments of the present application described and shown in the drawings herein can be arranged and designed in various different configurations.

[0019] The present application provides a dynamic traceable data interaction method based on a DAG rule engine, comprising:

[0020] A CAE (Computer Aided Engineering) data model is constructed, and data operation is performed through the CAE data model. The CAE data model refers to a data model focusing on data storage after data abstraction of CAE simulation data. CAE simulation data is of multiple types and high dimensions, and each type is usually associated with specific concept semantics in the simulation field. There are relationships such as nesting and parallelism between data and data. Data operation refers to simulation operation on data.

[0021] In some embodiments, the CAE data model is constructed, and data operation is performed through the CAE data model, comprising:

[0022] CAE simulation data is abstracted into simulation concept semantics and simulation data, and the simulation data is taken as the CAE data model. Simulation concept semantics refers to abstract information of data, which can include simulation object categories, parameter physical meanings, and field-specific association rules between data.

[0023] A basic object tree is constructed for simulation data in the CAE data model; the object tree is divided into multiple layers from top to bottom, the upper layer object includes multiple lower layer objects, and each object includes attribute parameters. The basic object tree refers to the object tree constructed for all data in the CAE data model. The attribute parameters of each object can be represented by Boolean, number, string, array and dictionary, etc. For example, each piece of data can be regarded as an object, and the object tree stores the attribute information of each object itself and the relationship between objects, which is a containing relationship. For a certain object, it stores the name of the object, the type of the object, the value of the data, the validity of the data, and other attributes, as well as the sub-objects contained by the object. Specifically, a “mesh_001” object can have “mesh type”, “tetrahedral mesh parameters”, “hexahedral mesh parameters” and other sub-objects. For the “mesh type” object, it has an int integer as the value attribute of the data, which is used to indicate whether it is a tetrahedral mesh or a hexahedral mesh; and for the “tetrahedral mesh parameters” object, it can have “element size”, “growth rate”, “curvature control” and other sub-objects; and for the “element size” object, it can have “average element size”, “minimum element size”, “maximum element size” and other sub-objects.

[0024] The objects or object combinations in the basic object tree are nested and represented through the add-delete-modify-query interface to obtain a requirement object tree. The add-delete-modify-query interface refers to a unified interface provided by the CAE data model for basic operations on object data in the basic object tree. The standardized entrance for data operation is realized, and it is ensured that all data processing behaviors follow uniform rules to avoid operation confusion. The requirement object tree refers to the object tree obtained by adding, deleting, modifying and querying the basic object tree according to simulation requirements. The object refers to the basic unit carrying simulation data in the CAE data model, and each object includes its own attribute information (such as name, data type, value, validity and validity, etc.), and can include multiple sub-objects. The object combination refers to a set composed of multiple objects having a containing relationship, the upper layer object in the set contains one or more lower layer objects, and the lower layer object can further include sub-objects, forming a hierarchical structure, corresponding to a group of data entities having a correlation relationship in the simulation scene.

[0025] The object data in the requirement object tree is processed through the visitor pattern to realize various operations (i.e., personalized operations) of the data. The visitor pattern refers to a programming design pattern for implementing personalized operations of the data in the CAE data model, the core of which is to separate the interpretation right and processing logic of the data from the requirement object tree (data carrier) and assign them to a special visitor (functional module); the requirement object tree only provides a data access interface, and different visitors interpret and process the data according to their own requirements, realize the decoupling of data storage and data operation, and adapt to diversified data processing scenarios. The personalized operation refers to a non-general data processing behavior realized by the visitor pattern based on the requirement object tree data, which needs to be designed in combination with the specific functional requirements of the CAE simulation, is different from the basic data operations such as adding, deleting, modifying and inquiring, and aims to meet the customized requirements such as data verification, report export and visual display, and the operation process does not modify the storage structure of the requirement object tree itself. Taking the mesh_001 in the CAE software as an example, the structure of the requirement object tree is mesh_001, tetrahedral mesh parameters, element size and average element size / minimum element size in turn, and the data processing flow of the parameter verification visitor can be: the visitor traverses the mesh_001 requirement object tree, reads the average element size and minimum element size data in turn, verifies the data legality according to the CAE mesh partitioning rules (such as the minimum element size needs to be > 0), outputs the invalid parameter prompt if the minimum element size is negative, and completes the personalized operation of data verification. For the report export visitor processing data: the visitor accesses the mesh_001 requirement object tree, extracts the mesh type (value 0, representing tetrahedron), average element size (5 mm), minimum element size (3 mm) and other data, arranges them into a mesh parameter report according to a preset format, and exports them as an Excel document, realizing the personalized operation of data reporting.

[0026] In some embodiments, the requirement object tree is also mapped into a document object (such as a json document, an xml document, etc.), and the document object is accessed in a binary manner. For example, the simulation data in the data model comes from different fields and different problems, although the data is huge, the data itself is an object tree composed of a plurality of computer programming basic objects, and this object tree can be mapped into a document object, and the data access performance can be improved through binary access and other means.

[0027] A DAG rule engine is constructed and data operations are updated by updating the DAG rule engine. The DAG rule engine is used to centrally process the association change rules of the data in the requirement object tree, and maintain the directed acyclic graph (DAG) relationship between the data. In some embodiments, the DAG can be centrally stored in the DAG rule engine, or can be stored separately on each data object (i.e., stored on the object tree), and the implementation can vary. The object itself can be stored in the DAG, or the full path on the object tree can be stored. For example, the "tetrahedron mesh parameter" object of "mesh_001" is invalid when the "mesh type" is equal to 1, and valid when the "mesh type" is equal to 0. The validity of the " / mesh_001 / tetrahedron mesh parameter" object is affected by the value of the " / mesh_001 / mesh type" object, so both the " / mesh_001 / tetrahedron mesh parameter" object and the " / mesh_001 / mesh type" object should be added to the same chain of the DAG.

[0028] In some embodiments, the DAG rule engine is constructed and data operations are updated by updating the DAG rule engine, including:

[0029] Based on the association change relationship between the object data, the association change rules of the object data are determined. The association change relationship refers to the dynamic dependency association between the data (objects) in the requirement object tree in the CAE software, which is manifested as a corresponding relationship that when a certain data (target object) changes, other associated data (observer object) will be adjusted. The association change rule refers to an abstract description of the association change relationship of the data in the CAE software, which is used to clearly define the specific adjustment logic (such as parameter value synchronization, validity switching, and / or quantity matching, etc.) that the observer object needs to perform after the target object data changes.

[0030] Based on the association change rules, an association change relationship graph between the object data is constructed. As shown in Figure 1 The association change relationship graph is a directed acyclic graph used to represent the association change relationship between the object data. Among them, A, B, C, D and E are different objects in the requirement object tree.

[0031] When the object data change in the demand object tree is identified, the associated data of the change data is changed according to the association change relationship graph, and the personalized (multiple) operations of the data are updated. The change data refers to the data object that has changed. The associated data refers to other object data that has an association relationship with the change data. For example, (1) after the value of a certain parameter of object A changes, the value of a certain parameter of object B also needs to change synchronously; (2) the value of a certain parameter of object D needs to be consistent with the number of objects C added by the user at all times; (3) object E can be added or deleted by the user multiple times, and the value of a certain parameter of object F needs to refer to a certain object E; (4) whether a certain parameter of object G is enabled depends on the value of a certain parameter of object H, and the like.

[0032] When the association change rule change is identified, a new association change relationship graph is generated based on the changed association change rule, and the rule change is performed according to the new association change relationship graph, and the personalized (multiple) operations of the data are updated. The changed association change rule refers to the association change rule that has changed. Based on the changed association change rule, a new association change relationship graph can be obtained. The rule engine can be implemented using the observer design pattern and the programming idea of callback, as shown in Figure 2 , which includes a target (i.e., a data object) A and a target C, and a map object of observer information (DAG information, including associated objects and association relationships, such as other data objects B and E that have an association relationship with the data object (target) A, and multiple association functions with the data object B: an initial association function , a first association function , a second association function related to the data object E, and other data objects D and E that have an association relationship with the data object (i.e., the target) C, and third and fourth association functions and , and a pure function ruleEngine() that executes rules. The map records the mapping relationship between all target objects in the system and the observers of the target objects, and the changes (which type of rule to execute) that the observers will make after receiving updates. The ruleEngine() internally implements the processing of all rules, including which rule the target object and the observer object belong to when the function is executed, and the data of the observer object is updated after the function is executed.

[0033] The data modification interface is called through the user interface to perform updating data operation and display. The user interface can be a display screen. The data modification interface is used to receive instructions input by the user through the user interface. In some embodiments, the data modification interface is called through the user interface to perform updating data operation and display, including: sending a data modification instruction through the data modification interface and storing the data modification instruction; generating a changed data object and / or a changed associated change rule based on the data modification instruction, and updating personalized operation(s) of the data; and updating the user interface display based on the personalized operation(s) of the data.

[0034] The application also provides a dynamic traceable data interaction system based on a DAG rule engine. Based on the MVC mode in software development, CAE software can be divided into three parts: data model, logic control and interface display. Therefore, the dynamic traceable data interaction system based on the DAG rule engine can include a data model part, a logic control part and an interface display part.

[0035] The data model part is used to perform data operation. The data model part includes a CAE data model, through which data operation is performed. The CAE data model includes a data abstraction unit, a basic object tree construction unit, a requirement object tree construction unit and a data operation unit. The data abstraction unit is used to abstract CAE simulation data into simulation concept semantics and simulation data, and the simulation data is used as the CAE data model. The basic object tree construction unit is used to construct a basic object tree for the simulation data in the CAE data model. The object tree is divided into multiple layers from top to bottom. The upper layer object includes multiple lower layer objects, and each object includes attribute parameters. The requirement object tree construction unit is used to nest objects or object combinations in the basic object tree through a CRUD interface to obtain a requirement object tree. The data operation unit is used to process object data in the requirement object tree through a visitor mode to realize personalized operation(s) of the data.

[0036] The CAE simulation data types are various and high-dimensional, and each type is usually associated with specific concept semantics in the simulation field. There are nesting, juxtaposition and other relationships between data and data. The simulation concept semantics is extracted from the data model, and the data model focuses on data storage. The data contained in the software is regarded as an object tree, which is divided into multiple layers from top to bottom. The upper layer objects can include multiple lower layer objects, and each object has its own attribute parameters, which can be represented by nesting Boolean, numerical, string, array and / or dictionary, etc. basic programming objects or combinations of objects. (It can also be uniformly represented by the "variant" type in modern programming languages) That is, although the simulation data in the data model may come from different fields, different problems, and large amounts of data, the data itself is an object tree composed of several computer programming basic objects when stored, and this object tree can be mapped to a document object (such as a json document and / or an xml document). Further, the data access performance can be improved by binary access and other means. The data model provides data addition, deletion, modification and query interfaces.

[0037] In terms of implementation, the composition pattern in the design pattern can be used for programming implementation of data objects to realize unified storage of data; the visitor pattern is used to give different visitors the right to interpret data to realize personalized (multiple) operations on data. Of course, the data can also be accessed by using the subclassing method instead of the visitor pattern.

[0038] The logic control part adopts the observer design pattern and the callback method to realize automatic change of the system after the data changes to maintain the correctness of the remaining data. The logic control part includes a DAG rule engine, which updates the data operation by updating the DAG rule engine. The DAG rule engine includes an associated change rule determination unit, an associated change relationship graph construction unit and a data update unit; the associated change rule determination unit is used to determine the associated change rule of the object data based on the associated change relationship between the object data; the associated change relationship graph construction unit is used to construct the associated change relationship graph between the object data based on the associated change rule; the associated change relationship graph is a directed acyclic graph for representing the associated change relationship between the object data; the data update unit is used to change the associated data of the changed data according to the associated change relationship graph when the object data in the demand object tree is identified to change, and update the personalized (multiple) operation of the data; when the associated change rule is identified to change, a new associated change relationship graph is generated based on the changed associated change rule, and the rule is changed according to the new associated change relationship graph, and the personalized (multiple) operation of the data is updated.

[0039] In addition to the access and modification of the data model, the present application focuses on how the system automatically changes to maintain the correctness of the remaining data after a data change. (In CAE software, there are many such scenarios: when selecting a tetrahedral mesh during mesh partitioning, the relevant parameter data of the hexahedral mesh should immediately become invisible (invalid), and vice versa if the user switches to a hexahedral mesh, the relevant parameter data of the tetrahedral mesh should become invalid. For example, the value of a parameter of object B depends on the value of a parameter of object A and needs to change synchronously.) The association between data changes can be abstracted as a series of "rules". A "rule" is that after the data of a certain object changes, how the associated objects should change. For example: (1) after the value of a parameter of object A changes, the value of a parameter of object B also needs to change synchronously; (2) the value of a parameter of object D needs to always be consistent with the number of objects C added by the user; (3) object E can be added or deleted by the user, and the value of a parameter of object F needs to refer to a certain object E. (4) whether a parameter of object G is enabled depends on the value of a parameter of object H. And so on. There can be many such change rules in the software, and these rules can be triggered one-to-many and chain. For example, object A changes to trigger objects B and C to change, and object C changes to further trigger objects D and E to change. In order to avoid circular dependencies, the association between data changes is a directed acyclic graph (DAG) as shown in FIG. 1. Figure 1 The module that centrally processes rules and maintains the DAG is the "rule engine". After a data (target) changes, the rule engine is triggered, and its associated objects (observers) change according to the corresponding rules, which will trigger the rule engine to execute the changes, and so on according to the directed acyclic graph recursively. After the execution is complete, the data model of the system remains correct.

[0040] At the implementation level, the rule engine can be implemented using the observer design pattern and the programming idea of callback, which includes a map object that records the relationship between targets and observers (DAG information), and a pure function ruleEngine() that executes rules. The map records the mapping relationship between all target objects and observers in the system, and what changes the observer will make (which type of rule to execute) after receiving the update. ruleEngine() internally implements the processing of all rules, and its input is the target object, the observer object, and which rule it belongs to. After the function is executed, the data of the observer object is updated.

[0041] The interface display part is used for interface display and / or personalized operation of the simulation data in the data model. The interface display part includes a user interface and a data modification interface, and the interface display part performs interface display and / or personalized operation of the simulation data in the data model by receiving a data modification instruction sent by the data modification interface.

[0042] The user interface is responsible for displaying the data model to the user, and the user can directly read the simulation data in the data model for interface display or implement other functions. However, for data modification, in order to avoid the problem of confusion and poor maintainability caused by the fact that data model can be modified everywhere in the interface. The application draws on the design idea of "one-way data flow", and the data model provides a unified data modification interface to the upper layer (such as the interface). Data modification, rule engine triggering, and interface data refreshing are all encapsulated in this interface. The user's modification of the data can only be performed by sending instructions to call this interface. After storing the instructions, the changes of the data model can be recorded and traced.

[0043] The above is only the preferred embodiment of the present application and is not used to limit the present application. For those skilled in the art, the present application can have various modifications and changes. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A method for dynamic traceable data interaction based on DAG rule engine, characterized in that, The method comprises the following steps: constructing a CAE data model and performing data operation through the CAE data model; extracting CAE simulation data into simulation concept semantics and simulation data, and taking the simulation data as a CAE data model; constructing a basic object tree for the simulation data in the CAE data model; the object tree is divided into multiple layers from top to bottom, the upper layer object comprises multiple lower layer objects, and each object comprises attribute parameters; nesting representation of objects or object combinations in the basic object tree is performed through an add, delete, modify and query interface, and a requirement object tree is obtained; object data in the requirement object tree is processed through a visitor mode, and multiple operations on the data are realized; a DAG rule engine is constructed, and data operation is updated through updating the DAG rule engine; the association change rule of the object data is determined based on the association change relationship between the object data; an association change relationship graph between the object data is constructed based on the association change rule; the association change relationship graph is a directed acyclic graph for representing the association change relationship between the object data; when the object data change in the requirement object tree is identified, the association data of the changed data is changed according to the association change relationship graph, and the multiple operations on the data are updated; when the association change rule change is identified, a new association change relationship graph is generated based on the changed association change rule, the rule change is performed according to the new association change relationship graph, and the multiple operations on the data are updated; the observer design mode and the callback method are adopted to realize automatic change in the system after the data change to maintain the correctness of the data; the data modification interface is called through a user interface to perform update data operation and display; a data modification instruction is sent through the data modification interface, and the data modification instruction is stored; the changed data object and / or the changed association change rule are generated based on the data modification instruction, and the multiple operations on the data are updated; the user interface display is updated based on the multiple operation results of the data.

2. The method of claim 1, wherein, The requirement object tree is also mapped to a document object, and the document object is accessed in a binary manner.

3. A DAG rule engine based dynamic traceable data interaction system utilizing a DAG rule engine based dynamic traceable data interaction method according to any one of claims 1-2, characterized in that, The method comprises a data model part, a logic control part and an interface display part; the data model part is used for data operation; the logic control part adopts the observer design mode and the callback method to realize automatic change in the system after the data change to maintain the correctness of the remaining data; the interface display part is used for interface display and / or individual operation of the simulation data in the data model.

4. The dynamic traceable data interaction system based on DAG rule engine according to claim 3, characterized in that, The data model part comprises a CAE data model, and data operation is performed through the CAE data model; the logic control part comprises a DAG rule engine, and data operation is updated through updating the DAG rule engine; the interface display part comprises a user interface and a data modification interface, and the simulation data in the data model is displayed and / or individually operated through receiving the data modification instruction sent by the data modification interface.

5. The dynamic traceable data interaction system based on DAG rule engine according to claim 4, characterized in that, The CAE data model comprises a data extraction unit, a basic object tree construction unit, a requirement object tree construction unit and a data operation unit; The data abstraction unit is configured to abstract CAE simulation data into simulation concept semantics and simulation data, and to take the simulation data as a CAE data model; The base object tree construction unit is configured to construct a base object tree for simulation data in the CAE data model; The object tree is divided into multiple layers from top to bottom, and an upper layer object includes multiple lower layer objects, and each object includes attribute parameters; The requirement object tree construction unit is configured to perform nested representation on objects or object combinations in the base object tree through an add, delete, modify and query interface, to obtain a requirement object tree; The data operation unit is configured to process object data in the requirement object tree through a visitor mode, to implement multiple operations on data.

6. The dynamic traceable data interaction system based on DAG rule engine according to claim 5, characterized in that, The system further includes a storage unit configured to map the requirement object tree into a document object, and to access the document object in a binary manner.

7. The dynamic traceable data interaction system based on DAG rule engine according to claim 4, characterized in that, The DAG rule engine includes an association change rule determination unit, an association change relationship graph construction unit and a data updating unit; The association change rule determination unit is configured to determine an association change rule of object data based on an association change relationship between the object data; The association change relationship graph construction unit is configured to construct an association change relationship graph between the object data based on the association change rule; the association change relationship graph is a directed acyclic graph used to represent the association change relationship between the object data; The data updating unit is configured to, when object data change in the requirement object tree is identified, change associated data of the changed data according to the association change relationship graph, and to update multiple operations on data; when an association change rule change is identified, a new association change relationship graph is generated based on the changed association change rule, and a rule change is performed according to the new association change relationship graph, to update multiple operations on data.

Images