Service warehouse storage and reference method and system based on modularization mode

Abstract

The invention relates to the technical field of data processing, and discloses a service warehouse storage and reference method and system based on a modularization mode, and the method comprises the steps: constructing a double-track view warehouse comprising a template view warehouse and a standard view warehouse, extracting the time period and content demands of a development task, and generating a development demand set; a reference data set is established based on component deployment information of a previous period, an optimal storage and reference strategy is solved by combining storage, dependency and scheduling quantity constraints with the purpose of minimizing service component deployment times, and finally double warehouses are controlled to execute storage and reference, so that efficient management of the componentized service warehouse is realized. Therefore, through the arrangement of the double-track view warehouse, the problem of component scheduling disorder caused by limited warehouse storage, dynamic component demand change and complex dependency relationship in MBSE development can be effectively solved, refined planning and efficient multiplexing of component storage are realized, resource consumption of component updating scheduling is reduced, and cross-team development efficiency is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data processing, and in particular to a service warehouse storage and reference method and system based on a componentization mode. BACKGROUND

[0002] With the wide application of model-based system engineering (MBSE) in the development field of complex systems such as vehicle electronics, industrial software, and intelligent hardware, componentization development has become a core means to improve the development efficiency of MBSE. By decomposing system functions into reusable service components (such as signal analysis components, security encryption components, and data storage components), one-time development and multiple reuse are achieved, and the cost of repeated development across projects and teams is reduced.

[0003] In the collaborative development scenario of multiple development teams (such as multiple ECU development teams and device development teams within the same enterprise jointly promoting a complex system project), component management faces two core needs: one is the reuse demand of general components (such as basic components such as data encryption and log collection that all teams need to use, which need to ensure consistency and reliability); the other is the individualized component management demand of teams (such as customized components developed by each team for specific business scenarios, which need to retain flexibility and self-management authority).

[0004] At the same time, there are two objective constraints in actual development: one is the limited storage resources of the warehouse (the physical or cloud storage capacity has an upper limit and cannot store all component versions unlimitedly); the other is the dynamic change of component demand (the demand for component type, version, and function is different at different development periods and different tasks, and the component storage and reference strategy needs to be dynamically adjusted). SUMMARY

[0005] The present application provides a service warehouse storage and reference method and system based on a componentization mode, aiming to solve at least one of the above technical problems.

[0006] To achieve the above purpose, the present application provides a service warehouse storage and reference method based on a componentization mode, which comprises the following steps: S1: Constructing a view warehouse of development teams; wherein the view warehouse includes a template view warehouse for each development team and a standard view warehouse for several development teams; S2: When receiving several development tasks of each development team for the current warehouse service period, extracting the development period demand and development content in the development tasks, and generating a development demand set based on the component call demand corresponding to the development period demand and development content; S3: Establishing a component call benchmark data set according to the component deployment information of the last scheduling period of the standard view warehouse in the previous warehouse service period; S4: based on the development requirement set and the component call benchmark data set, considering the component occupation space limit of the standard view warehouse, the dependency relationship between components and the constraint condition set constructed by the cycle scheduling quantity limit, taking the minimum service component deployment times as the optimization objective, using an optimization algorithm to solve the optimal storage and reference strategy of each service component in the template view warehouse and the standard view warehouse; S5: according to the optimal storage and reference strategy, controlling the template view warehouse and the standard view warehouse to execute the service component storage and reference of the current warehouse service period.

[0007] Optionally, step S1: constructing the view warehouse of the development team, specifically comprising: S11: constructing a standard view warehouse, establishing a first communication link between the standard view warehouse and a standard library administrator; wherein the first communication link is configured to drive the standard view warehouse to deploy the service component in the component warehouse-in request when the component warehouse-in request uploaded by the standard library administrator is transmitted; S12: constructing a plurality of template view warehouses, establishing a second communication link between the template view warehouses and the standard library administrator; wherein the second communication link is configured to upload the service component in the template view warehouse to the standard library administrator, and drive the standard library administrator to generate a component warehouse-in request based on the service component passed the detection after the deployment detection and the component detection.

[0008] Optionally, in S12, the deployment detection and the component detection specifically comprise: S121: the standard library administrator judges whether the category and period of the uploaded component conform to the corresponding deployment category and deployment period in the optimal storage and reference strategy of the current warehouse service period; S122: the standard library administrator performs component detection on the uploaded component, including at least one or more combined detection items such as component security scanning, code quality analysis and interface function verification.

[0009] Optionally, step S1: constructing the view warehouse of the development team, further comprising: S13: establishing a third communication link between each development team and the template view warehouse allocated to it; wherein the third communication link is configured to transmit the service component encapsulated in the view form created by the development team to the template view warehouse for storage; S14: establishing a fourth communication link between each development team and the standard view warehouse; wherein the fourth communication link is configured to realize the calling of the service component deployed in the standard view warehouse by each development team when performing the development task.

[0010] Optionally, step S2: when receiving a plurality of development tasks of each development team for the current warehouse service period, extracting the development period requirement and the development content in the development task, generating a development requirement set based on the component call requirement corresponding to the development period requirement and the development content, specifically including: S21: when receiving a plurality of development tasks of each development team for the current warehouse service period, extracting the development period requirement and the development content in the development task; S22: determining the component call requirement of each development task based on the development content, and generating a development requirement set by using the development period requirement and the component call requirement.

[0011] Optionally, S22: based on the development content, determining the component call requirement of each development task, and generating a development requirement set by using the development period requirement and the component call requirement, specifically including: S221: using a natural language processing tool to extract a plurality of technical keywords and a plurality of functional requirement words in the development content; S222: performing word group matching by using a preset technical association word group of each service component and the technical keywords of each development task, calculating the matching rate of the technical association word of each service component in the plurality of technical keywords, extracting a plurality of service components with a matching rate exceeding a preset threshold, and realizing a first screening action of the service component of each development task; S223: using a preset functional association word group of each service component under different component versions to judge the inclusion relationship between the preset functional association word group and the plurality of functional requirement words of the development task, extracting the service component version in which the preset functional association word group is completely included in the plurality of functional requirement words, and realizing a second screening action of the service component of each development task; S224: generating a development requirement set of each development task by using the development period requirement and the service component candidate set after the two screening actions.

[0012] Optionally, step S3: establishing a component call benchmark data set according to the component deployment information of the last scheduling period of the standard view warehouse in the previous warehouse service period, specifically including: S31: querying the component deployment database of the standard view warehouse, and extracting the optimal storage and reference strategy of the standard view warehouse in the previous warehouse service period recorded in the component deployment database; S32: determining the component type and component version of each service component deployed in the standard view warehouse according to the optimal storage and reference strategy of the previous warehouse service period, and generating a component deployment benchmark data; S33: Inquire attribute information of a plurality of service components of each template view warehouse; wherein the attribute information comprises component type, component version, component occupation space, component storage location, component dependency relationship and version dependency relationship; S34: Based on the component deployment benchmark data and the attribute information of a plurality of service components, establish a component calling benchmark data set.

[0013] Optionally, step S4: Based on the development demand set and the component calling benchmark data set, consider a constraint condition set constructed by component occupation space limitation of the standard view warehouse, dependency relationship between components and periodic scheduling quantity limitation, take minimizing service component deployment times as an optimization objective, and solve optimal storage and reference strategy of each service component in the template view warehouse and the standard view warehouse by using an optimization algorithm, specifically comprising: S41: Extract development time period demand of each development task in the development demand set and a service component candidate set with different component types and component versions, extract component deployment benchmark data in the component calling benchmark data set and attribute information of a plurality of service components; S42: Take component type and component version of a service component deployed by the standard view warehouse in each scheduling period of a current warehouse service time period as a planning decision variable, take that sum of component occupation spaces of all service components deployed by the standard view warehouse in each scheduling period of the current warehouse service time period does not exceed component occupation space limitation allocated to the standard view warehouse as a first constraint condition, take that service components deployed by the standard view warehouse in each scheduling period of the current warehouse service time period contain at least one version of each component type of a service component candidate set of each development task running in a development time period corresponding to the scheduling period and corresponding dependency components of the service component as a second constraint condition, and take that deployment times of service components by the standard view warehouse in each scheduling period of the current warehouse service time period does not exceed maximum detection quantity of a single scheduling period by a standard library administrator as a third constraint condition; S43: Take minimum deployment times of service components by the standard view warehouse in the current warehouse service time period as an optimization objective, and solve optimal storage and reference strategy of component type and component version of service components deployed by the standard view warehouse in each scheduling period of the current warehouse service time period by using an optimization algorithm.

[0014] Optionally, step S5: Control service component storage and reference of the template view warehouse and the standard view warehouse in the current warehouse service time period according to the optimal storage and reference strategy, specifically comprising: S51: Extract component type and component version of service components deployed by the standard view warehouse in each scheduling period of the current warehouse service time period planned in the optimal storage and reference strategy; S52: According to the component type and component version of the service component deployed in each scheduling period of the plan, the template view warehouse controls the corresponding service component to be uploaded to the standard view warehouse by the standard library administrator in each scheduling period, and the standard view warehouse controls the corresponding service component to be cleared in each scheduling period, so that the service component storage and reference of the template view warehouse and the standard view warehouse are realized.

[0015] In addition, in order to realize the above-mentioned purpose, the application further provides a service warehouse storage and reference system based on a componentization mode, comprising: A construction module is configured to construct a view warehouse of a development team, wherein the view warehouse comprises a template view warehouse used exclusively by each development team and a standard view warehouse used commonly by a plurality of development teams. A extraction module is configured to extract development period requirements and development contents in a plurality of development tasks of each development team for a current warehouse service period when the development tasks are received, and generate a development requirement set based on component call requirements corresponding to the development period requirements and the development contents. A establishment module is configured to establish a component call benchmark data set according to component deployment information of the last scheduling period of the standard view warehouse in a previous warehouse service period. A solving module is configured to solve an optimal storage and reference strategy of each service component in the template view warehouse and the standard view warehouse based on the development requirement set and the component call benchmark data set, a constraint condition set constructed by considering a component occupation space limit of the standard view warehouse, a dependency relationship between components and a cycle scheduling quantity limit, and an optimization algorithm with an optimization objective of minimizing service component deployment times. An execution module is configured to control the template view warehouse and the standard view warehouse to execute service component storage and reference of the current warehouse service period according to the optimal storage and reference strategy.

[0016] The application has the advantages that a service warehouse storage and reference method and system based on a componentization mode are provided, a double-track view warehouse comprising a template view warehouse (used exclusively by a team) and a standard view warehouse (used commonly by a plurality of teams) is constructed, period and content requirements of development tasks are extracted to generate a development requirement set, a benchmark data set is established based on component deployment information of a previous period, an optimal storage and reference strategy is solved with an objective of minimizing service component deployment times by combining storage, dependency and scheduling quantity constraints, and finally the double warehouse is controlled to execute storage and reference, so that efficient management of a componentized service warehouse is realized. Therefore, the application can effectively solve the problems of limited warehouse storage, dynamic component requirement changes and complex dependency relationships in MBSE development, realize fine planning and efficient reuse of component storage, reduce resource consumption of component update scheduling, and improve cross-team development efficiency. BRIEF DESCRIPTION OF DRAWINGS

[0017] Figure 1 A flowchart of a service warehouse storage and reference method based on the componentization mode of the present application; Figure 2 A structural diagram of a service warehouse storage and reference system based on the componentization mode of the present application. DETAILED DESCRIPTION

[0018] In order to make the objectives, technical solutions and advantages of the present application clearer, the present application is further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and do not limit the present application.

[0019] The embodiment of the present application provides a service warehouse storage and reference method based on the componentization mode, referring to Figure 1 , Figure 1 A flowchart of a service warehouse storage and reference method based on the componentization mode of the present application.

[0020] In the embodiment, a service warehouse storage and reference method based on the componentization mode, the method comprises the following steps: S1: constructing a view warehouse of a development team; wherein the view warehouse comprises a template view warehouse dedicated to each development team and a standard view warehouse shared by several development teams; S2: when receiving several development tasks of each development team for a current warehouse service period, extracting development period requirements and development contents in the development tasks, and generating a development requirement set based on component calling requirements corresponding to the development period requirements and the development contents; S3: establishing a component calling benchmark data set according to component deployment information of the last scheduling cycle of the previous warehouse service period in the standard view warehouse; S4: based on the development requirement set and the component calling benchmark data set, considering a constraint condition set constructed by taking into account component occupation space limitations of the standard view warehouse, dependency relationships between components and cycle scheduling quantity limitations, taking the minimum service component deployment times as an optimization objective, and using an optimization algorithm to solve an optimal storage and reference strategy of each service component in the template view warehouse and the standard view warehouse; S5: according to the optimal storage and reference strategy, controlling the template view warehouse and the standard view warehouse to execute service component storage and reference in the current warehouse service period.

[0021] It should be noted that in the multi-development team collaborative development scenario (such as multiple ECU development teams and equipment development teams in the same enterprise jointly promoting complex system projects), component management faces two core needs: one is the reuse demand of general components (such as basic components such as data encryption and log collection that all teams need to use, which need to ensure consistency and reliability); the second is the individual component management demand of the team (such as customized components developed by each team for specific business scenarios, which need to retain flexibility and self-management authority).

[0022] At the same time, there are two objective constraints in actual development: one is the limited storage resources of the warehouse (there is an upper limit to the physical or cloud storage capacity, which cannot store all component versions unlimitedly); the second is the dynamic change of component demand (there are differences in component type, version, and function demand at different development periods and different tasks, which need to dynamically adjust the component storage and reference strategy). The traditional component storage and reference method has been difficult to adapt to the efficient development needs of MBSE multi-team collaboration.

[0023] In order to solve the above problems, the embodiment builds a double-track view warehouse including a template view warehouse (team-only) and a standard view warehouse (multi-team shared), extracts the period and content demand of the development task to generate a development demand set, establishes a benchmark data set based on the component deployment information of the previous period, and solves the optimal storage and reference strategy with the minimum service component deployment times as the target combining storage, dependency, and scheduling quantity constraints. Finally, control the storage and reference of the double warehouse to realize the efficient management of the componentized service warehouse, which can effectively solve the component scheduling confusion problem caused by limited warehouse storage, dynamic change of component demand, and complex dependency relationship in MBSE development, realize the fine planning and efficient reuse of component storage, reduce the resource consumption of component update scheduling, and improve the cross-team development efficiency.

[0024] In the preferred embodiment, step S1: building a view warehouse of the development team, specifically includes: S11: building a standard view warehouse, establishing a first communication link between the standard view warehouse and a standard library administrator; wherein the first communication link is configured to deploy the service components in the component warehouse entry request when the component warehouse entry request uploaded by the standard library administrator is transmitted; S12: building a plurality of template view warehouses, establishing a second communication link between the template view warehouses and the standard library administrator; wherein the second communication link is configured to upload the service components in the template view warehouse to the standard library administrator, and drive the standard library administrator to generate a component warehouse entry request based on the service components that pass the detection after the deployment detection and component detection.

[0025] On this basis, step S1: building a view warehouse of the development team, further includes: S13: Establish a third communication link between each development team and the assigned template view repository; wherein the third communication link is configured to transmit the view form encapsulated service components created by the development team to the template view repository for storage; S14: Establish a fourth communication link between each development team and the standard view repository; wherein the fourth communication link is configured to enable each development team to call the service components deployed in the standard view repository when performing development tasks.

[0026] In this embodiment, a four-level communication link management system is designed: by constructing a standard view repository and establishing a first communication link between it and the standard library administrator, and by constructing several template view repositories and establishing a second communication link between them and the standard library administrator, the component deployment of the standard repository and the in-repository audit transmission of the template repository components are realized; by establishing a third communication link between the development team and the assigned template view repository, and a fourth communication link between the development team and the standard view repository, the storage transmission of team customized components and the calling transmission of standard components are realized.

[0027] Thus, through the design of the first and second communication links, the communication rights and responsibilities of the standard library administrator and the dual repository are clarified, the transmission process of components from template repository creation to standard repository deployment is standardized, disorderly component storage is avoided, and the authority and compliance of standard repository components are guaranteed; through the design of the third and fourth communication links, the component storage channel between the team and the template repository and the component calling channel between the team and the standard repository are opened, ensuring that the team can both manage personalized components independently and conveniently reuse enterprise-level general components, balancing team flexibility and enterprise standardization.

[0028] Further, in S12, deployment detection and component detection include: S121: The standard library administrator determines whether the category and period of the uploaded component meet the corresponding deployment category and deployment period in the optimal storage and reference strategy of the current repository service period; S122: The standard library administrator performs component detection on the uploaded component, including at least one or more combined detection items such as component security scanning, code quality analysis, and interface function verification.

[0029] In this embodiment, the standard library administrator first obtains the optimal storage and referencing strategy for each repository service period. This strategy specifies the component categories and deployment periods to be deployed in the current period. The administrator compares the category of the uploaded component (such as the device temperature warning component) and the planned deployment period with the corresponding requirements in the optimal strategy to determine whether they match. Subsequently, the administrator performs multi-dimensional quality checks on the uploaded components. The checks include at least one or more of the following combinations: component security scanning (checking for malicious code and vulnerabilities), code quality analysis (checking code redundancy, readability, and standardization), and interface function verification (checking whether the component interface can receive / output data normally and whether it conforms to general interface standards). Only when all checks pass can the component enter the subsequent repository entry process.

[0030] Therefore, this invention verifies the compliance of components uploaded from the template repository to the standard library administrator by determining whether the component category and time period conform to the optimal strategy and performing component security scans.

[0031] In a preferred embodiment, step S2: Upon receiving several development tasks from each development team for the current repository service period, extract the development period requirements and development content from the development tasks, and generate a development requirement set based on the component call requirements corresponding to the development period requirements and development content, specifically including: S21: When receiving several development tasks from each development team for the current repository service period, extract the development period requirements and development content from the development tasks; S22: Based on the development content, determine the component call requirements for each development task, and generate a development requirement set using the development time period requirements and the component call requirements.

[0032] Based on this, S22: Based on the development content, determine the component call requirements for each development task, and generate a development requirement set using the development time period requirements and the component call requirements, specifically including: S221: Use natural language processing tools to extract several technical keywords and several functional requirement words from the development content; S222: Perform phrase matching by using the preset technical association phrases of each service component with the technical keywords of each development task, calculate the matching rate of the technical association phrases of each service component in several technical keywords, extract several service components with matching rates exceeding a preset threshold, and realize the initial screening action of service components for each development task. S223: judging the inclusion relationship between the preset function association word group and the several function requirement words of the development task, extracting the service component version in which the preset function association word group is entirely contained in the several function requirement words, and realizing the re-screening action of the service component for each development task; S224: generating the development requirement set of each development task by using the development period requirement and the service component candidate set after the two screening actions.

[0033] In this embodiment, for the development task of each development team in the current service period, the development period requirement and the development content of the task are extracted, the component calling requirement is determined based on the development content, and the development requirement set is generated by integration. When generating the development requirement set, the keywords are extracted by natural language processing, the technology component similarity is calculated, the inclusion relationship of the function requirement words is judged, the service component is screened twice, and the development requirement set is generated in combination with the development period requirement.

[0034] Specifically, first, a natural language processing (NLP) tool is used to process the text description of the development content (such as “real-time position collection and obstacle detection of industrial robots”), and extract technical keywords (such as “industrial robot”, “position collection”, “obstacle detection”) and function requirement words (such as “centimeter-level precision” and “automatic error correction”); in the initial screening, each service component is pre-configured with a “technical association word group” (such as the technical association word group of the “robot position collection component” is “industrial robot, position collection, real-time data”), the matching rate of the technical association words of each service component in the several technical keywords is calculated, and the components with a matching rate exceeding a preset threshold are extracted to form a preliminary component candidate set (excluding components that do not match the technical field); in the re-screening, different versions of each component are pre-configured with a “function association word group” (such as the function association word group of “robot position collection component V2.0” is “centimeter-level precision”), the inclusion relationship between the preset function association word group and the several function requirement words of the development task is judged, the service component version in which the preset function association word group is entirely contained in the several function requirement words is extracted, and the final component candidate set is formed; finally, in generating the requirement set, the development period requirement (such as “week 3”) of each task is associated with the final component candidate set (such as “robot position collection component V2.0 or later version” and “robot obstacle detection component V1.5 or later version”), the requirement record of each task is generated, and the development requirement set is summarized.

[0035] In the preferred embodiment, step S3: establishing a component calling benchmark data set according to the component deployment information of the last scheduling period of the previous warehouse service period in the standard view warehouse, specifically including: S31: query the component deployment database of the standard view warehouse, and extract the optimal storage and reference strategy of the standard view warehouse in the previous warehouse service period recorded in the component deployment database; S32: determine the component type and component version of each service component deployed in the standard view warehouse according to the optimal storage and reference strategy of the previous warehouse service period, and generate component deployment benchmark data; S33: query the attribute information of a plurality of service components of each template view warehouse; wherein the attribute information includes component type, component version, component occupied space, component storage location, component dependency relationship and version dependency relationship; S34: based on the component deployment benchmark data and the attribute information of a plurality of service components, establish a component call benchmark data set.

[0036] In this embodiment, first, the component deployment database (storing historical scheduling strategy and deployment record) of the standard view warehouse is accessed, the optimal storage and reference strategy of the last scheduling period of the previous warehouse service period is extracted, the strategy records all component information deployed in the previous period of the standard warehouse, then based on the optimal strategy of the previous period, the core information of each deployed component is disassembled: component type, component version, to form component deployment benchmark data (reflecting the historical deployment state of the standard warehouse), then the component attribute database of each template view warehouse is accessed, and the attribute information of all service components is extracted, including component type, component version, component occupied space, component storage location, component dependency relationship (such as “dependent on data encryption component”), version dependency relationship (such as “only compatible with V1.4 and above versions”), finally by integrating the component deployment benchmark data (historical deployment of the standard warehouse) and the attribute information of all template components, a component call benchmark data set is formed.

[0037] In the preferred embodiment, step S4: based on the development requirement set and the component call benchmark data set, considering the constraint condition set constructed by the component occupied space limit of the standard view warehouse, the dependency relationship between components and the period scheduling quantity limit, taking the minimum service component deployment times as the optimization objective, using an optimization algorithm to solve the optimal storage and reference strategy of each service component in the template view warehouse and the standard view warehouse, specifically including: S41: extract the development period requirement of each development task in the development requirement set and the service component candidate set with different component types and component versions, extract the component deployment benchmark data in the component call benchmark data set and the attribute information of a plurality of service components; S42: taking the component type and component version of the service component deployed by the standard view warehouse in each scheduling period of the current warehouse service period as a planning decision variable, taking the sum of the component occupation space of all service components deployed by the standard view warehouse in each scheduling period of the current warehouse service period not exceeding the component occupation space limit allocated to the standard view warehouse as a first constraint condition, taking the service component deployed by the standard view warehouse in each scheduling period of the current warehouse service period containing at least one version of each component type in the service component candidate set of each development task running in the scheduling period and the dependent component corresponding to the service component as a second constraint condition, and taking the number of times of performing the deployment of the service component by the standard view warehouse in each scheduling period of the current warehouse service period not exceeding the maximum detection number of the standard library administrator in a single scheduling period as a third constraint condition; S43: taking the minimum number of service component deployments of the standard view warehouse in the current warehouse service period as an optimization target, and solving the optimal storage and reference strategy of the service component deployed by the standard view warehouse in each scheduling period of the current warehouse service period by using an optimization algorithm.

[0038] In the embodiment, the development period demand and the component candidate set of each task are extracted from the development demand set, and the component deployment benchmark data and the template component attribute are extracted from the component call benchmark data set to provide input data for modeling. After that, the component type and version deployed by the standard warehouse in each scheduling period of the current service period are defined as the core decision variable, the first constraint (storage constraint) that the sum of the occupation space of all deployed components of the standard warehouse in each period ≤ the storage limit allocated to the warehouse, the second constraint (dependency constraint) that the components deployed in each period need to contain at least one version of each component type in the component candidate set of the task in the period and the dependent component corresponding to the service component, and the third constraint (scheduling quantity constraint) that the number of component deployments in each period ≤ the maximum detection number of the standard library administrator in a single period are constructed, and an optimization algorithm is used to solve the optimal storage and reference strategy.

[0039] Therefore, based on the development demand set and the component call benchmark data set, the component type and version of each scheduling period of the standard view warehouse are taken as the decision variable, the storage, dependency, and scheduling quantity constraints are combined, the minimum number of component deployments is taken as the target, and an optimization algorithm is used to solve the optimal storage and reference strategy, so that the optimal strategy with the least number of deployments can be found under multiple constraints, the component demand of each team is met, the warehouse storage occupation, dependency integrity, and scheduling workload are controlled, and the balance between resource consumption and demand satisfaction is achieved.

[0040] In the preferred embodiment, step S5: according to the optimal storage and reference strategy, the template view warehouse and the standard view warehouse perform the service component storage and reference of the current warehouse service period, specifically including: S51: Extract the component type and component version of the service component deployed by the standard view warehouse in each scheduling period of the current warehouse service period according to the optimal storage and reference strategy planned; S52: According to the component type and component version of the service component deployed in each scheduling period, control the template view warehouse to upload the corresponding service component to the standard view warehouse through the standard library administrator in each scheduling period, and control the standard view warehouse to clean up the corresponding service component in each scheduling period, so as to realize the storage and reference of the service components in the template view warehouse and the standard view warehouse.

[0041] In this embodiment, according to the component type and version of the standard view warehouse in each scheduling period of the optimal storage and reference strategy, the template view warehouse uploads the corresponding component to the standard warehouse, and the standard warehouse cleans up the unnecessary components, so as to realize the component storage and reference of the double-warehouse. The optimal strategy is converted into executable warehouse operation, which ensures that the component storage state of the double-warehouse matches the demand, and guarantees that the team can call the required components in time.

[0042] Reference Figure 2 , Figure 2 The structure diagram of the service warehouse storage and reference system based on the componentization mode according to the embodiment of the application is shown.

[0043] As shown in Figure 2 , the service warehouse storage and reference system based on the componentization mode according to the embodiment of the application comprises: A construction module 10 is configured to construct a view warehouse of a development team; wherein the view warehouse comprises a template view warehouse for each development team and a standard view warehouse for several development teams; An extraction module 20 is configured to extract development period demand and development content in a development task when receiving the development task of each development team for a current warehouse service period, and generate a development demand set based on the component call demand corresponding to the development period demand and the development content; An establishment module 30 is configured to establish a component call benchmark data set according to the component deployment information of the standard view warehouse in the last scheduling period of the previous warehouse service period; A solving module 40 is configured to solve the optimal storage and reference strategy of each service component in the template view warehouse and the standard view warehouse by using an optimization algorithm, with the constraint condition set constructed by considering the component occupation space limitation of the standard view warehouse, the dependency relationship between components and the cycle scheduling quantity limitation, and with the optimization objective of minimizing the service component deployment times, based on the development demand set and the component call benchmark data set. The execution module 50 is configured to control the template view repository and the standard view repository to execute the service component storage and reference according to the optimal storage and reference strategy during the current repository service period.

[0044] Other embodiments or specific implementations of the service repository storage and reference system based on the componentization mode can refer to the above-mentioned method embodiments, and will not be described here.

[0045] It can be understood that, in the description of the present specification, the description of the terms "an embodiment", "another embodiment", "other embodiments", or "first embodiment to Nth embodiment" means that the specific features, structures, materials or characteristics described in combination with the embodiment or example are included in at least one embodiment or example of the present application. In the present specification, the illustrative description of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described can be combined in any one or more embodiments or examples in a suitable manner.

[0046] It should be noted that, in this paper, the terms "include", "contain" or any other variants thereof are intended to cover non-exclusive inclusion, so that the process, method, article or system including a series of elements not only includes those elements, but also includes other elements not explicitly listed, or includes elements inherent to such process, method, article or system. Without more limitations, the element defined by the statement "including a" does not exclude the existence of other identical elements in the process, method, article or system including the element.

[0047] The above is only the preferred embodiment of the present application, and does not limit the patent scope of the present application, and any equivalent structure or equivalent process transformation using the content of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A service repository storage and referencing method based on componentization pattern, characterized in that, The method comprises the following steps: S1: constructing a view warehouse of a development team; wherein the view warehouse comprises a template view warehouse dedicated to each development team and a standard view warehouse shared by several development teams; S2: when receiving several development tasks of each development team for a current warehouse service period, extracting development period requirements and development contents in the development tasks, and generating a development requirement set based on component call requirements corresponding to the development period requirements and the development contents; S3: establishing a component call benchmark data set according to component deployment information of the last scheduling cycle of the standard view warehouse in a previous warehouse service period; S4: based on the development requirement set and the component call benchmark data set, considering a constraint condition set constructed by taking into account component space limitations, dependency relationships between components and cycle scheduling quantity limitations of the standard view warehouse, taking the minimum service component deployment times as an optimization objective, and solving an optimal storage and reference strategy of each service component in the template view warehouse and the standard view warehouse by using an optimization algorithm; S5: controlling the template view warehouse and the standard view warehouse to perform service component storage and reference in the current warehouse service period according to the optimal storage and reference strategy.

2. The component-based pattern based service repository storage and referencing method of claim 1, wherein, Step S1: constructing a view warehouse of a development team, specifically comprising: S11: constructing a standard view warehouse and establishing a first communication link between the standard view warehouse and a standard library administrator; wherein the first communication link is configured to drive the standard view warehouse to deploy a service component in a component storage request when the standard library administrator uploads the component storage request; S12: constructing several template view warehouses and establishing a second communication link between the template view warehouses and the standard library administrator; wherein the second communication link is configured to upload a service component in the template view warehouse to the standard library administrator, and drive the standard library administrator to generate a component storage request based on the service component passing the detection after performing deployment detection and component detection.

3. The component-based pattern based service repository storage and referencing method of claim 2, wherein, In S12, the deployment detection and the component detection specifically comprise: S121: the standard library administrator judges whether the category and the period of the uploaded component conform to the corresponding deployment category and deployment period in the optimal storage and reference strategy of the current warehouse service period; S122: the standard library administrator performs component detection on the uploaded component by at least one or more combined detection items such as component security scanning, code quality analysis and interface function verification.

4. The component-based pattern based service repository storage and referencing method of claim 2, wherein, Step S1: constructing a view warehouse of a development team, further comprising: S13: establishing a third communication link between each development team and the template view warehouse allocated to the development team; wherein the third communication link is configured to transmit a service component in a view form created by the development team to the template view warehouse for storage; S14: establishing a fourth communication link between each development team and the standard view warehouse; wherein the fourth communication link is configured to realize calling of a service component stored in the standard view warehouse by each development team when performing a development task.

5. The component-based pattern based service repository storage and referencing method of claim 1, wherein, Step S2: when receiving a plurality of development tasks of each development team for the current warehouse service period, extracting the development period requirement and the development content in the development task, generating a development requirement set based on the component call requirement corresponding to the development period requirement and the development content, specifically including: S21: when receiving a plurality of development tasks of each development team for the current warehouse service period, extracting the development period requirement and the development content in the development task; S22: determining the component call requirement of each development task based on the development content, and generating a development requirement set using the development period requirement and the component call requirement.

6. The component-based pattern based service repository storage and referencing method of claim 5, wherein, S22: based on the development content, determine the component call requirement of each development task, and generate a development requirement set using the development period requirement and the component call requirement, specifically including: S221: use natural language processing tools to extract a plurality of technical keywords and a plurality of functional requirement words in the development content; S222: perform word group matching using the preset technical association word group of each service component and the technical keywords of each development task, calculate the matching rate of the technical association word of each service component in the plurality of technical keywords, extract a plurality of service components with a matching rate exceeding a preset threshold, and realize the first screening action of the service component for each development task; S223: use the preset functional association word group of each service component under different component versions to determine the inclusion relationship between the preset functional association word group and the plurality of functional requirement words of the development task, and extract the service component version in which the preset functional association word group is completely included in the plurality of functional requirement words, to realize the second screening action of the service component for each development task; S224: use the development period requirement and the service component candidate set after the two screening actions to generate a development requirement set for each development task.

7. The component-based pattern based service repository storage and referencing method of claim 1, wherein, Step S3: according to the component deployment information of the standard view warehouse in the last scheduling period of the previous warehouse service period, establish a component call benchmark data set, specifically including: S31: query the component deployment database of the standard view warehouse, and extract the optimal storage and reference strategy of the standard view warehouse in the previous warehouse service period recorded in the component deployment database; S32: according to the optimal storage and reference strategy of the previous warehouse service period, determine the component type and component version of each service component deployed in the standard view warehouse, and generate component deployment benchmark data; S33: query the attribute information of a plurality of service components of each template view warehouse; wherein the attribute information includes component type, component version, component occupied space, component storage location, component dependency relationship and version dependency relationship; S34: based on the component deployment benchmark data and the attribute information of the plurality of service components, establish a component call benchmark data set.

8. The component-based pattern based service repository storage and referencing method of claim 7, wherein, Step S4: based on the development requirement set and the component call benchmark data set, considering the constraint condition set constructed by the component occupation space limit of the standard view warehouse, the dependency relationship between components and the cycle scheduling quantity limit, taking the minimum service component deployment times as the optimization objective, using an optimization algorithm to solve the optimal storage and reference strategy of each service component in the template view warehouse and the standard view warehouse, specifically including: S41: extracting the development period requirement of each development task in the development requirement set and the service component candidate set with different component types and component versions, extracting the component deployment benchmark data in the component call benchmark data set and the attribute information of several service components; S42: taking the component type and component version of the service component deployed by the standard view warehouse in each scheduling period of the current warehouse service period as the planning decision variable, taking the sum of the component occupation space of all service components deployed by the standard view warehouse in each scheduling period of the current warehouse service period does not exceed the component occupation space limit allocated to the standard view warehouse as the first constraint condition, taking the service component deployed by the standard view warehouse in each scheduling period of the current warehouse service period contains: at least one version of each component type in the service component candidate set of each development task running in the development period corresponding to the scheduling period and the dependent component corresponding to the service component as the second constraint condition, taking the deployment times of the service component by the standard view warehouse in each scheduling period of the current warehouse service period does not exceed the maximum detection quantity of the standard library administrator in a single scheduling period as the third constraint condition; S43: taking the minimum service component deployment times of the standard view warehouse in the current warehouse service period as the optimization objective, using an optimization algorithm to solve the optimal storage and reference strategy of the component type and component version of the service component deployed by the standard view warehouse in each scheduling period of the current warehouse service period.

9. The component-based pattern based service repository storage and referencing method of claim 8, wherein, Step S5: according to the optimal storage and reference strategy, controlling the template view warehouse and the standard view warehouse to execute the service component storage and reference in the current warehouse service period, specifically including: S51: extracting the component type and component version of the service component deployed by the standard view warehouse in each scheduling period of the current warehouse service period in the optimal storage and reference strategy; S52: according to the component type and component version of the service component deployed in each scheduling period, controlling the template view warehouse to upload the corresponding service component to the standard view warehouse in each scheduling period, and controlling the standard view warehouse to clear the corresponding service component in each scheduling period, realizing the service component storage and reference of the template view warehouse and the standard view warehouse.

10. A component-based service repository storage and reference system, comprising: The system comprises: a construction module configured to construct a view warehouse of a development team; wherein the view warehouse comprises a template view warehouse dedicated to each development team and a standard view warehouse shared by several development teams; The extraction module is configured to extract development period requirements and development contents in a plurality of development tasks of each development team for a current warehouse service period when the development tasks are received, and generate a development requirement set based on component call requirements corresponding to the development period requirements and the development contents; The establishment module is configured to establish a component call benchmark data set according to component deployment information of the standard view warehouse in a last scheduling cycle of a previous warehouse service period; The solving module is configured to solve, based on the development requirement set and the component call benchmark data set, a constraint condition set constructed by considering a component occupation space limit of the standard view warehouse, a dependency relationship between components, and a cycle scheduling quantity limit, to minimize a service component deployment quantity as an optimization target, and to solve, by using an optimization algorithm, an optimal storage and reference strategy of each service component in the template view warehouse and the standard view warehouse; The execution module is configured to control the template view warehouse and the standard view warehouse to execute service component storage and reference of the current warehouse service period according to the optimal storage and reference strategy.

Images