CN109324787B

CN109324787B - Business software development method and device and terminal equipment

Info

Publication number: CN109324787B
Application number: CN201810948980.6A
Authority: CN
Inventors: 郑明都; 吴健; 雷利文; 谢宏; 潘海韬
Original assignee: Shenzhen Yihua Computer Co Ltd
Current assignee: Shenzhen Yihua Computer Co Ltd
Priority date: 2017-08-18
Filing date: 2018-08-20
Publication date: 2022-05-10
Anticipated expiration: 2038-08-20
Also published as: CN109324787A; CN107632825A

Abstract

The embodiment of the invention is suitable for the technical field of software development and discloses a method, a device, terminal equipment and a storage medium for developing service software, wherein the method comprises the following steps: generating one or more process nodes based on one or more process node templates selected by a user according to a service function required to be realized and process node template parameters configured for the process node templates by the user; the process node template is obtained by analyzing various service requirements and performing abstract induction; and connecting each flow node by adjusting the processing logic sequence of the flow node to generate a business flow chart and a business flow configuration file corresponding to the business flow chart. The embodiment of the invention can reduce the development and maintenance difficulty of the service software, effectively improve the development efficiency, reduce the technical threshold of the development and maintenance of the service software and save the development cost.

Description

Business software development method and device and terminal equipment

Technical Field

The invention belongs to the technical field of software development, and particularly relates to a business software development method, a business software development device, terminal equipment and a computer readable storage medium.

Background

The business handling is closely related to the life of people, and the aspects related to the business handling comprise the industries of banking, telecommunication, electric power, medical treatment, aviation, retail and the like. At present, the development technology threshold of application software for service handling is high, engineers mastering the programming technology are not familiar with the terminal service, and personnel familiar with the terminal service are not familiar with the programming technology, so that the innovation difficulty of the terminal service is high, and the development efficiency of service software is low.

Disclosure of Invention

In view of this, embodiments of the present invention provide a service software development method, an apparatus, a terminal device, and a computer-readable storage medium, so as to solve the problem in the prior art that the service software development method is low in efficiency.

A first aspect of an embodiment of the present invention provides a method for developing service software, including:

generating one or more process nodes based on one or more process node templates selected by a user according to a service function required to be realized and process node template parameters configured for the process node templates by the user; the process node template is obtained by analyzing various service requirements and performing abstract induction;

and connecting each flow node by adjusting the processing logic sequence of the flow node to generate a business flow chart and a business flow configuration file corresponding to the business flow chart.

Optionally, after the connecting each flow node by adjusting the processing logic sequence of the flow node to generate a service flow diagram and a service flow configuration file corresponding to the service flow diagram, the method further includes:

and placing the service process configuration file in a process execution platform for execution so as to realize corresponding service functions.

Optionally, the flow node template includes a service Agent and a control Agent; the service Agent comprises a device Agent, a page Agent and a sub-process Agent; the control agents comprise a start Agent, a branch Agent, a confluence Agent and an end Agent.

Optionally, the sub-process Agent includes a first conventional attribute page, a process attribute page, a first script attribute page, and a first remark attribute page; the node template of the sub-process Agent is a node template based on a QT event driven technology;

the specific process of generating the sub-process nodes according to the sub-process agents selected by the user and the process node template parameters configured for the sub-process agents by the user respectively comprises the following steps:

receiving a first click instruction of the user for clicking the sub-process Agent;

displaying a configuration page of the sub-process Agent according to the first click instruction;

receiving a first conventional attribute parameter, a first script attribute parameter and a first remark attribute parameter which are input by the user according to display information of the configuration page of the sub-process Agent; the first conventional attribute parameters comprise a process name and a process exit;

instantiating the sub-process Agent according to the first conventional attribute parameter, the first script attribute parameter and the first remark attribute parameter to generate the sub-process node.

Optionally, the page Agent is a flow node template for processing a webpage, wherein the flow node template is based on a QT event-driven technology and is used for realizing an event-driven mechanism based on the QT event-driven technology or based on a NodeJS built-in event technology;

the page Agent comprises a second conventional attribute page, a page attribute page, a first pin setting attribute page, a page script attribute page, a second script attribute page and a second remark attribute page;

the specific process of generating the page flow node according to the page Agent selected by the user and the flow node parameters respectively configured for the page Agent by the user comprises the following steps:

receiving a second click instruction of the user for clicking the page Agent;

displaying a configuration page of the page Agent according to the second click instruction;

receiving a second conventional attribute parameter, a page attribute parameter, a webpage script parameter, a second script attribute parameter, a first pin setting parameter and a second remark parameter which are input by the user according to a configuration page of the page Agent;

the second conventional attribute parameters comprise a webpage display position parameter, an input device parameter, a key event response parameter and an interface jump parameter; the page attribute parameters comprise page configuration parameters, page initialization setting parameters and input setting parameters;

and instantiating the page Agent according to the second conventional attribute parameter, the page attribute parameter, the webpage script parameter, the second script attribute parameter, the first pin setting parameter and the second remark parameter to generate a page flow node.

Optionally, the start Agent and the end Agent both include a remark attribute setting page; the converging Agent and the branching Agent both comprise a remark attribute setting interface and a pin setting interface;

the starting Agent, the ending Agent, the converging Agent and the branching Agent are flow node templates for realizing an event-driven mechanism based on a QT event-driven technology or a NodeJS built-in event technology and used for logic processing.

Optionally, the device Agent comprises an event method execution sequence; the event method execution sequence comprises a plurality of Agent assembly events and execution methods corresponding to the Agent assemblies; the Agent component comprises a hardware equipment function component and a software support component, wherein both the hardware equipment function component and the software support component are provided with an event trigger mechanism; the equipment Agent is a node template for realizing an event-driven mechanism based on a QT event-driven technology or a NodeJS built-in event technology;

the equipment Agent comprises a third conventional attribute page, a third script attribute page, a second pin setting page and a third remark attribute page.

Optionally, the flow node template parameters include an execution instruction and a trigger event, where the trigger event is triggered by the execution instruction; the equipment Agent comprises trigger equipment and execution equipment;

the specific process of generating a plurality of process nodes according to the plurality of equipment agents selected by the user and the process node template parameters configured for the plurality of equipment agents by the user respectively comprises the following steps:

receiving an execution device and a trigger device selected by a user;

receiving at least one execution instruction and a plurality of first trigger events set for the selected execution device by a user, and receiving at least one second execution function and a plurality of second trigger events set for the selected trigger device by the user, so that the selected execution device causes one trigger event in the plurality of trigger events to occur when receiving the first execution instruction, and the selected trigger device is triggered to run the corresponding second execution function through the one trigger event;

and taking the corresponding second execution function as a third trigger event of the next trigger device until the process nodes with the functions corresponding to the execution device and the trigger device are generated.

Optionally, the method further comprises:

and after the execution instructions of the at least two execution devices are operated, the trigger device executes the trigger event.

Optionally, the method further comprises:

debugging the business flow chart;

and if the debugging is successful, saving the business flow chart as a business flow file in a custom format.

Optionally, the method further comprises:

updating the dynamic library in real time; the dynamic library comprises the name of the flow node template and flow node template parameters configured for the flow node template by a user;

receiving a query instruction, acquiring the flow node template parameters corresponding to the name of the flow node template in the query instruction from the dynamic library based on the name of the flow node template in the query instruction, and displaying the flow node template parameters.

Optionally, the method further comprises:

forming the business process graph into a business process file;

constructing a business process execution engine based on the business process file;

and executing the process of the business process file by utilizing the business process execution engine to realize business software.

A second aspect of an embodiment of the present invention provides a service software development apparatus, including:

a flow node generating unit, configured to generate one or more flow nodes based on one or more flow node templates selected by a user according to a service function to be implemented and flow node template parameters configured by the user for the flow node templates; the process node template is obtained by analyzing various service requirements and performing abstract induction;

and the business process generating unit is used for connecting each flow node by adjusting the processing logic sequence of the flow node to generate a business process diagram and a business process configuration file corresponding to the business process diagram.

A third aspect of the embodiments of the present invention provides a terminal device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the steps of the method according to any one of the above first aspects when executing the computer program.

A fourth aspect of embodiments of the present invention provides a computer-readable storage medium, in which a computer program is stored, which, when executed by a processor, performs the steps of the method according to any one of the above-mentioned first aspects.

Compared with the prior art, the embodiment of the invention has the following beneficial effects:

the embodiment of the invention generates the process nodes by acquiring the process node template selected by the user and the configuration information set for the process node template, associates each process node according to the processing logic sequence determined by the actual business requirement, and generates the visual business process diagram and the corresponding business process configuration file. The business software development can be realized by modifying and configuring the business process configuration file in an imaging way, and a complex computer programming language development environment can be separated. That is, the business development is simple like 'stacking blocks', and the programming realization and maintenance of complex business become simple and understandable through imaging design, so that the development and maintenance difficulty of business software can be reduced, the development efficiency is effectively improved, the technical threshold of the development and maintenance of the business software is reduced, and the development cost is saved; in addition, the complete isolation of the version of the software secondary development from the primary development can be realized, the effective control of the version of the program code is realized, the secondary development does not need to use the complex development environment of the primary development, the secondary development only needs to drag and configure parameters of the flow node template, and the technical threshold of software engineering is obviously reduced.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.

Fig. 1 is a schematic flow chart illustrating an implementation process of a business software development method according to an embodiment of the present invention;

FIG. 2 is a diagram illustrating an exemplary functionality provided by an embodiment of the present invention;

FIG. 3 is a diagram illustrating parameter information of a flow node template according to an embodiment of the present invention;

FIG. 4 is a diagram illustrating parameter information of another flow node template according to an embodiment of the present invention;

fig. 5 is a schematic flow chart illustrating an implementation of a business software development method according to an embodiment of the present invention;

FIG. 6 is a diagram of another example of functionality provided by an embodiment of the invention;

FIG. 7 is a diagram illustrating parameter information of a flow node template according to an embodiment of the present invention;

FIG. 8 is a schematic diagram illustrating an implementation flow of a business software development method according to an embodiment of the present invention;

FIG. 9 is a schematic diagram of a sub-process Agent provided by an embodiment of the invention;

FIG. 10 is a diagram of a conventional property page of a sub-process Agent provided by an embodiment of the invention;

FIG. 11 is a schematic view of a process attribute page of a sub-process Agent according to an embodiment of the present invention;

FIG. 12 is a schematic diagram of a script property page of a sub-process Agent provided by an embodiment of the invention;

fig. 13 is a schematic diagram of an html ui flow node template provided in an embodiment of the present invention;

fig. 14 is a schematic view of a flow node for "inputting a transfer-in account" according to an embodiment of the present invention;

FIG. 15 is a schematic diagram of a conventional property page of an html UI flow node template provided by an embodiment of the present invention;

fig. 16 is a schematic view of a page configuration page of an html ui flow node template according to an embodiment of the present invention;

FIG. 17 is a schematic diagram of a script page of an html UI flow node template provided by an embodiment of the present invention FIG. 18

Fig. 18 is a schematic diagram of a pin setting page of an html ui flow node template according to an embodiment of the present invention;

FIG. 19 is a schematic diagram of a control Agent provided by an embodiment of the invention;

FIG. 20 is a diagram of a device Agent regular property page provided by an embodiment of the present invention;

FIG. 21 is a schematic diagram of an Agent setup interface provided by an embodiment of the invention;

fig. 22 is a block diagram illustrating a configuration of a service software development apparatus according to an embodiment of the present invention;

fig. 23 is a schematic diagram of a terminal device according to an embodiment of the present invention.

Detailed Description

In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the invention. It will be apparent, however, to one skilled in the art that the present invention may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present invention with unnecessary detail.

In order to explain the technical means of the present invention, the following description will be given by way of specific examples.

Example one

Fig. 1 is a schematic diagram illustrating an implementation flow of a business software development method according to an embodiment of the present invention. As shown in fig. 1, the business software development method specifically includes the following steps S101 to S102.

Step S101: generating one or more process nodes based on one or more process node templates selected by a user according to a service function required to be realized and process node template parameters configured for the process node templates by the user; the process node template is obtained by analyzing various service requirements and performing abstract induction.

Generating a function instance according to a plurality of process node templates selected by a user and parameter information configured for the plurality of process node templates by the user respectively; and completing the business function corresponding to one sub-process in the business process through one function example or the combination of a plurality of function examples.

It should be noted that the flow node templates are generated by analyzing various service requirements and performing abstract induction, so that various service requirements can be realized in a parameter configuration manner in a service development flow stage. The flow node templates are various agents. And instantiating the flow node template to generate a corresponding flow node.

The description of the flow node template, the flow nodes and the service functions is as follows:

the flow node template is a reusable module, and corresponding parameter information is configured on the flow node template to realize corresponding functions. Business needs include, but are not limited to, banking needs, medical needs, transportation needs, and communication needs. Different service requirements are realized through corresponding service functions. The business functions of the user for handling various banking businesses are as follows: the system comprises a bank drawing business, a bank deposit business, a bank inquiry business, a bank password changing business, a bank transfer business and the like. The flow nodes are correspondingly implemented as the service functions, specifically, one service function is implemented by one flow node, or one service function is implemented by a plurality of flow nodes. The process node generating process is generated according to a plurality of process node templates selected by a user and parameter information configured for the plurality of process node templates by the user.

The business process comprises a main process and a plurality of sub-processes, and one sub-process comprises at least one process node. And completing the business function corresponding to a sub-process in the business process through one process node or the combination of a plurality of process nodes.

Optionally, the process node template includes a service process node template and a control process node template. The service Agent comprises a device Agent, a page Agent and a sub-process Agent; the control agents comprise a start Agent, a branch Agent, a confluence Agent and an end Agent. Further, the page agents comprise a common page Agent and an input page Agent. Specifically, the method comprises the following steps:

if the equipment Agent is the equipment Agent, acquiring an input port, an output port, a trigger device, a trigger event, an execution device and an execution function which are set by a user for the equipment Agent, and generating an equipment instantiation Agent;

if the page is a common page Agent, acquiring common page parameters set by a user for the common page Agent, and generating a common page instantiation Agent;

if the input page is the input page Agent, acquiring input page parameters set by a user for the input page Agent, and generating an input page instantiation Agent;

if the sub-process Agent is the sub-process Agent, acquiring the number of output ports set by a user for the sub-process Agent and the name of the output ports, and generating a sub-process instantiation Agent;

if the start Agent is the start Agent, acquiring the number of output ports of the start Agent and the name of the output ports, and generating an instantiation start Agent;

the branch Agent acquires the number of output ports of the start Agent and the name of the output ports, and generates a branch instantiation Agent; different ones of the output ports trigger execution of different ones of the flow branches or sub-flow branches associated therewith;

the converging Agent acquires the number of different input ports, the name of the input port and the name of the converged output port of the converging Agent, and generates a converging instantiation Agent;

and the ending Agent acquires the input port of the ending Agent and the name of the input port, and generates an ending instantiation Agent.

The service flow node template and the control flow node template are multiplexed, that is, the service flow node template or the control flow node template can be configured, and the configured service flow node template and the configured control flow node template are combined to form a function example. For example, when the business process is a financial self-service terminal business process, the business process node template may include an equipment process node template, a common page process node template, a password input process node template, and a sub-process node template; the control flow node templates may include a start flow node template, an end flow node template, a branch flow node template, and a join flow node template. And selecting corresponding process node templates according to the function examples to be constructed, wherein the corresponding process node templates comprise at least one business process node template and at least one control process node template. Configuring parameters for a flow node template, and setting a trigger event (trigger function) for triggering the equipment Agent to start and an execution main body of the trigger event, namely trigger equipment; and an execution event (execution function) after the flow node template is started and an execution subject of the execution event, namely, an execution device. Generally, one process node template has input pins and output pins, the input pins and the output pins of the process node template are defined, and a function instance is constructed by connecting the input pins of one process node template with the output pins of another process node template.

The following description is made in conjunction with the actual situation:

for example, a graphical programming implementation of the function of clearing customer data information.

An example of the function of clearing the client data information is shown in fig. 2.

In the function example shown in fig. 2, a total of four process node templates are used to implement the sub-process, and the two control process node templates and the two service process node templates include:

1) starting a flow node template: marking the beginning of the sub-flow.

2) "clear this customer transaction information" business process node template: the method comprises the steps of adopting an equipment process node template, configuring parameter information for the equipment process node template, wherein the configured parameter information is shown in figure 3, and the parameter information comprises a trigger equipment Action, an execution equipment Action and an output pin output and is used for realizing a functional fragment of 'clearing the current customer transaction information' in a sub-process.

The working principle of clearing the customer transaction information is as follows: entering a service process node template of 'clearing the current customer transaction information' from an input pin, wherein a function Action is triggered by Active (), after the function is executed, an execution method (execution event) of execution equipment is called, namely data Pool Remove Section (QString), a parameter TRAN input by a user represents clearing the transaction information, and then Action is called, wherein Deliver (QString) is output from a pin with a pin name of output.

3) "clear customer information" business process node template: the device process node template is adopted, and parameter information is configured for the device process node template as shown in fig. 4, wherein the parameter information includes a trigger device Action, an execution device Action and an output pin output.

The working principle is as follows:

and entering the flow node template from an input pin, triggering a function Action, and calling an execution method of the execution equipment after the function is executed, wherein the function Action comprises a dataPool RemoveSection (QString), an input parameter is Customer which represents that transaction information is cleared, and then calling an Action, a Deliver (QString) and goes out from a pin with a pin name of output.

4) And (4) ending the flow node template: marking the end of the sub-flow.

Step S102: and connecting each flow node by adjusting the processing logic sequence of the flow node to generate a business flow chart and a business flow configuration file corresponding to the business flow chart.

That is, the multiple process nodes are associated according to the association information among the multiple process nodes, and the business process diagram is displayed in the editing page based on the business process diagram generated by the associated multiple process nodes.

It should be noted that the service flow configuration file may be executed under a fixed software architecture, the service software in the prior art is a stack of programming language codes, and the service software provided in this embodiment is a combination of an implemented fixed software architecture and a service flow configuration file, where the software architecture is basically unchanged, the service flow configuration file may be analyzed and executed, and the software function of the corresponding service is implemented by designing and modifying the service configuration file with a low technical threshold.

The association relationship may be that after the execution device in one function instance a executes the execution function, the result of the execution function is used as a trigger event, and the execution device in another function instance B is correspondingly triggered to start; and connecting the output pin of the function instance A with the input pin of the function instance B by the user, responding to the received operation instruction of the user, generating a corresponding connection relation, similarly completing the connection of all related function instances, namely generating a visual business flow chart, and displaying the visual business flow chart in an editing page.

Optionally, on the basis of the above scheme, after the connecting each flow node by adjusting the processing logic sequence of the flow node to generate a service flow diagram and a service flow configuration file corresponding to the service flow diagram, the method may further include: and placing the service process configuration file in a process execution platform for execution so as to realize corresponding service functions.

It should be noted that the process node may be converted into the service process configuration file.

Optionally, on the basis of the above scheme, the method further includes the following steps:

debugging the business flow chart;

The debugging may be to debug the whole service flow chart, or to debug a certain function instance (flow node) separately, and then debug the whole service flow chart, if the debugging is successful, the visual service flow chart and the parameter information are saved as a service flow file in a custom format (for example, word). And if the debugging is wrong, modifying according to the error prompt until the debugging is successful. It is understood that the following are the cases: the generated visual business flow chart can be directly executed without debugging.

It should be noted that the service in the embodiment of the present invention may specifically be a banking service, and it is understood that in other embodiments, the service may also be other types of services, which is not limited herein.

In this embodiment, a flow node is generated by obtaining a flow node template selected by a user and configuration information set for the flow node template, and each flow node is associated according to a processing logic sequence determined by an actual service requirement to generate a visual service flow diagram and a corresponding service flow configuration file. The business software development can be realized by modifying and configuring the business process configuration file in an imaging way, and a complex computer programming language development environment can be separated. That is, the business development is simple like a building block stack, and the programming realization and maintenance of complex business become simple and understandable through imaging design, so that the development and maintenance difficulty of business software can be reduced, the development efficiency is effectively improved, the technical threshold of the development and maintenance of the business software is reduced, and the development cost is saved; in addition, the complete isolation of the version of the software secondary development from the primary development can be realized, the effective control of the version of the program code is realized, the secondary development does not need to use the complex development environment of the primary development, the secondary development only needs to drag and configure parameters of the flow node template, and the technical threshold of software engineering is obviously reduced.

Example two

Fig. 5 is a schematic flow chart illustrating an implementation of the business software development method according to the second embodiment of the present invention. On the basis of the first embodiment, when the process node template selected by the user is the device Agent, the process node template parameter information at least includes an execution instruction and a trigger event, the trigger event is triggered by the execution instruction, and a specific process of generating a plurality of device process nodes according to the plurality of device agents selected by the user and the process node template parameters configured for the plurality of device agents by the user includes steps S201 to S203.

Step S201: and receiving the execution device and the trigger device selected by the user.

Step S202: receiving at least one execution instruction and a plurality of first trigger events set for the selected execution device by the user, and receiving at least one second execution function and a plurality of second trigger events set for the selected trigger device by the user, so that the selected execution device causes one trigger event in the plurality of trigger events to occur when receiving the first execution instruction, and the selected trigger device is triggered to run the corresponding second execution function through the one trigger event.

Step S203: and taking the corresponding second execution function as a third trigger event of the next trigger device until generating a device process node with the function corresponding to the execution device and the trigger device.

Such as graphical programming implementations of card-swallowed sub-processes.

The sub-processes of deposit, withdrawal, transfer, inquiry, password change and the like all comprise the function of card swallowing, and when the sub-processes come out from a card swallowing pin, the card swallowing sub-process is required to be called to execute card swallowing operation.

An example implementation of the card-swallowing function is shown in fig. 6:

in the above flowchart, a total of three process node templates are used to implement the process, and two control process node templates and one service process node template include:

1) starting a flow node template: marking the beginning of the card-swallowing process.

2) And (4) ending the flow node template: marking the end of the card-swallowing process.

3) A 'card-swallowing' service flow node template: an equipment process node template is adopted, and two trigger devices are configured for the equipment process node template: action and IDC; four execution devices: action, IDC, JPTR and DeviceManager; an output pin output.

The working principle of the card swallowing function example is as follows:

referring to FIG. 6 and FIG. 7, when the flow node template is entered from the input pin, the function Action:: Active () is triggered, and after the function is executed, the execution method Capture () of the execution device IDC is called, namely IDC:: Capture ().

If IDC shows that after the Capture () is executed, an event CardCaptured () is triggered, then the IDC goes out from an output pin with the pin name of output, then the running water information is printed, an execution method PrintRawData (QSTring) of the execution equipment JPTR is called, and information such as card swallowing numbers and the like is returned. If IDC:: Capture () has finished executing the post-trigger event hardware _ Error (), then go out from the output pin with the pin name output.

If IDC shows that the Capture () triggers the event CardTaken () after the execution, the IDC goes out from the output pin with the pin name output.

If IDC:, the trigger event CardCapture () is triggered after the execution of Capture (), then go out from the output pin with the pin name output.

Finally, an Action trigger function pinDeliver (QSTring) of the trigger device indicates that the trigger is triggered when the Action goes out of a certain specified output pin of the Action, the Action refers to that the Action goes out of the output pin to trigger the function, and then a script function DeviceManager in a parameter information system is called: : callscript func, executes a script named reflardrecord.

Triggering to enter an Action, calling a built-in object to generate a function active (), calling a Deliver () to go out from an output pin, continuously calling a trigger function of trigger equipment and executing an execution Action (function) of the equipment to form an autonomous body, and the autonomous body is not controlled by any external function, including an execution flow engine.

Optionally, after the at least two execution devices run their respective execution instructions, the trigger device executes a trigger event.

When the confluence flow node template is used, triggering the next branch to operate after at least two branches before merging are all completed; a branch may be a device flow node template.

According to the embodiment of the invention, the trigger event set by the user for the execution equipment is received, so that the trigger equipment triggers the execution equipment to run the execution instruction through the trigger event, the trigger function of the trigger equipment is continuously called, and the execution action of the execution equipment is executed, so that an autonomous body is formed, the function corresponding to the function instance is completed, and the function is independent, so that the independent development can be realized, and the development efficiency is higher.

EXAMPLE III

On the basis of the first embodiment, fig. 8 is a schematic diagram illustrating an implementation flow of a business software development method provided by the third embodiment of the present invention. As shown in fig. 8, on the basis of the first embodiment, the business software development method further includes the following steps S301 to S302.

Step S301: updating the dynamic library in real time; the dynamic library comprises the name of the flow node template and flow node template parameters configured for the flow node template by a user;

step S302: and receiving a query instruction, acquiring flow node template parameter information corresponding to the name of the flow node template in the query instruction from the dynamic library based on the name of the flow node template in the query instruction, and displaying the parameter information.

The dynamic library at least comprises parameter information, the parameter information at least comprises the name of the process node template, when the process node template needs to be added, the dynamic library is updated in real time, the parameter information of the process node template is read from the dynamic library, and the added process node template takes effect immediately. When a user needs to query specific parameter information of a certain process node template, corresponding parameter information is displayed based on the name of the process node template in a query instruction input by the user.

The embodiment of the invention updates the dynamic library in real time, reads the parameter information of the flow node template from the dynamic library, displays the corresponding parameter information based on the name of the flow node template in the query instruction input by the user, is convenient to modify and adjust some parameters according to actual needs, and has strong pertinence and flexible processing mode.

Example four

Each process node is provided with a corresponding process node template, corresponding parameters are configured for the process node templates according to actual needs, and then corresponding process nodes can be generated according to the configured parameters and the process node templates.

The present embodiment will describe a flow node template of a sub-flow Agent.

The sub-process Agent comprises a first conventional attribute page, a process attribute page, a first script attribute page and a first remark attribute page; the node template of the sub-process Agent is a node template based on a QT event driven technology;

the specific process of generating the sub-process node according to the sub-process Agent selected by the user and the parameter information configured for the sub-process Agent by the user may include:

receiving a first click instruction of a user for clicking the sub-process Agent;

receiving a first conventional attribute parameter, a first script attribute parameter and a first remark attribute parameter which are input by a user according to display information of a configuration page of the sub-process Agent; the first conventional attribute parameters comprise a process name and a process exit;

and instantiating the sub-process Agent according to the first conventional attribute parameter, the first script attribute parameter and the first remark attribute parameter to generate a process node of the sub-process Agent.

Specifically, after clicking the sub-process Agent, the user pops up a configuration page of the process node template, and the configuration page includes a conventional attribute page, a process attribute page, a script attribute page and a remark attribute page.

It should be noted that the first conventional attribute parameter may include information such as a process node name and a process footer; the script attribute parameters may include information about the parameters of the script that need to be loaded.

The flow node template of the sub-flow Agent shown in fig. 9, the conventional attribute page diagram of the flow node of the sub-flow Agent shown in fig. 10, the flow attribute page diagram of the flow node of the sub-flow Agent shown in fig. 11, and the script attribute page diagram of the flow node of the sub-flow Agent shown in fig. 12 will be described below.

The conventional property page shown in FIG. 10 can set nested sub-flow names and output pins. When a flow that has already been implemented is loaded, output pins are typically added, and the output pins in the icon are automatic in the Agent after the sub-flow settings have been added. The item content of the conventional attribute page is a read-only attribute and is mainly used for displaying a process attribute variable with a scope being the whole sub-process. These flow attribute variables are added in the sub-flows through the regular property pages in the flow attributes.

The process attribute page is a read-only attribute and is mainly used for displaying the process attribute variable with the scope being the whole sub-process. These flow attribute variables are added in the sub-flow through the regular property page in the flow attribute, as shown in FIG. 11.

As shown in the script Property Page diagram of FIG. 12, content in the current scripting environment is added by restoring the default script button. If a script is to be used, a default script is first added. In order to facilitate the editing and modification of the script, a search and replacement function is added in the script environment. The contents to be searched are input in the search editing box, and the contents meeting the search requirement are marked by yellow ground color in the editing environment. And the content which is in accordance with the searching requirement in the previous and next can be selected through <, >. And inputting the search content in the search editing box, and replacing the search content with the content to be replaced input in the editing box. Clicking the replacement button can replace the content meeting the search requirement under the current cursor with the replacement content, but does not search the next content meeting the search requirement. When the replacing and searching button is clicked, the content meeting the searching requirement under the current cursor can be replaced, and the next content meeting the searching requirement is searched. When all the replacement buttons are clicked, all the contents meeting the search requirement are replaced by the replacement contents. If the function in the engineering public script needs to be called, the engineering public script can be selected and loaded; and if the sub-process public script needs to be called, the sub-process public script can be selected and loaded.

The remark property page is the only property page in the Action Source property setting dialog box, is used for annotating the function of a process, can also remark notes in the development process, and is equivalent to the function of notes.

The user can click the flow node template shown in fig. 9, corresponding parameters are configured in dialog boxes such as a conventional property page, a flow property page, a script property page, a remark property page and the like in sequence, sub-flow agents are instantiated through a QT event-driven technology, and corresponding sub-flow Agent flow nodes can be obtained.

The QT event-driven technology or the NodeJS built-in event technology enables the service component template to generate flow nodes capable of realizing different service functions through instantiation, and each service flow node can be organized into a service flow, so that the terminal service is realized by running on the running platform. And connecting all service nodes through certain logic by utilizing a signal and slot function mechanism by utilizing a QT event driving technology to form a service sub-process.

After the flow node of the corresponding sub-flow Agent is generated, it can be converted into a JavaScript Object Notation (JSON) file. The JSON file can also be converted into a process node of the sub-process Agent. That is, the sub-process node templates, the instantiated sub-process node templates, and the corresponding JSON files can be transformed with each other, and the JSON files can be executed by the process platform.

It can be seen that, in the embodiment, by developing a uniform sub-process Agent, programming of a sub-process Agent node service function is realized through configuration, and graphical programming is realized; and the sub-process Agent instantiates and generates sub-process nodes with certain functions through parameter configuration, and can convert the process files in the JS form for the process execution platform to load and run. The difficulty in programming the sub-process nodes is greatly reduced, the technical threshold and the cost are reduced, and the difficulty and the cost of software maintenance are greatly simplified; in addition, the sub-process function implements and multiplexes the process node templates. The use of the processing sub-process is beneficial to the reutilization of the process resources, the complexity of the whole structure is reduced, the understanding is convenient, and the development period is shortened.

EXAMPLE five

The following describes a flow node template of a page Agent.

The page Agent is a flow node template which is based on a QT event driving technology, directly or indirectly inherits a QObject class, has a slot function-event mechanism and has an automatic event triggering function and is used for webpage processing; or, the page Agent is a node template for realizing an event-driven mechanism based on the NodeJS built-in event technology;

the process of generating the page flow node according to the page Agent selected by the user and the parameter information configured for the page Agent by the user may specifically include:

receiving a second click instruction of a user for clicking the page Agent;

receiving a second conventional attribute parameter, a page attribute parameter, a webpage script parameter, a second script attribute parameter, a first pin setting parameter and a second remark parameter which are input by a user according to a configuration page of a page Agent;

The page Agent is used for processing the webpage, namely the page Agent is an html UI flow node template which can be mainly used for a page with a key and a button response, and the flow node template has an Agent function, can be directly or indirectly inherited to a QOject class and has an automatic event triggering function. QT event-driven technology or a NodeJS built-in event technology mechanism can be adopted to enable the flow node template of the page Agent to produce flow nodes with corresponding service functions through instantiation, then a plurality of service flow nodes form a service flow according to certain processing logic, and the service flow is operated to realize corresponding terminal services.

After the process of the page Agent is encapsulated into the process node template, a user can configure the page through a plurality of parameters provided by the process node template, and generate the process node with the corresponding function after configuring the corresponding parameters. The following description will be made with reference to an html ui flow node that implements the "input transfer to account" function. Description will be given with reference to the schematic diagram of the html ui flow node template shown in fig. 13, the schematic diagram of the "enter transfer account" flow node shown in fig. 14, the schematic diagram of the conventional attribute page of the html ui flow node template shown in fig. 15, the schematic diagram of the page configuration page of the html ui flow node template shown in fig. 16, the schematic diagram of the web script page of the html ui flow node template shown in fig. 17, and the schematic diagram of the pin setting page of the html ui flow node template shown in fig. 18.

A user can add an Agent html ui flow node template (shown in fig. 13) in the Agent toolbar of the flowedit to a work area, and then open an attribute configuration page of the flow node template, wherein the attribute configuration page comprises pages such as a normal page, a page configuration page, a web page script, a pin setting page and a remark page, and is used for configuring corresponding parameter information on different pages, and then corresponding instantiation flow nodes can be generated. As shown in fig. 15, the conventional property configuration page through which the response of the web page display screen, the input device, and the key event can be set. The web page display device includes a front screen (mainWin), a rear screen (SecondWin), and an additional screen, and refers to a position where the loaded web page is to be displayed, i.e., whether the loaded web page is displayed on the front screen, the rear screen, or the additional screen of the web page device. The input device refers to a device which can perform page input, and generally comprises a password keyboard (PIN) of a front screen and a rear maintenance keyboard of a rear screen. The method can be used for setting an automatic input device opening function, an automatic input device closing function or a reset timer during key input, wherein the automatic input device opening function refers to opening the input function of the input device after the webpage is loaded successfully; the automatic closing of the input device refers to the input function of automatically closing the web page when the web page is finished; resetting the timer upon pressing a key refers to restarting the timer upon pressing a key. The method can also set key jump setting, and can set information such as key or element ID, pin, page matching mode and the like on a jump setting page, wherein the page matching mode can have matching modes such as including and ending. The key skip setting can add and delete key skips.

As shown in the page configuration diagram of fig. 16, page setting, page initial setting, input setting, and the like can be performed through the page. The page settings can add, modify, delete, load pages. When the page needs to be added, the add button can be clicked, and a page setting dialog box pops up. Through the page setting dialog box, a page name, a page matching mode, timeout time and the like can be set, the page name refers to a page needing to be loaded, the page matching mode is divided into an inclusion mode and a sum mode. It is also possible to set whether the added page is set as a start page. The initial values of the elements on the page can be set through the page initialization setting, and the page initialization setting can be added, modified and deleted. The input setting page is mainly used for setting input and playback rules of the page, and input settings can be added, modified and deleted.

As shown in the schematic diagram of the web script property page in fig. 17, the web script property page provides a script editing environment in which the JS script can be directly used to achieve a desired effect. The content in the current script environment can be added by replying a default script button, if the script needs to be used, the default script is added, and the editing and the modification of the script can be facilitated through the searching and replacing functions provided by the page. The Pin setting page, as shown in fig. 18, through which input pins can be added, deleted, modified. The remark attribute page can be used for annotating the functional role of a flow, and can also be used for remarking the notes in the development process, which is equivalent to the function of a note. After the configuration is completed, an HtmlUI flow node as in fig. 14 may be generated.

It can be seen that the embodiment realizes the programming of the service function of the page node through configuration by developing a uniform page Agent, and realizes the graphical programming; and the page Agent instantiates and generates a page flow node with a certain function through parameter configuration, and the page flow node can convert the flow file in the JS form and is used for loading and running the flow execution platform. The method greatly reduces the difficulty in realizing page flow node programming, lowers the technical threshold and cost, and greatly simplifies the difficulty and cost of software maintenance.

EXAMPLE six

The present embodiment will describe the relevant contents of the control Agent.

The control agents include a start Agent, a branch Agent, a merge Agent, and an end Agent. The End Agent comprises an Agent End and an Agent Null. The starting Agent and the ending Agent both comprise remark attribute setting pages; the converging Agent and the branching Agent both comprise remark attribute setting interfaces and pin setting interfaces;

the start Agent, the end Agent, the converging Agent and the branching Agent are flow node templates for logic processing based on a QT event-driven technology or a NodeJS built-in event technology.

The start Agent flow node is the start node of each flow, and therefore, the start Agent has no input pin, only an output pin. The remark attribute page of the start Agent is used for annotating the functional role of a flow, and also can remark the notice in the development process, which is equivalent to the function of a note. The branch Agent comprises an input pin and a plurality of output pins, and the plurality of input pins can flow out simultaneously, so that simultaneous multitasking is realized. The pin setting attribute page of the branch Agent can be used for modifying and deleting output pins. When the pins need to be added, the adding button can be clicked, and then the related information of the added pins can be set.

The merge Agent node may also be referred to as a merge processing stage, which may merge multiple flows, and the merge Agent includes multiple input pins and only one output pin. The attribute setting of the converging Agent can be realized through a pin attribute page. The Agent node comprises an Agent End node and an Agent Null node, wherein the Agent Null node refers to no processing and is mainly used for ending a flow which does not need processing and comprises an input pin and no output pin; while Agent End indicates the End of a flow with no input pins and no output pins. The Start Agent, the Agent Null node template, the Agent End node template and the joining Agent can be referred to the schematic diagram of the control Agent shown in fig. 19, wherein Start is the Start Agent, Action target is the joining Agent, Null is the Agent Null node template, and End is the Agent End node template.

It can be seen that, in the embodiment, by developing a uniform control Agent, a corresponding service flow node can be instantiated and generated after a corresponding parameter is configured, so that graphical programming is realized. And the flow node template can be converted with the JS flow file, and the JS flow file can be loaded and operated by the flow execution platform. The method greatly reduces the difficulty in realizing the programming of the flow nodes, lowers the technical threshold and the cost, and greatly simplifies the difficulty and the cost in maintaining the software.

EXAMPLE seven

The present embodiment will describe the relevant content of the device Agent.

The equipment Agent comprises an event method execution sequence; the event method execution sequence comprises trigger events of a plurality of Agent components and execution methods corresponding to the Agent components; the Agent component comprises a hardware device functional component and a software supporting component, and both the hardware device functional component and the software supporting component are provided with event triggering mechanisms; the node template of the equipment Agent is a node template which is directly or indirectly inherited to a QObject class and provided with a slot function-event mechanism based on a QT event driving technology; or, the Agent is a node template for realizing an event-driven mechanism based on a NodeJS built-in event technology;

The execution method can be an Agent component corresponding to an Agent component event or an execution method of an event of another Agent component. Parameters used by functions such as events and methods of the Agent components can be obtained by accessing a data pool, local data of the service flow nodes and configuration files.

The hardware equipment functional component and the software supporting component can normalize functional interfaces of various hardware and software in advance to form the corresponding hardware equipment functional component and the corresponding software supporting component. The normalized hardware device function component and the software support component form a middleware which is used as an interface for realizing the most basic function granularity of the terminal application program, and the terminal can use the interfaces as basic function units to carry out logic composition.

An Agent Device, i.e. a Device process, the Device Agent comprises one input pin and a plurality of input pins. The attribute configuration of the flow node template can be realized by a conventional attribute page, a script attribute page, a pin setting attribute page, a remark attribute page and the like.

The conventional attribute page of the equipment Agent is mainly used for processing the relevant logic service of the equipment, and comprises trigger equipment, trigger events, execution equipment, execution Agent, parameters and the like. Referring to the schematic diagram of the device Agent regular property page shown in fig. 20, the operations of moving up, moving down, adding, modifying, deleting, etc. can be realized through the page. When the add button is clicked, an Agent setting interface as shown in fig. 21 pops up, and the trigger device, trigger time, execution device, execution method, parameter name, etc. of the Agent can be set through the page. The script attribute page of the equipment Agent can provide an editing environment of the script, and can perform operations such as adding a default script and checking a flow script. The pin setting property page can be used for adding, modifying, deleting input and output pins and the like. The notes tab may be used to annotate the functional role of a process, notes, etc.

It can be seen that, in the embodiment, by developing a uniform device Agent, programming of the device node service function is realized through configuration, and graphical programming is realized; the equipment Agent instantiates and generates an equipment flow node with a certain function through parameter configuration, and the equipment flow node can convert the flow file in the JS form and is used for loading and running the flow execution platform. The method greatly reduces the difficulty in realizing the programming of the equipment process nodes, reduces the technical threshold and the cost, and greatly simplifies the difficulty and the cost of software maintenance.

Example eight

Referring to fig. 22, a block diagram of a service software development apparatus according to an eighth embodiment of the present invention is shown. The service software development device 40 includes: a generating unit 41 and an associating unit 42. The specific functions of each unit are as follows:

a flow node generating unit 41, configured to generate one or more flow nodes based on one or more flow node templates selected by a user according to a service function to be implemented and flow node template parameters configured by the user for the flow node templates; the process node template is obtained by analyzing various service requirements and performing abstract induction;

and a service flow generating unit 42, configured to connect each flow node by adjusting the processing logic sequence of the flow node, and generate a service flow diagram and a service flow configuration file corresponding to the service flow diagram.

Optionally, the method further comprises:

and the execution unit is used for placing the service process configuration file in a process execution platform for execution so as to realize corresponding service functions. Optionally, the flow node template includes a service Agent and a control Agent; the service Agent comprises a device Agent, a page Agent and a sub-process Agent; the control agents include a start Agent, a branch Agent, a merge Agent, and an end Agent.

the flow node generating unit is specifically configured to:

and instantiating the sub-process Agent according to the first conventional attribute parameter, the first script attribute parameter and the first remark attribute parameter to generate a sub-process node.

Optionally, the page Agent is based on a QT event-driven technology or a nodjs built-in event technology, such as directly or indirectly inheriting a QObject class, having a slot function-event mechanism and having an automatic event trigger function, or adopting a flow node template for web page processing of a nodjs callback function technology mechanism;

the page Agent comprises a second conventional attribute page, a page attribute page, a first pin setting attribute page, a page script attribute page, a second script attribute page and a second remark attribute page.

The flow node generating unit is specifically configured to:

receiving a second click instruction of a user for clicking the page Agent;

Optionally, the starting Agent and the ending Agent correspondingly comprise remark attribute setting pages; the converging Agent and the branching Agent both comprise remark attribute setting interfaces and pin setting interfaces;

Optionally, the device Agent comprises an event method execution sequence; the event method execution sequence comprises trigger events of a plurality of Agent components and execution methods corresponding to the Agent components; the Agent component comprises a hardware device functional component and a software supporting component, and both the hardware device functional component and the software supporting component are provided with event triggering mechanisms; the equipment Agent is based on a QT event driving technology or a NodeJS built-in event technology, such as directly or indirectly inheriting from a QObject class and a node template with a slot function-event mechanism, or adopting a NodeJS call-back function technical mechanism;

Optionally, the flow node template parameters include an execution instruction and a trigger event, and the trigger event is triggered by the execution instruction; the equipment Agent comprises trigger equipment and execution equipment;

the flow node generating unit is specifically configured to:

receiving an execution device and a trigger device selected by a user;

receiving at least one execution instruction and a plurality of first trigger events set for the selected execution device by the user, and receiving at least one second execution function and a plurality of second trigger events set for the selected trigger device by the user, so that the selected execution device causes one trigger event in the plurality of trigger events to occur when receiving the first execution instruction, and the selected trigger device is triggered to run the corresponding second execution function through one trigger event;

and taking the corresponding second execution function as a third trigger event of the next trigger device until the flow nodes of the functions corresponding to the execution device and the trigger device are generated.

Optionally, the method further comprises:

and the execution unit is used for triggering the equipment to execute the trigger event after the at least two execution equipment run respective execution instructions.

Optionally, the method further comprises:

the debugging unit is used for debugging the business flow chart;

and the storage unit is used for storing the visual business flow chart as a business flow file in a user-defined format if the debugging is successful.

Optionally, the method further comprises:

the updating unit is used for updating the dynamic library in real time; the dynamic library comprises the name of the flow node template and flow node template parameters configured for the flow node template by a user;

and the query unit is used for receiving the query instruction, acquiring the flow node template parameters corresponding to the name of the flow node template in the query instruction from the dynamic library based on the name of the flow node template in the query instruction, and displaying the flow node template parameters.

Optionally, the method further comprises:

the forming unit is used for forming the business flow chart into a business flow file;

the construction unit is used for constructing a business process execution engine based on the business process file;

and the implementation unit is used for implementing the process of the business process file by utilizing the business process execution engine to implement the business software.

It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.

It should also be understood that the above-mentioned serial numbers of the embodiments of the present invention are merely for description, and do not represent the advantages and disadvantages of the embodiments.

Example nine

Fig. 23 is a schematic diagram of a terminal device according to an embodiment of the present invention. As shown in fig. 23, the terminal device 23 of this embodiment includes: a processor 230, a memory 231, and a computer program 232, such as a business software development method program, stored in the memory 231 and executable on the processor 230. The processor 230 executes the computer program 232 to implement the steps in the above-mentioned business software development method embodiments, such as the steps S101 to S102 shown in fig. 1. Alternatively, the processor 230, when executing the computer program 232, implements the functions of each module or unit in each device embodiment described above, for example, the functions of the modules 41 to 42 shown in fig. 21.

Illustratively, the computer program 232 may be divided into one or more modules or units, which are stored in the memory 231 and executed by the processor 230 to accomplish the present invention. The one or more modules/units may be a series of computer program instruction segments capable of performing specific functions, which are used to describe the execution process of the computer program 120 in the terminal device 23. For example, the computer program 232 may be divided into a flow node generation unit and a business flow generation unit, and the specific functions of each unit are as follows:

The terminal device 23 may be a desktop computer, a notebook, a palm computer, a cloud server, or other computing devices. The terminal device may include, but is not limited to, a processor 230, a memory 231. Those skilled in the art will appreciate that fig. 23 is merely an example of a terminal device and is not limiting and may include more or fewer components than shown, or some components may be combined, or different components, for example, the terminal device may also include input output devices, network access devices, buses, etc.

The Processor 230 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The storage 231 may be an internal storage unit of the terminal device 23, such as a hard disk or a memory of the terminal device 23. The memory 231 may also be an external storage device of the terminal device 23, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like, which are provided on the terminal device 23. Further, the memory 231 may also include both an internal storage unit and an external storage device of the terminal device 23. The memory 231 is used for storing the computer program and other programs and data required by the terminal device. The memory 231 may also be used to temporarily store data that has been output or is to be output.

It should be clear to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional units and modules is only used for illustration, and in practical applications, the above function distribution may be performed by different functional units and modules as needed, that is, the internal structure of the apparatus may be divided into different functional units or modules to perform all or part of the above described functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the modules or units is only one logical division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated modules/units, if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, all or part of the flow of the method according to the embodiments of the present invention may also be implemented by a computer program, which may be stored in a computer-readable storage medium, and when the computer program is executed by a processor, the steps of the method embodiments may be implemented. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, and the like. It should be noted that the computer readable medium may contain content that is subject to appropriate increase or decrease as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media does not include electrical carrier signals and telecommunications signals as is required by legislation and patent practice.

The above-mentioned embodiments are only used for illustrating the technical solutions of the present invention, and not for limiting the same; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present invention, and are intended to be included within the scope of the present invention.

Claims

1. A business software development method is characterized by comprising the following steps:

generating one or more process nodes based on one or more process node templates selected by a user according to a service function required to be realized and process node template parameters configured for the process node templates by the user; the process node template is obtained by analyzing various service requirements and performing abstract induction; the flow node template comprises a business Agent and a control Agent; the service Agent comprises a device Agent, a page Agent and a sub-process Agent; the control agents comprise a start Agent, a branch Agent, a confluence Agent and an end Agent; the equipment Agent comprises trigger equipment and execution equipment; the process node templates are provided with input pins and output pins, and the input pin of one process node template is connected with the output pin of the other process node template to construct a function example; connecting each flow node by adjusting the processing logic sequence of the flow node to generate a business flow diagram and a business flow configuration file corresponding to the business flow diagram;

the process of generating one or more flow nodes comprises:

receiving an execution device and a trigger device selected by a user;

receiving at least one execution instruction and a plurality of first trigger events set for the selected execution device by the user, and receiving at least one second execution function and a plurality of second trigger events set for the selected trigger device by the user, so that the selected execution device causes one trigger event in the plurality of trigger events to occur when receiving the first execution instruction, and the selected trigger device is triggered to execute the corresponding second execution function through the one trigger event;

taking the corresponding second execution function as a third trigger event of the next trigger device until a process node with a function corresponding to the execution device and the trigger device is generated;

instantiating the sub-process Agent according to the first conventional attribute parameter, the first script attribute parameter and the first remark attribute parameter, generating the sub-process node, and converting the sub-process node into a JavaScript object numbered notation file.

2. The business software development method of claim 1, wherein after the generating a business process diagram and a business process configuration file corresponding to the business process diagram by connecting each of the process nodes by adjusting the processing logic order of the process nodes, further comprises:

3. The business software development method of claim 1, wherein the page Agent is a flow node template for web page processing that implements an event-driven mechanism based on a QT event-driven technique or based on a NodeJS built-in event technique:

receiving a second click instruction of the user for clicking the page Agent;

4. The business software development method of claim 1, wherein the start Agent and the end Agent each comprise a remark attribute setting page; the converging Agent and the branching Agent both comprise a remark attribute setting interface and a pin setting interface;

5. The business software development method of claim 1, wherein the device Agent comprises an event method execution sequence; the event method execution sequence comprises trigger events of a plurality of Agent components and execution methods corresponding to the Agent components; the Agent component comprises a hardware device function component and a software supporting component, wherein both the hardware device function component and the software supporting component are provided with event triggering mechanisms; the equipment Agent is a node template for realizing an event-driven mechanism based on a QT event-driven technology or a NodeJS built-in event technology;

6. The business software development method of claim 5, wherein the flow node template parameters include an execution instruction and a triggering event, the triggering event being triggered by the execution instruction.

7. The business software development method of claim 6, further comprising:

8. The business software development method of claim 1, further comprising:

debugging the business flow chart;

9. The business software development method of claim 1, further comprising:

receiving a query instruction, acquiring the process node template parameters corresponding to the name of the process node template in the query instruction from the dynamic library based on the name of the process node template in the query instruction, and displaying the process node template parameters.

10. The business software development method of claim 1, further comprising:

forming the business process graph into a business process file;

11. A business software development apparatus, comprising:

a flow node generating unit, configured to generate one or more flow nodes based on one or more flow node templates selected by a user according to a service function to be implemented and flow node template parameters configured by the user for the flow node templates; the process node template is obtained by analyzing various service requirements and performing abstract induction; the flow node template comprises a service Agent and a control Agent; the service Agent comprises a device Agent, a page Agent and a sub-process Agent; the control agents comprise a start Agent, a branch Agent, a confluence Agent and an end Agent; the equipment Agent comprises trigger equipment and execution equipment; the process node templates are provided with input pins and output pins, and the input pin of one process node template is connected with the output pin of the other process node template to construct a function example;

a service flow generation unit, configured to connect each of the flow nodes by adjusting a processing logic sequence of the flow node, and generate a service flow diagram and a service flow configuration file corresponding to the service flow diagram;

the flow node generating unit is specifically configured to:

receiving an execution device and a trigger device selected by a user;

the flow node generating unit is specifically configured to:

12. A terminal device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the steps of the method according to any of claims 1 to 10 when executing the computer program.

13. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 10.