CN114661275A - Visual low-code system development platform - Google Patents
Visual low-code system development platform Download PDFInfo
- Publication number
- CN114661275A CN114661275A CN202210222543.2A CN202210222543A CN114661275A CN 114661275 A CN114661275 A CN 114661275A CN 202210222543 A CN202210222543 A CN 202210222543A CN 114661275 A CN114661275 A CN 114661275A
- Authority
- CN
- China
- Prior art keywords
- module
- visual
- user interface
- graphical user
- result
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/34—Graphical or visual programming
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
- G06F8/44—Encoding
- G06F8/443—Optimisation
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
The invention provides a visual low-code system development platform, and aims to solve the problems that in the prior art, a software system is long in development time period and high in labor cost. The visual low-code system development platform comprises: the system comprises a visualization module, a parser module and a process engine; the visual module defined with attributes and configuration comprises a graphical user interface, a visual business control and a process editor; the graphical user interface is used for laying out a visual business control and a visual process editor; the visual business control is arranged on the graphical user interface in a dragging mode; the visual process editor is arranged on the image graphical user interface in a dragging mode and is used for connecting visual business controls to form business process logic; the resolver module dynamically executes codes written on the visualization module by a user through the nodejs virtual machine; the process driving engine is used for driving the visualization module to work according to the business process. The development period is short, and the development cost of enterprises is reduced.
Description
Technical Field
The invention belongs to the technical field of system development, and particularly relates to a visual low-code system development platform.
Background
Software development is the process of building a software system or software parts in a system according to user requirements. Software development is a system engineering that includes requirement capture, requirement analysis, design, implementation, and testing. Software is typically implemented in a programming language, and is typically developed using software development tools by those skilled in the art who have the knowledge of the programming language.
In the traditional development, the programming development is more friendly to programmers, a lot of time for learning a programming language is spent on completing a system and software with general functions in a careless way without programming experience, and the development of the system is difficult to complete without programming logic thinking capability even if the system is learned. In addition, in the traditional development, not only needs to acquire and analyze user requirements in the early stage, but also needs to perform frame design and code writing in the middle stage, and finally needs to perform multiple rounds of tests to implement landing, so that the development period is long, and even if small-project development is performed, the development period needs about one month. The traditional development mode mainly depends on IT technical personnel to operate, and the technical personnel have high cost and high purchase price of system software.
Disclosure of Invention
The invention provides a visual low-code system development platform, and aims to solve the problems that in the prior art, a software system is long in development time period and high in labor cost.
In order to solve the technical problems, the technical scheme adopted by the invention is as follows:
a visual low-code system development platform, comprising: the system comprises a visualization module, a parser module and a process engine; the visualization module comprises a graphical user interface, a visualization business control and a process editor;
the graphical user interface: defining attributes and configurations, and laying out visual business controls and visual process editors;
the visual business control: defining attributes and configuration, and laying out on a graphical user interface in a dragging mode;
the visual flow editor: defining attributes and configurations, and arranging the attributes and the configurations on an image graphical user interface in a dragging mode and connecting visual business controls to form business process logic;
the resolver module: dynamically executing the attribute and configuration of each visualization module, and dynamically executing codes written on the visualization modules by a user through nodejs virtual machines;
the process-driven engine: and the visual module is used for driving the visual module to work according to the business process.
The further improved scheme is as follows: the visual low-code system development platform also comprises a routing module for processing authority and logs.
The further improved scheme is as follows: the routing module comprises a user-defined graphical user interface query route, a component data query route, a flow request route and a general system route.
The further improved scheme is as follows: the resolver module comprises a resolver module, a graphical user interface rendering resolver, a visual business control data query resolver and a visual business control verification resolver.
The further improved scheme is as follows: the visual low-code system development platform also comprises a data processing layer module, and the visual module can be inquired, added, modified, deleted, created, modified and customized sql by the data processing layer module.
Based on the scheme, the data processing layer module can adjust the properties and the configuration of the graphical user interface, the visual business control and the process editor so as to adapt to a system to be developed.
The further improved scheme is as follows: the visual low-code system development platform further comprises an exception handling module, an application module, a permission module and an approval module.
The permission module can judge the permission of the user, and the approval module is used for approval.
The further improved scheme is as follows: the application system developed by adopting the visual low-code system development platform has the following front-end triggering process:
s1, respectively sending an application module ID query request, a graphical user interface ID query request, a visual service control ID query request and a user permission verification request to a routing module through an application system;
s2, sending a request for inquiring whether the application module ID exists to the application module through the routing module;
s3, the application module inquires whether the application module ID exists through the data processing layer module;
s4, the data processing layer module returns the query result to the application module;
s5, if the application module ID is abnormal, an error is reported through an abnormal processing module;
s6, if the exception handling module reports an error, returning error information to the application system;
s7, if the application module ID exists, the application module returns a result of successful verification to the routing module;
s8, sending a request for inquiring whether the graphical user interface ID exists to the graphical user interface module through the routing module;
s9, the graphical user interface module inquires whether the ID of the graphical user interface exists through the data processing layer module;
s10, the data processing layer module returns the query result to the graphical user interface module;
s11, if the graphical user interface ID is abnormal, an error is reported through an abnormality processing module;
s12, if the exception handling module reports an error, returning error information to the application system;
s13, if the graphical user interface ID exists, the graphical user interface module returns a result of successful verification to the routing module;
s14, sending a request for inquiring whether the visual business control ID exists to the graphical user interface module through the routing module;
s15, the graphical user interface module inquires whether the visual business control ID exists through the data processing layer module;
s16, the data processing layer module returns the query result to the graphical user interface module;
s17, if the visual business control ID is abnormal, reporting an error through an abnormal processing module;
s18, if the exception handling module reports an error, returning error information to the application system;
s19, if the visual business control ID exists, the graphical user interface module returns a result of successful verification to the routing module;
s20, judging whether the visual business control needs to judge the authority through the routing module;
s21, if necessary, sending a request for verifying the user authority to the verification module through the routing module;
s22, the verification module inquires whether the user authority is right through the data processing layer module;
s23, the data processing layer module returns the query result to the verification module;
s24, if the user authority is abnormal, an error is reported through the abnormal processing module;
s25, if the exception handling module reports an error, returning error information to the application system;
s26, if the user authority is possessed, the verification module returns a result of successful verification to the routing module;
s27, sending a judgment result to the graphical user interface module through the routing module to judge whether the current visual business control is bound with the form, if so, reading the form rule, and verifying the uploading parameter, otherwise, not verifying;
s28, the graphical user interface module sends a verification form rule to the parser module;
s29, the resolver module returns a successful verification result to the graphical user interface module;
s30, if the verification is abnormal in the resolver module, an error is reported to the abnormal processing module;
s31, the exception handling module sends exception information to the application system;
s32, after the resolver module returns a successful verification result to the graphical user interface module, the graphical user interface module returns a successful verification result to the routing module;
s33, entering a resolver module if the application module ID, the graphical user interface ID, the visual service control ID and the user right are successfully verified;
s34, judging whether the current visual business control is bound with the flow, if not, changing the relevant flow by the query table; if so, inquiring a binding process;
s35, inquiring the flow from the data processing layer module;
s36, returning a flow inquiry result;
s37, if the process needs to start the affair, entering the affair process, otherwise entering the non-affair process;
s38, circularly executing a flow list, and executing according to different flow nodes in sequence; if the flow type is the script type, executing the resolver;
s39, if the node is the judgment node and the execution result is the error code, calling the error process;
s40, after calling error handling, sending an exception handling request to an exception handling module;
s41, the exception handling module returns error information to the application system;
s42, if the process node is an approval node, executing an approval process, finishing the current process, and carrying out approval of the subsequent process;
s43, executing an approval process through an approval module;
s44, returning an approval result to the analysis module;
s45, if the node is the end node, ending the process;
s46, returning the result to the routing module;
and S47, returning the result to the application system.
The invention has the beneficial effects that:
in the invention, the visualization module comprises a graphical user interface, a visualization business control and a process editor; the graphical user interface, the visual business control and the process editor are all provided with predefined attributes and configurations, the customization of the functional nodes can be quickly realized by dragging the visual business control to the graphical user interface, and the business process logic can be quickly formed by connecting the visual business control by dragging the process editor to the graphical user interface; the attributes and the configuration of each visualization module can be dynamically executed through the analysis module, codes (pre-written and bound codes) written on the visualization modules by a user are dynamically executed through the nodejs virtual machine, the codes do not need to be rewritten, and the layout of the visualization business controls on the whole graphical user interface and the layout of business process logics among the visualization business controls are completed in a dragging mode. And the visualization module can be driven to work according to the business process logic edited on the graphical user interface through the process engine.
When the visualized low-code system development platform is used and the application system is built by the modular building method, a user can be helped to realize the simultaneous building and the simultaneous online, the low-code system development platform does not need professional code development, 80-100% of functions can be completed by a visualized dragging mode, the development period is short, a large amount of labor cost is saved, and the development cost of an enterprise is reduced.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings that are required to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present invention and therefore should not be considered as limiting the scope, and it will be apparent to those skilled in the art that other relevant drawings can be obtained from the drawings without inventive effort.
Fig. 1 is a schematic diagram of modules related to the present invention.
FIG. 2 is an effect diagram of a visualization module in the present invention.
FIG. 3 is a front-end trigger flow diagram of an application system developed based on the visual low-code system development platform of the present invention.
Detailed Description
The technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments of the invention without inventive step, are within the scope of the invention.
Referring to fig. 1 and 2, a visual low-code system development platform includes: the system comprises a visualization module, a parser module and a process engine; the visualization module comprises a graphical user interface, a visualization business control and a process editor;
the graphical user interface: defining attributes and configurations, and laying out visual business controls and visual process editors;
the visual business control: defining attributes and configuration, and laying out on a graphical user interface in a dragging mode;
the visual flow editor: defining attributes and configurations, and arranging the attributes and the configurations on an image graphical user interface in a dragging mode and connecting visual business controls to form business process logic;
the resolver module: dynamically executing the attribute and configuration of each visualization module, and dynamically executing codes written on the visualization modules by a user through nodejs virtual machines;
the process-driven engine: and the visual module is used for driving the visual module to work according to the business process.
On the basis of the scheme, the visual low-code system development platform further comprises a routing module for processing the authority and the log. Specifically, the routing module comprises a custom graphical user interface query route, a component data query route, a process request route and a general system route.
On the basis of any scheme, the parser module comprises a parser module, a graphical user interface rendering parser, a visual business control data query parser and a visual business control verification parser.
On the basis of any scheme, the visual low-code system development platform further comprises a data processing layer module, and the visual module can be queried, added, modified, deleted, created, modified and customized sql through the data processing layer module. The data processing layer module can adjust the properties and the configuration of the graphical user interface, the visual business control and the process editor so as to adapt to a system to be developed.
Referring to fig. 2, the visual low-code system development platform in the present invention may further include an exception handling module, an application module, an authority module, an approval module, a tool module, an administrator module, an interface protocol authentication module, and the like.
Referring to fig. 3, the following front-end triggering process of the system developed based on the visualized low-code system development platform of the present invention further describes the present invention:
the application system developed by the visual low-code system development platform has the following front-end triggering process:
s1, respectively sending an application module ID query request, a graphical user interface ID query request, a visual service control ID query request and a user permission verification request to the routing module through the application system;
s2, sending a request for inquiring whether the application module ID exists to the application module through the routing module;
s3, the application module inquires whether the application module ID exists through the data processing layer module;
s4, the data processing layer module returns the query result to the application module;
s5, if the application module ID is abnormal, an error is reported through the abnormal processing module;
s6, if the exception handling module reports an error, returning error information to the application system;
s7, if the application module ID exists, the application module returns a result of successful verification to the routing module;
s8, sending a request for inquiring whether the graphical user interface ID exists to the graphical user interface module through the routing module;
s9, the graphical user interface module (page module) inquires whether the graphical user interface ID exists through the data processing layer module;
s10, the data processing layer module returns the query result to the graphical user interface module;
s11, if the graphical user interface ID is abnormal, an error is reported through the abnormal processing module;
s12, if the exception handling module reports an error, returning error information to the application system;
s13, if the graphical user interface ID exists, the graphical user interface module returns a result of successful verification to the routing module;
s14, sending a request for inquiring whether the ID of the visual business control (button) exists to the graphical user interface module through the routing module;
s15, the graphical user interface module inquires whether the visual business control ID exists through the data processing layer module;
s16, the data processing layer module returns the query result to the graphical user interface module;
s17, if the visual business control ID is abnormal, reporting an error through an abnormal processing module;
s18, if the exception handling module reports an error, returning error information to the application system;
s19, if the visual business control ID exists, the graphical user interface module returns a result of successful verification to the routing module;
s20, judging whether the visual business control needs to judge the authority through the routing module;
s21, if necessary, sending a request for verifying the user authority to the verification module through the routing module;
s22, the verification module inquires whether the user authority is right through the data processing layer module;
s23, the data processing layer module returns the query result to the verification module;
s24, if the user authority is abnormal, an error is reported through the abnormal processing module;
s25, if the exception handling module reports an error, returning error information to the application system;
s26, if the user authority is possessed, the verification module returns a result of successful verification to the routing module;
s27, sending a judgment result to the graphical user interface module through the routing module to judge whether the current visual business control is bound with the form, if so, reading the form rule, and verifying the uploading parameter, otherwise, not verifying;
s28, the graphical user interface module sends a verification form rule to the parser module;
s29, the resolver module returns a successful verification result to the graphical user interface module;
s30, if the verification is abnormal in the resolver module, an error is reported to the abnormal processing module;
s31, the exception handling module sends exception information to the application system;
s32, after the resolver module returns a successful verification result to the graphical user interface module, the graphical user interface module returns a successful verification result to the routing module;
s33, if the application module ID, the graphical user interface ID, the visual service control ID and the user authority are successfully verified, entering a resolver module;
s34, judging whether the current visual business control is bound with the flow, if not, changing the relevant flow by the query table; if so, inquiring a binding process;
s35, inquiring the flow from the data processing layer module;
s36, returning a flow inquiry result;
s37, if the process needs to start the affair, entering the affair process, otherwise entering the non-affair process;
s38, circularly executing a flow list, and executing according to different flow nodes in sequence; if the flow type is the script type, executing the resolver;
s39, if the node is the judgment node and the execution result is the error code, calling the error process;
s40, sending an exception handling request to an exception handling module after invoking error handling;
s41, the exception handling module returns error information to the application system;
s42, if the process node is an approval node, executing an approval process, finishing the current process, and carrying out approval of the subsequent process;
s43, executing an approval process through an approval module;
s44, returning an approval result to the analysis module;
s45, if the follow-up is the examination and approval process, ending and returning the result by the routing module;
s46, returning a result to the application system;
s47, if the node is the end node, ending the process;
s48, returning the result to the routing module;
and S49, returning the result to the application system.
The present invention is not limited to the above alternative embodiments, and any other various products can be obtained by anyone in the light of the present invention, but any changes in shape or structure thereof fall within the protection scope of the present invention, which falls within the scope of the claims of the present invention.
Claims (7)
1. A visual low-code system development platform, comprising: the system comprises a visualization module, a parser module and a process engine; the visualization module comprises a graphical user interface, a visualization business control and a process editor;
the graphical user interface: defining attributes and configurations, and laying out visual business controls and visual process editors;
the visual business control comprises the following steps: defining attributes and configuration, and laying out on a graphical user interface in a dragging mode;
the visual flow editor: defining attributes and configuration, and laying out the attributes and the configuration on an image graphical user interface in a dragging mode and connecting visual business controls to form business process logic;
the resolver module: dynamically executing the attribute and configuration of each visualization module, and dynamically executing codes written on the visualization modules by a user through nodejs virtual machines;
the process engine; and the visual module is used for driving the visual module to work according to the business process.
2. A visual low-code system development platform according to claim 1, characterized in that: and the system also comprises a routing module for processing the authority and the log.
3. A visual low-code system development platform according to claim 2, characterized in that: the routing module comprises a user-defined graphical user interface query route, a component data query route, a flow request route and a general system route.
4. A visual low-code system development platform according to claim 1, characterized in that: the resolver module comprises a resolver module, a graphical user interface rendering resolver, a visual business control data query resolver and a visual business control verification resolver.
5. A visual low-code system development platform according to any one of claims 1 to 4, characterized in that: the system also comprises a data processing layer module, and the visual module can be inquired, added, modified, deleted, created and modified by a data sheet and self-defined sql by the data processing layer module.
6. A visual low-code system development platform according to claim 5, characterized in that: the system also comprises an exception handling module, an application module, a permission module and an approval module.
7. A visual low-code system development platform according to claim 6, characterized in that: the application system developed by adopting the visual low-code system development platform has the following front-end triggering process:
s1, respectively sending an application module ID query request, a graphical user interface ID query request, a visual service control ID query request and a user permission verification request to the routing module through the application system;
s2, sending a request for inquiring whether the application module ID exists to the application module through the routing module;
s3, the application module inquires whether the application module ID exists through the data processing layer module;
s4, the data processing layer module returns the query result to the application module;
s5, if the application module ID is abnormal, an error is reported through the abnormal processing module;
s6, if the exception handling module reports an error, returning error information to the application system;
s7, if the application module ID exists, the application module returns the result of successful verification to the routing module;
s8, sending a request for inquiring whether the graphical user interface ID exists to the graphical user interface module through the routing module;
s9, the graphical user interface module inquires whether the graphical user interface ID exists through the data processing layer module;
s10, the data processing layer module returns the query result to the graphical user interface module;
s11, if the graphical user interface ID is abnormal, an error is reported through the abnormal processing module;
s12, if the exception handling module reports an error, returning error information to the application system;
s13, if the graphical user interface ID exists, the graphical user interface module returns a result of successful verification to the routing module;
s14, sending a request for inquiring whether the visual business control ID exists to the graphical user interface module through the routing module;
s15, the graphical user interface module inquires whether the visual business control ID exists through the data processing layer module;
s16, the data processing layer module returns the query result to the graphical user interface module;
s17, if the visual business control ID is abnormal, reporting an error through an abnormal processing module;
s18, if the exception handling module reports an error, returning error information to the application system;
s19, if the visual business control ID exists, the graphical user interface module returns a result of successful verification to the routing module;
s20, judging whether the visual business control needs to judge the authority through the routing module;
s21, if necessary, sending a request for verifying the user authority to the verification module through the routing module;
s22, the verification module inquires whether the user authority is right through the data processing layer module;
s23, the data processing layer module returns the query result to the verification module;
s24, if the user authority is abnormal, an error is reported through the abnormal processing module;
s25, if the exception handling module reports an error, returning error information to the application system;
s26, if the user authority is possessed, the verification module returns a result of successful verification to the routing module;
s27, sending a judgment result to the graphical user interface module through the routing module to judge whether the current visual business control is bound with the form, if so, reading the form rule, and verifying the uploading parameter, otherwise, not verifying;
s28, the graphical user interface module sends a verification form rule to the parser module;
s29, the resolver module returns a successful verification result to the graphical user interface module;
s30, if the verification is abnormal in the resolver module, an error is reported to the abnormal processing module;
s31, the exception handling module sends exception information to the application system;
s32, after the resolver module returns a successful verification result to the graphical user interface module, the graphical user interface module returns a successful verification result to the routing module;
s33, entering a resolver module if the application module ID, the graphical user interface ID, the visual service control ID and the user right are successfully verified;
s34, judging whether the current visual business control is bound with the flow, if not, changing the relevant flow by the query table; if so, inquiring a binding process;
s35, inquiring the flow from the data processing layer module;
s36, returning a flow inquiry result;
s37, if the process needs to start the affair, entering the affair process, otherwise entering the non-affair process;
s38, circularly executing a flow list, and executing according to different flow nodes in sequence; if the flow type is the script type, executing the resolver;
s39, if the node of the process flow is a judgment node and the execution result is an error code, calling error processing;
s40, after calling error handling, sending an exception handling request to an exception handling module;
s41, the exception handling module returns error information to the application system;
s42, if the process node is an approval node, executing an approval process, finishing the current process, and carrying out approval of the subsequent process;
s43, executing an approval process through an approval module;
s44, returning an approval result to the analysis module;
s45, if the node is the end node, ending the process;
s46, returning the result to the routing module;
and S47, returning the result to the application system.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210222543.2A CN114661275A (en) | 2022-03-07 | 2022-03-07 | Visual low-code system development platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210222543.2A CN114661275A (en) | 2022-03-07 | 2022-03-07 | Visual low-code system development platform |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114661275A true CN114661275A (en) | 2022-06-24 |
Family
ID=82029138
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210222543.2A Pending CN114661275A (en) | 2022-03-07 | 2022-03-07 | Visual low-code system development platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114661275A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115857907A (en) * | 2023-02-06 | 2023-03-28 | 卓望数码技术（深圳）有限公司 | Business flow dynamic assembly system and method |
| CN117111928A (en) * | 2023-10-24 | 2023-11-24 | 摩尔元数(福建)科技有限公司 | Low-code platform page secondary development system and method |
-
2022
- 2022-03-07 CN CN202210222543.2A patent/CN114661275A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115857907A (en) * | 2023-02-06 | 2023-03-28 | 卓望数码技术（深圳）有限公司 | Business flow dynamic assembly system and method |
| CN117111928A (en) * | 2023-10-24 | 2023-11-24 | 摩尔元数(福建)科技有限公司 | Low-code platform page secondary development system and method |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105700888B (en) | A kind of visualization quick development platform based on jbpm workflow engine | |
| CN114661275A (en) | Visual low-code system development platform | |
| Jena et al. | A novel approach for test case generation from UML activity diagram | |
| US20040064805A1 (en) | Enterprise scoped software factory | |
| JPH11296544A (en) | Structured data management system and computer-readable recording medium where structured data management program is recorded | |
| US8752030B1 (en) | Process abstraction and tracking, systems and methods | |
| CN101316201A (en) | Multi-terminal mode script device and data processing method and automatization test system | |
| CN112380255A (en) | Service processing method, device, equipment and storage medium | |
| CN112732579B (en) | Automatic test method and system for WebUI | |
| CN112001594A (en) | Robot management system based on material contract management and management method thereof | |
| CN104657274A (en) | Method and device for testing software interface | |
| CN112579455B (en) | Automatic interface testing method and device, electronic equipment and storage medium | |
| WO2004104824A1 (en) | User interface application development deice and development method | |
| CN111274136B (en) | Onboard software test management system and test process management method | |
| Weißleder et al. | An evaluation of model-based testing in embedded applications | |
| CN111444109B (en) | Mobile terminal UI automatic test method and system | |
| CN114297961A (en) | Chip test case processing method and related device | |
| CN212460603U (en) | Robot management system based on material contract management | |
| CN117370217A (en) | Automatic interface test result generation method based on python | |
| CN115269387A (en) | Automatic interface testing method and device | |
| CN115687054A (en) | Self-adaptive test method and device based on service segmentation and restoration | |
| CN114385243A (en) | Method and device for automatically issuing instructions for controlling layout engine | |
| KR102046622B1 (en) | Software service system based on workflow and computer program that performs each step of the system | |
| CN116795378B (en) | Method and device for arranging and executing process based on code dynamic compiling | |
| Talby et al. | A process-complete automatic acceptance testing framework |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication |