Business scene arrangement platform construction method and device based on standard component, equipment and storage medium

Abstract

The embodiment of the invention provides a business scene arrangement platform construction method based on a standard component, and the method comprises the steps: combining a user demand in a component demand document with a standard component, and outputting a decoupled function point and corresponding input and output information; taking the decoupled function points as input, performing retrieval in a standard component library, and if the function points are not retrieved, generating component codes based on the decoupled function points; comprehensively testing the standard component based on the component code; if the test is passed, outputting a package component; inputting and outputting parameters into the packaging component, carrying out vectorization processing, outputting a packaged standardized component, and storing the packaged standardized component into a standard component library; on the basis of the business scene data, performing scene construction on the packaged standardized component by writing a specific function module, and outputting the standard component after scene construction; and testing, optimizing and packaging the standard component after the scene is established to obtain an application program corresponding to the business scene.

Description

Technical Field

[0001] The present invention relates to the technical field of software development, and in particular to, but is not limited to, a method, device, equipment and storage medium for constructing a business scenario orchestration platform based on standard components. Background Art

[0002] Traditional application development requires developers to write a large amount of customized code for each specific business scenario. Developers need to deeply understand business requirements, design systems, and write business logic code. Therefore, the code writing process has problems such as long development cycle, high cost, difficult maintenance, and difficulty in quickly responding to business changes.

[0003] In recent years, low-code development platforms have gradually emerged, lowering the threshold for application development by providing a visual development environment and a pre-set component library. Users can quickly build applications by dragging components and configuring parameters. The application of large models usually relies on fixed architectures and processes, lacking flexibility and configurability. Users need to use specific application programming interfaces (APIs) or frameworks, and cannot dynamically adjust models and functions according to specific business needs. This limitation makes it complicated to integrate multiple open source large models, knowledge bases, and vectorized models, and building specific business scenarios (such as retrieval augmented generation (RAG) applications) is time-consuming and inefficient. For example, in a low-code development system and method in the prior art, a visual project management module, a business editing module, and a page design module are used, allowing users to quickly build applications by dragging components and configuring parameters. Most of the existing low-code development platforms focus on page design and simple business logic processing, and lack support for complex business scenario orchestration and process management.

[0004] The shortcomings of existing low-code development platforms are: (1) Insufficient support for complex business scenarios. Although low-code development platforms provide a visual development environment and a pre-set component library, most platforms still focus on page design and simple business logic processing. There is insufficient support for complex business scenarios involving complex business logic, multi-system integration, advanced data processing, etc.; (2) Poor scalability: When facing new business scenarios, existing technologies often need to modify or expand the original system, resulting in poor system scalability; (3) The lack of intuitive operation methods makes it difficult for non-technical personnel to participate in the construction and application of models; (4) The process of integrating different open source models and knowledge bases is complicated, which leads to a longer development cycle. Summary of the invention

[0005] In order to solve the above-mentioned technical problems existing in the prior art, the present invention provides a method, device, equipment and storage medium for constructing a business scenario orchestration platform based on standard components.

[0006] The technical method of the embodiment of the present invention is implemented as follows:

[0007] In a first aspect, an embodiment of the present invention provides a method for constructing a business scenario orchestration platform based on standard components, the method comprising:

[0008] Obtain the user's component requirement document and historical operation data; use a preset deep decoupler to combine the user requirements in the component requirement document with the standard components in the pre-built standard component library, and output the decoupled function points and corresponding input and output information;

[0009] The decoupled function point is used as input, and a preset retriever is used to search in the standard component library. If an available component matching the decoupled function point is retrieved, the available component is output; if not, the decoupled function point is input into a preset code generator to generate a component code;

[0010] Based on the component code, call the test case generator to perform a comprehensive test on the standard component; if a bug occurs during the test, fix the bug; if the test passes, output the encapsulated component;

[0011] Inputting output parameters into the encapsulable component and performing vectorization processing, outputting encapsulated standardized components and storing them in the standard component library;

[0012] Based on the business scenario data, by writing specific functional modules, the packaged standardized components are constructed in the scenario, and the standard components after the constructed scenario are output;

[0013] Taking the standard components after the scene is built and the business scenario data as input, the standard components after the scene is built are deeply tested according to a preset efficient initial debugging model, and the tested standard components are output;

[0014] Inputting the tested standard components and the historical operation data into a preset hybrid recommendation algorithm, optimizing the tested standard components, and outputting the optimized standard components;

[0015] Taking the optimized standard components as input, API interface training, interface packaging and tool integration are carried out in sequence to output an application corresponding to the business scenario.

[0016] In a second aspect, an embodiment of the present invention provides a device for constructing a business scenario orchestration platform based on standard components, the device comprising:

[0017] An acquisition module is used to obtain a user's component requirement document and historical operation data; using a preset deep decoupler, the user requirements in the component requirement document are combined with standard components in a pre-built standard component library, and the decoupled function points and corresponding input and output information are output;

[0018] A retrieval module, used to take the decoupled function point as input, search the standard component library through a preset searcher, and if an available component matching the decoupled function point is found, output the available component; if not found, input the decoupled function point into a preset code generator to generate component code;

[0019] A calling module is used to call the test case generator based on the component code to perform a comprehensive test on the standard component; if a bug occurs during the test, the bug is fixed; if the test passes, the encapsulated component is output;

[0020] A vectorization module, used for inputting and outputting parameters into the encapsulable component and performing vectorization processing, outputting the encapsulated standardized component and storing it in the standard component library;

[0021] A building module is used to build a scenario for the packaged standardized components based on business scenario data by writing specific functional modules, and output the standard components after the scenario is built;

[0022] A testing module is used to take the standard components after the scene is built and the business scenario data as input, perform in-depth testing on the standard components after the scene is built according to a preset efficient initial debugging model, and output the tested standard components;

[0023] An optimization module, used for inputting the tested standard components and the historical operation data into a preset hybrid recommendation algorithm, optimizing the tested standard components, and outputting the optimized standard components;

[0024] The encapsulation module is used to take the optimized standard components as input, perform API interface training, interface encapsulation and tool integration in sequence, and output an application corresponding to the business scenario.

[0025] In some embodiments, the pre-built standard component library is constructed in the following manner: based on the type of functional application required by the user, the required components of each large model application are defined, and the interfaces and properties of the required components are unified to obtain standard components; the standard components are stored in the initial standard component library, and a unique identifier and metadata description are assigned to each of the standard components; the metadata description includes the component name, functional description and dependencies; each of the standard components is customized based on the stored custom writing module, and integrated into the initial standard component library to obtain the pre-built standard component library.

[0026] In some embodiments, the business scenario data includes business type data, scenario scale data, and processing requirement data; the historical operation data includes drag component behavior data, property configuration behavior data, and rule definition data.

[0027] In a third aspect, an embodiment of the present invention provides an electronic device, comprising: a memory for storing executable instructions; and a processor for implementing the above-mentioned method for constructing a business scenario orchestration platform based on standard components when executing the executable instructions stored in the memory.

[0028] In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium storing executable instructions for causing a processor to execute the executable instructions to implement the above-mentioned method for constructing a business scenario orchestration platform based on standard components.

[0029] The method for constructing a business scenario orchestration platform based on standard components provided in an embodiment of the present invention constructs a full-link closed loop of demand-component-test-feedback. On the one hand, the business orchestration efficiency is improved, that is, the conversion cycle from demand to executable system is shortened from 7 people / day to less than 2 hours; on the other hand, the component reuse rate is improved, that is, through the intelligent retrieval and generation mechanism, the component reuse rate reaches 78% (the industry average is 35%); thirdly, the system self-optimization capability is achieved, that is, 12-15 new components are automatically deposited every month, and the test case coverage rate reaches 97.3%. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] Figure 1 It is a flowchart of a method for constructing a business scenario orchestration platform based on standard components provided by an embodiment of the present invention;

[0031] Figure 2 It is a schematic diagram of the composition structure of a device for constructing a business scenario orchestration platform based on standard components provided by an embodiment of the present invention;

[0032] Figure 3 It is a schematic diagram of the composition structure of a device for building a business scenario orchestration platform based on standard components provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0033] In order to make the purpose, technical solutions and advantages of the present invention clearer, the present invention will be further described in detail below in conjunction with the accompanying drawings. The described embodiments should not be regarded as limiting the present invention. All other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of the present invention.

[0034] In the following description, reference is made to "some embodiments", which describe a subset of all possible embodiments, but it is understood that "some embodiments" may be the same subset or different subsets of all possible embodiments, and may be combined with each other without conflict. Unless otherwise defined, all technical and scientific terms used in the embodiments of the present invention have the same meaning as those commonly understood by those skilled in the art to which the embodiments of the present invention pertain. The terms used in the embodiments of the present invention are only for the purpose of describing the embodiments of the present invention and are not intended to limit the present invention.

[0035] Although there are some similar platforms and tools on the market, most of them still rely on fixed architectures and lack the ability of personalized customization and deep integration. Therefore, although some alternatives can be found, the present invention has obvious advantages in terms of flexibility, user-friendliness and integration capabilities. For example, the components in the standard component library can be implemented using different technology stacks to adapt to different business needs and technical environments.

[0036] The following describes an exemplary application of a business scenario orchestration platform construction device based on standard components in an embodiment of the present invention. The business scenario orchestration platform construction device based on standard components provided in an embodiment of the present invention can be implemented as a terminal or a server. In one implementation, the business scenario orchestration platform construction device based on standard components provided in an embodiment of the present invention can be implemented as various types of terminals such as laptops, tablet computers, desktop computers, mobile devices, etc.; in another implementation, the business scenario orchestration platform construction device based on standard components provided in an embodiment of the present invention can also be implemented as a server, wherein the server can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content distribution networks (CDN, Content Delivery Network), and big data and artificial intelligence platforms. The terminal and the server can be directly or indirectly connected by wired or wireless communication, which is not limited in the embodiment of the present invention. Below, an exemplary application of a business scenario orchestration platform construction device based on standard components when implemented as a server will be described.

[0037] See also Figure 1 The embodiment of the present invention provides a method for constructing a business scenario orchestration platform based on standard components. Figure 1 is a flow chart of a method for constructing a business scenario orchestration platform based on standard components provided by an embodiment of the present invention, which will be combined with Figure 1 The steps shown are explained.

[0038] Step S110, obtaining the user's component requirement document and historical operation data; using a preset deep decoupler, combining the user requirements in the component requirement document with the standard components in a pre-built standard component library, and outputting the decoupled function points and corresponding input and output information.

[0039] In the invention, the pre-qualified deep decoupler refers to the requirement d proposed by the user, which should be implemented by p standard components C and their connection method F. The deep decoupler is a nonlinear mapping function:

[0040] ;

[0041] in, Represents the decoupled function points and their input and output interfaces. The decoupling goal is to minimize the matching error between the function points and components. Through the user requirement document D, D contains a large number of triplets in the knowledge graph (i.e., two components and the connection method). Compared with traditional retrieval and vectorized retrieval methods, the knowledge graph combines micro-decoupling (neighbor entity representation) and macro-decoupling (semantic independence). Especially in the process of code flow compilation, this advantage is magnified, and the comprehensive measurement accuracy is improved by 20-30%. Through the knowledge graph, n similar requirement documents are retrieved, and the requirement d is converted into a standard requirement document type using a large model. The output result is calculated for similarity with the annotated component library to obtain the combination with the smallest matching error between the function point and the component, and output it.

[0042] In some embodiments, the component requirement document describes in detail the user's expected functions, performance, interfaces, etc. of a specific component. This document is the basic input for subsequent operations and clarifies the user's specific needs.

[0043] In some embodiments, the historical operation data records various operation information related to the component in the past, such as operation steps, operation time, operation results, etc. These data can be used for subsequent operations such as optimization of the component, and the usage and performance of the component can be better understood by analyzing the historical data.

[0044] In some embodiments, the preset deep decoupler is a pre-set tool or algorithm, which is used to decompose and parse the user requirements in the component requirement document and combine them with the standard components in the pre-built standard component library, thereby outputting the decoupled function points and corresponding input and output information. It realizes the refinement of user requirements and the association of standardized components.

[0045] In some embodiments, the standard component library is a collection of various standard components that have specific functions and specifications and can be retrieved and used as basic modules. The standard component library is an important source of components in the entire process.

[0046] Step S120, taking the decoupled function point as input, searching in the standard component library through a preset retriever, if an available component matching the decoupled function point is retrieved, outputting the available component; if not retrieved, inputting the decoupled function point into a preset code generator to generate component code.

[0047] In some embodiments, function points are specific functional units obtained by decoupling user requirements through a deep decoupler. Each function point represents a specific function of a component and is the basis for subsequent retrieval and code generation.

[0048] In some embodiments, the input and output information refers to information corresponding to a function point, describing the input data required by the function point during operation and the output data generated. Such information is crucial for determining the behavior of the function point and the interaction with other components.

[0049] In some embodiments, the preset retriever is a preset retrieval tool or algorithm for searching for available components matching the decoupled function points in the standard component library. It searches according to certain matching rules to determine whether there is a suitable component that can be used directly.

[0050] In some embodiments, available components refer to components retrieved from a standard component library and matching the decoupled functional points. These components can be directly used in subsequent processes without regenerating code.

[0051] In some embodiments, the preset code generator is a preset tool or algorithm that can generate corresponding component codes according to the requirements of the function point when no available component matching the function point is retrieved in the standard component library.

[0052] Step S130, based on the component code, calling the test case generator to perform a comprehensive test on the standard component; if a bug occurs during the test, the bug is fixed; if the test passes, the encapsulated component is output.

[0053] In the present invention, based on the generated component code, a test case generator is called to generate comprehensive test cases to test the standard components. If a bug is found during the test, that is, there is a problem with the component, the bug is fixed to ensure the quality of the component. If the test passes, it means that there is no obvious problem with the component, and the encapsulated component is output to prepare for the next encapsulation process.

[0054] Step S140, inputting output parameters into the encapsulable component and performing vectorization processing, outputting the encapsulated standardized component and storing it in the standard component library.

[0055] In the present invention, output parameters are input into the encapsulated component, and these parameters are vectorized to convert the component into an encapsulated standardized component. The encapsulated standardized component is then stored in a standard component library so that the component can be reused in other projects later.

[0056] Step S150, based on the business scenario data, by writing specific function modules, the scenario is constructed for the packaged standardized components, and the standard components after the scenario is constructed are output.

[0057] In the present invention, based on the business scenario data, by writing a specific functional module and combining it with the encapsulated standardized components, the scenario is built. This step enables the components to adapt to specific business scenarios, meet actual business needs, and output the standard components after the scenario is built.

[0058] Step S160, taking the standard components after the scene is built and the business scenario data as input, performing in-depth testing on the standard components after the scene is built according to a preset efficient initial debugging model, and outputting the tested standard components.

[0059] In some embodiments, the business scenario data describes the relevant data of the business scenario in which the component is actually applied, such as business processes, business rules, data formats, etc. The scenario is constructed based on the business scenario data to make the component more in line with actual business needs.

[0060] In the present invention, the standard components after the scene is built and the business scenario data are used as input, and the standard components are deeply tested according to the preset efficient initial debugging model. Through this test, possible problems of the components in the actual business scenario can be found, and debugging can be performed, and finally the tested standard components are output.

[0061] Step S170, inputting the tested standard components and the historical operation data into a preset hybrid recommendation algorithm, optimizing the tested standard components, and outputting the optimized standard components.

[0062] In some embodiments, the preset hybrid recommendation algorithm is a pre-set algorithm that combines multiple recommendation strategies, takes tested standard components and historical operation data as input, and optimizes the standard components to improve the performance and applicability of the components.

[0063] In the present invention, the tested standard components and historical operation data are input into a preset hybrid recommendation algorithm, and the algorithm optimizes the tested standard components according to these data. By analyzing the historical operation data and the test results of the components, the algorithm can improve the performance, function and other aspects of the components and output the optimized standard components.

[0064] Step S180, using the optimized standard components as input, sequentially performing API interface training, interface encapsulation and tool integration, and outputting an application corresponding to the business scenario.

[0065] In some embodiments, API interface training refers to training the application programming interface (API) of the optimized standard component so that it can better interact and communicate with other systems or components. Through training, the API interface can process requests and return responses more accurately.

[0066] In the present invention, the optimized standard components are used as input, and API interface training is performed in sequence to enable the interface to better interact with other systems; interface encapsulation is performed to make the interface have a unified specification and format; tool integration is performed to integrate the components with related tools. After these steps, the application corresponding to the business scenario is finally output, realizing the transformation from user needs to actual applications.

[0067] The embodiment of the present invention provides a method for constructing a business scenario orchestration platform based on standard components. The present invention constructs a standard component library and builds a business scenario orchestration platform. First, standardized components and parameter configurations improve the development efficiency of complex application scenarios; second, users can quickly adjust component combinations to adapt to different business needs and enhance the flexibility of business scenarios; third, intuitive drag-and-drop operations and Python customization functions reduce the difficulty of participation for non-technical personnel; fourth, by integrating intelligent auxiliary tools, the intelligence level of the system is improved and the difficulty of construction is reduced.

[0068] In some embodiments, the pre-built standard component library in step S120 is built in the following manner:

[0069] Based on the type of functional application required by the user, define the required components of each large model application, and unify the interfaces and properties of the required components to obtain standard components; store the standard components in the initial standard component library, and assign a unique identifier and metadata description to each of the standard components; the metadata description includes the component name, functional description and dependencies; customize each of the standard components based on the stored custom writing module, and integrate it into the initial standard component library to obtain the pre-built standard component library.

[0070] In some embodiments, the business scenario data includes business type data, scenario scale data, and processing requirement data; the historical operation data includes drag component behavior data, property configuration behavior data, and rule definition data.

[0071] The following describes an exemplary application of an embodiment of the present invention in a practical application scenario.

[0072] The present invention proposes a business scenario flexible orchestration platform based on standard components and its construction method, aiming to solve the deficiencies of existing technologies in developing large model applications in terms of flexibility, scalability and intelligence. The main process steps of the present invention include:

[0073] Step 1: Build a standard component library

[0074] Step 1.1, component definition: define the overall process, model language, knowledge base, vectorization, prompt words, retriever, data input, format conversion, information extraction, model loading, output and other components by type, unify the interface and properties to facilitate user understanding and use.

[0075] Step 1.2, component packaging and storage: Standard components are stored in the standard component library, and each component is assigned a unique identifier and metadata description. The metadata description includes the component name, function description, and dependencies.

[0076] Step 1.3 allows users to customize components according to their personal needs. Users can use Python to write specific functional modules and integrate them into standardized components to achieve personalized system expansion.

[0077] Step 2: Build a business scenario orchestration platform

[0078] Step 2.1, set up the user interface layer and business logic layer in the overall architecture of the business scenario orchestration platform. The user interface provides a component selection bar and a business process board; the business logic layer automatically builds the scenario business process based on the business process board.

[0079] In step 2.2, users can combine components to generate a complete business process by simply dragging and dropping. This interface should support the connection between different components and the logical setting of the process.

[0080] Step 2.3, implement the configuration function of standard components at the user interface layer. For the configuration of internal parameters, users can simply set parameters through the configuration interface on the graphical interface to effectively bind major open source models, knowledge bases and vectorized models. The configuration process will include selecting models, setting input and output parameters, and defining the order of model calls.

[0081] Step 2.4 introduces the debugging function, which enables users to conduct field tests after building business scenarios. Users can run the set scenarios directly on the platform, view the output results in real time, and adjust parameters to optimize the results.

[0082] In step 2.5, the business scenario constructed by the user can be saved as a template for subsequent use.

[0083] Step 3: Integrate smart assistant tools

[0084] Step 3.1, data collection and processing: Collect historical user operation data, including user behavior records such as dragging components, configuring properties, defining rules, etc. on the platform. At the same time, collect relevant data of business scenarios, such as business type, data scale, and processing requirements.

[0085] Step 3.2, algorithm training integration: The method is to use a hybrid recommendation algorithm that combines collaborative filtering and deep learning. The algorithm is trained on the data set constructed in step 3.1. After the model training is completed, the API interface is designed, and docker is used to complete the interface encapsulation and tool integration.

[0086] Figure 2 is a schematic diagram of the composition structure of a device for constructing a business scenario orchestration platform based on standard components provided by an embodiment of the present invention, such as Figure 2As shown, a device 200 for constructing a business scenario orchestration platform based on standard components includes: an acquisition module 201, which is used to obtain a user's component requirement document and historical operation data; using a preset deep decoupler, combining the user requirements in the component requirement document with the standard components in a pre-built standard component library, and outputting decoupled function points and corresponding input and output information; a retrieval module 202, which is used to use the decoupled function points as input, and search the standard component library through a preset retriever, and if an available component matching the decoupled function point is retrieved, the available component is output; if not, the decoupled function point is input into a preset code generator to generate component code; a calling module 203, which is used to call a test case generator based on the component code to perform a comprehensive test on the standard component; if a bug occurs in the test, the bug is fixed; if the test passes, the encapsulated component is output; a vectorization module 204, which is used to The input and output parameters of the encapsulated component are vectorized, and the encapsulated standardized component is output and stored in the standard component library; the construction module 205 is used to build the scenario for the encapsulated standardized component based on the business scenario data by writing a specific function module, and output the standard component after the scenario is built; the testing module 206 is used to use the standard component after the scenario is built and the business scenario data as input, and according to the preset efficient initial debugging model, perform in-depth testing on the standard component after the scenario is built, and output the tested standard component; the optimization module 207 is used to input the tested standard component and the historical operation data into a preset hybrid recommendation algorithm, optimize the tested standard component, and output the optimized standard component; the encapsulation module 208 is used to use the optimized standard component as input, perform API interface training, interface encapsulation and tool integration in sequence, and output an application corresponding to the business scenario.

[0087] In some embodiments, the pre-built standard component library is constructed in the following manner: based on the type of functional application required by the user, the required components of each large model application are defined, and the interfaces and properties of the required components are unified to obtain standard components; the standard components are stored in the initial standard component library, and a unique identifier and metadata description are assigned to each of the standard components; the metadata description includes the component name, functional description and dependencies; each of the standard components is customized based on the stored custom writing module, and integrated into the initial standard component library to obtain the pre-built standard component library.

[0088] In some embodiments, the business scenario data includes business type data, scenario scale data, and processing requirement data; the historical operation data includes drag component behavior data, property configuration behavior data, and rule definition data.

[0089] It should be noted that the description of the device of the embodiment of the present invention is similar to the description of the above method embodiment, and has similar beneficial effects as the same method embodiment, so it will not be repeated. For technical details not disclosed in the embodiment of the device, please refer to the description of the method embodiment of the present invention for understanding.

[0090] It should be noted that in the embodiment of the present invention, if the above-mentioned method for constructing a business scenario orchestration platform based on standard components is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present invention, or the part that contributes to the relevant technology, can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for enabling a terminal to execute all or part of the methods described in each embodiment of the present invention. The aforementioned storage medium includes: various media that can store program codes, such as a U disk, a mobile hard disk, a read-only memory (ROM, Read Only Memory), a magnetic disk or an optical disk. In this way, the embodiment of the present invention is not limited to any specific combination of hardware and software.

[0091] Correspondingly, an embodiment of the present invention provides an electronic device, Figure 3 FIG. 1 is a schematic diagram of the structure of an electronic device provided by an embodiment of the present invention. Figure 3 As shown, the electronic device 300 at least includes: a processor 301 and a storage medium 302 configured to store executable instructions, wherein the processor 301 generally controls the overall operation of the electronic device 300. The storage medium 302 is configured to store instructions and applications executable by the processor 301, and can also cache data to be processed or processed by the processor 301 and each module in the electronic device 300, which can be implemented by flash memory (FLASH) or random access memory (RAM, Random Access Memory).

[0092] An embodiment of the present invention provides a storage medium storing executable instructions, wherein the executable instructions are stored. When the executable instructions are executed by a processor, the processor will be caused to execute the method provided by the embodiment of the present invention, for example, Figure 1 The method shown.

[0093] In some embodiments, the storage medium can be a computer-readable storage medium, for example, a ferroelectric random access memory (FRAM), a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a flash memory, a magnetic surface memory, an optical disk, or a compact disk read-only memory (CD-ROM); it can also be various devices including one or any combination of the above memories.

[0094] In some embodiments, executable instructions may be in the form of a program, software, software module, script or code, written in any form of programming language (including compiled or interpreted languages, or declarative or procedural languages), and may be deployed in any form, including as a stand-alone program or as a module, component, subroutine or other unit suitable for use in a computing environment.

[0095] As an example, executable instructions may, but need not correspond to, a file in a file system, may be stored as part of a file storing other programs or data, such as one or more scripts in a Hyper Text Markup Language (HTML) document, in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files storing one or more modules, subroutines, or code portions). As an example, executable instructions may be deployed to be executed on one electronic device, or on multiple electronic devices located at one location, or on multiple electronic devices distributed at multiple locations and interconnected by a communication network.

[0096] The above description is only an embodiment of the present invention and is not intended to limit the protection scope of the present invention. Any modification, equivalent replacement and improvement made within the spirit and scope of the present invention are included in the protection scope of the present invention.

[0097] It should be understood that "one embodiment" or "an embodiment" mentioned throughout the specification means that specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the present invention. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner. It should be understood that in various embodiments of the present invention, the size of the serial number of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present invention. The serial numbers of the above-mentioned embodiments of the present invention are only for description and do not represent the advantages and disadvantages of the embodiments.

[0098] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method or device. In the absence of further restrictions, an element defined by the statement "comprises one..." does not exclude the presence of other identical elements in the process, method, article or device including the element. In several embodiments provided by the present invention, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as: multiple units or components can be combined, or can be integrated into another system, or some features can be ignored, or not executed.

[0099] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present invention, which should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims

1. A method for constructing a business scenario orchestration platform based on standard components, characterized in that: The method comprises: Obtain the user's component requirement document and historical operation data; use a preset deep decoupler to combine the user requirements in the component requirement document with the standard components in the pre-built standard component library, and output the decoupled function points and corresponding input and output information; The decoupled function point is used as input, and a preset retriever is used to search in the standard component library. If an available component matching the decoupled function point is retrieved, the available component is output; if not, the decoupled function point is input into a preset code generator to generate a component code; Based on the component code, call the test case generator to perform a comprehensive test on the standard component; if a bug occurs during the test, fix the bug; if the test passes, output the encapsulated component; Inputting output parameters into the encapsulable component and performing vectorization processing, outputting encapsulated standardized components and storing them in the standard component library; Based on the business scenario data, by writing specific functional modules, the packaged standardized components are constructed in the scenario, and the standard components after the constructed scenario are output; Taking the standard components after the scene is built and the business scenario data as input, the standard components after the scene is built are deeply tested according to a preset efficient initial debugging model, and the tested standard components are output; Inputting the tested standard components and the historical operation data into a preset hybrid recommendation algorithm, optimizing the tested standard components, and outputting the optimized standard components; Taking the optimized standard components as input, API interface training, interface packaging and tool integration are carried out in sequence to output an application corresponding to the business scenario.

2. The method according to claim 1, characterized in that The pre-built standard component library is constructed in the following way: Based on the type of functional application programs required by users, the required components of each large model application are defined, and the interfaces and properties of the required components are unified to obtain standard components; The standard components are stored in an initial standard component library, and a unique identifier and a metadata description are assigned to each standard component; the metadata description includes a component name, a functional description, and a dependency relationship; Each of the standard components is customized based on the stored custom writing module and integrated into the initial standard component library to obtain the pre-built standard component library.

3. The method according to claim 1, characterized in that The business scenario data includes business type data, scenario scale data and processing requirement data; The historical operation data includes drag component behavior data, property configuration behavior data and rule definition data.

4. A device for constructing a business scenario orchestration platform based on standard components, characterized in that: The device comprises: An acquisition module is used to obtain a user's component requirement document and historical operation data; using a preset deep decoupler, the user requirements in the component requirement document are combined with standard components in a pre-built standard component library, and the decoupled function points and corresponding input and output information are output; A retrieval module, used to take the decoupled function point as input, search the standard component library through a preset searcher, and if an available component matching the decoupled function point is found, output the available component; if not found, input the decoupled function point into a preset code generator to generate component code; A calling module is used to call the test case generator based on the component code to perform a comprehensive test on the standard component; if a bug occurs during the test, the bug is fixed; if the test passes, the encapsulated component is output; A vectorization module, used for inputting and outputting parameters into the encapsulable component and performing vectorization processing, outputting the encapsulated standardized component and storing it in the standard component library; A building module is used to build a scenario for the packaged standardized components based on business scenario data by writing specific functional modules, and output the standard components after the scenario is built; A testing module is used to take the standard components after the scene is built and the business scenario data as input, perform in-depth testing on the standard components after the scene is built according to a preset efficient initial debugging model, and output the tested standard components; An optimization module, used for inputting the tested standard components and the historical operation data into a preset hybrid recommendation algorithm, optimizing the tested standard components, and outputting the optimized standard components; The encapsulation module is used to take the optimized standard components as input, perform API interface training, interface encapsulation and tool integration in sequence, and output an application corresponding to the business scenario.

5. An electronic device, characterized in that: include: A memory for storing executable instructions; The processor is used to implement the method for constructing a business scenario orchestration platform based on standard components as described in any one of claims 1 to 3 when executing the executable instructions stored in the memory.

6. A computer-readable storage medium, characterized in that: Executable instructions are stored, which are used to cause the processor to execute the executable instructions to implement the method for constructing a business scenario orchestration platform based on standard components as described in any one of claims 1 to 3.

Images