Method, device and system for generating a transaction application

Abstract

The application provides a transaction application generation method, a generation device and a generation system. The method comprises the following steps: determining a plurality of transaction actions and a total control logic according to transaction requirements, the total control logic comprising a plurality of continuous control logics, one transaction action corresponding to one control logic, and the control logic comprising an execution condition and an execution sequence of the corresponding transaction action; calling a control component corresponding to each control logic from a database, and calling a function component corresponding to each transaction action from the database, the control logic corresponding to the control component one by one, the transaction action corresponding to the function component one by one, the control component being used for executing the corresponding control logic, and the function component being used for executing the corresponding transaction action; and assembling the control component and the function component into an application program according to the total control logic and running the application program. The method solves the problem that the prior art cannot generate a transaction application program based on service level reuse assets.

Description

Technical Field

[0001] The present application relates to the field of data transaction technology, and in particular to a method for generating a transaction application, a generating device, a computer-readable storage medium, and a generating system. Background Art

[0002] With the booming software industry, various organizations and enterprises that rely on software applications are gradually establishing enterprise-level applications and architectures. However, with the continuous expansion of enterprise applications, enterprises are encountering significant difficulties and bottlenecks in software component reuse, service reuse, and personalized software customization. Specifically, regarding component and service reuse, most enterprises achieve this through copying and pasting software code and simple component reuse. This approach has the following problems: first, it significantly increases the workload of software developers; second, due to issues such as staff turnover and code loss, reusability is greatly reduced; third, there is no complete reuse system, and the reuse is usually pieced together, resulting in confusion and failure during reuse, which in turn increases costs.

[0003] The existing trading business R&D has the following main defects:

[0004] 1. Existing transaction development methods primarily rely on R&D personnel implementing the product or simply reusing existing assets, which leads to significant business ambiguity. While prototyping can alleviate barriers between business, product, and R&D personnel to a certain extent, in many scenarios, the actual business process, inputs and outputs, and actual results remain separate. This results in significant discrepancies between the actual results and the intended outcomes.

[0005] 2. Currently, there's no real-world approach or method for leaving the unpredictability and scalability of business transactions to business or product personnel. In most cases, business personnel provide requirements definitions to R&D personnel, who then analyze the requirements and develop the software, often using a customized approach. This approach forces R&D personnel to implement software based entirely on the requirements, so even small changes can lead to changes to the entire software, creating a significant workload.

[0006] 3. In the current technical implementation, there is no implementation that combines business processes, logical control, transaction modules and transaction virtual operation scenarios.

[0007] 4. Currently, asset reuse generally remains at the code or component level. There is no fine-grained division of existing software code and services to form service-level inherent assets, thereby handing these assets over to business personnel or product personnel for DIY transaction implementation or customized transaction implementation. Summary of the Invention

[0008] The main purpose of this application is to provide a method, a generating device, a computer-readable storage medium and a generating system for a transaction application, so as to solve the problem in the prior art that it is impossible to generate a transaction application based on service-level reused assets.

[0009] According to one aspect of an embodiment of the present application, a method for generating a transaction application is provided, the method comprising: determining, based on transaction requirements, multiple transaction actions and an overall control logic, the overall control logic comprising multiple continuous control logics, one transaction action corresponding to one control logic, the control logic comprising execution conditions and an execution order of the corresponding transaction action; calling a control component corresponding to each control logic from a database, and calling a functional component corresponding to each transaction action from the database, the control logic corresponding to the control component one-to-one, the transaction action corresponding to the functional component one-to-one, the control component being used to execute the corresponding control logic, the functional component being used to execute the corresponding transaction action, the control component and the functional component being components created based on historical transaction processes and stored in the database; assembling the control component and the functional component into an application according to the overall control logic and running the application.

[0010] Optionally, calling the control component corresponding to each of the control logics from the database, and calling the functional component corresponding to each of the transaction actions from the database, includes: obtaining a first call path corresponding to each of the control logics, and obtaining a second call path corresponding to each of the transaction actions, the control logics having a one-to-one correspondence with the first call path, and the transaction actions having a one-to-one correspondence with the second call path, the first call path being a path for calling the control component from the database, and the second call path being a path for calling the functional component from the database; calling the control component corresponding to each of the control logics from the database according to the first call path, and calling the control component corresponding to each of the transaction actions from the database according to the second call path, the first call path being a one-to-one correspondence with the control component, and the second call path being a one-to-one correspondence with the functional component.

[0011] Optionally, before calling the control component corresponding to each control logic from the database and calling the functional component corresponding to each transaction action from the database, the method further includes: creating the control component and the functional component according to the historical transaction process, the coupling principle and the mutual exclusion principle, and storing the control component and the functional component in the database, so that the coupled components are allowed to execute sequentially and the mutually exclusive components are prohibited from executing sequentially, the coupled component is the control component or the functional component created according to the coupling principle, and the mutually exclusive component is the control component or the functional component created according to the mutual exclusion principle.

[0012] Optionally, before calling the control component corresponding to each control logic from the database and calling the functional component corresponding to each transaction action from the database, the method further includes: setting the corresponding first calling path for each control component in the database and setting the corresponding second calling path for each functional component in the database.

[0013] Optionally, before assembling the control components and the functional components into an application according to the overall control logic and running the application, the method further includes: determining whether there are any syntactic errors in the overall control logic, and determining whether there are any semantic errors in the overall control logic; if the overall control logic has any syntactic errors, sending a syntactic error message notification; if the overall control logic has any semantic errors, sending a semantic error message notification.

[0014] Optionally, assembling the control component and the functional component into an application according to the overall control logic and running the application includes: running the control component and the functional component according to the overall control logic to simulate the transaction process and obtain a simulation result; when the simulation result meets the transaction requirements, assembling the control component and the functional component into the application according to the overall control logic and running the application.

[0015] Optionally, the types of the control components include at least a branch type, a loop type, a timing type and a parallel type, and the functional components include at least a data processing component and a transaction processing component.

[0016] According to another aspect of an embodiment of the present application, a device for generating a transaction application is also provided, the device comprising: a determination unit, configured to determine, based on transaction requirements, multiple transaction actions and an overall control logic, the overall control logic comprising multiple continuous control logics, one transaction action corresponding to one control logic, the control logic comprising the execution conditions and execution order of the corresponding transaction actions; a calling unit, configured to call a control component corresponding to each of the control logics from a database, and to call a functional component corresponding to each of the transaction actions from the database, the control logic corresponding to the control component being in one-to-one correspondence, the transaction action corresponding to the functional component being in one-to-one correspondence, the control component being configured to execute the corresponding control logic, the functional component being configured to execute the corresponding transaction action, the control component and the functional component being components created based on historical transaction processes and stored in the database; a generation unit, configured to assemble the control component and the functional component into an application according to the overall control logic and run the application.

[0017] According to another aspect of the embodiments of the present application, a computer-readable storage medium is further provided, wherein the computer-readable storage medium includes a stored program, wherein when the program is executed by a processor, the processor executes any one of the methods for generating a transaction application.

[0018] According to another aspect of an embodiment of the present application, a system for generating a transaction application is also provided, comprising: one or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs include a method for generating a transaction application for executing any one of the aforementioned transactions.

[0019] In the method for generating the above-mentioned transaction application, first, based on the transaction requirements, multiple transaction actions and the overall control logic are determined. The above-mentioned overall control logic includes multiple continuous control logics, one transaction action corresponds to one control logic, and the above-mentioned control logic includes the execution conditions and execution order of the corresponding transaction actions; then, the control components corresponding to each of the above-mentioned control logics are called from the database, and the functional components corresponding to each of the above-mentioned transaction actions are called from the above-mentioned database. The above-mentioned control logics correspond one-to-one to the above-mentioned control components, and the above-mentioned transaction actions correspond one-to-one to the above-mentioned functional components. The above-mentioned control components are used to execute the corresponding above-mentioned control logics, and the above-mentioned functional components are used to execute the corresponding above-mentioned transaction actions. The above-mentioned control components and the above-mentioned functional components are both components created according to the historical transaction process and stored in the above-mentioned database; finally, the above-mentioned control components and the above-mentioned functional components are assembled into an application according to the above-mentioned overall control logic and the above-mentioned application is run. The method determines the transaction actions, execution conditions, and execution order of the transaction actions of the transaction process based on transaction requirements. Then, the corresponding control components and functional components are called from the database, and the control components and functional components are assembled into an application capable of executing the transaction process according to the execution conditions and execution order of the transaction actions. The application is run to complete the transaction. The control components and functional components are both service-level assets created based on historical transaction processes. This method solves the problem in the existing technology that it is impossible to generate transaction applications based on service-level reused assets. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The drawings that constitute part of this application are used to provide a further understanding of this application. The illustrative embodiments of this application and their descriptions are used to explain this application and do not constitute an improper limitation on this application. In the drawings:

[0021] Figure 1 A flowchart showing a method for generating a transaction application according to an embodiment of the present application is shown;

[0022] Figure 2 A flowchart showing a method for generating a transaction application according to a specific embodiment of the present application is shown;

[0023] Figure 3 A schematic diagram showing a control component and a functional component according to an embodiment of the present application is shown;

[0024] Figure 4 A schematic diagram showing a device for generating a transaction application according to an embodiment of the present application is shown;

[0025] Figure 5 A schematic diagram showing a visual interactive interface of a system for generating a transaction application according to an embodiment of the present application is shown;

[0026] Figure 6A schematic diagram showing a control area of ​​a visual interactive interface of a system for generating a transaction application according to an embodiment of the present application;

[0027] Figure 7 A schematic diagram showing a transaction area of ​​a visual interactive interface of a system for generating a transaction application according to an embodiment of the present application is shown;

[0028] Figure 8 A schematic diagram of an interactive area of ​​a visual interactive interface of a system for generating a transaction application according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0029] It should be noted that the following detailed descriptions are illustrative and intended to provide further explanation of the present application. Unless otherwise specified, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which the present application belongs.

[0030] It should be noted that the terms used herein are only for describing specific embodiments and are not intended to limit the exemplary embodiments according to the present application. As used herein, unless the context clearly indicates otherwise, the singular form is also intended to include the plural form. In addition, it should be understood that when the terms "comprise" and / or "include" are used in this specification, they indicate the presence of features, steps, operations, devices, components and / or combinations thereof.

[0031] It should be understood that when an element (such as a layer, film, region, or substrate) is described as being "on" another element, the element may be directly on the other element or intervening elements may be present. Moreover, in the specification and claims, when it is described that an element is "connected to" another element, the element may be "directly connected to" the other element or "connected to" the other element through a third element.

[0032] As mentioned in the background technology, it is impossible to generate transaction applications based on service-level reused assets in the existing technology. In order to solve the above problem, a typical embodiment of the present application provides a method for generating a transaction application, a generating device, a computer-readable storage medium and a generating system.

[0033] According to an embodiment of the present application, a method for generating a transaction application is provided.

[0034] Figure 1 FIG is a flow chart of a method for generating a transaction application according to an embodiment of the present application. Figure 1 As shown, the method includes the following steps:

[0035] Step S101: Determine multiple transaction actions and overall control logic based on transaction requirements. The overall control logic includes multiple consecutive control logics, with each transaction action corresponding to one control logic. The control logic includes the execution conditions and execution order of the corresponding transaction actions.

[0036] Step S102: Calling the control components corresponding to the control logics from the database, and calling the function components corresponding to the transaction actions from the database. The control logics correspond to the control components one-to-one, and the transaction actions correspond to the function components one-to-one. The control components are used to execute the corresponding control logics, and the function components are used to execute the corresponding transaction actions. Both the control components and the function components are created based on historical transaction processes and stored in the database.

[0037] In order to quickly call the functional components and control components from the database, in an optional embodiment, before the above step S102, the above method further includes:

[0038] Step S201: setting the corresponding first calling path for each of the control components in the database, and setting the corresponding second calling path for each of the function components in the database.

[0039] In the above embodiment, if Figure 2 As shown, the first call path corresponding to each control component is configured at the front end, the second call path corresponding to each functional component is configured, and the first call path and the second call path are written into the cache in the form of configuration data. Then, the configuration data is persisted in the database, so that each control component and functional component stored in the database has a corresponding call path, thereby realizing the rapid calling of the control components and functional components in the database through the call path.

[0040] Optionally, this application does not limit the specific process of calling the control components corresponding to each of the above-mentioned control logics from the database, and calling the functional components corresponding to each of the above-mentioned transaction actions from the above-mentioned database. Any feasible method falls within the scope of protection of this application.

[0041] For example, in an optional implementation, the above step S102 includes:

[0042] Step S1021: Obtain a first call path corresponding to each of the control logics, and a second call path corresponding to each of the transaction actions. The control logics correspond to the first call paths, and the transaction actions correspond to the second call paths. The first call path is the path for calling the control component from the database, and the second call path is the path for calling the function component from the database.

[0043] Step S1021, according to the above-mentioned first calling path, the corresponding control component of each control logic is called from the above-mentioned database, and according to the second calling path, the corresponding control component of each transaction action is called from the above-mentioned database, the first calling path corresponds to the control component one by one, and the second calling path corresponds to the function component one by one.

[0044] In the above-mentioned embodiment, as shown in Figure 2 After receiving the transaction demand, the transaction action and the control logic are determined to determine the function components and the control components that need to be called to complete the transaction process. After determining the transaction action and the control logic, the configuration data is read from the cache to quickly obtain the calling path of the function components and the calling path of the control components that need to be called. Then, the function components and the control components are called from the database according to the calling path through the gateway and the microservice, and the function components and the control components are called through the calling path to realize the quick calling of the function components and the control components.

[0045] In order to assemble the existing assets into reusable service-level assets, in an optional embodiment, before step S102, the method further comprises:

[0046] Step S301, according to the above-mentioned historical transaction process, the coupling principle and the mutual exclusion principle, the control component and the function component are created and stored in the database, so that the coupling component is allowed to be executed in sequence, and the mutual exclusion component is prohibited to be executed in sequence, the coupling component is the control component or the function component created according to the coupling principle, and the mutual exclusion component is the control component or the function component created according to the mutual exclusion principle.

[0047] In the above implementation, in order to assemble existing assets into reusable service-level assets, the existing code assets are substantially assembled and deposited according to the historical transaction process, coupling principle and mutual exclusion principle, and reusable service-level control components and functional components are created. The control logic corresponding to each control component is the control logic commonly used in the historical transaction process, and the transaction action corresponding to each functional component is the transaction action commonly used in the historical transaction process. The characteristic of creating components according to the coupling principle is that the coupled components are mutually dependent. For example, if the transaction action corresponding to coupling component A is executed, the transaction action corresponding to coupling component B must be executed first, and then the transaction action corresponding to coupling component A must be executed. After the transaction action of coupled component C, the transaction action corresponding to coupled component C must be executed. The characteristics of components created according to the mutual exclusion principle are that mutually exclusive components exclude each other and mutually exclusive components cannot serve as input and output to each other. For example, mutually exclusive component A and mutually exclusive component B exclude each other. Before and after the transaction action corresponding to mutually exclusive component A is executed, the transaction action corresponding to mutually exclusive component B cannot be executed. For another example, mutually exclusive components cannot serve as input and output to each other. For example, the input of mutually exclusive component A cannot be used as the output of mutually exclusive component B. Through the coupling principle and the mutual exclusion principle, the existing assets are divided into fine-grained parts to the greatest extent, and the existing assets can be assembled into reusable service-level assets.

[0048] In order to ensure the controllability of the transaction process, the types of control components and functional components must be strictly divided when creating them. In an optional implementation, the types of the above-mentioned control components include at least branch type, loop type, timing type and parallel type, and the above-mentioned functional components include at least data processing components and transaction business processing components.

[0049] In the above embodiment, if Figure 3As shown, the branch component is a control component of the branch type, the loop component is a control component of the loop type, the timing component is a control component of the timing type, and the parallel component is a control component of the parallel type. In addition to the branch component, the loop component, the timing component, and the parallel component, the control component further includes a connection line component, a start component, an end component, and a variable component. The variable component is mainly used to provide an input parameter entry for a business operator running a transaction application, so that the business operator can adjust the input parameter to make the transaction application running result meet the expected effect of the business operator. For example, when assembling a user login application with a visual interface, the user name and the password need to be input. At this time, the variable component needs to be used to provide an entry for inputting the user name and the password. The data processing component included in the function component includes a new record component, a delete record component, a modify record component, and a query record component, which respectively complete the transaction actions of adding a record, modifying a record, deleting a record, and querying a record. The transaction business processing component included in the function component includes a new transaction component, a delete transaction component, a modify transaction component, and a query transaction component, which respectively complete the transaction actions of adding a transaction, modifying a transaction, deleting a transaction, and querying a transaction. On the basis of meeting the coupling principle and the mutual exclusion principle, any two components in the control component and the function component can be input and output to each other. In addition to completing the corresponding transaction action, the function component can also be used as the input of the control component. For example, the input of the condition component can be a function component with a Boolean type output result, and the input of the loop component can be a function component with a numerical type output result. By strictly dividing the types of the control component and the function component, the controllability of the transaction process is ensured, and the existing assets are divided into control components and function components in the maximum degree of granularity. On the basis of meeting the coupling principle and the mutual exclusion principle, the control components and the function components can be combined into new service level assets at will, so that the asset library becomes larger and easier to use.

[0050] In step S103, the control components and the function components are assembled into an application according to the total control logic, and the application is run.

[0051] In order to generate a transaction application that can be run, in an optional embodiment, before step S103, the method further includes:

[0052] In step S401, it is determined whether the total control logic has a syntax error, and whether the total control logic has a semantic error.

[0053] In step S402, in the case where the total control logic has the syntax error, a syntax error message is sent for notification, and in the case where the total control logic has the semantic error, a semantic error message is sent for notification.

[0054] It should be noted that the present application is programmed by two high-level programming languages of front end and back end, for example, the front end interactive program, middle control logic, data transmission analysis and service combination logic are compiled by using JavaScript, VUE and JAVA, etc. to realize the generation method of the above transaction application program.

[0055] In the above embodiment, the front end transmits the data such as transaction actions and total control logic involved in the implementation of the transaction process determined by the business personnel to the back end for persistence. After receiving the transaction actions and total control logic, the back end performs syntax checking and semantic analysis to determine whether there is a syntax and semantic error in executing the transaction actions according to the control logic, and feeds back to the business personnel when there is a syntax error and semantic error. In the case where there is no syntax error and semantic error, the control logic and function components corresponding to the control components according to the total control logic are executed, and the running results are returned to the business personnel of the front end.

[0056] Optionally, the present application does not limit the specific process of assembling the control components and the function components into an application program according to the total control logic and running the application program, and any feasible way belongs to the protection scope of the present application.

[0057] For example, in an optional embodiment, the above step S103 includes:

[0058] Step S1031, running the control components and the function components according to the total control logic to simulate the transaction process, and obtaining a simulation result;

[0059] Step S1032, assembling the control components and the function components into the application program according to the total control logic and running the application program in the case where the simulation result meets the transaction demand.

[0060] In the above embodiment, the generation process of the transaction application program is divided into trial running and formal release running. In the trial running process, the technology such as baffle is used to prevent the transaction application program from writing to the actual environment during the trial running, so as to prevent the generation of dirty data. During the trial running, the business personnel can modify the transaction actions and control logic according to the running result of the transaction application program viewed by the front end, until the simulation result meeting the transaction demand is obtained. At this time, the transaction application program can be formally released and run, the transaction application program will control and affect the formal environment, and the virtual transaction will be promoted to the formal transaction.

[0061] The method for generating the transaction application comprises the following steps: firstly, determining a plurality of transaction actions and a total control logic according to a transaction demand, wherein the total control logic comprises a plurality of continuous control logics, one transaction action corresponds to one control logic, and the control logic comprises an execution condition and an execution sequence of the corresponding transaction action; secondly, calling a control component corresponding to each control logic from a database and calling a function component corresponding to each transaction action from the database, wherein the control logic corresponds to the control component one by one, the transaction action corresponds to the function component one by one, the control component is used for executing the corresponding control logic, the function component is used for executing the corresponding transaction action, and the control component and the function component are components created according to historical transaction processes and stored in the database; and finally, assembling the control component and the function component into an application program according to the total control logic and running the application program. The method determines the transaction actions and the execution condition and the execution sequence of the transaction actions of the transaction process according to the transaction demand, then calls the corresponding control component and the function component from the database, assembles the control component and the function component into the application program capable of executing the transaction process according to the execution condition and the execution sequence of the transaction actions, and runs the application program to complete the transaction, wherein the control component and the function component are service-level assets created according to the historical transaction processes, and the method solves the problem that the prior art cannot generate the transaction application program based on the service level.

[0062] It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although the logical order is shown in the flowchart, in some cases, the steps shown or described herein can be executed in an order different from that shown herein.

[0063] The embodiment of the present application further provides a transaction application generation device. It should be noted that the transaction application generation device of the embodiment of the present application can be used to execute the method for generating the transaction application provided by the embodiment of the present application. The transaction application generation device provided by the embodiment of the present application is introduced as follows.

[0064] Figure 4 is a schematic diagram of the transaction application generation device according to the embodiment of the present application. As shown in Figure 4 , the device comprises:

[0065] A determination unit 10 is configured to determine a plurality of transaction actions and a total control logic according to a transaction demand, wherein the total control logic comprises a plurality of continuous control logics, one transaction action corresponds to one control logic, and the control logic comprises an execution condition and an execution sequence of the corresponding transaction action;

[0066] The calling unit 10 is configured to call the control components corresponding to the control logics from the database, and to call the functional components corresponding to the transaction actions from the database. The control logics correspond to the control components one-to-one, and the transaction actions correspond to the functional components one-to-one. The control components are configured to execute the corresponding control logics, and the functional components are configured to execute the corresponding transaction actions. Both the control components and the functional components are created based on historical transaction processes and stored in the database.

[0067] In order to quickly call the functional components and control components from the database, in an optional embodiment, the above-mentioned device further includes:

[0068] The setting unit is used to set the corresponding first calling path for each of the control components in the database, and to set the corresponding second calling path for each of the functional components in the database.

[0069] In the above embodiment, if Figure 2 As shown, the first call path corresponding to each control component is configured at the front end, the second call path corresponding to each functional component is configured, and the first call path and the second call path are written into the cache in the form of configuration data. Then, the configuration data is persisted in the database, so that each control component and functional component stored in the database has a corresponding call path, thereby realizing the rapid calling of the control components and functional components in the database through the call path.

[0070] Optionally, this application does not limit the specific process of calling the control components corresponding to each of the above-mentioned control logics from the database, and calling the functional components corresponding to each of the above-mentioned transaction actions from the above-mentioned database. Any feasible method falls within the scope of protection of this application.

[0071] For example, in an optional embodiment, the calling unit includes:

[0072] an acquisition module, configured to acquire a first call path corresponding to each of the control logics and a second call path corresponding to each of the transaction actions, wherein the control logics correspond to the first call paths, and the transaction actions correspond to the second call paths, wherein the first call paths are paths for calling the control components from the database, and the second call paths are paths for calling the functional components from the database;

[0073] The calling module is used to call the control components corresponding to each of the control logics from the database according to the first calling path, and call the control components corresponding to each of the transaction actions from the database according to the second calling path. The first calling path corresponds one-to-one to the control components, and the second calling path corresponds one-to-one to the functional components.

[0074] In the above embodiment, if Figure 2 As shown, after receiving the transaction demand, the transaction action and control logic are first determined to determine the functional components and control components that need to be called to complete the transaction process. After determining the transaction action and control logic, the configuration data is read from the cache to quickly obtain the calling path of the functional components that need to be called and the calling path of the control components that need to be called. Then, the functional components and control components are centrally called from the database according to the calling path through gateways and microservices, and the functional components and control components are called through the calling path to achieve rapid calling of the functional components and control components.

[0075] In order to assemble existing assets into reusable service-level assets, in an optional embodiment, the apparatus further includes:

[0076] A creation unit is used to create the above-mentioned control component and the above-mentioned functional component according to the above-mentioned historical transaction process, coupling principle and mutual exclusion principle, and store the above-mentioned control component and the above-mentioned functional component in the above-mentioned database, so that the coupled components are allowed to execute sequentially and the mutually exclusive components are prohibited from executing sequentially. The above-mentioned coupling component is the above-mentioned control component or the above-mentioned functional component created according to the above-mentioned coupling principle, and the above-mentioned mutually exclusive component is the above-mentioned control component or the above-mentioned functional component created according to the above-mentioned mutual exclusion principle.

[0077] In the above implementation, in order to assemble existing assets into reusable service-level assets, the existing code assets are substantially assembled and deposited according to the historical transaction process, coupling principle and mutual exclusion principle, and reusable service-level control components and functional components are created. The control logic corresponding to each control component is the control logic commonly used in the historical transaction process, and the transaction action corresponding to each functional component is the transaction action commonly used in the historical transaction process. The characteristic of creating components according to the coupling principle is that the coupled components are mutually dependent. For example, if the transaction action corresponding to coupling component A is executed, the transaction action corresponding to coupling component B must be executed first, and then the transaction action corresponding to coupling component A must be executed. After the transaction action of coupled component C, the transaction action corresponding to coupled component C must be executed. The characteristics of components created according to the mutual exclusion principle are that mutually exclusive components exclude each other and mutually exclusive components cannot serve as input and output to each other. For example, mutually exclusive component A and mutually exclusive component B exclude each other. Before and after the transaction action corresponding to mutually exclusive component A is executed, the transaction action corresponding to mutually exclusive component B cannot be executed. For another example, mutually exclusive components cannot serve as input and output to each other. For example, the input of mutually exclusive component A cannot be used as the output of mutually exclusive component B. Through the coupling principle and the mutual exclusion principle, the existing assets are divided into fine-grained parts to the greatest extent, and the existing assets can be assembled into reusable service-level assets.

[0078] In order to ensure the controllability of the transaction process, the types of the control components and the function components are strictly divided when the control components and the function components are created. In an optional embodiment, the types of the control components include at least the branch type, the loop type, the timing type and the parallel type, and the function components include at least the data processing component and the transaction service processing component.

[0079] In the above embodiment, as shown in Figure 3 The branch component is the control component of the branch type, the loop component is the control component of the loop type, the timing component is the control component of the timing type, and the parallel component is the control component of the parallel type. In addition to the branch component, the loop component, the timing component and the parallel component, the control component also includes the connection line component, the start component, the end component and the variable component. The variable component mainly provides an input parameter entry for the service personnel running the transaction application, so that the service personnel can adjust the input parameter to make the running result of the transaction application meet the expected effect of the service personnel. For example, when assembling a user login application with a visual interface, the username and the password need to be input. At this time, the variable component is needed to provide an entry for inputting the username and the password. The data processing component of the function component includes the record adding component, the record deleting component, the record modifying component and the record querying component, which respectively complete the transaction actions of adding records, modifying records, deleting records and querying records. The transaction service processing component of the function component includes the transaction adding component, the transaction deleting component, the transaction modifying component and the transaction querying component, which respectively complete the transaction actions of adding transactions, modifying transactions, deleting transactions and querying transactions. On the basis of meeting the coupling principle and the mutual exclusion principle, any two components in the control component and the function component can be input and output to each other. In addition to completing the corresponding transaction action, the function component can also be used as the input of the control component. For example, the input of the condition component can be a function component with a Boolean type output result, and the input of the loop component can be a function component with a numerical type output result. By strictly dividing the types of the control components and the function components, the controllability of the transaction process is ensured, and the existing assets are divided into control components and function components with the maximum granularity. On the basis of meeting the coupling principle and the mutual exclusion principle, the control components and the function components can be randomly combined into new service level assets, so that the asset library becomes larger and easier to use.

[0080] The generating unit 30 is configured to assemble the control components and the function components into an application according to the total control logic and run the application.

[0081] In order to be able to generate a transaction application that can be run, in an optional embodiment, the device further includes:

[0082] a judgment unit, configured to judge whether the overall control logic has any syntax errors and whether the overall control logic has any semantic errors;

[0083] The sending unit is used to send a syntax error message notification when the above-mentioned syntax error exists in the above-mentioned overall control logic, and to send a semantic error message notification when the above-mentioned semantic error exists in the above-mentioned overall control logic.

[0084] It should be noted that this application is programmed using two high-level programming languages, front-end and back-end, such as JavaScript, VUE and JAVA, to compile front-end interactive programs, middle-end control logic, data transmission analysis and service combination logic to implement the above-mentioned transaction application generation method.

[0085] In the above implementation, the front end transmits data such as transaction actions and overall control logic involved in implementing the transaction process determined by the business personnel to the back end for persistence. After receiving the transaction actions and overall control logic, the back end performs syntax verification and semantic analysis to determine whether there are grammatical and semantic errors in executing the transaction actions according to the control logic shown, and feedback is given to the business personnel if there are grammatical errors and semantic errors. If there are no grammatical errors and semantic errors, the control logic corresponding to the control component and the transaction actions corresponding to the functional component will be executed according to the overall control logic, and the operation results will be returned to the business personnel at the front end.

[0086] Optionally, the present application does not limit the specific process of assembling the above-mentioned control components and the above-mentioned functional components into an application according to the above-mentioned overall control logic and running the above-mentioned application. Any feasible method falls within the scope of protection of the present application.

[0087] For example, in an optional embodiment, the generating unit includes:

[0088] A simulation module, configured to operate the control component and the functional component according to the overall control logic to simulate the transaction process and obtain simulation results;

[0089] A generation module is used to assemble the control components and the functional components into the application program according to the overall control logic and run the application program when the simulation results meet the transaction requirements.

[0090] In the above implementation mode, the generation process of the transaction application is divided into trial operation and formal release operation. During the trial operation, baffles and other technologies are used to prevent the transaction application from writing to the actual environment during the trial operation to prevent the generation of dirty data. During the trial operation, business personnel can view the operation results of the transaction application based on the front end, and modify the transaction actions and control logic with reference to the operation results until a simulation result that meets the transaction requirements is obtained. At this time, the transaction application can be officially released and run. The transaction application will control and influence the formal environment, and the virtual transaction will be promoted to a formal transaction.

[0091] In the generating device of the above-mentioned transaction application, the determining unit determines multiple transaction actions and the overall control logic according to the transaction requirements. The above-mentioned overall control logic includes multiple continuous control logics. One of the above-mentioned transaction actions corresponds to one of the above-mentioned control logics. The above-mentioned control logic includes the execution conditions and execution order of the corresponding above-mentioned transaction actions; the calling unit calls the control components corresponding to each of the above-mentioned control logics from the database, and calls the functional components corresponding to each of the above-mentioned transaction actions from the above-mentioned database. The above-mentioned control logics correspond one-to-one to the above-mentioned control components, and the above-mentioned transaction actions correspond one-to-one to the above-mentioned functional components. The above-mentioned control components are used to execute the corresponding above-mentioned control logics, and the above-mentioned functional components are used to execute the corresponding above-mentioned transaction actions. The above-mentioned control components and the above-mentioned functional components are both components created according to the historical transaction process and stored in the above-mentioned database; the generating unit assembles the above-mentioned control components and the above-mentioned functional components into an application according to the above-mentioned overall control logic and runs the above-mentioned application. The device determines the transaction actions of the transaction process and the execution conditions and execution order of the transaction actions based on the transaction requirements, then calls the corresponding control components and functional components from the database, and assembles the control components and functional components into an application capable of executing the transaction process according to the execution conditions and execution order of the transaction actions, and runs the application to complete the transaction. Among them, the control components and functional components are both service-level assets created based on historical transaction processes. The device solves the problem in the existing technology that it is impossible to generate transaction applications based on service-level reused assets.

[0092] The generating device of the transaction application comprises a processor and a memory. The determining unit, calling unit and generating unit are all stored in the memory as program units. The processor executes the program units stored in the memory to realize corresponding functions.

[0093] The processor includes a kernel, which retrieves the corresponding program unit from the memory. One or more kernels can be configured, and kernel parameters can be adjusted to address the existing problem of being unable to reuse assets based on service levels to generate trading applications.

[0094] The memory can include non-persistent memory in a computer readable medium, random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash memory (flash RAM), and the memory includes at least one memory chip.

[0095] The embodiment of the present application provides a computer readable storage medium, the computer readable storage medium comprises a stored program, wherein the program is executed by a processor, and the processor executes the generation method of the transaction application.

[0096] The embodiment of the present application provides a transaction application generation system, comprising: one or more processors, a memory and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs comprise a program for executing the generation method of the transaction application.

[0097] The transaction application generation system comprises one or more processors, a memory and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs comprise a program for executing the generation method of the transaction application. The system determines the transaction action of the transaction process and the execution condition and execution order of the transaction action according to the transaction demand, then calls the corresponding control component and function component from the database, and assembles the control component and function component into an application program capable of executing the transaction process according to the execution condition and execution order of the transaction action, and runs the application program to complete the transaction, wherein the control component and the function component are both service-level assets created according to historical transaction processes, and the system solves the problem that assets cannot be reused to generate a transaction application program based on a service level in the prior art.

[0098] In order to execute the above method, the transaction application generation system provides a visual application program, and the visual application program comprises a visual interactive page, such as Figure 5 As shown in the figure, the visual interactive page comprises a menu area, a control area, a transaction area and an interaction area, wherein:

[0099] The control area, such as Figure 6As shown, the control area mainly includes control logic modules and transaction action modules, the control logic modules include start modules, end modules and condition modules, etc., wherein the start modules correspond to control start components, the end modules correspond to end components, the condition modules correspond to condition components, the transaction action modules include modules corresponding to each transaction action, for example, a verification code verification login module, there are corresponding function components in the database to execute the transaction action corresponding to the transaction action module, business personnel can select the corresponding control logic module according to the control logic required to realize the transaction process in the control area of the visual interactive page, and select the corresponding transaction action module according to the transaction action required to realize the transaction process;

[0100] Transaction area: business personnel select the corresponding control logic module according to the control logic required to realize the transaction process in the control area and drag it to the transaction area, select the corresponding transaction action module according to the transaction action required to realize the transaction process and drag it to the transaction area, then, according to the transaction action execution sequence and execution condition, combine the control logic module and the transaction action module together, for example, as shown in Figure 7 As shown, when assembling a user login application with a visual interface, to realize the verification transaction action, a start module, a condition module, a whether to need verification code module, a verification code verification login module, a verification code free login module and an end module are dragged to the transaction area and combined according to the transaction requirements;

[0101] Menu area: including delete button, trial run button and release button, etc., the delete button is used to delete the control logic module and the transaction action module dragged to the transaction area, the trial run button is used for trial run operation, and the release button is used for formal release operation;

[0102] Interaction area, used to show the running result of the transaction application, the running result can be a visual interface or data, for example, as shown in Figure 8 As shown, when assembling a user login application with a visual interface, the visual user login interface will be displayed in the interaction area after the business personnel press the trial run button of the menu area.

[0103] It should be noted that, as shown in Figure 7 As shown, each control logic module and transaction action module has a unique socket shape, the socket realizes the coupling relationship and mutual exclusion relationship between the control component corresponding to the control logic module and the function component corresponding to the transaction action module, for example, the start module cannot have a pre-module, therefore the upper part of the socket cannot match with other modules, the end module cannot have a post-module, and the lower part of the end module socket cannot have other modules.

[0104] The embodiment of the present application provides a device, the device comprises a processor, a memory and a program stored on the memory and executable on the processor, and at least the following steps are implemented when the processor executes the program:

[0105] In step S101, a plurality of transaction actions and total control logic are determined according to transaction requirements, the total control logic comprises a plurality of continuous control logics, one transaction action corresponds to one control logic, and the control logic comprises an execution condition and an execution sequence of the corresponding transaction action;

[0106] In step S102, a control component corresponding to each control logic is called from a database, and a function component corresponding to each transaction action is called from the database, the control logic corresponds to the control component one by one, the transaction action corresponds to the function component one by one, the control component is used for executing the corresponding control logic, the function component is used for executing the corresponding transaction action, and the control component and the function component are components created according to historical transaction processes and stored in the database;

[0107] In step S103, the control component and the function component are assembled into an application program according to the total control logic, and the application program is run.

[0108] The device herein can be a server, a PC, a PAD, a mobile phone or the like.

[0109] The present application further provides a computer program product, when executed on a data processing device, is suitable for executing a program initialized with at least the following method steps:

[0110] In step S101, a plurality of transaction actions and total control logic are determined according to transaction requirements, the total control logic comprises a plurality of continuous control logics, one transaction action corresponds to one control logic, and the control logic comprises an execution condition and an execution sequence of the corresponding transaction action;

[0111] In step S102, a control component corresponding to each control logic is called from a database, and a function component corresponding to each transaction action is called from the database, the control logic corresponds to the control component one by one, the transaction action corresponds to the function component one by one, the control component is used for executing the corresponding control logic, the function component is used for executing the corresponding transaction action, and the control component and the function component are components created according to historical transaction processes and stored in the database;

[0112] In step S103, the control component and the function component are assembled into an application program according to the total control logic, and the application program is run.

[0113] In the above embodiments of the present application, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0114] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only exemplary. For example, the division of the above-mentioned units can be a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0115] The units described above as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0116] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0117] If the above-mentioned integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a computer-readable storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, server or network device, etc.) to execute all or part of the steps of the above-mentioned methods of each embodiment of the present application. The aforementioned computer-readable storage medium includes: various media that can store program codes, such as a U disk, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk.

[0118] From the above description, it can be seen that the above embodiments of the present application achieve the following technical effects:

[0119] 1) In the method for generating a transaction application of the present application, firstly, a plurality of transaction actions and a total control logic are determined according to a transaction requirement, the total control logic comprises a plurality of continuous control logics, one transaction action corresponds to one control logic, and the control logic comprises an execution condition and an execution sequence of the corresponding transaction action; then, control components corresponding to the control logics are called from a database, and function components corresponding to the transaction actions are called from the database, the control logic corresponds to the control component one by one, and the transaction action corresponds to the function component one by one, the control component is used to execute the corresponding control logic, the function component is used to execute the corresponding transaction action, the control component and the function component are both components created according to a historical transaction process and stored in the database; finally, the control components and the function components are assembled into an application according to the total control logic, and the application is run. The method determines the transaction actions and the execution condition and the execution sequence of the transaction actions of the transaction process according to the transaction requirement, then calls the corresponding control components and function components from the database, and assembles the control components and the function components into the application capable of executing the transaction process according to the execution condition and the execution sequence of the transaction actions, and runs the application to complete the transaction, wherein the control components and the function components are both service-level assets created according to the historical transaction process, and the method solves the problem that the prior art cannot generate a transaction application based on service-level reuse of assets.

[0120] 2) In the generation device of the transaction application of the present application, the determination unit determines multiple transaction actions and the overall control logic according to the transaction requirements. The above-mentioned overall control logic includes multiple continuous control logics. One of the above-mentioned transaction actions corresponds to one of the above-mentioned control logics. The above-mentioned control logic includes the execution conditions and execution order of the corresponding above-mentioned transaction actions; the calling unit calls the control components corresponding to each of the above-mentioned control logics from the database, and calls the functional components corresponding to each of the above-mentioned transaction actions from the above-mentioned database. The above-mentioned control logics correspond one-to-one to the above-mentioned control components, and the above-mentioned transaction actions correspond one-to-one to the above-mentioned functional components. The above-mentioned control components are used to execute the corresponding above-mentioned control logics, and the above-mentioned functional components are used to execute the corresponding above-mentioned transaction actions. The above-mentioned control components and the above-mentioned functional components are both components created according to the historical transaction process and stored in the above-mentioned database; the generation unit assembles the above-mentioned control components and the above-mentioned functional components into an application according to the above-mentioned overall control logic and runs the above-mentioned application. The device determines the transaction actions of the transaction process and the execution conditions and execution order of the transaction actions based on the transaction requirements, then calls the corresponding control components and functional components from the database, and assembles the control components and functional components into an application capable of executing the transaction process according to the execution conditions and execution order of the transaction actions, and runs the application to complete the transaction. Among them, the control components and functional components are both service-level assets created based on historical transaction processes. The device solves the problem in the existing technology that it is impossible to generate transaction applications based on service-level reused assets.

[0121] 3) The transaction application generation system of the present application includes: one or more processors, memory, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs include a generation method for executing the transaction application. The system determines the transaction actions of the transaction process and the execution conditions and execution order of the transaction actions based on the transaction requirements, then calls the corresponding control components and functional components from the database, and assembles the control components and functional components into an application capable of executing the transaction process according to the execution conditions and execution order of the transaction actions, and runs the application to complete the transaction. The control components and functional components are both service-level assets created based on historical transaction processes. This system solves the problem in the prior art of being unable to generate transaction applications based on service-level reused assets.

[0122] The above description is merely a preferred embodiment of the present application and is not intended to limit the present application. Various modifications and variations are possible for those skilled in the art. Any modifications, equivalent substitutions, or improvements made within the spirit and principles of the present application shall be included within the scope of protection of the present application.

Claims

1. A method for generating a transaction application, characterized in that: The method comprises: Determine multiple transaction actions and overall control logic based on transaction requirements. The overall control logic includes multiple consecutive control logics. Each transaction action corresponds to one control logic. The control logic includes execution conditions and execution order of the corresponding transaction actions. Calling the control components corresponding to each control logic from the database, and calling the functional components corresponding to each transaction action from the database, wherein the control logics correspond to the control components one-to-one, and the transaction actions correspond to the functional components one-to-one, the control components are used to execute the corresponding control logics, and the functional components are used to execute the corresponding transaction actions, and both the control components and the functional components are created based on historical transaction processes and stored in the database; Assembling the control components and the functional components into an application according to the overall control logic and running the application; Before calling the control components corresponding to each of the control logics from the database and calling the functional components corresponding to each of the transaction actions from the database, the method further includes: creating the control components and the functional components according to the historical transaction process, the coupling principle, and the mutual exclusion principle, and storing the control components and the functional components in the database, so that coupled components are allowed to execute sequentially and mutually exclusive components are prohibited from executing sequentially, the coupled components being the control components or the functional components created according to the coupling principle, and the mutually exclusive components being the control components or the functional components created according to the mutual exclusion principle. The characteristic of components created according to the coupling principle is that the coupled components are mutually dependent, and the characteristic of components created according to the mutual exclusion principle is that the mutually exclusive components are mutually exclusive and cannot have input or output to each other; Calling the control component corresponding to each control logic from the database, and calling the functional component corresponding to each transaction action from the database, includes: obtaining a first call path corresponding to each control logic, and obtaining a second call path corresponding to each transaction action, the control logic and the first call path have a one-to-one correspondence, the transaction action and the second call path have a one-to-one correspondence, the first call path is the path for calling the control component from the database, and the second call path is the path for calling the functional component from the database.

2. The method according to claim 1, characterized in that Calling the control components corresponding to each of the control logics from the database, and calling the function components corresponding to each of the transaction actions from the database, further comprising: According to the first calling path, the control component corresponding to each control logic is called from the database, and according to the second calling path, the functional component corresponding to each transaction action is called from the database. The first calling path corresponds one-to-one to the control component, and the second calling path corresponds one-to-one to the functional component.

3. The method according to claim 2, characterized in that Before calling the control components corresponding to the control logics from the database and calling the function components corresponding to the transaction actions from the database, the method further includes: The first calling path is set to each control component in the database, and the second calling path is set to each functional component in the database.

4. The method according to claim 1, wherein Before assembling the control components and the functional components into an application according to the overall control logic and running the application, the method further includes: Determining whether there are any syntax errors in the overall control logic, and determining whether there are any semantic errors in the overall control logic; If the overall control logic has the syntax error, a syntax error message notification is sent; if the overall control logic has the semantic error, a semantic error message notification is sent.

5. The method according to claim 1, wherein Assembling the control components and the functional components into an application according to the overall control logic and running the application includes: Running the control component and the functional component according to the overall control logic to simulate the transaction process and obtain simulation results; In the case that the simulation result meets the transaction requirements, the control components and the functional components are assembled into the application according to the overall control logic and the application is run.

6. The method according to any one of claims 1 to 5, characterized in that The types of the control components include at least a branch type, a loop type, a timing type and a parallel type, and the functional components include at least a data processing component and a transaction processing component.

7. A device for generating a transaction application, characterized in that: The device comprises: a determination unit, configured to determine, based on transaction requirements, a plurality of transaction actions and an overall control logic, wherein the overall control logic includes a plurality of consecutive control logics, each transaction action corresponds to one control logic, and the control logic includes execution conditions and an execution order of the corresponding transaction actions; a calling unit, configured to call a control component corresponding to each control logic from a database, and to call a function component corresponding to each transaction action from the database, wherein the control logic corresponds to the control component in a one-to-one manner, and the transaction action corresponds to the function component in a one-to-one manner, the control component is configured to execute the corresponding control logic, and the function component is configured to execute the corresponding transaction action, and both the control component and the function component are created based on historical transaction processes and stored in the database; a generating unit, configured to assemble the control components and the functional components into an application program according to the overall control logic and run the application program; The apparatus further includes: a creation unit, configured to create the control component and the functional component according to the historical transaction process, the coupling principle, and the mutual exclusion principle, and store the control component and the functional component in the database before calling the control component corresponding to each control logic from the database and calling the functional component corresponding to each transaction action from the database, so that coupled components are allowed to execute sequentially and mutually exclusive components are prohibited from executing sequentially, wherein the coupled component is the control component or the functional component created according to the coupling principle, and the mutually exclusive component is the control component or the functional component created according to the mutual exclusion principle. The characteristic of components created according to the coupling principle is that the coupled components are mutually dependent, and the characteristic of components created according to the mutual exclusion principle is that the mutually exclusive components are mutually exclusive and cannot have input or output to each other; The calling unit includes: an acquisition module, used to obtain a first call path corresponding to each control logic, and obtain a second call path corresponding to each transaction action. The control logic has a one-to-one correspondence with the first call path, and the transaction action has a one-to-one correspondence with the second call path. The first call path is a path for calling the control component from the database, and the second call path is a path for calling the functional component from the database.

8. A computer-readable storage medium, characterized in that The computer-readable storage medium includes a stored program, wherein when the program is executed by a processor, the processor executes the method for generating a transaction application according to any one of claims 1 to 6.

9. A system for generating a transaction application, characterized in that: include: One or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and are configured to be executed by the one or more processors, and the one or more programs include a method for generating a transaction application according to any one of claims 1 to 6.

Images