Component introduction method, device and equipment

Abstract

The embodiment of the invention discloses a component introduction method, device and equipment. The method comprises the steps of receiving an introduction request instruction which is triggered by a user and aims at a target component; in response to the introduction request instruction, obtaining a type and an application scene of the target component contained in the introduction request instruction; according to the type and the application scene of the target component, determining a plurality of target evaluation tools corresponding to the target component, and a calling sequence and a dependency relationship among the plurality of target evaluation tools; according to the calling sequence and the dependency relationship, utilizing the plurality of target evaluation tools to perform evaluation processing on the target component to obtain an evaluation result for the target component; and determining whether to introduce the target component according to the evaluation result.

Description

Technical Field

[0001] This document relates to the field of computer technology, and in particular to a component introduction method, device and equipment. Background Art

[0002] Open source technology, with its open, shared and free characteristics, has boosted the construction of digital software. Driven by the pressure of self-control, quality improvement and efficiency increase, the software industry is increasingly choosing open source technology products as part of its "distributed" architecture, and open source technology has become an important technical support for software development and construction.

[0003] However, while digital software construction has achieved positive results such as technological innovation and business empowerment, it also faces many security risks, so it is necessary to conduct multi-faceted evaluation and processing of the introduced open source components.

[0004] At present, when evaluating open source components, developers are more likely to evaluate them based on component introduction materials, other user experiences, and local environment testing and verification. This process is not only time-consuming and labor-intensive, but also the selection experience is heavily dependent on personal experience, which is difficult to replicate and accumulate on a large scale, resulting in poor component evaluation efficiency and accuracy. To this end, the embodiments of this specification provide a technical solution for improving the evaluation efficiency and accuracy of open source components to improve the effect of component introduction. Summary of the invention

[0005] The purpose of the embodiments of this specification is to provide a technical solution for improving the evaluation efficiency and accuracy of open source components to improve the effect of component introduction.

[0006] In order to implement the above technical solution, the embodiments of this specification are implemented as follows: A component introduction method provided in an embodiment of the present specification includes: receiving an introduction request instruction for a target component triggered by a user; in response to the introduction request instruction, obtaining the type and application scenario of the target component contained in the introduction request instruction; determining, according to the type and application scenario of the target component, multiple target evaluation tools corresponding to the target component, and a calling order and dependency relationship between the multiple target evaluation tools; according to the calling order and dependency relationship, using the multiple target evaluation tools to respectively evaluate the target component to obtain an evaluation result for the target component; and determining whether to introduce the target component according to the evaluation result.

[0007] A component introduction device provided in an embodiment of the present specification includes: an instruction receiving module, which is used to receive an introduction request instruction for a target component triggered by a user; an information acquisition module, which is used to obtain the type and application scenario of the target component contained in the introduction request instruction in response to the introduction request instruction; a tool determination module, which is used to determine, according to the type and application scenario of the target component, a plurality of target evaluation tools corresponding to the target component, as well as a calling order and dependency relationship between the plurality of target evaluation tools; a component evaluation module, which is used to evaluate the target component respectively according to the calling order and dependency relationship using the plurality of target evaluation tools to obtain an evaluation result for the target component; and an introduction judgment module, which is used to determine, according to the evaluation result, whether to introduce the target component.

[0008] A component introduction device provided in an embodiment of the present specification comprises: a processor; and a memory arranged to store computer executable instructions, wherein the executable instructions, when executed, cause the processor to: receive an introduction request instruction for a target component triggered by a user; in response to the introduction request instruction, obtain the type and application scenario of the target component contained in the introduction request instruction; determine, according to the type and application scenario of the target component, a plurality of target evaluation tools corresponding to the target component, and a calling order and dependency relationship between the plurality of target evaluation tools; according to the calling order and dependency relationship, respectively perform evaluation processing on the target component using the plurality of target evaluation tools to obtain an evaluation result for the target component; and determine, according to the evaluation result, whether to introduce the target component.

[0009] The embodiments of the present specification also provide a storage medium, which is used to store computer-executable instructions, and the executable instructions implement the following process when executed by a processor: receiving an introduction request instruction for a target component triggered by a user; in response to the introduction request instruction, obtaining the type and application scenario of the target component contained in the introduction request instruction; determining, according to the type and application scenario of the target component, multiple target evaluation tools corresponding to the target component, and the calling order and dependency relationship between the multiple target evaluation tools; according to the calling order and dependency relationship, using the multiple target evaluation tools to evaluate the target component respectively, and obtain an evaluation result for the target component; and determining whether to introduce the target component according to the evaluation result.

[0010] The embodiments of the present specification also provide a computer program product, including a computer program, which implements the following process when executed by a processor: receiving an introduction request instruction for a target component triggered by a user; in response to the introduction request instruction, obtaining the type and application scenario of the target component contained in the introduction request instruction; determining, according to the type and application scenario of the target component, multiple target evaluation tools corresponding to the target component, and the calling order and dependency relationship between the multiple target evaluation tools; according to the calling order and dependency relationship, using the multiple target evaluation tools to evaluate the target component respectively, and obtain an evaluation result for the target component; and determining whether to introduce the target component according to the evaluation result. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to more clearly illustrate the technical solutions in the embodiments of this specification or the prior art, the drawings required for use in the embodiments or the prior art description will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative labor. Figure 1 A method embodiment is introduced for a component of this specification; Figure 2 A method embodiment is introduced for yet another component of this specification; Figure 3 A schematic diagram of a component introduction process of this specification; Figure 4 A method embodiment is introduced for yet another component of this specification; Figure 5 A method embodiment is introduced for yet another component of this specification; Figure 6 This is an embodiment of a data processing device of the present specification; Figure 7 An apparatus embodiment is introduced as a component in this specification. DETAILED DESCRIPTION

[0012] The embodiments of this specification provide a component introduction method, device and equipment.

[0013] In order to enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below in conjunction with the drawings in the embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this specification.

[0014] The embodiments of this specification provide a technical solution for improving the evaluation efficiency and accuracy of open source components to improve the effect of component introduction. Open source technology has promoted the construction of digital software due to its open, shared and free characteristics. Driven by the pressure of self-controllability, quality improvement and efficiency increase, the software industry increasingly chooses open source technology products as components of its "distributed" architecture, and open source technology has become an important technical support for software development and construction. However, while achieving positive results such as technological innovation and business empowerment, digital software construction also faces many security risks, so it is necessary to conduct multi-faceted evaluation and processing of the introduced open source components. At present, when evaluating and processing open source components, it is more dependent on developers to evaluate and process open source components based on component introduction materials, other user experiences and local environment testing and verification. This process is not only time-consuming and labor-intensive, but also the selection experience is heavily dependent on personal experience, which is difficult to replicate and accumulate on a large scale, resulting in poor component evaluation efficiency and evaluation accuracy. To this end, the embodiments of this specification provide a technical solution for improving the evaluation efficiency and evaluation accuracy of open source components to improve the effect of component introduction. In this scheme, by receiving the introduction request instruction for the target component triggered by the user, in response to the introduction request instruction, the type and application scenario of the target component contained in the introduction request instruction are obtained, and according to the type and application scenario of the target component, multiple target evaluation tools corresponding to the target component and the calling order and dependency relationship between the multiple target evaluation tools are determined, and according to the calling order and dependency relationship, multiple target evaluation tools are used to evaluate the target component respectively, and the evaluation result for the target component is obtained, and according to the evaluation result, it is determined whether to introduce the target component. First, since the target evaluation tool is determined according to the type and application scenario of the target component, the target component can be evaluated and processed in a targeted manner through the target evaluation tool, thereby improving the accuracy of the evaluation. Secondly, according to the calling order and dependency relationship between the multiple target evaluation tools determined by the type and application scenario of the target component, multiple target evaluation tools can be used in an orderly manner to evaluate and process the target component respectively, thereby improving the evaluation efficiency and evaluation effect, so that according to the obtained evaluation result, it can be quickly and accurately determined whether to introduce the target component, thereby improving the component introduction effect.

[0015] like Figure 1 As shown, the embodiment of this specification provides a component introduction method, and the execution subject of the method can be a server, wherein the server can be an independent server, or a server cluster composed of multiple servers, etc. In this embodiment, the execution subject is taken as an example to be described in detail, and the method can specifically include the following steps: In step S102, an import request instruction for a target component triggered by a user is received.

[0016] The target component may be any importable component, for example, the target component may be an open source component whose source code is public and allows use, modification and distribution.

[0017] In implementation, when components are introduced into the management and control system, the microservice architecture can be used to build an integrated management platform to determine the scalability and maintainability of the component introduction management and control system. The integrated management platform can be used to manage evaluation tools. The integrated management platform can achieve seamless docking and data sharing between different evaluation tools through preset interface protocols and data exchange standards to solve the problem of data islands.

[0018] In the integrated management platform, users can enter basic information of the target component (such as the target component's identification, name, type, application scenario, etc.) in the system interface and trigger an introduction request for the target component. That is, the server can receive the introduction request instruction for the target component initiated by the user.

[0019] In step S104, in response to the import request instruction, the type and application scenario of the target component contained in the import request instruction are obtained.

[0020] Among them, the type of target component may include database type, framework type, middleware type, library type, source code type, etc., and the application scenario of the target component may include production environment scenario, test environment scenario, specific business scenario, etc. The type and application scenario of the target component can be selected according to different actual application scenarios. The embodiments of this specification do not make specific limitations on this.

[0021] During implementation, the server can obtain the type and application scenario of the target component contained in the basic information of the target component. Specifically, the server can use a parser to extract and process the basic information of the target component, and perform format conversion on the extracted information to obtain the type and application scenario of the target component that can be identified within the system. In step S106, multiple target evaluation tools corresponding to the target component, as well as the calling sequence and dependency relationship between the multiple target evaluation tools are determined according to the type and application scenario of the target component.

[0022] In implementation, the integrated management platform can be configured with a tool registration and management module to provide a tool management interface, allowing administrators to register and manage various assessment tools, and each assessment tool must comply with the preset interface protocol and data exchange standards defined by the integrated management platform to ensure that the assessment tool can be seamlessly connected to the integrated management platform.

[0023] The server can determine multiple target evaluation tools corresponding to the target component, as well as the calling order and dependency relationship between the multiple target evaluation tools based on the pre-trained generation model and the type and application scenario of the target component. The generation model can be a model built based on a preset machine learning algorithm.

[0024] Alternatively, the server may also determine multiple target evaluation tools corresponding to the target component based on the type and application scenario of the target component according to the correspondence between pre-set component types, application scenarios, and evaluation tools. Then, the server may determine the calling order and dependency relationship between the multiple target evaluation tools based on information such as the data calling relationship between the target evaluation tools.

[0025] In addition, the above-mentioned multiple target evaluation tools, and the method for determining the calling order and dependency relationship between multiple target evaluation tools is an optional and feasible determination method. In actual application scenarios, there may be multiple different determination methods. Different determination methods can be selected according to different actual application scenarios. The embodiments of this specification do not make specific limitations on this.

[0026] In step S108, multiple target evaluation tools are used to evaluate the target components according to the calling sequence and dependency relationship to obtain evaluation results for the target components.

[0027] During implementation, the server can use multiple target evaluation tools to evaluate and process the target components separately according to the calling order and dependency relationships. In addition, a data exchange center module can be configured in the integrated management platform. The data exchange center can serve as a data exchange hub between the evaluation tools and is responsible for data collection, processing and distribution. In this way, through a unified data format and transmission protocol, accurate transmission and sharing of data between different evaluation tools can be ensured.

[0028] In order to achieve seamless connection between different assessment tools, it is also necessary to define interface protocols and data exchange standards. For example, for API interface specifications, it is necessary to define the API interfaces of each assessment tool, as well as the parameters, return values ​​and other information of the API interfaces. For data format specifications, it is necessary to define the data format used for data exchange (such as JSON, XML, etc.), as well as the naming rules of data fields, data types and other information. For transmission protocols, it is necessary to define preset transmission protocols (such as HTTP, HTTPS, etc.) to ensure the security and reliability of data transmission.

[0029] In step S110, it is determined whether to introduce the target component according to the evaluation result.

[0030] In implementation, the server may determine the introduction risk type corresponding to the target component based on the evaluation results according to the pre-trained detection model. The server may determine whether to introduce the target component according to the introduction risk type corresponding to the target component. The detection model may be a classification model built based on a preset machine learning algorithm, and the introduction risk type may include high risk, medium risk, low risk, and the like.

[0031] Alternatively, the server may also send the evaluation result to a preset management party, and receive introduction suggestion information fed back by the preset management party, so as to determine whether to introduce the target component according to the introduction suggestion information.

[0032] In addition, there may be various methods for determining the introduction of a target component, and different methods for determining the introduction may be selected according to different actual application scenarios, and the embodiments of this specification do not specifically limit this.

[0033] The embodiment of this specification provides a component introduction method, which receives an introduction request instruction for a target component triggered by a user, responds to the introduction request instruction, obtains the type and application scenario of the target component contained in the introduction request instruction, determines multiple target evaluation tools corresponding to the target component according to the type and application scenario of the target component, and the calling order and dependency relationship between the multiple target evaluation tools, and uses multiple target evaluation tools to evaluate and process the target component respectively according to the calling order and dependency relationship, obtains the evaluation result for the target component, and determines whether to introduce the target component according to the evaluation result. First, since the target evaluation tool is determined according to the type and application scenario of the target component, the target component can be evaluated and processed in a targeted manner through the target evaluation tool, thereby improving the accuracy of the evaluation. Secondly, according to the calling order and dependency relationship between the multiple target evaluation tools determined by the type and application scenario of the target component, multiple target evaluation tools can be used in an orderly manner to evaluate and process the target component respectively, thereby improving the evaluation efficiency and evaluation effect. In this way, according to the obtained evaluation result, it is possible to quickly and accurately determine whether to introduce the target component, thereby improving the component introduction effect.

[0034] In practical applications, there are various specific processing methods for determining multiple target evaluation tools corresponding to the target component in the above step S106 according to the type and application scenario of the target component. An optional processing method is provided below, such as Figure 2 As shown, the processing may specifically include the following steps S1062 to S1066.

[0035] In step S1062, the evaluation priority corresponding to the target component is obtained.

[0036] Among them, the evaluation priority can be determined based on basic information such as the application scenario and type of the component.

[0037] In implementation, the server may determine the evaluation priority of the component in advance based on basic information such as the component application scenario and type, and then determine the evaluation priority corresponding to the target component based on the component identifier of the target component.

[0038] For example, the server may determine the evaluation priority of the component based on the basic information of the component according to a pre-trained priority determination model, wherein the priority determination model may be a model constructed according to a preset machine learning algorithm.

[0039] Alternatively, the evaluation priority corresponding to the component may be determined manually based on basic information of the component, historical evaluation results of the component, and other information.

[0040] The method for determining the evaluation priority corresponding to the component may vary according to different actual application scenarios. The corresponding determination method can be selected according to the actual application scenario, and the embodiments of this specification do not make specific limitations on this.

[0041] In step S1064, according to the type and application scenario of the target component and the evaluation priority corresponding to the target component, a target rule corresponding to the target component is selected from a pre-built rule library.

[0042] In implementation, a scenario-based orchestration engine can also be built into the integrated management platform. The scenario-based orchestration engine can select target rules corresponding to the target component from a pre-built rule library based on the type, application scenario, and evaluation priority of the target component submitted by the user.

[0043] For example, a parser can be built into the integrated management platform. The parser is one of the key components of the scenario-based orchestration engine. The parser can be used to parse the introduction application submitted by the user (i.e., the introduction request instruction for the target component), extract key information such as the type of the target component, application scenario, etc., and then match the rules in the pre-built rule library based on the extracted key information and the evaluation priority of the target component to obtain the target rule corresponding to the target component.

[0044] Among them, the parser can be used to extract information: when a user can submit an application for the introduction of an open source component through the system interface, the user needs to fill in the basic information of the open source component (such as type and usage scenario, etc.). The parser can automatically extract these key information from the introduction application and convert the format of the extracted key information into a format that can be recognized within the system.

[0045] The parser can also be used for rule matching: after extracting key information, the parser can match the key information and the rules in the rule library. For example, by comparing the type of target component, application scenario, evaluation priority and other conditions, the target rule in the pre-built rule library that matches the target component can be determined.

[0046] In step S1066, according to the target rule, multiple target evaluation tools corresponding to the target component are selected from the multiple evaluation tools, as well as the calling sequence and dependency relationship between the multiple target evaluation tools.

[0047] In implementation, the integrated management platform can also be equipped with a pre-built rule base, which is the basis of the scenario-based orchestration engine. The rule base stores rules and process configurations corresponding to different types, different application scenarios, and different evaluation priorities. These rules can be formulated based on industry best practices, expert experience, and specific needs within the organization to ensure the scientificity and rationality of the evaluation process.

[0048] Among them, the rule base can be used for rule formulation: the rules in the rule base can be formulated by system administrators or experts with corresponding permissions. They can formulate detailed evaluation processes and tool configuration rules based on the type of components (such as databases, frameworks, libraries, etc.), application scenarios (such as production environments, test environments, specific business scenarios, etc.) and evaluation priorities (such as license compliance, security, performance, etc.).

[0049] The rule base can also be used to update rules: as the open source ecosystem develops and the internal needs of the organization change, the rule base can be updated regularly. System administrators can add, modify or delete rules through the integrated management platform to ensure the timeliness and accuracy of the evaluation process.

[0050] In practical applications, evaluation tools include but are not limited to security evaluation tools, license evaluation tools, performance evaluation tools, and maintainability evaluation tools. The evaluation of the introduction of open source components can include license compliance evaluation, component package security evaluation, code quality evaluation, performance testing, community support and ecological compatibility evaluation, etc. Correspondingly, the evaluation tools can include security evaluation tools, license evaluation tools, performance evaluation tools, and maintainability evaluation tools, such as Figure 3 As shown, the assessment tools corresponding to different assessment dimensions may include: 1. License compliance assessment: License assessment tools such as FOSSA, WhiteSource, SnykLicense, Black Duck by Synopsys, etc. can help automatically detect the licenses of open source components and can be used to ensure that the components match the organization's compliance policies.

[0051] 2. Security assessment: Security assessment tools such as OpenSSF Scorecards, OWASPDependency-Check, Snyk, Sonatype Nexus Lifecycle, etc. can check for known security vulnerabilities in open source software and are used to evaluate the project's security practices and vulnerability response capabilities.

[0052] 3. Regarding code quality and maintenance status: Maintainability assessment tools can be static code analysis tools such as CodeClimate, LGTM (bySemmle), SonarQube, etc., which can be used to evaluate code quality, such as complexity, duplicate code, potential defects, etc.

[0053] The activity and maintenance status of a project can be evaluated through indicators such as contribution activities on platforms such as GitHub and GitLab, issue response speed, and PR merge rate.

[0054] 4. For performance evaluation: Performance evaluation tools such as JMeter, Gatling, LoadRunner and other stress testing tools can be used to evaluate performance indicators such as component response speed and resource consumption.

[0055] In practical applications, in the above step S108, according to the calling order and dependency relationship, multiple target evaluation tools are used to evaluate the target components respectively, and there are many specific processing methods to obtain the evaluation results for the target components. The following is an optional processing method, such as Figure 2 As shown, the processing may specifically include the following steps S1082 to S1086.

[0056] In step S1082, multiple target evaluation tools are used to evaluate the target components according to the calling order and dependency relationship, and a sub-evaluation result corresponding to each target evaluation tool is obtained.

[0057] In implementation, a built-in configurator can also be included in the integrated management platform. The configurator can automatically select and configure multiple target evaluation tools based on the target rules matched by the parser, including the calling order, dependencies, and parameter settings between the target evaluation tools, to ensure the targetedness and accuracy of the evaluation process.

[0058] The configurator can be used to select the evaluation tool: the configurator can select the evaluation tool corresponding to the target rule as the target evaluation tool according to the configuration in the rule base. These target evaluation tools may include license compliance scanning tools (i.e., licensing evaluation tools), security vulnerability detection tools (i.e., security evaluation tools), code quality analysis tools (i.e., maintainability evaluation tools), etc.

[0059] The configurator can also be used to set parameters: In addition to selecting the assessment tool, the configurator can also set the tool's parameters according to the configuration in the rule base. These parameters may include scanning scope, detection depth, output format, etc., to ensure the accuracy and usability of the assessment results.

[0060] The configurator can also perform process orchestration: The configurator can also be responsible for arranging the order of the evaluation process. For example, it can determine the calling order and dependencies of each evaluation tool based on the configuration in the rule base to ensure the orderly progress of the evaluation process.

[0061] In addition, if Figure 3 As shown, the configurator can also perform tool arrangement and access control arrangement, etc., wherein tool arrangement can include determining target evaluation tools according to target rules, and access control arrangement can be performed according to basic information (such as performance indicator information, etc.) of each target evaluation tool.

[0062] The server can use multiple target evaluation tools to evaluate the target components respectively according to the calling order and dependency relationship between the multiple target evaluation tools determined by the configurator, and obtain the sub-evaluation result corresponding to each target evaluation tool.

[0063] In step S1084, the sub-assessment results corresponding to each target assessment tool are converted according to preset result conversion rules to obtain the converted sub-assessment results corresponding to each target assessment tool.

[0064] In implementation, since the evaluation dimensions of each target evaluation tool may be different, the sub-evaluation results corresponding to each target evaluation tool can be converted so that the sub-evaluation results corresponding to each target evaluation tool can be converted to the same dimension. That is, the evaluation results for the target components can be quickly and accurately determined based on the converted sub-evaluation results.

[0065] Among them, the result conversion rule can be a conversion rule preset according to manual experience, or the result conversion rule can also be a conversion rule determined according to historical evaluation sub-results and a rule generation model (such as a large language model, a model built based on a machine learning algorithm, etc.). There can be various methods for determining the result conversion rule, and different conversion rules can be selected according to different actual application scenarios. The embodiments of this specification do not make specific limitations on this.

[0066] In step S1086, the converted sub-evaluation results are sorted, and the evaluation result for the target component is determined based on the sorted converted sub-evaluation results.

[0067] In implementation, since the evaluation dimensions of the converted sub-evaluation results are the same, the converted sub-evaluation results can be sorted, and then the evaluation results for the target component can be determined based on the sorted converted sub-evaluation results. For example, the sorted converted sub-evaluation results can be determined as the evaluation results for the target component.

[0068] In practical applications, the target rules can also be updated. There are many specific ways to update the rules. Here is an optional way to update the rules. Figure 4 As shown, the processing may specifically include the following steps S402 to S404.

[0069] In step S402, feedback information from the user regarding the evaluation result is received.

[0070] In step S404, the target rules are updated according to the feedback information.

[0071] During implementation, information such as component types and application scenarios may be updated quickly, so the determined evaluation results may have low accuracy. Therefore, the server can update the target rules in real time based on the user's feedback on the evaluation results to accurately perform component evaluation based on the updated target rules.

[0072] In actual applications, before selecting the target rule corresponding to the target component from the pre-built rule library according to the type and application scenario of the target component and the evaluation priority corresponding to the target component, a rule library can also be built according to the historical component. There are many specific processing methods for building the rule library. The following is an optional processing method, such as Figure 5 As shown, the processing may specifically include the following steps S502 to S506.

[0073] In step S502, historical components and corresponding historical evaluation results are obtained.

[0074] In step S504, a pre-trained rule generation model is used to determine a plurality of evaluation rules according to historical components and corresponding historical evaluation results, and a rule base is constructed according to the evaluation rules.

[0075] Among them, the rule generation model is a model built based on a preset machine learning algorithm.

[0076] In implementation, the scenario-based orchestration engine also has the ability to be intelligent and dynamically adjusted. It can continuously optimize the evaluation rules and process configurations based on historical evaluation data (i.e. historical components and corresponding historical evaluation results) and user feedback information.

[0077] For example, the scenario-based orchestration engine can make intelligent recommendations: by analyzing historical evaluation data, the scenario-based orchestration engine can identify common problems and risk points, and provide intelligent recommendations when users submit new introduction applications. These recommendations may include priority evaluation tools, key evaluation dimensions, etc.

[0078] The scenario-based orchestration engine can also be adjusted dynamically: when the open source ecosystem or internal organizational needs change, the scenario-based orchestration engine can automatically adjust the evaluation rules and process configuration. This dynamic adjustment mechanism ensures the timeliness and flexibility of the evaluation process.

[0079] After the user submits an application to introduce an open source component, the system will automatically start the evaluation process. The entire process includes several steps: 1. Information entry: Users can enter basic information such as component type and application scenario through the system interface.

[0080] 2. Evaluation tool call: The system can automatically call the corresponding target evaluation tool to evaluate license compliance, security, code quality, etc. according to the configurator of the scenario-based orchestration engine.

[0081] 3. Result summary and analysis: The system can collect the output results of each target assessment tool, summarize and analyze them. The sub-assessment results are scored and sorted through intelligent algorithms so that users can quickly understand the overall situation of the components.

[0082] 4. Evaluation report generation: Based on the evaluation results, the system can automatically generate a detailed evaluation report, including the evaluation process, evaluation results, recommendations on whether to allow admission, etc.

[0083] 5. User feedback and decision-making: Users can make decisions based on the evaluation report and choose whether to continue introducing the component.

[0084] In the evaluation process, the system can call various evaluation tools through the integrated management platform. Each evaluation tool can perform the evaluation task according to the preset evaluation process and parameter settings, and return the evaluation results to the system. The system can collect the evaluation results of each evaluation tool through the data exchange center and conduct unified processing and analysis. This mechanism ensures the automation and efficiency of the evaluation process.

[0085] The above evaluation process, through the integrated framework and scenario-based orchestration engine, realizes a comprehensive, efficient and accurate evaluation of the introduction of open source software (components). The entire evaluation process is highly automated, reducing manual intervention and error rates, and improving evaluation efficiency.

[0086] The embodiment of this specification provides a component introduction method, which receives an introduction request instruction for a target component triggered by a user, responds to the introduction request instruction, obtains the type and application scenario of the target component contained in the introduction request instruction, determines multiple target evaluation tools corresponding to the target component according to the type and application scenario of the target component, and the calling order and dependency relationship between the multiple target evaluation tools, and uses multiple target evaluation tools to evaluate and process the target component respectively according to the calling order and dependency relationship, obtains the evaluation result for the target component, and determines whether to introduce the target component according to the evaluation result. First, since the target evaluation tool is determined according to the type and application scenario of the target component, the target component can be evaluated and processed in a targeted manner through the target evaluation tool, thereby improving the accuracy of the evaluation. Secondly, according to the calling order and dependency relationship between the multiple target evaluation tools determined by the type and application scenario of the target component, multiple target evaluation tools can be used in an orderly manner to evaluate and process the target component respectively, thereby improving the evaluation efficiency and evaluation effect. In this way, according to the obtained evaluation result, it is possible to quickly and accurately determine whether to introduce the target component, thereby improving the component introduction effect.

[0087] The above is a component introduction method provided in the embodiment of this specification. Based on the same idea, the embodiment of this specification also provides a component introduction device, such as Figure 6 shown.

[0088] The component introduction device includes: an instruction receiving module 601, an information acquisition module 602, a tool determination module 603, a component evaluation module 604 and an introduction judgment module 605, wherein: The instruction receiving module 601 is used to receive an import request instruction for a target component triggered by a user; An information acquisition module 602 is used to obtain the type and application scenario of the target component contained in the import request instruction in response to the import request instruction; A tool determination module 603 is used to determine a plurality of target evaluation tools corresponding to the target component, and a calling sequence and dependency relationship between the plurality of target evaluation tools according to the type and application scenario of the target component; A component evaluation module 604 is used to evaluate the target components respectively using the multiple target evaluation tools according to the calling sequence and the dependency relationship to obtain evaluation results for the target components; The introduction judgment module 605 is used to determine whether to introduce the target component according to the evaluation result.

[0089] In the embodiment of this specification, the tool determination module 603 is used to: Obtaining the evaluation priority corresponding to the target component; According to the type and application scenario of the target component and the evaluation priority corresponding to the target component, a target rule corresponding to the target component is selected from a pre-built rule library; According to the target rule, the multiple target evaluation tools corresponding to the target component and the calling sequence and dependency relationship between the multiple target evaluation tools are selected from the multiple evaluation tools.

[0090] In the embodiments of this specification, the evaluation tools include but are not limited to security evaluation tools, license evaluation tools, performance evaluation tools, and maintainability evaluation tools.

[0091] In the embodiment of this specification, the component evaluation module 604 is used to: According to the calling sequence and dependency relationship, the target components are evaluated respectively by using the multiple target evaluation tools to obtain sub-evaluation results corresponding to each target evaluation tool; According to the preset result conversion rules, the sub-assessment results corresponding to each of the target assessment tools are converted to obtain the converted sub-assessment results corresponding to each of the target assessment tools; The converted sub-evaluation results are sorted, and the evaluation result for the target component is determined according to the sorted converted sub-evaluation results.

[0092] In the embodiment of this specification, the device further includes: An information receiving module, used for receiving feedback information from the user regarding the evaluation result; A rule updating module is used to update the target rule according to the feedback information.

[0093] In the embodiment of this specification, the device further includes: A result acquisition module, used to obtain historical components and corresponding historical evaluation results; A rule generation module is used to use a pre-trained rule generation model to determine multiple evaluation rules according to the historical components and corresponding historical evaluation results, and to build the rule base according to the evaluation rules. The rule generation model is a model built based on a preset machine learning algorithm.

[0094] The embodiment of the present specification provides a component introduction device, which receives an introduction request instruction for a target component triggered by a user, responds to the introduction request instruction, obtains the type and application scenario of the target component contained in the introduction request instruction, determines multiple target evaluation tools corresponding to the target component according to the type and application scenario of the target component, and the calling order and dependency relationship between the multiple target evaluation tools, and uses multiple target evaluation tools to evaluate and process the target component respectively according to the calling order and dependency relationship, obtains the evaluation result for the target component, and determines whether to introduce the target component according to the evaluation result. First, since the target evaluation tool is determined according to the type and application scenario of the target component, the target component can be evaluated and processed in a targeted manner through the target evaluation tool, thereby improving the accuracy of the evaluation. Secondly, according to the calling order and dependency relationship between the multiple target evaluation tools determined by the type and application scenario of the target component, multiple target evaluation tools can be used in an orderly manner to evaluate and process the target component respectively, thereby improving the evaluation efficiency and evaluation effect. In this way, according to the obtained evaluation result, it is possible to quickly and accurately determine whether to introduce the target component, thereby improving the component introduction effect.

[0095] The above is a component introduction device provided in the embodiment of this specification. Based on the same idea, the embodiment of this specification also provides a component introduction device, such as Figure 7 shown.

[0096] The component introduction device may provide a terminal device or a server, etc. for the above-mentioned embodiments.

[0097] The component introduction device may have relatively large differences due to different configurations or performances, and may include one or more processors 701 and memory 702, and the memory 702 may store one or more storage applications or data. Among them, the memory 702 may be a short-term storage or a persistent storage. The application stored in the memory 702 may include one or more modules (not shown in the figure), and each module may include a series of computer executable instructions for the component introduction device. Furthermore, the processor 701 may be configured to communicate with the memory 702, and execute a series of computer executable instructions in the memory 702 on the component introduction device. The component introduction device may also include one or more power supplies 703, one or more wired or wireless network interfaces 704, one or more input and output interfaces 705, and one or more keyboards 706.

[0098] Specifically in this embodiment, the component introduction device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer executable instructions for introducing the component into the device, and the one or more programs are configured to be executed by one or more processors, including computer executable instructions for performing the following: Receive an import request instruction for a target component triggered by a user; In response to the import request instruction, obtaining the type and application scenario of the target component contained in the import request instruction; Determining, according to the type and application scenario of the target component, a plurality of target evaluation tools corresponding to the target component, and a calling order and dependency relationship between the plurality of target evaluation tools; According to the calling sequence and the dependency relationship, using the multiple target evaluation tools, respectively evaluate the target components to obtain evaluation results for the target components; According to the evaluation result, it is determined whether to introduce the target component.

[0099] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the component introduction device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0100] The embodiment of the present specification provides a component introduction device, which receives an introduction request instruction for a target component triggered by a user, responds to the introduction request instruction, obtains the type and application scenario of the target component contained in the introduction request instruction, determines multiple target evaluation tools corresponding to the target component according to the type and application scenario of the target component, and the calling order and dependency relationship between the multiple target evaluation tools, and uses multiple target evaluation tools to evaluate and process the target component respectively according to the calling order and dependency relationship, obtains the evaluation result for the target component, and determines whether to introduce the target component according to the evaluation result. First, since the target evaluation tool is determined according to the type and application scenario of the target component, the target component can be evaluated and processed in a targeted manner through the target evaluation tool, thereby improving the accuracy of the evaluation. Secondly, according to the calling order and dependency relationship between the multiple target evaluation tools determined by the type and application scenario of the target component, multiple target evaluation tools can be used in an orderly manner to evaluate and process the target component respectively, thereby improving the evaluation efficiency and evaluation effect. In this way, according to the obtained evaluation result, it is possible to quickly and accurately determine whether to introduce the target component, thereby improving the component introduction effect.

[0101] Furthermore, based on the above Figures 1 to 5 In one embodiment, the present specification further provides a storage medium for storing computer executable instruction information. In a specific embodiment, the storage medium may be a USB flash drive, an optical disk, a hard disk, etc. When the computer executable instruction information stored in the storage medium is executed by the processor, the following process can be implemented: Receive an import request instruction for a target component triggered by a user; In response to the import request instruction, obtaining the type and application scenario of the target component contained in the import request instruction; Determining, according to the type and application scenario of the target component, a plurality of target evaluation tools corresponding to the target component, and a calling order and dependency relationship between the plurality of target evaluation tools; According to the calling sequence and the dependency relationship, using the multiple target evaluation tools, respectively evaluate the target components to obtain evaluation results for the target components; According to the evaluation result, it is determined whether to introduce the target component.

[0102] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the above-mentioned storage medium embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0103] The embodiment of this specification provides a storage medium, which receives an introduction request instruction for a target component triggered by a user, responds to the introduction request instruction, obtains the type and application scenario of the target component contained in the introduction request instruction, determines multiple target evaluation tools corresponding to the target component according to the type and application scenario of the target component, and the calling order and dependency relationship between the multiple target evaluation tools, and uses multiple target evaluation tools to evaluate and process the target component respectively according to the calling order and dependency relationship, obtains the evaluation result for the target component, and determines whether to introduce the target component according to the evaluation result. First, since the target evaluation tool is determined according to the type and application scenario of the target component, the target component can be evaluated and processed in a targeted manner through the target evaluation tool, thereby improving the accuracy of the evaluation. Secondly, according to the calling order and dependency relationship between the multiple target evaluation tools determined by the type and application scenario of the target component, multiple target evaluation tools can be used in an orderly manner to evaluate and process the target component respectively, thereby improving the evaluation efficiency and evaluation effect. In this way, according to the obtained evaluation result, it is possible to quickly and accurately determine whether to introduce the target component, thereby improving the component introduction effect.

[0104] Furthermore, based on the above Figures 1 to 5 In one or more embodiments of the present specification, a computer program product is provided, including a computer program. When the computer program in the computer program product is executed by a processor, the following process can be implemented: Receive an import request instruction for a target component triggered by a user; In response to the import request instruction, obtaining the type and application scenario of the target component contained in the import request instruction; Determining, according to the type and application scenario of the target component, a plurality of target evaluation tools corresponding to the target component, and a calling order and dependency relationship between the plurality of target evaluation tools; According to the calling sequence and the dependency relationship, using the multiple target evaluation tools, respectively evaluate the target components to obtain evaluation results for the target components; According to the evaluation result, it is determined whether to introduce the target component.

[0105] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the above-mentioned computer program product embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0106] The embodiment of this specification provides a computer program product, which receives an introduction request instruction for a target component triggered by a user, responds to the introduction request instruction, obtains the type and application scenario of the target component contained in the introduction request instruction, determines multiple target evaluation tools corresponding to the target component according to the type and application scenario of the target component, and the calling order and dependency relationship between the multiple target evaluation tools, and uses multiple target evaluation tools to evaluate the target component according to the calling order and dependency relationship, and obtains the evaluation result for the target component, and determines whether to introduce the target component according to the evaluation result. First, since the target evaluation tool is determined according to the type and application scenario of the target component, the target component can be evaluated and processed in a targeted manner through the target evaluation tool, thereby improving the accuracy of the evaluation. Secondly, according to the calling order and dependency relationship between the multiple target evaluation tools determined by the type and application scenario of the target component, multiple target evaluation tools can be used in an orderly manner to evaluate and process the target component respectively, thereby improving the evaluation efficiency and evaluation effect, so that, according to the obtained evaluation result, it is possible to quickly and accurately determine whether to introduce the target component, thereby improving the component introduction effect.

[0107] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0108] In the 1990s, it was very clear whether the improvement of a technology was hardware improvement (for example, improvement of the circuit structure of diodes, transistors, switches, etc.) or software improvement (improvement of the method flow). However, with the development of technology, many improvements of the method flow today can be regarded as direct improvements of the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that the improvement of a method flow cannot be implemented with a hardware entity module. For example, a programmable logic device (PLD) (such as a field programmable gate array (FPGA)) is such an integrated circuit whose logical function is determined by the user's programming of the device. Designers can "integrate" a digital system on a PLD by programming themselves, without having to ask chip manufacturers to design and make dedicated integrated circuit chips. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly implemented by "logic compiler" software, which is similar to the software compiler used when developing and writing programs, and the original code before compilation must also be written in a specific programming language, which is called hardware description language (HDL). There is not only one kind of HDL, but many kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also know that it is only necessary to program the method flow slightly in the above-mentioned hardware description languages ​​and program it into the integrated circuit, and then it is easy to obtain the hardware circuit that implements the logic method flow.

[0109] The controller may be implemented in any suitable manner, for example, the controller may take the form of a microprocessor or processor and a computer-readable medium storing a computer-readable program code (e.g., software or firmware) executable by the (micro)processor, a logic gate, a switch, an application-specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, and the memory controller may also be implemented as part of the control logic of the memory. It is also known to those skilled in the art that, in addition to implementing the controller in a purely computer-readable program code manner, the controller may be implemented in the form of a logic gate, a switch, an application-specific integrated circuit, a programmable logic controller, and an embedded microcontroller by logically programming the method steps. Therefore, such a controller may be considered as a hardware component, and the devices for implementing various functions included therein may also be considered as structures within the hardware component. Or even, the devices for implementing various functions may be considered as both software modules for implementing the method and structures within the hardware component.

[0110] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0111] For the convenience of description, the above devices are described in terms of functions and are divided into various units. Of course, when implementing one or more embodiments of this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0112] Those skilled in the art will appreciate that the embodiments of this specification may be provided as methods, systems, or computer program products. Therefore, one or more embodiments of this specification may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, one or more embodiments of this specification may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

[0113] The embodiments of this specification are described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the embodiments of this specification. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable fraud case serial and parallel device to produce a machine, so that the instructions executed by the processor of the computer or other programmable fraud case serial and parallel device generate instructions for implementing the processes in the process. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0114] These computer program instructions may also be stored in a computer readable memory capable of directing a computer or other programmable fraud case serial and parallel device to operate in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0115] These computer program instructions may also be loaded onto a computer or other programmable device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0116] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0117] Memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0118] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined in this article, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0119] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0120] Those skilled in the art will appreciate that the embodiments of this specification may be provided as methods, systems or computer program products. Therefore, one or more embodiments of this specification may be in the form of a complete hardware embodiment, a complete software embodiment or an embodiment combining software and hardware. Furthermore, one or more embodiments of this specification may be in the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0121] One or more embodiments of the present specification may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. One or more embodiments of the present specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0122] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0123] The above description is only an embodiment of this specification and is not intended to limit this document. For those skilled in the art, this specification may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this specification should be included in the scope of the claims of this specification.

Claims

1. A component introduction method, the method comprising: Receive an import request instruction for a target component triggered by a user; In response to the import request instruction, obtaining the type and application scenario of the target component contained in the import request instruction; Determining, according to the type and application scenario of the target component, a plurality of target evaluation tools corresponding to the target component, and a calling order and dependency relationship between the plurality of target evaluation tools; According to the calling sequence and the dependency relationship, using the multiple target evaluation tools, respectively evaluate the target components to obtain evaluation results for the target components; According to the evaluation result, it is determined whether to introduce the target component.

2. The method according to claim 1, wherein determining, according to the type and application scenario of the target component, a plurality of target evaluation tools corresponding to the target component, and a calling sequence and dependency relationship between the plurality of target evaluation tools comprises: Obtaining the evaluation priority corresponding to the target component; According to the type and application scenario of the target component and the evaluation priority corresponding to the target component, a target rule corresponding to the target component is selected from a pre-built rule library; According to the target rule, the multiple target evaluation tools corresponding to the target component and the calling sequence and dependency relationship between the multiple target evaluation tools are selected from the multiple evaluation tools.

3. The method according to claim 2, wherein the assessment tool includes but is not limited to a security assessment tool, a license assessment tool, a performance assessment tool, and a maintainability assessment tool.

4. The method according to claim 3, wherein the step of evaluating the target components respectively using the plurality of target evaluation tools according to the calling sequence and the dependency relationship to obtain evaluation results for the target components comprises: According to the calling sequence and dependency relationship, the target components are evaluated respectively by using the multiple target evaluation tools to obtain sub-evaluation results corresponding to each target evaluation tool; According to the preset result conversion rules, the sub-assessment results corresponding to each of the target assessment tools are converted to obtain the converted sub-assessment results corresponding to each of the target assessment tools; The converted sub-evaluation results are sorted, and the evaluation result for the target component is determined according to the sorted converted sub-evaluation results.

5. The method according to claim 2, further comprising: receiving feedback information from the user regarding the evaluation result; The target rule is updated according to the feedback information.

6. The method according to claim 2, before selecting a target rule corresponding to the target component from a pre-built rule library according to the type and application scenario of the target component and the evaluation priority corresponding to the target component, further comprises: Obtain historical components and corresponding historical evaluation results; A pre-trained rule generation model is used to determine multiple evaluation rules according to the historical components and the corresponding historical evaluation results, and the rule base is constructed according to the evaluation rules. The rule generation model is a model constructed based on a preset machine learning algorithm.

7. A component introduction device, comprising: An instruction receiving module, used to receive an import request instruction for a target component triggered by a user; An information acquisition module, configured to obtain, in response to the import request instruction, the type and application scenario of the target component contained in the import request instruction; A tool determination module, used to determine a plurality of target evaluation tools corresponding to the target component, and a calling sequence and dependency relationship between the plurality of target evaluation tools according to the type and application scenario of the target component; A component evaluation module, configured to evaluate the target components respectively using the plurality of target evaluation tools according to the calling sequence and the dependency relationship, and obtain evaluation results for the target components; The introduction judgment module is used to determine whether to introduce the target component according to the evaluation result.

8. An electronic device, characterized in that: The method comprises a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the computer program implements the steps of the component introduction method according to any one of claims 1 to 6 when executed by the processor.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the component introduction method according to any one of claims 1 to 6 are implemented.

10. A computer program product, characterized in that The invention comprises a computer program, which, when executed by a processor, implements the steps of the component introduction method according to any one of claims 1 to 6.

Images