Component assembling system and method, electronic device, storage medium and program product

Abstract

The invention relates to the technical field of component assembling, and discloses a component assembling system and method, electronic equipment, a storage medium and a program product, and the component assembling system comprises a component market, a visual assembling designer and an application assembling model; the component market is used for storing a plurality of first target components; the visual assembly designer is used for acquiring demand information input by a user and analyzing the demand information to obtain a demand model; the application assembly model is used for matching the demand model with a plurality of first target components in the component market to obtain a plurality of second target components which are successfully matched, and sending the plurality of second target components to a developer for auditing; and the application assembly model is further used for assembling the multiple second target components passing the audit of the developer and sending the assembly result to the developer for audit, the matched components are analyzed and selected according to the user requirements, component assembly is carried out, and the flexibility of component assembly is improved.

Description

Technical Field

[0001] This invention relates to the field of component assembly technology, and more specifically to component assembly systems, methods, electronic devices, storage media, and program products. Background Technology

[0002] With the development of computer technology, the demand for enterprise-level software development is increasing. Enterprise-level software development has a long cycle, taking months or even years from business requirements analysis to function implementation. Customization costs are high, as personalized enterprise needs require additional development, further increasing costs. User participation is low, as developers cannot directly participate in system design and must communicate indirectly through the IT (Information Technology) department, which can easily lead to requirement discrepancies. Maintenance is complex, functional modules are highly coupled, and updates or adjustments require redevelopment, resulting in poor flexibility and making it difficult for component functions to quickly adapt to actual business needs.

[0003] While low-code / no-code platforms have emerged in related technologies, their core logic is deeply dependent on the platform, making them tied to vendors. Application customization and scalability are limited, initial development costs are low but long-term costs are high, and the integration of AI (Artificial Intelligence) and data intelligence capabilities is insufficient, making it difficult to meet the complex and ever-changing business innovation needs. Summary of the Invention

[0004] This invention provides a component assembly system, method, electronic device, storage medium, and program product to address the problem that low-code / no-code platforms in related technologies are unable to meet the complex and ever-changing business innovation needs.

[0005] In a first aspect, the present invention provides a component assembly system, comprising: a component marketplace, a visual assembly designer, and an application assembly model; the component marketplace is used to store multiple first target components; the first target components are components with a unified component interface specification developed by developers using a preset component development tool; the visual assembly designer is used to acquire user-input requirement information, analyze the requirement information, and obtain a requirement model; the requirement model is used to represent multiple tasks corresponding to the requirement information and the execution order of the multiple tasks; the application assembly model is used to match the requirement model with multiple first target components in the component marketplace to obtain multiple successfully matched second target components, and send the multiple second target components to developers for review; the application assembly model is also used to assemble the multiple second target components approved by the developers, and send the assembly result to the developers for review.

[0006] The component assembly system of this invention includes: a component marketplace, a visual assembly designer, and an application assembly model. The component marketplace stores multiple first target components. These first target components are components with a unified component interface specification developed by developers using pre-defined component development tools, avoiding incompatibility issues between component interfaces from different developers. No additional adaptation adjustments are needed during subsequent assembly. All components are stored in the component marketplace, allowing for rapid matching of the component corresponding to the required information during subsequent component matching and invocation. The visual assembly designer of this invention acquires user-inputted requirement information, analyzes the requirement information, and obtains a requirement model representing multiple tasks corresponding to the requirement information and the execution order of these tasks. This transforms user requirements into structured task logic, avoiding misunderstandings between user requirements and development goals. This invention utilizes an assembly model to match a requirement model with multiple first target components in the component market, resulting in multiple successfully matched second target components. These second target components are then sent to developers for review. The assembly model also assembles these approved second target components and sends the assembly results back to the developers for further review. This invention automatically matches the requirement model with components in the component market, replacing the manual process of screening components one by one, significantly reducing the time and manpower costs of component selection. The review of the matched second target components prevents component matching errors. This invention automates component assembly, shortening the development cycle from user requirements to finished component. The review of the final assembly result, through two review stages, reduces the probability of incorrect component selection and assembly logic errors, ensuring the reliability of the final assembly result. Compared with related technologies, this invention does not require platform binding, reducing the cost of component assembly and improving the flexibility of component assembly.

[0007] In one optional implementation, the visual assembly designer includes an intent recognition module, an action acquisition module, and a requirement model construction module; the intent recognition module is used to recognize intents based on requirement information to obtain intent description text; the action acquisition module is used to extract multiple tasks corresponding to the requirement information from the intent description text; the requirement model construction module is used to perform dependency analysis based on the intent description text to obtain the execution order of multiple tasks, and generate a requirement model based on the multiple tasks and the execution order.

[0008] In one alternative implementation, the application assembly model includes a component matching module; the component matching module is used to determine a target matching score based on the task type similarity, keyword vector similarity, field matching degree and semantic matching degree between each task and each first target component, and to determine multiple second target components based on the target matching score.

[0009] In one optional implementation, the application assembly model further includes a business blueprint generation module and a component assembly module; the business blueprint generation module is used to determine multiple execution nodes according to the execution order of multiple tasks, and generate a business process blueprint based on the multiple execution nodes; the component assembly module is used to assemble multiple second target components approved by developers according to the business process blueprint to obtain the assembly result.

[0010] In one optional implementation, the application assembly model further includes: an assembly result testing module and a component operation control module; the assembly result testing module is used to test multiple second target components in the assembly result according to the test set, and generate a test report based on the test results; the component operation control module is used to deploy multiple second target components in the assembly result to a preset environment after the test is passed, so as to control the operation of multiple second target components in the assembly result.

[0011] In one optional implementation, the system further includes an integration adapter and a metadata repository; the integration adapter is used to interface with external devices to obtain data used by the multiple second target components in the assembly result after deploying them to a preset environment; the metadata repository is used to store data during the component assembly process.

[0012] Secondly, the present invention provides a component assembly method, comprising: storing multiple first target components; the first target components are components with a unified component interface specification developed by developers using a preset component development tool; acquiring user-input requirement information, analyzing the requirement information to obtain a requirement model; the requirement model is used to characterize multiple tasks corresponding to the requirement information and the execution order of the multiple tasks; matching the requirement model with multiple first target components in a component marketplace to obtain multiple successfully matched second target components, and sending the multiple second target components to developers for review; assembling the multiple second target components approved by the developers, and sending the assembly result to the developers for review.

[0013] Thirdly, the present invention provides an electronic device comprising: a memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the computer instructions to perform the component assembly method of the second aspect described above.

[0014] Fourthly, the present invention provides a computer-readable storage medium storing computer instructions for causing a computer to perform the component assembly method of the second aspect described above.

[0015] Fifthly, the present invention provides a computer program product, including computer instructions for causing a computer to execute the component assembly method described in the second aspect. Attached Figure Description

[0016] To more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0017] Figure 1 This is a schematic diagram of an application scenario according to an embodiment of the present invention; Figure 2 This is a schematic diagram of a first structure of a component assembly system according to an embodiment of the present invention; Figure 3 This is a schematic diagram of a second structure of a component assembly system according to an embodiment of the present invention; Figure 4 This is a schematic diagram of the first process of a component assembly method according to an embodiment of the present invention; Figure 5 This is a schematic diagram of a second process for a component assembly method according to an embodiment of the present invention; Figure 6 This is a schematic diagram of the hardware structure of an electronic device according to an embodiment of the present invention. Detailed Implementation

[0018] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0019] It is understood that before using the technical solutions disclosed in the various embodiments of the present invention, users should be informed of the types, scope of use, and usage scenarios of the personal information involved in the present invention and their authorization should be obtained in accordance with relevant laws and regulations through appropriate means.

[0020] The terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this invention, "a plurality of" means two or more, unless otherwise explicitly specified.

[0021] As an optional application scenario of this invention, such as Figure 1 As shown, application 101 is installed in terminal device 110, and user 130 can interact with application 101 through terminal device 110 and / or access device of terminal device 110.

[0022] For example, application 101 can be any application that provides question-and-answer related services. For instance, application 101 could be a question-and-answer interactive application, such as a text-to-text application, an image-to-text application, etc. Figure 1 In the application scenario shown, if application 101 is active, the terminal device 110 can display the interface 102 of application 101. The interface 102 may include various pages that application 101 can provide, such as interactive pages, settings pages, query pages, etc.

[0023] In some embodiments, terminal device 110 is communicatively connected to server 120 to provide services to application 101. Terminal device 110 may be a mobile terminal, fixed terminal, or portable terminal, including but not limited to mobile phones, desktop computers, laptop computers, multimedia tablets, e-book devices, gaming devices, or any combination thereof, including accessories and peripherals of these devices or any combination thereof. In some embodiments, terminal device 110 may also support any type of interface, and server 120 may be various types of computing systems or servers capable of providing computing power, including but not limited to mainframes, edge computing nodes, and computing devices in cloud environments.

[0024] It should be noted that, Figure 1 This is merely an example of an application scenario and does not limit the scope of protection of this invention.

[0025] The embodiments of the present invention will now be described with reference to the accompanying drawings. It should be understood that the pages shown in the drawings are merely examples, and various page designs are possible in practice. The various graphic elements on the page may have different arrangements and different visual representations; one or more elements may be omitted or replaced, and one or more other elements may also be present, without any limitation in the embodiments of the present invention. Furthermore, the embodiments described below primarily pertain to terminal device 110. It should be understood that the actions described relative to terminal device 110 can be performed by application 101 on terminal device 110, or can be performed by application 101 in conjunction with its server (e.g., server 120).

[0026] This invention provides a component assembly system that selects matching components through user needs analysis and assembles them, thereby improving the flexibility of component assembly.

[0027] According to an embodiment of the present invention, a component assembly system embodiment is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0028] This embodiment provides a component assembly system. Figure 2 This is a first structural diagram of a component assembly system according to an embodiment of the present invention, such as... Figure 2 As shown, the system includes: a component marketplace 201, a visual assembly designer 202, and an application assembly model 203.

[0029] Component Marketplace 201 is used to store multiple first target components; the first target components are components with a unified component interface specification developed by developers using preset component development tools.

[0030] Among them, Component Marketplace 201 is a web portal for all developers. This portal provides fine-grained classification, tagging, and version management of components, and displays all approved first-target components. Developers can browse, search, and view the details, user reviews, and version history of first-target components here.

[0031] In some optional implementations, the component marketplace 201 stores multiple first target components that have been uploaded and packaged by developers, and also stores metadata for each first target component, including name, version, detailed description, function category, tags, screenshots, user documentation, etc.

[0032] In some optional implementations, Component Marketplace 201 integrates static code security scanning tools, dependency vulnerability databases, and API (Application Programming Interface) specification verifiers to perform automated quality and security screening on uploaded first target components.

[0033] In some optional implementations, the Component Marketplace 201 provides developers with an interface for functional testing, UI / UX (User Interface / User Experience) review, and documentation integrity checks to ensure that components meet production environment standards.

[0034] In some optional implementations, the default component development tool is an integrated development environment or scaffolding tool for developers to use to quickly create components that conform to platform specifications. The default component development tool provides a unified component interface specification and clearly defines the component's input parameters, output data, configurable properties, triggerable events, and other contracts with structured data (such as JSON Schema, a metadata specification based on JSON format).

[0035] In some optional implementations, the default component development tool includes local debugging, simulation testing, and one-click packaging functions, which can package the developed components into a standard zip format (containing code, metadata description files, icons, version information, etc.).

[0036] The visual assembly designer 202 is used to obtain the user-input requirement information, analyze the requirement information, and obtain the requirement model; the requirement model is used to represent the multiple tasks corresponding to the requirement information and the execution order of the multiple tasks.

[0037] The visual assembly designer 202 is used to visualize information during the component assembly process. The visual assembly designer 202 is equipped with an AI interactive interface, which provides a natural language input box. Users can describe their needs here to obtain the needs information and trigger AI recommendations and automatic assembly.

[0038] In some alternative implementations, the visual assembly designer 202 is used to display a plurality of first target components and a plurality of successfully matched second target components.

[0039] In some optional implementations, the visual assembly designer 202 includes a logic canvas for displaying an initial blueprint generated by AI, allowing users to fine-tune and refine the blueprint by dragging and drawing connecting lines. It also includes a property configuration panel for parametrically configuring selected components and process nodes between components; all configurations can be completed using non-code methods such as forms and dropdown selections.

[0040] The application assembly model 203 is used to match the requirement model with multiple first target components in the component market to obtain multiple successfully matched second target components, and then send the multiple second target components to the developers for review.

[0041] The application assembly model 203 is also used to assemble multiple second target components that have been approved by the developers, and to send the assembly results to the developers for review.

[0042] The application assembly model 203 includes a description file that describes information about multiple second target components. It precisely defines the second target components used, the connection relationships between the second target components, the data mapping, and the configuration parameters of each second target component. The runtime engine of the application assembly model 203 is responsible for loading, parsing, and executing the application assembly model. The engine parses the model, instantiates each component in sequence, passes data between components according to the connection relationships, and executes the logic encapsulated inside the components, thereby driving the operation of the entire assembled application.

[0043] In some alternative implementations, the final assembly result can be an application model, an application system, etc.

[0044] The component assembly system provided in this embodiment includes: a component marketplace, a visual assembly designer, and an application assembly model. The component marketplace stores multiple first target components. These first target components are components with a unified component interface specification developed by developers using preset component development tools, avoiding incompatibility issues between component interfaces from different developers. No additional adaptation adjustments are needed during subsequent assembly. All components are stored in the component marketplace, allowing for rapid matching of the component corresponding to the requirement information during subsequent component matching and invocation. The visual assembly designer of this embodiment acquires user-input requirement information, analyzes the requirement information, and obtains a requirement model representing multiple tasks corresponding to the requirement information and the execution order of these tasks. This transforms user requirements into structured task logic, avoiding misunderstandings between user requirements and development goals. The application assembly model in this invention is used to match a requirement model with multiple first target components in the component market to obtain multiple successfully matched second target components. These second target components are then sent to developers for review. The application assembly model is also used to assemble these approved second target components and send the assembly results back to the developers for review. This invention automatically matches the requirement model with components in the component market, replacing the manual process of screening components one by one, significantly reducing the time and manpower costs of component screening. The review of the matched second target components prevents component matching errors. This invention automates component assembly, shortening the development cycle from user requirements to finished component. The review of the final assembly result, through two review stages, reduces the probability of incorrect component selection and assembly logic errors, ensuring the reliability of the final assembly result. Compared with related technologies, this invention does not require platform binding, reducing the cost of component assembly and improving the flexibility of component assembly.

[0045] This embodiment provides a component assembly system. Figure 3 This is a second structural diagram of a component assembly system according to an embodiment of the present invention, such as... Figure 3As shown, the system includes: a component marketplace 301, a visual assembly designer 302, and an application assembly model 303. The component marketplace 301 stores multiple first target components; these first target components are components with a unified component interface specification developed by developers using preset component development tools. The visual assembly designer 302 acquires user-input requirement information, analyzes the requirement information, and obtains a requirement model; the requirement model represents multiple tasks corresponding to the requirement information and the execution order of these tasks. The application assembly model 303 matches the requirement model with multiple first target components in the component marketplace to obtain multiple successfully matched second target components, and sends these second target components to developers for review. The application assembly model 303 also assembles the multiple second target components approved by developers and sends the assembly result to developers for review.

[0046] In some optional implementations, the visual assembly designer 302 includes an intent recognition module 3021, an action acquisition module 3022, and a requirement model construction module 3023; the intent recognition module 3021 is used to recognize intents based on requirement information to obtain intent description text; the action acquisition module 3022 is used to extract multiple tasks corresponding to the requirement information from the intent description text; the requirement model construction module 3023 is used to perform dependency analysis based on the intent description text to obtain the execution order of multiple tasks, and generate a requirement model based on the multiple tasks and the execution order.

[0047] The demand information consists of natural language demand text input by the user through the AI ​​interactive interface, and the input text is stored in a buffer as a string.

[0048] In this embodiment of the invention, before performing intent recognition on the demand information, the demand information used for input is subjected to text normalization processing, such as removing stop words, standardizing formats (e.g., time, amount, unit), and normalizing synonyms (e.g., unifying approval, review, and approval into approval).

[0049] In this embodiment of the invention, the intent recognition module 3021 is used to perform intent recognition on the demand information through an intent classification model to obtain intent description text. For example, after performing intent recognition on the demand information, the obtained intent description text is: "Build an approval process system".

[0050] In this embodiment of the invention, the action acquisition module 3022 calls the named entity recognition model to extract multiple tasks from the intent description text, including business entities and action sets. For example, the extracted multiple business entities include leave application, applicant, approver, etc.; the action set includes actions such as submission, approval, and recording.

[0051] In some optional implementations, the requirement model building module 3023 is used to decompose multiple tasks to obtain multiple task nodes, infer the execution order of multiple tasks based on semantic order and syntactic dependency analysis of the intent description text, and build a requirement model based on the multiple task nodes and the execution order of multiple tasks.

[0052] For example, after task decomposition, multiple task nodes are obtained, including: form submission, supervisor approval, data writing, etc. Task dependency reasoning determines the execution order of multiple tasks: submission, approval, writing to the database, etc.

[0053] In some optional implementations, the application assembly model 303 includes a component matching module 3031; the component matching module 3031 is used to determine a target matching score based on the task type similarity, keyword vector similarity, field matching degree and semantic matching degree between each task and each first target component, and to determine multiple second target components based on the target matching score.

[0054] Specifically, the target matching score is determined by obtaining the task type similarity, keyword vector similarity, field matching degree, and semantic matching degree between each task and each first target component. For example, the formula is:

[0055] in, Score the target match degree. Task type similarity between each task and each first target component As the weight for task type similarity, Keyword vector similarity between each task and each first target component The similarity weights of keyword vectors The field matching degree between each task and each first target component. As the field matching degree weight, The semantic matching degree between each task and each first target component. This represents the semantic matching weight.

[0056] In some optional implementations, determining multiple second target components based on the target matching score includes: sorting the target matching scores, and selecting a preset number of components as second target components from the target matching score sequence, wherein the preset number can be determined according to the actual number of tasks.

[0057] In some optional implementations, the application assembly model 303 further includes a business blueprint generation module 3032 and a component assembly module 3033; the business blueprint generation module 3032 is used to determine multiple execution nodes according to the execution order of multiple tasks, and generate a business process blueprint based on the multiple execution nodes; the component assembly module 3033 is used to assemble multiple second target components approved by developers according to the business process blueprint to obtain the assembly result.

[0058] The business blueprint generation module 3032 is used to construct a component execution directed graph based on the execution order of multiple tasks obtained by dependency reasoning, perform semantic matching on the fields between multiple second target components, generate multiple execution nodes, and thus obtain a business process blueprint. For example, when the semantic matching degree between multiple second target components is greater than 0.8, they are considered to be able to connect. The multiple execution nodes include: condition judgment nodes, branch nodes, exception capture nodes, and loop nodes, etc.

[0059] In some optional implementations, the component assembly module 3033 is used to convert the business process blueprint into an executable application model to obtain an assembly result. Specifically, it is converted according to the component list, connection relationship, data mapping, condition configuration and exception handling description, etc., to obtain the assembly result. The assembly result is in JSON or YAML format and can be directly executed at runtime.

[0060] In some optional implementations, the application assembly model 303 further includes: an assembly result testing module 3034 and a component operation control module 3035; the assembly result testing module 3034 is used to test multiple second target components in the assembly result according to the test set, and generate a test report based on the test results; the component operation control module 3035 is used to deploy multiple second target components in the assembly result to a preset environment after the test is passed, so as to control the operation of multiple second target components in the assembly result.

[0061] The test suite includes normal process tests, abnormal process tests, field boundary tests, and performance tests. Each test is executed and the results are recorded. The pass rate is obtained by dividing the number of successful test cases by the total number of test cases. A test report is generated based on the pass rate, failed test cases, alarm items, performance metrics, and component coverage.

[0062] In some optional implementations, the component operation control module 3035 is used to select environments such as Kubernetes and Serverless based on the dependency relationships obtained by dependency inference. In the preset environment, it performs image download, dependency injection, service startup, health check, registers the entry point to the gateway, and automatically generates a Uniform Resource Locator (URL).

[0063] In some alternative implementations, the component operation control module 3035 is also used to enable monitoring services and collect logs, throughput, latency, and error events.

[0064] In some optional implementations, the system also includes an integration adapter 304 and a metadata repository 305; the integration adapter 304 is used to interface with external devices to obtain data used by the multiple second target components in the assembly result after deploying them to a preset environment; the metadata repository 305 is used to store data during the component assembly process.

[0065] Among them, the integration adapter 304 is used to interface with common external systems (such as MySQL, ERP, SAP, etc.). It provides a declarative configuration interface, and users only need to fill in the address of the target system, authentication key and other necessary information to complete the integration configuration without writing integration code.

[0066] In some alternative implementations, the metadata repository 305 is used to store and manage the metadata of all components (such as interface definitions, configuration item descriptions), user-assembled application models, and business data generated by the application.

[0067] In this embodiment of the invention, standardized development tools ensure the quality and security of component development. The AI-assisted engine directly transforms natural language requirements into executable application blueprints, enabling users to quickly start and complete application construction. AI recommendations avoid the tedious process of manually searching for components, and automatic orchestration provides best practice references, which not only speeds up assembly but also reduces logical errors caused by misunderstandings, improving assembly efficiency and quality. The platform can continuously learn new business scenarios and component characteristics through AI, enabling the recommendation and automatic orchestration capabilities to continuously evolve and enhancing the system's adaptability.

[0068] This embodiment provides a component assembly method that can be used in computer devices. Figure 4 This is a first flowchart of a component assembly method according to an embodiment of the present invention, such as... Figure 4 As shown, the process includes the following steps: Input business requirements; parse the requirement logic to generate a requirement model; query the component library and match it according to the requirement model; assemble and debug the successfully matched components to generate a business process; perform automated testing on the assembly results, output a test report, and deploy the assembly results online.

[0069] This embodiment provides a component assembly method that can be used in computer devices. Figure 5 This is a second flowchart of a component assembly method according to an embodiment of the present invention, such as... Figure 5 As shown, the process includes the following steps: Step S501: Store multiple first target components; the first target components are components with a unified component interface specification developed by developers using preset component development tools.

[0070] Step S502: Obtain the user-inputted requirement information, analyze the requirement information, and obtain the requirement model; the requirement model is used to represent the multiple tasks corresponding to the requirement information and the execution order of the multiple tasks.

[0071] Step S503: Match the requirement model with multiple first target components in the component market to obtain multiple successfully matched second target components, and send the multiple second target components to the developers for review.

[0072] Step S504: Assemble the multiple second target components that have been approved by the developers, and send the assembly results to the developers for review.

[0073] In some optional implementations, user-inputted requirement information is obtained, and the requirement information is analyzed to obtain a requirement model, including: performing intent recognition based on the requirement information to obtain intent description text; extracting multiple tasks corresponding to the requirement information from the intent description text; performing dependency analysis based on the intent description text to obtain the execution order of the multiple tasks; and generating a requirement model based on the multiple tasks and the execution order.

[0074] In some optional implementations, the demand model is matched with multiple first target components in the component market to obtain multiple successfully matched second target components, including: determining the target matching score based on the task type similarity, keyword vector similarity, field matching degree and semantic matching degree between each task and each first target component, and determining multiple second target components based on the target matching score.

[0075] In some optional implementations, assembling multiple second target components approved by developers includes: determining multiple execution nodes according to the execution order of multiple tasks; generating a business process blueprint based on the multiple execution nodes; and assembling the multiple second target components approved by developers based on the business process blueprint to obtain an assembly result.

[0076] In some optional implementations, the component assembly method further includes: testing multiple second target components in the assembly result according to a test set, and generating a test report based on the test results.

[0077] In some optional implementations, the component assembly method further includes: after the test is passed, deploying multiple second target components from the assembly result to a preset environment to control the operation of the multiple second target components from the assembly result.

[0078] In some optional implementations, the component assembly method further includes: after deploying multiple second target components from the assembly result to a preset environment, interfacing with an external device to obtain data used by the multiple second target components from the assembly result.

[0079] In some alternative implementations, the component assembly method further includes storing data from the component assembly process.

[0080] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention.

[0081] The following is a detailed reference. Figure 6 This diagram illustrates a suitable structural design for implementing an electronic device according to embodiments of the present invention. The electronic device may include a processor (e.g., a central processing unit, graphics processor, etc.) 601, which can perform various appropriate actions and processes based on a program stored in read-only memory (ROM) 602 or a program loaded from memory 608 into random access memory (RAM) 603. RAM 603 also stores various programs and data required for the operation of the electronic device. The processor 601, ROM 602, and RAM 603 are interconnected via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0082] Typically, the following devices can be connected to I / O interface 605: input devices 606 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 607 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; memory devices 608 including, for example, magnetic tapes, hard disks, etc.; and communication devices 609. Communication device 609 allows electronic devices to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 6 Electronic devices with various devices are shown, but it should be understood that it is not required to implement or have all of the devices shown, and more or fewer devices may be implemented or have instead.

[0083] In particular, according to embodiments of the present invention, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of the present invention include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device 609, or installed from a memory 608, or installed from a ROM 602. When the computer program is executed by the processor 601, it performs the functions defined in the component assembly method of the embodiments of the present invention.

[0084] Figure 6 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments of the present invention.

[0085] This invention also provides a computer-readable storage medium. The methods described above according to embodiments of the invention can be implemented in hardware or firmware, or implemented as computer code that can be recorded on a storage medium, or implemented as computer code downloaded via a network and originally stored on a remote storage medium or a non-transitory machine-readable storage medium and then stored on a local storage medium. Thus, the methods described herein can be processed by software stored on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. The storage medium can be a magnetic disk, optical disk, read-only memory, random access memory, flash memory, hard disk, or solid-state drive, etc.; further, the storage medium can also include combinations of the above types of memory. It is understood that a computer, processor, microprocessor controller, or programmable hardware includes storage components capable of storing or receiving software or computer code. When the software or computer code is accessed and executed by the computer, processor, or hardware, the component assembly method shown in the above embodiments is implemented.

[0086] A portion of this invention can be applied as a computer program product, such as computer program instructions, which, when executed by a computer, can invoke or provide the methods and / or technical solutions according to the invention through the operation of the computer. Those skilled in the art will understand that the forms in which computer program instructions exist in a computer-readable medium include, but are not limited to, source files, executable files, installation package files, etc. Correspondingly, the ways in which computer program instructions are executed by a computer include, but are not limited to: the computer directly executing the instructions, or the computer compiling the instructions and then executing the corresponding compiled program, or the computer reading and executing the instructions, or the computer reading and installing the instructions and then executing the corresponding installed program. Here, the computer-readable medium can be any available computer-readable storage medium or communication medium accessible to a computer.

[0087] Although embodiments of the invention have been described in conjunction with the accompanying drawings, those skilled in the art can make various modifications and variations without departing from the spirit and scope of the invention, and such modifications and variations all fall within the scope defined by the appended claims.

Claims

1. An assembly assembly system, characterized by, The system comprises a component market, a visual assembly designer, and an application assembly model. The component market is configured to store a plurality of first target components, wherein the first target components are components developed by a developer using a preset component development tool and have a unified component interface specification. The visual assembly designer is configured to obtain requirement information input by a user, analyze the requirement information, and obtain a requirement model, wherein the requirement model is used to represent a plurality of tasks corresponding to the requirement information and an execution order of the plurality of tasks. The application assembly model is configured to match the requirement model with the plurality of first target components in the component market, obtain a plurality of second target components that pass the matching, and send the plurality of second target components to the developer for review. The application assembly model is further configured to assemble the plurality of second target components that pass the review by the developer, and send an assembly result to the developer for review.

2. The system of claim 1, wherein, The visual assembly designer comprises an intention recognition module, an action acquisition module, and a requirement model construction module. The intention recognition module is configured to perform intention recognition according to the requirement information, and obtain an intention description text. The action acquisition module is configured to extract a plurality of tasks corresponding to the requirement information from the intention description text. The requirement model construction module is configured to perform dependency analysis according to the intention description text, obtain an execution order of the plurality of tasks, and generate the requirement model according to the plurality of tasks and the execution order.

3. The system of claim 1 or 2, wherein, The application assembly model comprises a component matching module. The component matching module is configured to determine a target matching degree score according to a task type similarity, a keyword vector similarity, a field matching degree, and a semantic matching degree between each task and each first target component, and determine the plurality of second target components according to the target matching degree score.

4. The system of claim 2, wherein, The application assembly model further comprises a business blueprint generation module and a component assembly module. The business blueprint generation module is configured to determine a plurality of execution nodes according to the execution order of the plurality of tasks, and generate a business process blueprint according to the plurality of execution nodes. The component assembly module is configured to assemble the plurality of second target components that pass the review by the developer according to the business process blueprint, and obtain the assembly result.

5. The system of claim 1 or 2, wherein, The application assembly model further comprises an assembly result test module and a component running control module. The assembly result test module is configured to test the plurality of second target components in the assembly result according to a test set, and generate a test report according to a test result. The component running control module is configured to deploy the plurality of second target components in the assembly result to a preset environment to control running of the plurality of second target components in the assembly result after the test passes.

6. The system of claim 5, wherein, The system further comprises an integration adapter and a metadata warehouse. The integrated adapter is configured to be connected with an external device after the plurality of second target components in the assembly result are deployed to a preset environment, and to obtain data used by the plurality of second target components in the assembly result. The metadata warehouse is configured to store data in a component assembly process.

7. A method of assembling a component, characterized by, The method comprises: storing a plurality of first target components; the first target components are components developed by a developer using a preset component development tool and having a unified component interface specification; obtaining user input requirement information, analyzing the requirement information, and obtaining a requirement model; the requirement model is used to represent a plurality of tasks corresponding to the requirement information and an execution order of the plurality of tasks; matching the requirement model with the plurality of first target components in a component market, obtaining a plurality of second target components that are matched successfully, and sending the plurality of second target components to the developer for review; assembling the plurality of second target components that pass the review of the developer, and sending an assembly result to the developer for review.

8. An electronic device, comprising: comprise: a memory and a processor, which are in communication connection with each other, the memory stores computer instructions, and the processor executes the computer instructions to perform the component assembly method of claim 7.

9. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer instructions, and the computer instructions are used to make a computer execute the component assembly method of claim 7.

10. A computer program product, characterised in that, The computer instructions are used to make a computer execute the component assembly method of claim 7.

Images