CN118394405B - Traceability method and traceability system for low-code platform module - Google Patents

Abstract

The invention discloses a tracing method and a tracing system for a low-code platform module, wherein the method comprises the following steps: defining module information of a low code platform based on a preset module definition; according to the module definition, in the process of designing and defining pages, entities, business logic, workflows and events by the current low-code platform, module information is extracted and a dependency relationship is constructed by analyzing definition data; the method comprises the steps of carrying out directed graph data structure storage on module information extracted from analysis definition data and dependence association; extracting a module number, constructing and displaying all dependency graphs related to the module according to the module number, and displaying through a chart; and deleting the module information and the dependent module record information related to the module information according to the module number. The invention displays the dependency relationship between the modules through the directed graph, realizes the comprehensive tracing of the modules in the low-code platform, and improves the transparency and controllability of the development process.

Description

A tracing method and system for low-code platform modules

Technical Field

The present invention relates to the field of data processing technology, and more specifically, to a tracing method and system for a low-code platform module.

Background Art

With the rapid development of low-code platforms, more and more companies and developers are beginning to adopt low-code technologies to quickly build and deploy applications; however, in the development process of low-code platforms, module tracing and management has become an important issue; traditional code tracing methods are difficult to directly apply to low-code platforms, so a module tracing algorithm suitable for low-code platforms is needed.

Summary of the invention

The purpose of the present invention is to provide a tracing method and system for low-code platform modules, which can realize comprehensive tracing of modules in the low-code platform and improve the transparency and controllability of the development process.

A first aspect of the present invention provides a tracing method for a low-code platform module, comprising:

Define the module information of the low-code platform based on the preset module definition;

According to the module definition, in the current low-code platform, during the design and definition of pages, entities, business logic, workflows, and events, module information is extracted and dependencies are constructed by parsing the definition data;

The module information and dependency association extracted from the parsed definition data are stored in a directed graph data structure;

Extract the module number, build and display all dependency graphs related to the module according to the module number, and display them through charts;

Delete the module information and related dependent module record information according to the module number.

In this solution, the steps of defining the module information of the low-code platform specifically include:

Obtain materials used in the design software process of the low-code platform;

The material is set as a module, wherein when there is only one material in the module, it is set as an atomic module; when there are two or more materials in the module, it is set as a combined module;

Based on the preset identifier, each material is identified to obtain the module identifier;

Based on the preset classification and numbering standards, the modules are numbered and classified to obtain module numbers and module types.

In this solution, the parsed definition data is specifically: parsed json data of page design, parsed json data of business logic design, parsed json data of entity definition, parsed json data of event definition, and parsed json data of workflow definition.

In this solution, the step of parsing the json data of the page design specifically includes:

Extract page parameters, page variable module information and record them;

Extract the page’s imported data source module information and record it;

Extract and record the module information used by each component of the page. The module information includes variables, expressions, functions, action flows, data sources, and business logic.

Extract the page action flow and the module information used in the action flow and record them;

Extract the number, title and module type of the current page;

The number, title, and module type of the current page are recorded in the corresponding module information table, and are dependently associated with the recorded page data.

In this solution, the steps of parsing the json data designed by the business logic specifically include:

Extract business logic input module information and record it;

Extract business logic and introduce data source module information and record it;

Extract and record the information of each node module of the business logic, and extract and record the information of the business logic output parameter module;

The number, name and module type of the current business logic are extracted and recorded in the corresponding module information table, and are dependently associated with the recorded business logic data.

In this solution, the step of parsing the JSON data defined by the entity specifically includes:

Extract the entity's field module information and record it;

Extract the current entity's ID, entity name and module type;

The number, entity name and module type of the current entity are recorded in the corresponding module information table, and are dependently associated with the recorded entity data.

In this solution, the step of parsing the JSON data of the event definition specifically includes:

Extract the attribute module information of the event and record it;

Extract the subscribed business logic module information and record it;

Extract the current event number, event name and module type;

The number, event name and module type of the current event are recorded in the corresponding module information table, and are dependently associated with the recorded event data.

In this solution, the step of parsing the json data defined by the workflow specifically includes:

Extract work flow parameter module information and record it;

Extract and record the information of each node module in the workflow;

Extract the current workflow number, workflow name and module type;

The number, name and module type of the current workflow are recorded in the corresponding module information table, and are dependently associated with the recorded workflow data.

This plan also includes:

Extract the elements in the module, parse and record the elements in the module, and obtain the recorded element data;

Extract the module number, module name and module type;

The module number, module name and module type are recorded in the corresponding module information table, and the module dependency information is constructed with the corresponding recorded element data.

A second aspect of the present invention provides a traceability system for a low-code platform module, including: a definition module, an extraction module, a recording module, a traceability module, and a management module;

The definition module is used to perform module definition for all materials used in the low-code platform;

The extraction module is used to parse the current low-code platform to obtain modules and module definition lists;

The recording module is used to store the parsed module information;

The tracing module is used to construct a dependency association graph of the module according to the module number, module type and module name, and determine the dependency relationship of each module according to the dependency association graph;

The management module is used to manage the modules.

The present invention discloses a tracing method and system for low-code platform modules. The present invention displays the dependency relationship between modules through a directed graph, realizes comprehensive tracing of modules in the low-code platform, and improves the transparency and controllability of the development process; by recording the detailed information and dependency relationships of the modules, it helps developers to better understand and manage the modules; improves the development efficiency and quality of the low-code platform, and reduces development and maintenance costs.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 shows a flow chart of a tracing method of a low-code platform module of the present invention;

Figure 2 shows a block diagram of a traceability system of a low-code platform module of the present invention.

DETAILED DESCRIPTION

In order to more clearly understand the above-mentioned purpose, features and advantages of the present invention, the present invention is further described in detail below in conjunction with the accompanying drawings and specific embodiments. It should be noted that the embodiments of the present application and the features in the embodiments can be combined with each other without conflict.

In the following description, many specific details are set forth to facilitate a full understanding of the present invention. However, the present invention may also be implemented in other ways different from those described herein. Therefore, the protection scope of the present invention is not limited to the specific embodiments disclosed below.

Figure 1 shows a flow chart of a tracing method for a low-code platform module of the present invention.

As shown in FIG1 , the present invention discloses a tracing method for a low-code platform module, including:

S101, defining module information of the low-code platform based on a preset module definition;

S102, according to the module definition, in the process of designing and defining pages, entities, business logic, workflows, and events on the current low-code platform, extracting module information and building dependencies by parsing definition data;

S103, storing the module information and dependency association extracted from the parsed definition data in a directed graph data structure;

S104, extracting the module number, constructing and displaying all dependency association graphs related to the module according to the module number, and displaying them through a chart;

S105, deleting the module information and the related dependent module record information according to the module number.

According to an embodiment of the present invention, all material pages, entities, business logic, events, workflows used in the low-code platform, as well as elements used in the page, business logic, entity and event design process, including components, parameters, expressions, functions, action flows, data sources, entity fields, image materials, files, events and other attributes are defined as modules and classified according to different types; the dependent module record information related thereto is the module record information of all modules that have a dependency relationship with the corresponding deleted module. For example, if the module number is a, the dependency association graph related to the module number a is extracted. For example, if module b and module a have a dependency association, when module a is deleted, module b is also deleted at the same time; all dependency association graphs related to the module are all dependency association graphs of the module. For example, if the dependency association graph contains module a, module b and module c, the corresponding dependency association graph is related to module a, module b and module c.

According to an embodiment of the present invention, the step of defining module information of the low-code platform specifically includes:

Obtain materials used in the design software process of the low-code platform;

The material is set as a module, wherein when there is only one material in the module, it is set as an atomic module; when there are two or more materials in the module, it is set as a combined module;

Based on the preset identifier, each material is identified to obtain the module identifier;

Based on the preset classification and numbering standards, the modules are numbered and classified to obtain module numbers and module types.

It should be noted that the materials used in the design software process of the low-code platform are marked as modules. Materials are divided into two types: atomic materials and composite materials. Atomic materials include entity tables, fields in entity tables, business logic, data sources introduced by business logic, input parameters, variables, output parameters, expressions, nodes, events, event attributes, pages, page data sources, page input parameters, page action flows, action inflow parameters, action outflow parameters, expressions, action flow nodes, page components, picture materials, video materials, file materials, workflows, etc.; composite materials are designed by combining ancestral materials according to certain business needs, such as login modules, etc. Each module has a unique identifier.

According to an embodiment of the present invention, the parsed definition data is specifically: parsed json data of page design, parsed json data of business logic design, parsed json data of entity definition, parsed json data of event definition, and parsed json data of workflow definition.

It should be noted that by parsing the definition data, module extraction and tagging the dependencies between modules are completed, starting from the atomic module, gradually analyzing the combined modules, and recording the dependencies one by one.

According to an embodiment of the present invention, the step of parsing the JSON data of the page design specifically includes:

Extract page parameters, page variable module information and record them;

Extract the page’s imported data source module information and record it;

Extract and record the module information used by each component of the page. The module information includes variables, expressions, functions, action flows, data sources, and business logic.

Extract the page action flow and the module information used in the action flow and record them;

Extract the number, title and module type of the current page;

The number, title, and module type of the current page are recorded in the corresponding module information table, and are dependently associated with the recorded page data.

It should be noted that the recorded page data includes page parameters, page variable module information, page imported data source module information, module information used by each component of the page, page action flow and module information used in the action flow.

According to an embodiment of the present invention, the step of parsing the JSON data of the business logic design specifically includes:

Extract business logic input module information and record it;

Extract business logic and introduce data source module information and record it;

Extract and record the information of each node module of the business logic, and extract and record the information of the business logic output parameter module;

The number, name and module type of the current business logic are extracted and recorded in the corresponding module information table, and are dependently associated with the recorded business logic data.

It should be noted that the recorded business logic data includes business logic input parameter module information, business logic introduced data source module information, business logic each node module information, and business logic output parameter module information.

According to an embodiment of the present invention, the step of parsing the JSON data defined by the entity specifically includes:

Extract the entity's field module information and record it;

Extract the current entity's ID, entity name and module type;

The number, entity name and module type of the current entity are recorded in the corresponding module information table, and are dependently associated with the recorded entity data.

It should be noted that the recorded entity data includes the field module information of the entity.

According to an embodiment of the present invention, the step of parsing the JSON data of the event definition specifically includes:

Extract the attribute module information of the event and record it;

Extract the subscribed business logic module information and record it;

Extract the current event number, event name and module type;

The number, event name and module type of the current event are recorded in the corresponding module information table, and are dependently associated with the recorded event data.

It should be noted that the recorded event data includes the attribute module information of the event and the subscribed business logic module information.

According to an embodiment of the present invention, the step of parsing the JSON data of the workflow definition specifically includes:

Extract work flow parameter module information and record it;

Extract and record the information of each node module in the workflow;

Extract the current workflow number, workflow name and module type;

The number, name and module type of the current workflow are recorded in the corresponding module information table, and are dependently associated with the recorded workflow data.

According to an embodiment of the present invention, the recorded workflow data includes workflow parameter module information and workflow each node module information.

According to an embodiment of the present invention, it also includes:

Extract the elements in the module, parse and record the elements in the module, and obtain the recorded element data;

Extract the module number, module name and module type;

The module number, module name and module type are recorded in the corresponding module information table, and the module dependency information is constructed with the corresponding recorded element data.

It should be noted that the elements in the module include entities, business logic, workflow, events and page information, and the recorded element data includes recorded entity data, recorded business logic data, recorded workflow data, etc.

According to an embodiment of the present invention, the step of building a dependency relationship specifically includes:

Run the modules one by one. If module a can only run after module b is finished running, then module a and module b are set to have a dependency relationship, and module a depends on module b.

According to an embodiment of the present invention, it also includes:

Extract the directed graph of dependency relationships;

Determine the dependency relationship between modules based on the directed graph of dependency associations;

If there is mutual dependence or closed-loop dependence between the dependencies between modules, a warning message will be generated.

It should be noted that if module a depends on module b, and module b depends on module a, then it means that module a and module b are mutually dependent on each other; if module a depends on module b, module b depends on module c, and module c depends on module a, then it means that module a, module b and module c have a closed-loop dependency. The pairwise mutual dependency or closed-loop dependency is not allowed to exist. Therefore, a warning message is generated to prompt the user end that there is an error in the corresponding directed graph.

According to an embodiment of the present invention, it also includes:

When there is no dependency relationship between a module in the directed graph and other modules, the corresponding module is marked to obtain a marked module;

After deleting the marked modules one by one, run the low-code platform without the marked modules to obtain the running test results. If the running test results are normal, the corresponding marked modules are redundant modules.

If the running test result is abnormal, the corresponding marked module is not a redundant module.

It should be noted that the low-code platform is a platform that can run normally. When a module has no dependency relationship with other modules, it means that the corresponding module is a separately run module. If the corresponding marked module is deleted and the low-code platform without the marked module can run normally, it means that the corresponding marked module is a redundant module, and deleting the corresponding marked module is the correct operation. If the running test result is abnormal, the corresponding marked module will be restored.

According to an embodiment of the present invention, it also includes: when parsing the module information and dependency associations extracted from the definition data for graph data structure storage, modules without dependency associations are inserted for storage first, and modules with dependency associations are inserted for storage after the modules they depend on are inserted for storage.

It should be noted that, for example, if module a depends on module b, module b is inserted into the storage first, and then module a is inserted into the storage, and module b points to module a through a directed arrow to indicate that module a depends on module b.

Figure 2 shows a block diagram of a traceability system of a low-code platform module of the present invention.

As shown in FIG2 , the second aspect of the present invention provides a traceability system for a low-code platform module, including: a definition module, an extraction module, a recording module, a traceability module, and a management module;

The definition module is used to perform module definition for all materials used in the low-code platform;

The extraction module is used to parse the current low-code platform to obtain modules and module definition lists;

The recording module is used to store the parsed module information;

The tracing module is used to construct a dependency association graph of the module according to the module number, module type and module name, and determine the dependency relationship of each module according to the dependency association graph;

The management module is used to manage the modules.

According to an embodiment of the present invention, module definition is performed for all materials used in the low-code platform by defining modules, and then the defined module information is extracted. Through a preset parsing algorithm, each attribute in the corresponding json data is gradually parsed, and module data is automatically constructed according to the defined module classification. These data include module unique identifier, module name, module type, associated module number, creation event, creator, etc., which constitute the definition content of the module. After the json data is parsed, a parsed module definition list is obtained, and various module information is listed in the module definition list in sequence; the recording module contains a repository to store the parsed module information, and the storage method adopts a directed graph-based storage method to facilitate data tracing and association query; according to the module number, module type, and module name, the dependency association graph of the module can be quickly constructed, and it can be quickly and efficiently displayed in the form of a dependency association graph to quickly clarify the dependency relationship of each module; the management module includes a deletion unit and an update unit, and the deletion unit is used to delete the module and simultaneously delete the module dependency relationship and module record data; the update unit is used to update the module version and update the module dependency association graph at the same time.

The present invention discloses a tracing method and system for low-code platform modules. The present invention displays the dependency relationship between modules through a directed graph, realizes comprehensive tracing of modules in the low-code platform, and improves the transparency and controllability of the development process; by recording the detailed information and dependency relationships of the modules, it helps developers to better understand and manage the modules; improves the development efficiency and quality of the low-code platform, and reduces development and maintenance costs.

In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as: multiple units or components can be combined, or can be integrated into another system, or some features can be ignored, or not executed. In addition, the coupling, direct coupling, or communication connection between the components shown or discussed can be through some interfaces, and the indirect coupling or communication connection of the devices or units can be electrical, mechanical or other forms.

The units described above as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units; they may be located in one place or distributed on multiple network units; some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

In addition, all functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may be separately used as a unit, or two or more units may be integrated into one unit; the above-mentioned integrated units may be implemented in the form of hardware or in the form of hardware plus software functional units.

A person skilled in the art can understand that: all or part of the steps of implementing the above method embodiment can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it executes the steps of the above method embodiment; and the aforementioned storage medium includes: mobile storage devices, read-only memories (ROM, Read-Only Memory), random access memories (RAM, Random Access Memory), disks or optical disks, etc. Various media that can store program codes.

Alternatively, if the above-mentioned integrated unit of the present invention is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present invention can be essentially or partly reflected in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the methods described in each embodiment of the present invention. The aforementioned storage medium includes: various media that can store program codes, such as mobile storage devices, ROM, RAM, magnetic disks or optical disks.

Claims (8)

1. A tracing method for a low-code platform module, characterized by comprising: Define the module information of the low-code platform based on the preset module definition; According to the module definition, in the current low-code platform, during the design and definition of pages, entities, business logic, workflows, and events, module information is extracted and dependencies are constructed by parsing the definition data; The module information and dependency association extracted from the parsed definition data are stored in a directed graph data structure; Extract the module number, build and display all dependency graphs related to the module according to the module number, and display them through charts; Delete the module information and related dependent module record information according to the module number; The step of defining the module information of the low-code platform specifically includes: Obtain materials used in the design software process of the low-code platform; The material is set as a module, wherein when there is only one material in the module, it is set as an atomic module; when there are two or more materials in the module, it is set as a combined module; Based on the preset identifier, each material is identified to obtain the module identifier; Based on the preset classification and numbering standards, the modules are numbered and classified to obtain module numbers and module types; The parsing definition data specifically includes: parsing the json data of page design, parsing the json data of business logic design, parsing the json data of entity definition, parsing the json data of event definition, and parsing the json data of workflow definition. 2. According to a tracing method of a low-code platform module according to claim 1, it is characterized in that the step of parsing the JSON data of the page design specifically includes: Extract page parameters, page variable module information and record them; Extract the page’s imported data source module information and record it; Extract and record the module information used by each component of the page. The module information includes variables, expressions, functions, action flows, data sources, and business logic. Extract the page action flow and the module information used in the action flow and record them; Extract the number, title and module type of the current page; The number, title, and module type of the current page are recorded in the corresponding module information table, and are dependently associated with the recorded page data. 3. According to a low-code platform module tracing method according to claim 1, it is characterized in that the step of parsing the JSON data of the business logic design specifically includes: Extract business logic input module information and record it; Extract business logic and introduce data source module information and record it; Extract and record the information of each node module of the business logic, and extract and record the information of the business logic output parameter module; The number, name and module type of the current business logic are extracted and recorded in the corresponding module information table, and are dependently associated with the recorded business logic data. 4. According to a low-code platform module tracing method according to claim 1, it is characterized in that the step of parsing the JSON data defined by the entity specifically includes: Extract the entity's field module information and record it; Extract the current entity's ID, entity name and module type; The number, entity name and module type of the current entity are recorded in the corresponding module information table, and are dependently associated with the recorded entity data. 5. According to a low-code platform module tracing method according to claim 1, it is characterized in that the step of parsing the JSON data defined by the event specifically includes: Extract the attribute module information of the event and record it; Extract the subscribed business logic module information and record it; Extract the current event number, event name and module type; The number, event name and module type of the current event are recorded in the corresponding module information table, and are dependently associated with the recorded event data. 6. According to a low-code platform module tracing method according to claim 1, it is characterized in that the step of parsing the JSON data defined by the workflow specifically includes: Extract work flow parameter module information and record it; Extract and record the information of each node module in the workflow; Extract the current workflow number, workflow name and module type; The number, name and module type of the current workflow are recorded in the corresponding module information table, and are dependently associated with the recorded workflow data. 7. The tracing method of a low-code platform module according to claim 1, characterized in that it also includes: Extract the elements in the module, parse and record the elements in the module, and obtain the recorded element data; Extract the module number, module name and module type; The module number, module name and module type are recorded in the corresponding module information table, and the module dependency information is constructed with the corresponding recorded element data. 8. A tracing system for a low-code platform module, characterized in that it comprises: a definition module, an extraction module, a recording module, a tracing module and a management module; a program for implementing a tracing method for a low-code platform module as claimed in any one of claims 1 to 7; The definition module is used to perform module definition for all materials used in the low-code platform; The extraction module is used to parse the current low-code platform to obtain modules and module definition lists; The recording module is used to store the parsed module information; The tracing module is used to construct a dependency association graph of the module according to the module number, module type and module name, and determine the dependency relationship of each module according to the dependency association graph; The management module is used to manage the modules.