Business process link construction method and device, equipment, storage medium and computer program product

Abstract

The invention discloses a business process link construction method and device, equipment, a storage medium and a computer program product, and relates to the technical field of business process analysis, and the method comprises the steps: analyzing a source code of a business system, and collecting static data from an analysis result; the method comprises the following steps: acquiring corresponding dynamic data of a program code of a business system during operation by using a byte code enhancement technology, wherein the byte code is obtained by compiling a source code; generating business logic description of the business system based on the knowledge base and the prompt project corresponding to the business system; and constructing a business process link of the business system according to the static data, the dynamic data and the business logic description. According to the application, the business process link is accurately constructed from static and dynamic double perspectives, so that a user can conveniently carry out business change influence analysis and business change tracking; the service logic description of the service system is generated based on the knowledge base and the prompt project, so that the cost of manually maintaining the service logic in the service process link is reduced.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of business process analysis, and particularly relates to a business process link construction method and device, equipment, a storage medium and a computer program product. BACKGROUND

[0002] A business process link refers to a collection of a series of business activities or steps that are associated with each other and executed in sequence to achieve a specific business goal in an enterprise or organization, and it constitutes a complete business execution path. For example, when receiving an online order initiated by a user, the order can be processed according to the corresponding business process link (for example, it can include creating an order, locking inventory, pushing a payment page to the user, waiting for the user to successfully pay, and the like in sequence). Therefore, how to accurately construct a business process link has become an important research direction in the industry. SUMMARY

[0003] The main purpose of the present application is to provide a business process link construction method, device, equipment, storage medium and computer program product, which aims to solve the technical problem of how to accurately construct a business process link.

[0004] To achieve the above-mentioned purpose, the present application provides a business process link construction method, which comprises the following steps:

[0005] The source code of the business system is parsed, and static data is collected from the parsing result;

[0006] The bytecode enhancement technology is used to collect the dynamic data corresponding to the program code of the business system at runtime;

[0007] The business logic description of the business system is generated based on the knowledge base and the hint project corresponding to the business system;

[0008] The business process link of the business system is constructed according to the static data, the dynamic data and the business logic description.

[0009] In an embodiment, the parsing result includes a first parsing result, a second parsing result and a third parsing result, and the step of parsing the source code of the business system and collecting static data from the parsing result comprises:

[0010] The source code of the business system is parsed to obtain the first parsing result, and the first parsing result at least includes class information, method information, annotation information, field information, inter-method call relationship and inter-class call relationship;

[0011] The annotation information is parsed to obtain the second parsing result, and the second parsing result includes business process starting node information;

[0012] The class information, the method information and the field information are parsed to obtain the third parsing result, and the third parsing result contains URL address information;

[0013] Static data is collected from the first parsing result, the second parsing result and the third parsing result.

[0014] In an embodiment, the step of parsing the source code of the business system to obtain the first parsing result comprises:

[0015] The source code is parsed using a JavaParser tool to obtain the first parsing result, and the first parsing result is in the form of an abstract syntax tree.

[0016] In an embodiment, the step of collecting dynamic data corresponding to the program code of the business system at runtime using bytecode enhancement technology comprises:

[0017] Method-level index collection instructions, code block-level index collection instructions and interception instructions are generated according to user-defined collection logic;

[0018] Dynamic data corresponding to the program code of the business system at runtime is collected using bytecode enhancement technology based on the method-level index collection instructions, the code block-level index collection instructions and the interception instructions.

[0019] In an embodiment, the step of generating a business logic description of the business system based on a knowledge base and a prompt project corresponding to the business system comprises:

[0020] A knowledge base corresponding to the business system is constructed according to requirement documents, design documents and user correction data of a preset large model used to generate business knowledge of the business system.

[0021] A business logic description of the business system is generated based on the knowledge base and a prompt project.

[0022] In an embodiment, the step of constructing a business flow link of the business system according to the static data, the dynamic data and the business logic description comprises:

[0023] A publishing unit in the business system is determined and concatenated based on the static data and the dynamic data to obtain a concatenated link.

[0024] A business flow link of the business system is constructed according to the business logic description and the concatenated link.

[0025] In addition, to achieve the above object, the application further provides a business process link construction device, which comprises:

[0026] a first collection module, configured to parse source code of a business system and collect static data from the parsing result;

[0027] a second collection module, configured to collect dynamic data corresponding to program code of the business system at runtime by using bytecode enhancement technology;

[0028] a description generation module, configured to generate business logic description of the business system based on a knowledge base and a hint project corresponding to the business system;

[0029] a link construction module, configured to construct a business process link of the business system according to the static data, the dynamic data and the business logic description.

[0030] In addition, to achieve the above object, the application further provides a business process link construction device, which comprises a memory, a processor and a business process link construction program stored in the memory and executable on the processor, and the business process link construction program is configured to implement the steps of the business process link construction method.

[0031] In addition, to achieve the above object, the application further provides a storage medium, which is a computer readable storage medium, and the storage medium stores a business process link construction program, and the business process link construction program is executed by a processor to implement the steps of the business process link construction method.

[0032] In addition, to achieve the above object, the application further provides a computer program product, which comprises a business process link construction program, and the business process link construction program is executed by a processor to implement the steps of the business process link construction method.

[0033] The application parses the source code of a business system, and collects static data from the parsing result; collects dynamic data corresponding to the program code of the business system at runtime using bytecode enhancement technology; generates a business logic description of the business system based on a knowledge base and a hint project corresponding to the business system; and constructs a business process link of the business system according to the static data, the dynamic data, and the business logic description. The above method of the application collects static data from the parsing result of the source code of the business system, and collects dynamic data corresponding to the program code of the business system at runtime using bytecode enhancement technology, so as to accurately construct the business process link from the static and dynamic perspectives, facilitating the user to perform business change impact analysis and business change tracking; meanwhile, the application generates a business logic description of the business system based on a knowledge base and a hint project, thereby reducing the cost of manually maintaining the business logic in the business process link. BRIEF DESCRIPTION OF DRAWINGS

[0034] The accompanying drawings, which are incorporated herein and form part of the specification, illustrate embodiments consistent with the present application and, together with the description, further serve to explain the principles of the application.

[0035] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the accompanying drawings needed to be used in the embodiments or prior art description will be briefly introduced. Obviously, for those of ordinary skill in the art, other drawings can also be obtained based on these drawings without creative labor.

[0036] Figure 1 A flowchart of a first embodiment of a business process link construction method of the present application;

[0037] Figure 2 A flowchart of a second embodiment of a business process link construction method of the present application;

[0038] Figure 3 A flowchart of a third embodiment of a business process link construction method of the present application;

[0039] Figure 4 An overall architecture diagram of a business process link construction method of the present application;

[0040] Figure 5 A structural block diagram of a first embodiment of a business process link construction device of the present application;

[0041] Figure 6 A structural diagram of a business process link construction device of a hardware running environment related to the embodiment of the present application.

[0042] The implementation, functional features and advantages of the present application will be further described with reference to the embodiments and the accompanying drawings. DETAILED DESCRIPTION

[0043] It should be understood that the specific embodiments described herein are merely intended to explain the technical solutions of the present application, and are not intended to limit the present application.

[0044] It should be noted that the execution subject of the embodiments of the present application can be a computing service device with data processing, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or an electronic device capable of realizing the above functions, such as the above business process link construction device. The following describes each embodiment below by taking the business process link construction device as an example.

[0045] The embodiments of the present application provide a business process link construction method, which refers to Figure 1 , Figure 1 The flowchart of the first embodiment of the business process link construction method of the present application.

[0046] In the present embodiment, the business process link construction method comprises the following steps:

[0047] Step S10: The source code of the business system is parsed, and static data is collected from the parsing result.

[0048] It should be noted that the above business system can be a distributed system composed of multiple independent publishing units (such as order service, inventory service, payment service) and used for jointly completing a specific business goal (such as e-commerce transaction, payment settlement, etc.). The above source code can be the Java program source code and configuration file of each publishing unit in the business system.

[0049] It should be understood that the above static data can be structured metadata extracted by static parsing (when the business program is not running) of the source code, stored in a static database for business process link construction. The static data can include class node information, method node information, calling relationship between classes, and calling relationship between methods, etc., which are not limited by the present embodiment.

[0050] In a specific implementation, the information such as classes, methods, annotations, and fields contained in the source code can be parsed based on JavaParser (an open source Java code parsing tool). For configuration files, SnakeYaml tool or java.util.Properties class can be selected for parsing according to the file type.

[0051] Step S20: Dynamic data corresponding to the program code of the business system at runtime is collected using bytecode enhancement technology.

[0052] It should be noted that the collection can be performed according to user-defined logic, such as collecting runtime data of a user-specified source code block using bytecode enhancement technology, collecting manually embedded data of the user, and the like. The bytecode can be an intermediate representation form (such as a.class file) after source code compilation, containing class structure, method instructions, operation codes, and the like.

[0053] It should be understood that the dynamic data described above can be structured metadata extracted by dynamically analyzing (at runtime of the business program) the source code and stored in a dynamic database for business process link construction. The dynamic data can include user-specified code block data, embedded data, and the like, which are not limited in the embodiment.

[0054] Step S30: generating a business logic description of the business system based on a knowledge base and a prompt project corresponding to the business system.

[0055] It should be noted that the knowledge base can be a multi-source structured data set generated for the business logic description, used to provide a business context for generating the business logic description, thereby improving the accuracy and semantic consistency of the method-level description. The prompt project can be a structured instruction template for guiding the generation of the business logic description, which controls the generation quality of the business logic description by explicitly defining the task boundary, output format, and context.

[0056] In a specific implementation, the knowledge base can be used to provide a business context for the business logic description, thereby improving the accuracy and semantic consistency of the method-level description; the prompt project can be used to explicitly define the business execution order, input and output format, and the like, thereby controlling the generation quality of the business logic description.

[0057] Step S40: constructing a business process link of the business system according to the static data, the dynamic data, and the business logic description.

[0058] It should be noted that the business process link refers to a collection of a series of business activities or steps that are associated with each other and executed in sequence to achieve a specific business goal in an enterprise or organization, which constitutes a complete business execution path. For example, when a user initiates an order business online, the order business can be processed according to its corresponding business process link (which can include creating an order, locking inventory, pushing a payment page to the user, waiting for the user to successfully pay, and the like in sequence).

[0059] In a specific implementation, the static data can be used to determine the basic code structure, node label, and configuration pre-association of the business process link, the dynamic data can be used to determine the real indicators of the business process link at runtime, and the business logic description can be used to determine the description of each element in the business process link.

[0060] This embodiment parses the source code of the business system and collects static data from the parsing results; uses bytecode enhancement technology to collect dynamic data corresponding to the program code of the business system at runtime; generates a business logic description of the business system based on the knowledge base and prompt engineering corresponding to the business system; and constructs a business process link of the business system based on the static data, the dynamic data, and the business logic description. The above method of this embodiment collects static data from the parsing results of the business system source code and uses bytecode enhancement technology to collect dynamic data corresponding to the program code of the business system at runtime, thereby accurately constructing a business process link from both static and dynamic perspectives, making it convenient for users to perform business change impact analysis and business change tracking; at the same time, this embodiment also generates a business logic description of the business system based on the knowledge base and prompt engineering, thereby reducing the cost of manually maintaining business logic in the business process link.

[0061] refer to Figure 2 , Figure 2 This is a flow chart of the second embodiment of the business process link construction method of this application.

[0062] In a feasible implementation, the parsing result includes a first parsing result, a second parsing result, and a third parsing result, and step S10 may include:

[0063] Step S101: Parse the source code of the business system to obtain the first parsing result, which at least includes class information, method information, annotation information, field information, calling relationships between methods, and calling relationships between classes.

[0064] It should be understood that compared with algorithms such as ASM (Analysis, Synthesis and Modification) based on Java bytecode parsing, source code can retain more business meaning information in the code. Therefore, this embodiment can use JavaParser to parse the source code of the business system.

[0065] In the specific implementation, the source code can be parsed into an abstract syntax tree to obtain class node information, method node information, calling relationships between classes, and calling relationships between methods. At the same time, the Controller node and the remote call URL (Uniform Resource Locator) address can be identified during the parsing process for subsequent release unit concatenation.

[0066] Step S102: Parse the annotation information to obtain the second parsing result, which includes business process start node information.

[0067] It should be noted that the above annotation information can include information such as @RestController, @Controller, @GetMapping, @PostMapping, @PutMapping, and @DeleteMapping on the class and method.

[0068] Step S103: The class information, the method information, and the field information are parsed to obtain the third parsing result, and the third parsing result contains URL address information.

[0069] In a specific implementation, the present embodiment adapts two types of external request sending frameworks, OpenFeign and RestTemplate. For OpenFeign, the third parsing result can be obtained by parsing annotations such as @FeignClient, @GetMapping, @PostMapping, @PutMapping, and @DeleteMapping on the class and method.

[0070] In addition, for RestTemplate, the third parsing result can be obtained based on the following steps. First, when parsing the method called by the method in the class, if RestTemplate related calls are encountered, the method is marked, the request type is determined according to the method name and parameters, and then URL parsing is performed. Second, when parsing, first determine the URL parameter expression type of the called method: if it is a string constant, the current parameter value is the URL address of the RestTemplate call; if it is a simple name variable, the third step of parameter and variable transmission analysis is needed; if it is a binary or ternary operation expression, the fourth step of expression operation analysis is needed; if it is a method call, the fifth step of method call analysis is needed. Third, if the variable comes from the field, the value of the field is used as the URL address; if it comes from the parameter, the method is first marked as to be parsed, and the URL address is obtained by parsing and continuing to parse when the global concatenation is performed later; if it comes from the local variable, the local variable is continued to be judged by the second step. Fourth, first obtain all variable values used in the expression, and then use a tool to calculate the value of the expression as the URL address; if the variable comes from the parameter, the method needs to be set as to be parsed, and the value of the variable is obtained by continuing to parse when the global concatenation is performed later. Fifth, for the method call, only the case of obtaining the value from the Properties configuration attribute class, the URL address is obtained according to the configuration path combined with the configuration file parsing result.

[0071] Step S104: Static data is collected from the first parsing result, the second parsing result, and the third parsing result.

[0072] In a feasible implementation, the step S101 can include:

[0073] Step S1011: parsing the source code using a JavaParser tool to obtain the first parsing result, the first parsing result being in the form of an abstract syntax tree.

[0074] In a specific implementation, the first parsing result can be obtained based on the following steps. First, parse the configuration file of the source code. For a Yaml (a file type designed in a data serialization format) configuration file, use SnakeYaml (an open source library in Java for parsing YAML data) to parse the Yaml configuration file, and after parsing, perform flattening processing on the parsing result to facilitate subsequent value taking. For a Properties configuration file (a file in Java for storing key-value pair configuration information), use the java.util.Properties class (a class in the Java standard library for processing key-value pair configuration files) to parse the Properties configuration file. Second, obtain class-related information, including the fully qualified class name, the inherited class, the implemented interface, and the imported class name. Third, obtain all fields in the class, including the field type, the name, and the field value. For a field whose value is obtained from the configuration, the value of the field needs to be obtained in combination with the configuration file parsing result. Fourth, obtain method information in the class, including the method name, the parameter type, the number of parameters, and the return type. Fifth, obtain all method calls in the class, and determine the class to which the called method belongs. For a method call outside the class, the type of the method call instance object is determined in combination with the field, the parameter, or the local variable, and then the class to which the called method belongs is determined in combination with the class name imported by the current class. The fully qualified class name of a method call inside the class is the fully qualified name of the current class. Sixth, confirm the global method call relationship and prune the method. Global analysis of the above data can obtain the inter-method call relationship and the inter-class call relationship. At the same time, the method in a third-party package that is called is removed, and only the method included in the source code is retained. Finally, the method call relationship between the parent class and the child class and the method call relationship of the implemented interface are processed, thereby obtaining the first parsing result.

[0075] The embodiment parses the source code by using a JavaParser tool to obtain the first parsing result, the first parsing result is in the form of an abstract syntax tree, and the first parsing result at least includes class information, method information, annotation information, field information, inter-method calling relationship and inter-class calling relationship; the annotation information is parsed to obtain the second parsing result, the second parsing result includes business process starting node information; the class information, the method information and the field information are parsed to obtain the third parsing result, the third parsing result includes URL address information; and static data is collected from the first parsing result, the second parsing result and the third parsing result. The above method of the embodiment first parses the source code into an abstract syntax tree to obtain class node information, method node information, inter-class calling relationship and inter-method calling relationship; meanwhile, a Controller node and a remote calling URL address are identified in the parsing process, which are used for subsequent publishing unit concatenation, so that more detailed business meaning information in the code is retained, and the accuracy of the parsing result is improved.

[0076] Reference Figure 3 , Figure 3 The flowchart of a third embodiment of the business process link construction method of the application is shown in FIG. 3.

[0077] In a possible implementation, the step S20 can include:

[0078] Step S201: generating a method-level index collection instruction, a code block-level index collection instruction and an intercepting instruction according to a user-defined collection logic.

[0079] Step S202: collecting dynamic data corresponding to program code of the business system at runtime by using a bytecode enhancement technology based on the method-level index collection instruction, the code block-level index collection instruction and the intercepting instruction.

[0080] It should be understood that the execution process of the above method-level index collection instruction is: using ByteBuddy (a bytecode operation library based on the Java language) to enhance the definition of a Bean (an object instance managed and created by a Spring container) of Spring (a Java application development framework), and then performing a point according to the configuration before and after the method execution. Code way to intercept the method focused on in the Bean of Spring and obtain the method call index data, and finally asynchronously throw Kafka (a high-throughput, distributed message queue system), and perform Flink (a distributed stream data processing framework) aggregation statistics on the thrown data. The execution process of the above code block-level index collection instruction is: according to the fully qualified class name, method name, start line number, and end line number specified by the user, the code block is specified, and ByteBuddy is used to enhance the bytecode of the code block. When the application executes here, it will be intercepted and collected, thereby realizing the point of the code block link information. The execution process of the above interception instruction is: using an interceptor to intercept the client, for example, RestTemplate (a classic client tool class provided by Spring framework for initiating synchronous HTTP requests). If it has been registered to the Spring container, the Bean is obtained and the interceptor is added when the application starts, and the request URL is intercepted and initiated. If it is not registered to the Spring container, a code template is provided, and the user can manually add an interceptor to the client. After executing the above method-level index collection instruction, code block-level index collection instruction and interception instruction, the above dynamic data can be collected from the bytecode.

[0081] In a possible implementation, the step S30 can include:

[0082] Step S301: constructing a knowledge base corresponding to the business system according to a requirement document, a design document of the business system and correction data of a preset large model for generating business knowledge of the business system.

[0083] Step S302: generating a business logic description of the business system based on the knowledge base and a prompt project.

[0084] It can be understood that the embodiment is based on source code to generate business logic description in combination with knowledge base and Prompt (Prompt engineering). The knowledge base is constructed using requirement documents, design documents, and user correction data for preset large model generation description; the Prompt engineering is constructed by means of Prompt base framework, clear task purpose, appropriate sequence, fixed input and output format, and clear boundary processing conditions, and the most relevant 3 pieces of knowledge are carried when asking questions to increase the professionalism of the answers. Specifically, the generation process of the business logic description is as follows: consuming KAFKA data starts to use a preset large model to obtain a method description, uses an embedding model for vectorization processing, finds the most relevant n pieces of knowledge in a vector database, uses a rearrangement model to obtain the most relevant m pieces of knowledge, constructs a prompt, calls a dialogue large model to answer, and ends the answer.

[0085] In a possible implementation, the step S40 can include:

[0086] Step S401: determining and concatenating the publishing units in the business system based on the static data and the dynamic data to obtain a concatenated link.

[0087] It should be understood that the publishing units in the business system can be determined and concatenated to obtain a concatenated link based on the following steps. First, concatenate according to the URL address of remote calling, and preferentially use the dynamically collected URL address. Second, determine whether the URL address is a complete and valid URL address, and if so, proceed to the next step; otherwise, proceed to the fifth step of matching the publishing unit according to the request path. Third, parse the URL address to obtain the domain name, and query the relationship between the domain name and the publishing unit maintained during dynamic data collection, and if the publishing unit is queried, proceed to the next step; otherwise, proceed to the fifth step of matching the publishing unit according to the request path. Fourth, match the corresponding Controller node in the static database according to the queried publishing unit, request path, request type, and path layer number to complete the concatenation of the publishing unit. Fifth, if the URL address is not complete and valid in the second step or no publishing unit information is queried according to the domain name in the third step, then match the publishing unit according to the request path, first obtain all downstream service units of the current publishing unit through the full-link monitoring service, and then match the publishing unit according to the request path. Sixth, match and concatenate according to the request path, request type, and path layer number, and if multiple Controller nodes under the publishing unit are matched, preferentially take the publishing unit corresponding to the downstream service unit obtained through the full-link monitoring service. It should be noted that the URL address, publishing unit, request path, request type, path layer number, Controller node, and other information in the above steps can be obtained from the static data and the dynamic data.

[0088] Step S402: Constructing a business process link of the business system according to the business logic description and the serial link.

[0089] In a specific implementation, the above business logic description can be matched to each element in the serial link, thereby constructing a business process link of the business system.

[0090] This embodiment generates method-level indicator collection instructions, code block-level indicator collection instructions and interception instructions based on user-defined collection logic; based on the method-level indicator collection instructions, the code block-level indicator collection instructions and the interception instructions, bytecode enhancement technology is used to collect the dynamic data corresponding to the program code of the business system at runtime; based on the business system's requirement documents, design documents and user's correction data for the preset large model, a knowledge base corresponding to the business system is constructed, and the preset large model is used to generate the business knowledge of the business system; based on the knowledge base and the prompt project, a business logic description of the business system is generated; based on the static data and the dynamic data, the publishing units in the business system are determined and connected in series to obtain a series link; based on the business logic description and the series link, a business process link of the business system is constructed. The above method of this embodiment combines static data with dynamic data to build a more accurate business process link, thereby assisting users in tracing business logic changes, analyzing the impact of business logic changes, and other tasks; at the same time, this embodiment combines the preset large model when scanning static codes to generate method-level business logic descriptions that are more in line with daily communication; in addition, this embodiment supports manual point-insertion logs to collect code block-level indicators when collecting dynamic data, thereby facilitating users to understand the execution status within the method.

[0091] In particular, see Figure 4 , Figure 4 This is the overall architecture diagram of the business process link construction method of this application, which includes the application layer, service layer, data layer and support layer. Among them, the application layer includes business process link generation, business process link comparison and application risk prevention; the service layer includes user-triggered execution of business process link generation tasks, reading source code in the code repository and parsing it with javaparser, obtaining publishing units and service units, Controller node identification, remote call URL identification, business process node concatenation, large model acquisition of method-level business process description, method time consumption collection, method traffic collection, code block-level dynamic data collection, maintenance of the mapping relationship between domain names and publishing units, dynamic and static combination and publishing unit concatenation; the data layer includes MYSQL, KAFKA and REDIS; the support layer includes code repository and full-link monitoring service.

[0092] Reference Figure 5 , Figure 5A structural block diagram of a first embodiment of a service process link construction device of the present application is shown in the figure.

[0093] As shown in the figure, Figure 5 the service process link construction device comprises:

[0094] A first collection module 501 is configured to parse source code of a service system and collect static data from the parsing result;

[0095] A second collection module 502 is configured to collect dynamic data corresponding to program code of the service system at runtime by using bytecode enhancement technology;

[0096] A description generation module 503 is configured to generate a service logic description of the service system based on a knowledge base and a hint project corresponding to the service system;

[0097] A link construction module 504 is configured to construct a service process link of the service system according to the static data, the dynamic data and the service logic description.

[0098] The first embodiment parses source code of a service system and collects static data from the parsing result; collects dynamic data corresponding to program code of the service system at runtime by using bytecode enhancement technology; generates a service logic description of the service system based on a knowledge base and a hint project corresponding to the service system; and constructs a service process link of the service system according to the static data, the dynamic data and the service logic description. The above-mentioned method of the first embodiment collects static data from the parsing result of the source code of the service system and collects dynamic data corresponding to program code of the service system at runtime by using bytecode enhancement technology, so as to accurately construct a service process link from static and dynamic perspectives, which facilitates users to perform service change impact analysis and service change tracking. Meanwhile, the first embodiment also generates a service logic description of the service system based on a knowledge base and a hint project, thereby reducing the cost of manually maintaining service logic in the service process link.

[0099] Based on the first embodiment of the above-mentioned service process link construction device of the present application, a second embodiment of the service process link construction device of the present application is proposed.

[0100] In the embodiment, the analysis result includes a first analysis result, a second analysis result, and a third analysis result. The first acquisition module 501 is further configured to analyze source code of a business system to obtain the first analysis result, the first analysis result including at least class information, method information, annotation information, field information, inter-method calling relationship, and inter-class calling relationship; analyze the annotation information to obtain the second analysis result, the second analysis result including business process starting node information; analyze the class information, the method information, and the field information to obtain the third analysis result, the third analysis result including URL address information; and acquire static data from the first analysis result, the second analysis result, and the third analysis result.

[0101] Further, the first acquisition module 501 is further configured to analyze the source code using a JavaParser tool to obtain the first analysis result, the first analysis result being in the form of an abstract syntax tree.

[0102] Further, the second acquisition module 502 is further configured to generate method-level index acquisition instructions, code block-level index acquisition instructions, and intercepting instructions according to user-defined acquisition logic; and acquire dynamic data corresponding to program code of the business system at runtime using bytecode enhancement technology based on the method-level index acquisition instructions, the code block-level index acquisition instructions, and the intercepting instructions.

[0103] Further, the description generation module 503 is further configured to construct a knowledge base corresponding to the business system according to requirement documents, design documents, and user correction data of a preset large model, the preset large model being used to generate business knowledge of the business system; and generate a business logic description of the business system based on the knowledge base and a prompt project.

[0104] Further, the link construction module 504 is further configured to determine and concatenate publishing units in the business system based on the static data and the dynamic data to obtain concatenated links; and construct a business process link of the business system according to the business logic description and the concatenated links.

[0105] Other embodiments or specific implementation manners of the business process link construction apparatus of the present application can refer to the above-mentioned method embodiments, which will not be described herein again.

[0106] The application provides a business process link construction device, the business process link construction device comprising: at least one processor; and a memory connected in communication with the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the business process link construction method in the above embodiment one.

[0107] Reference will now be made to Figure 6 which shows a structural diagram of a business process link construction device suitable for implementing embodiments of the application. The business process link construction device in the embodiments of the application can include, but is not limited to, mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle-mounted terminals (for example, vehicle-mounted navigation terminals), and the like, and fixed terminals such as digital TVs, desktop computers, and the like. Figure 6 The illustrated business process link construction device is merely an example and should not impose any limitation on the functions and use range of the embodiments of the application.

[0108] As Figure 6 shown, the business process link construction device can include a processing apparatus 1001 (for example, a central processor, a graphics processor, or the like) that can perform various appropriate actions and processes according to programs stored in a read-only memory 1002 or loaded from a storage apparatus 1003 into a random access memory 1004. In the random access memory 1004, various programs and data required for operation of the business process link construction device are also stored. The processing apparatus 1001, the read-only memory 1002, and the random access memory 1004 are connected to each other through a bus 1005. An input / output interface 1006 is also connected to the bus. Generally, the following systems can be connected to the input / output interface 1006: input apparatuses 1007 including, for example, a touch screen, a touch pad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, and the like; output apparatuses 1008 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, and the like; the storage apparatus 1003 including, for example, a magnetic tape, a hard disk, and the like; and a communication apparatus 1009. The communication apparatus 1009 can allow the business process link construction device to perform wireless or wired communication with other devices to exchange data. Although the business process link construction device having various systems is shown in the figure, it should be understood that all the illustrated systems are not required to be implemented or provided. More or fewer systems can be alternatively implemented or provided.

[0109] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product comprising a computer program carried on a computer readable medium, the computer program containing program code for executing the method shown in the flowchart. In such embodiments, the computer program can be downloaded and installed from a network through a communication device, or installed from the storage device 1003, or installed from the read-only memory 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiments disclosed in the present application are executed.

[0110] The business process link construction device provided by the present application adopts the business process link construction method in the above-mentioned embodiments, and can solve the technical problem of how to accurately construct the business process link. Compared with the prior art, the business process link construction device provided by the present application has the same beneficial effects as the business process link construction method provided by the above-mentioned embodiments, and other technical features in the business process link construction device are the same as the features disclosed in the previous embodiment method, which will not be repeated here.

[0111] It should be understood that parts of the present application can be realized by hardware, software, firmware or a combination thereof. In the description of the above-mentioned embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0112] The above is merely specific embodiments of the present application, but the protection scope of the present application is not limited thereto, and any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in the present application, which should be covered in the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

[0113] The present application provides a computer readable storage medium having stored thereon computer readable program instructions (i.e. computer program) for executing the business process link construction method in the above-mentioned embodiments.

[0114] The computer readable storage medium provided in the present application may, for example, be a U disk, but is not limited to an electric, magnetic, optical, electromagnetic, infrared, or semiconductor system or device, or any combination thereof. More specific examples of the computer readable storage medium can include, but are not limited to, an electric connection with one or more conductive wires, a portable computer disk, a hard disk, a random access memory (RAM), a read only memory (ROM), an erasable programmable read only memory (EPROM or flash memory), an optical fiber, a portable compact disk read only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present embodiment, the computer readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system or device. The program code contained on the computer readable storage medium can be transmitted by any suitable medium, including but not limited to an electric wire, an optical cable, an RF (Radio Frequency), and the like, or any suitable combination thereof.

[0115] The above computer readable storage medium can be included in the business process link construction device, or can exist separately without being assembled into the business process link construction device.

[0116] The above computer readable storage medium carries one or more programs, which, when executed by the business process link construction device, enable the business process link construction device to write computer program code in one or more programming languages or combinations thereof for performing the operations of the present application. The programming languages include object-oriented programming languages such as Java, Smalltalk, C++, and conventional procedural programming languages such as "C" language or similar programming languages. The program code can be executed entirely on the user computer, partially on the user computer, as a separate software package, partially on the user computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer can be connected to the user computer by any kind of network, such as a LAN (Local Area Network) or a WAN (Wide Area Network), or connected to an external computer (such as an Internet service provider through the Internet).

[0117] The flowcharts and block diagrams in the drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowcharts or block diagrams can represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical functions. It should also be noted that in some alternative implementations, the functions noted in the blocks can occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently or the blocks can sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and / or flowchart illustrations, and combinations thereof, can be implemented by a dedicated hardware-based system that performs the specified functions or operations, or combinations of hardware and software.

[0118] The modules involved in the embodiments of the present application can be implemented in the form of software or in the form of hardware. In some cases, the name of the module does not constitute a limitation on the module itself.

[0119] The readable storage medium provided by the present application is a computer readable storage medium, which stores computer readable program instructions (i.e. computer program) for executing the business process link construction method described above, and can solve the technical problem of how to accurately construct a business process link. Compared with the prior art, the computer readable storage medium provided by the present application has the same beneficial effects as the business process link construction method provided by the above-mentioned embodiments, which will not be repeated here.

[0120] The present application also provides a computer program product comprising a computer program, which, when executed by a processor, implements the steps of the business process link construction method as described above.

[0121] The computer program product provided by the present application can solve the technical problem of business process link construction. Compared with the prior art, the computer program product provided by the present application has the same beneficial effects as the business process link construction method provided by the above-mentioned embodiments, which will not be repeated here.

[0122] The above only describes some embodiments of the present application, and does not limit the protection scope of the present application, and any equivalent structural transformation made by using the content of the present application specification and drawings, or direct / indirect application in other related technical fields is included in the protection scope of the present application.

Claims

1. A method for constructing a business process link, characterized in that: The method comprises the following steps: Parse the source code of the business system and collect static data from the parsing results; Using bytecode enhancement technology to collect dynamic data corresponding to the program code of the business system during runtime; Generate a business logic description of the business system based on the knowledge base and prompt engineering corresponding to the business system; A business process link of the business system is constructed according to the static data, the dynamic data and the business logic description.

2. The business process link construction method according to claim 1, characterized in that: The parsing results include a first parsing result, a second parsing result, and a third parsing result. The step of parsing the source code of the business system and collecting static data from the parsing results includes: Parsing the source code of the business system to obtain the first parsing result, wherein the first parsing result includes at least class information, method information, annotation information, field information, inter-method call relationships, and inter-class call relationships; Parsing the annotation information to obtain a second parsing result, wherein the second parsing result includes business process start node information; Parsing the class information, the method information, and the field information to obtain the third parsing result, wherein the third parsing result includes URL address information; Static data is collected from the first parsing result, the second parsing result, and the third parsing result.

3. The method for constructing a business process link according to claim 2, wherein: The step of parsing the source code of the business system to obtain the first parsing result includes: The source code is parsed using a JavaParser tool to obtain the first parsing result, which is expressed in the form of an abstract syntax tree.

4. The method for constructing a business process link according to claim 1, wherein: The step of using bytecode enhancement technology to collect dynamic data corresponding to the program code of the business system during runtime includes: Generate method-level indicator collection instructions, code block-level indicator collection instructions and interception instructions based on user-defined collection logic; Based on the method-level indicator collection instruction, the code block-level indicator collection instruction and the interception instruction, bytecode enhancement technology is used to collect dynamic data corresponding to the program code of the business system during runtime.

5. The method for constructing a business process link according to claim 1, wherein: The step of generating a business logic description of the business system based on the knowledge base and prompt engineering corresponding to the business system includes: Building a knowledge base corresponding to the business system based on the business system's requirements document, design document, and user-modified data for a preset large model, wherein the preset large model is used to generate business knowledge for the business system; A business logic description of the business system is generated based on the knowledge base and the prompt project.

6. The method for constructing a business process link according to claim 1, wherein: The step of constructing the business process link of the business system according to the static data, the dynamic data and the business logic description includes: Determine and connect the publishing units in the business system based on the static data and the dynamic data to obtain a series link; A business process link of the business system is constructed according to the business logic description and the serial link.

7. A business process link construction device, characterized in that: The business process link construction device includes: The first acquisition module is used to parse the source code of the business system and collect static data from the parsing results; A second collection module is used to use bytecode enhancement technology to collect dynamic data corresponding to the program code of the business system during runtime; A description generation module, configured to generate a business logic description of the business system based on the knowledge base and prompt engineering corresponding to the business system; A link construction module is used to construct a business process link of the business system according to the static data, the dynamic data and the business logic description.

8. A business process link construction device, characterized in that: The device includes: a memory, a processor, and a business process link construction program stored in the memory and executable on the processor, wherein the business process link construction program is configured to implement the steps of the business process link construction method according to any one of claims 1 to 6.

9. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a business process link construction program is stored on the storage medium. When the business process link construction program is executed by a processor, the steps of the business process link construction method according to any one of claims 1 to 6 are implemented.

10. A computer program product, characterized in that The computer program product includes a business process link construction program, which implements the steps of the business process link construction method according to any one of claims 1 to 6 when executed by a processor.

Images