CN110727457A - Component management method, device, storage medium and electronic equipment - Google Patents
Component management method, device, storage medium and electronic equipment Download PDFInfo
- Publication number
- CN110727457A CN110727457A CN201910818621.3A CN201910818621A CN110727457A CN 110727457 A CN110727457 A CN 110727457A CN 201910818621 A CN201910818621 A CN 201910818621A CN 110727457 A CN110727457 A CN 110727457A
- Authority
- CN
- China
- Prior art keywords
- component
- data
- stored data
- storage
- stored
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000007726 management method Methods 0.000 title claims abstract description 86
- 230000010354 integration Effects 0.000 claims abstract description 61
- 238000000034 method Methods 0.000 claims abstract description 44
- 238000012545 processing Methods 0.000 claims abstract description 35
- 238000012544 monitoring process Methods 0.000 claims description 29
- 238000013523 data management Methods 0.000 claims description 6
- 230000000712 assembly Effects 0.000 description 10
- 238000000429 assembly Methods 0.000 description 10
- 230000006870 function Effects 0.000 description 6
- 238000012423 maintenance Methods 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 3
- 230000006835 compression Effects 0.000 description 2
- 238000007906 compression Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 239000013307 optical fiber Substances 0.000 description 2
- 238000004806 packaging method and process Methods 0.000 description 2
- 230000002085 persistent effect Effects 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000008676 import Effects 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000003252 repetitive effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/93—Document management systems
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Data Mining & Analysis (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The disclosure relates to a component management method, a system, a storage medium and an electronic device, belonging to the technical field of component management, wherein the method comprises the following steps: receiving the components uploaded to the component management system and corresponding component information; processing the received components and the corresponding component information into pre-stored data; generating an integration strategy of the component according to the current component storage data and the pre-stored data of the component; and integrating the pre-stored data with the current assembly stored data of the assembly according to the assembly integration strategy to obtain the stored data of the assembly, and storing the stored data to a preset position. The uploaded component and the pre-stored current component storage data of the component are integrated, so that the automatic continuous integration of the component can be realized, the management of the component is supported by a data source, and the convenience and maintainability of component management are effectively improved.
Description
Technical Field
The present disclosure relates to the field of component management technologies, and in particular, to a component management method and apparatus, a storage medium, and an electronic device.
Background
A component is an assembly of one or more code segments that perform their respective functions into one or more separate parts. Different project work can be accomplished by different components.
At present, the management of the components is generally the storage management of various components through a component platform, most of the storage is common UI components, the continuous integrated management of various components is difficult to perform, the components are incomplete, the component maintenance is inconvenient, and the data source support cannot be achieved.
It is to be noted that the information disclosed in the above background section is only for enhancement of understanding of the background of the present disclosure, and thus may include information that does not constitute prior art known to those of ordinary skill in the art.
Disclosure of Invention
The purpose of the present disclosure is to provide a component management scheme, so as to effectively improve convenience and maintainability of component management at least to a certain extent under the condition of realizing continuous integrated management of components.
According to an aspect of the present disclosure, there is provided a component management method including:
receiving the components uploaded to the component management system and corresponding component information;
processing the received components and the corresponding component information into pre-stored data;
generating an integration strategy of the component according to the current component storage data and the pre-stored data of the component;
and integrating the pre-stored data with the current assembly stored data of the assembly according to the assembly integration strategy to obtain the stored data of the assembly, and storing the stored data to a preset position.
In an exemplary embodiment of the present disclosure, after the integrating the pre-stored data with the stored data of the current component of the component according to the integration policy of the component and saving the integrated data to a predetermined location, the method further includes:
receiving a component acquisition request of a target component;
generating a data acquisition message of the target component according to the component acquisition request;
acquiring the storage data of the target component according to the data acquisition message;
processing the stored data of the target component into release data;
and sending the release data to the demander of the target component.
In an exemplary embodiment of the present disclosure, the processing the storage data of the target component into release data includes:
analyzing the stored data to obtain pre-release data;
and setting a publishing parameter for the pre-publishing data according to the configuration requirement in the component acquisition request to obtain the publishing data.
In an exemplary embodiment of the present disclosure, the processing the received component and the corresponding component information into pre-stored data includes:
processing the component into first pre-stored data of the current storage format according to the current storage format of the current component storage data of the component;
and processing the component information into second pre-stored data of the preset component information storage format according to the preset component information storage format of the component.
In an exemplary embodiment of the present disclosure, the integrating, according to the integration policy of the component, the pre-stored data with the current component stored data of the component to obtain stored data of the component, and storing the stored data in a predetermined location includes:
integrating the pre-stored data of the component source data type with the current component storage data of the component source data type according to the integration strategy of the component to obtain storage data of the component source data type, and storing the storage data in a component source data management database;
and integrating the pre-stored data of the document type with the stored data of the current component of the document type according to the integration strategy of the component to obtain the stored data of the document type, and storing the stored data in a document type data management database.
In an exemplary embodiment of the present disclosure, after the stored data of the target component is processed into published data, the method further comprises:
configuring a component operating environment corresponding to the component operating environment identifier for the platform service module according to the component operating environment identifier carried in the component acquisition request;
and operating the component in the component operating environment, and displaying the operating process and the operating result of the component.
In an exemplary embodiment of the present disclosure, the method further comprises:
acquiring monitoring data of the target assembly;
generating a component monitoring report according to the monitoring data of the target component;
and acquiring a quality monitoring result of the target assembly according to the assembly monitoring report.
According to an aspect of the present disclosure, there is provided a component management apparatus, comprising:
the platform service module is used for receiving the components uploaded to the component management system and corresponding component information;
the data service module is used for processing the received components and the corresponding component information into pre-stored data;
the continuous integration module is used for generating an integration strategy of the component according to the current component storage data and the pre-stored data of the component;
and the storage module is used for integrating the pre-stored data with the current component storage data of the component according to the integration strategy of the component to obtain the storage data of the component and storing the storage data to a preset position.
According to an aspect of the present disclosure, there is provided a computer readable storage medium having a component management program stored thereon, wherein the component management program, when executed by a processor, implements the method of any one of the above.
According to an aspect of the present disclosure, there is provided an electronic apparatus, comprising:
a processor; and
a memory for storing a component manager of the processor; wherein the processor is configured to perform any of the methods described above via execution of the component management program.
The invention discloses a component management method and device. Firstly, receiving components uploaded to a component management system and corresponding component information; therefore, different components in the component management system can be accurately managed according to the component information corresponding to the components. Then, processing the received assembly and the corresponding assembly information into pre-stored data; the received different assemblies and the corresponding assembly information are processed into pre-stored data for unified integrated storage according to the unified management requirements of the assemblies in the assembly management system, so that the assembly data can be subjected to unified integrated management in the subsequent steps, and the management of the assemblies is guaranteed to be supported by a data source. Then, generating an integration strategy of the component according to the current component storage data and the pre-stored data of the component; in this way, accurate integration of the uploaded data of the component and the pre-stored data of the component in the subsequent steps can be realized. Finally, according to the integration strategy of the component, integrating the pre-stored data with the current component storage data of the component to obtain the storage data of the component, and storing the storage data to a preset position; the uploaded components and the pre-stored current component storage data of the components are integrated, so that the automatic continuous integration of the components can be realized, the management of the components is supported by a data source, and the convenience and maintainability of component management are effectively improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure. It is to be understood that the drawings in the following description are merely exemplary of the disclosure, and that other drawings may be derived from those drawings by one of ordinary skill in the art without the exercise of inventive faculty.
Fig. 1 schematically shows a flow chart of a component management method.
Fig. 2 schematically shows an application scenario example diagram of a component management method.
Fig. 3 schematically shows a flow chart of a component acquisition method.
Fig. 4 schematically shows a block diagram of a component management apparatus.
Fig. 5 schematically shows an example block diagram of an electronic device for implementing the above-described component management method.
Fig. 6 schematically illustrates a computer-readable storage medium for implementing the above-described component management method.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the disclosure. One skilled in the relevant art will recognize, however, that the subject matter of the present disclosure can be practiced without one or more of the specific details, or with other methods, components, devices, steps, and the like. In other instances, well-known technical solutions have not been shown or described in detail to avoid obscuring aspects of the present disclosure.
Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus their repetitive description will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.
In the present exemplary embodiment, a component management method is first provided, where the component management method may be executed on a server, or may also be executed on a server cluster or a cloud server, and of course, a person skilled in the art may also execute the method of the present invention on other platforms according to needs, and this is not particularly limited in the present exemplary embodiment. Referring to fig. 1, the component management method may include the steps of:
step S110, receiving the components uploaded to the component management system and corresponding component information;
step S120, processing the received components and the corresponding component information into pre-stored data;
step S130, generating an integration strategy of the component according to the current component storage data and the pre-stored data of the component;
step S140, according to the integration strategy of the component, integrating the pre-stored data with the current component storage data of the component to obtain the storage data of the component, and storing the storage data to a preset position.
In the above component management method. Firstly, receiving components uploaded to a component management system and corresponding component information; therefore, different components in the component management system can be accurately managed according to the component information corresponding to the components. Then, processing the received assembly and the corresponding assembly information into pre-stored data; the received different assemblies and the corresponding assembly information are processed into pre-stored data for unified integrated storage according to the unified management requirements of the assemblies in the assembly management system, so that the assembly data can be subjected to unified integrated management in the subsequent steps, and the management of the assemblies is guaranteed to be supported by a data source. Then, generating an integration strategy of the component according to the current component storage data and the pre-stored data of the component; in this way, accurate integration of the uploaded data of the component and the pre-stored data of the component in the subsequent steps can be realized. Finally, according to the integration strategy of the component, integrating the pre-stored data with the current component storage data of the component to obtain the storage data of the component, and storing the storage data to a preset position; the uploaded components and the pre-stored current component storage data of the components are integrated, so that the automatic continuous integration of the components can be realized, the management of the components is supported by a data source, and the convenience and maintainability of component management are effectively improved.
Hereinafter, each step in the above-described component management method in the present exemplary embodiment will be explained and explained in detail with reference to the drawings.
In step S110, the component uploaded to the component management system and the corresponding component information are received.
In the present exemplary embodiment, referring to fig. 2, the server 201 receives components of the component management system uploaded from the terminal 202 to the server 201 and corresponding component information. Maintenance and management of the components can then proceed. The server 201 may be any device having a data storage function for executing program instructions, such as a mobile phone, a computer, and the like, and the terminal 202 may be any device having a data transmission function, such as a mobile phone, a computer, and the like, which is not limited herein.
A component is an assembly of one or more code segments that perform their respective functions into one or more separate parts. The component information may describe detailed information of the component, such as development purpose, role, operation environment, application field, and the like of the component.
By receiving the components uploaded to the component management system and the corresponding component information, different components in the component management system can be accurately managed and maintained according to the component information corresponding to the components. For example, components may be categorized into the same purpose management categories according to their development use; meanwhile, the required components can be inquired according to the component information corresponding to the components.
In an embodiment of this example, the preset component uploading unit and the component information filling unit are characterized in that the receiving components uploaded to the component management system and corresponding component information includes:
receiving the components uploaded from the component uploading unit;
receiving component information corresponding to the component filled in from the component information filling unit.
The preset component uploading unit is an area for uploading data of the component, for example, a data uploading text box on the management interface. The component information filling unit is used for filling out the information area of the component according to a preset format or a user-defined format, for example, a component information filling text box on a management interface.
The component uploading unit receives the components uploaded by the user, and the component information filling unit fills the information of the components uploaded by the user, so that various components can be continuously collected, and the component information corresponding to the components can be accurately and conveniently acquired.
In step S120, the received component and the corresponding component information are processed into pre-stored data.
In the embodiment of the present example, the components and the corresponding component information need to be stored in different forms, and meanwhile, the components and the corresponding component information can ensure good maintenance and management of the components only if good relevance is ensured. The received data of the components and the corresponding component information are processed into the storage data, namely the initially received components and the component information are processed according to the maintenance and management requirements of the components to obtain the storage data meeting the maintenance and management requirements. For example, the components are compressed into a compressed file, and then personalized tags are added, and the automatic information keywords of the component information are filled in the component information form, and then the tags which are the same as the components are added.
The received different assemblies and the corresponding assembly information are processed into pre-stored data for unified integrated storage according to the unified management requirements of the assemblies in the assembly management system, so that the assembly data can be unified and integrated and managed in the subsequent steps, meanwhile, the management of the assemblies is guaranteed to be supported by a unified data source, and the assemblies can be conveniently and accurately stored and called.
In an embodiment of this example, the processing the received component and the corresponding component information into pre-stored data includes:
processing the component into first pre-stored data of the current storage format according to the current storage format of the current component storage data of the component;
and processing the component information into second pre-stored data of the preset component information storage format according to the preset component information storage format of the component.
The current component storage data of a component is data, e.g., a code package, etc., of the component that is historically stored within the component management system at the current point in time that the component is received. The current storage format of the current component storage data of the component is, for example, the storage format of the current time point component data, for example, the component for importing different classes of libraries has different suffixes such as vue,. js, and the like, so as to facilitate import management of the component, and the component can also be stored after being compressed. The processing of the component into the first pre-stored data is to process the component into data in the same format as the current storage format of the current component storage data of the component, for example, compiling the component into js and then performing compression and packaging. This may facilitate accurate integrated management of component data.
The preset component information storage format of the component is a storage format of information of the component preset in the component management system, for example, a preset standard component information management table and the like. Processing the component information into second pre-stored data, that is, processing the component information into information storage data in a preset component information storage format, for example, storing an attribute value of each attribute information in the component information into a preset table, and performing compression and packaging. This can facilitate accurate integrated management of component information data.
In step S130, an integration policy of the component is generated according to the current component storage data of the component and the pre-stored data.
In the embodiment of the present example, the integration policy of the component is a policy of integrating the pre-stored data of the uploaded component and the corresponding component information with the current component storage data already stored in the component management platform at the current time point of receiving the component. For example, a component is used for updating a target component currently stored in the component management system, and the integration policy of the component is the policy for replacing the target component with the received component. According to the current assembly storage data and the pre-stored data of the assembly, the two data are scanned by using the preset codes to obtain annotation keywords of the two storage data, the difference keywords of the pre-stored data relative to the storage data of the current assembly are obtained through keyword comparison, the difference keywords of the pre-stored data are cross, redundant and the like, and the integration strategy of a new assembly can be accurately obtained through searching the preset keyword relation and the integration strategy comparison table. The integration policy may be, for example, filling the received name of the component and the target integration name in the current component storage data of the component into a preset integration policy code template, respectively. In this way, accurate integration of the uploaded data of the component and the pre-stored data of the component in the subsequent steps can be realized.
In step S140, according to the integration policy of the component, the pre-stored data is integrated with the current component storage data of the component to obtain the storage data of the component, and the storage data is stored in a predetermined location.
In the embodiment of the present example, the uploaded component is integrated with the current component storage data of the component stored in advance by using the acquired integration policy of the component, that is, the automatic continuous integration of the component is realized by using the integration instruction. Therefore, the management of the components can be supported by a continuous data source, and the convenience and maintainability of the management of the components are effectively improved. Then, the storage data of the components are stored to the preset positions, namely, the storage data with different formats are respectively stored to the corresponding databases according to the management requirements, so that the query and the management of the storage data can be facilitated.
In an implementation manner of this example, the integrating, according to the integration policy of the component, the pre-stored data with the current component stored data of the component to obtain stored data of the component, and storing the stored data in a predetermined location includes:
integrating the pre-stored data of the component source data type with the current component storage data of the component source data type according to the integration strategy of the component to obtain storage data of the component source data type, and storing the storage data in a component source data management database;
and integrating the pre-stored data of the document type with the stored data of the current component of the document type according to the integration strategy of the component to obtain the stored data of the document type, and storing the stored data in a document type data management database.
The integration strategy of the component has corresponding type strategies according to different types of storage data, for example, the component source data type can be the integration strategy of a code instruction for operating the source data; document type integration policies that can structure query statements. The storage data of the document type is, for example, a component information table or the like, and document data is created for the component information by the service module.
The integration of the pre-stored data of the component source data type with the current component storage data of the component source data type of the component is, for example, the integration of the received pre-stored data of the component for updating with the storage data before updating in the current component storage data.
The integration of the pre-stored data of the document type with the current component storage data of the document type of the component is, for example, the integration of the storage data of replacing the data of a certain attribute in the information table of the component for updating with the data of the corresponding attribute before updating in the information table of the current component.
By storing document type data separately from other types of data, such as program files, management of components and component information may be facilitated.
In an implementation manner of this example, referring to fig. 3, after the integrating the pre-stored data with the stored data of the current component of the component according to the integration policy of the component and saving the integrated data to the predetermined location, the method further includes:
step S310, receiving a component acquisition request of a target component;
step S320, generating a data acquisition message of the target component according to the component acquisition request;
step S330, acquiring the storage data of the target component according to the data acquisition message;
step S340, processing the storage data of the target assembly into release data;
and step S350, sending the release data to the demander of the target component.
The component acquisition request of the target component is an acquisition request which is sent by the component demander and is required to acquire information containing the target component. The data acquisition message of the target component is a request instruction for processing the component acquisition request into a convention of the component management system, for example, a request instruction expressed by a structured query language. By sending the data acquisition message to the module storing the data, the stored data of the target component can be automatically queried and returned. Then, the acquired storage data of the target component is processed into release data, that is, the storage data of the target component is processed into codes which can be operated in an application environment such as android, for example, after the acquired storage data is converted into codes in a demand format of a demand side, parameter configuration is automatically performed according to configuration parameters in the component acquisition request, and release data which can be operated and released in the application environment of the demand side of the component is obtained. And finally, sending the release data to the demander of the target component. Therefore, the efficiency of releasing the components can be effectively ensured, and the user experience is improved.
In one embodiment of this example, the processing the stored data of the target component into published data includes:
analyzing the stored data to obtain pre-release data;
and setting a publishing parameter for the pre-publishing data according to the configuration requirement in the component acquisition request to obtain the publishing data.
The storage data is analyzed to obtain the pre-release data, which is, for example, the compressed storage data is decompressed to obtain decompressed pre-release data, that is, the pre-release component. The configuration requirement in the component acquisition request is a requirement of a component requirement platform for an attribute of a component, and includes an attribute value for a certain attribute, and an attribute value can be automatically set for the component by, for example, an attribute addition template t. Therefore, the efficiency and the individual requirements of component publishing can be effectively ensured.
In one embodiment of this example, after the stored data of the target component is processed into published data, the method further comprises:
configuring a component operating environment corresponding to the component operating environment identifier for the platform service module according to the component operating environment identifier carried in the component acquisition request;
and operating the component in the component operating environment, and displaying the operating process and the operating result of the component.
The component runtime environment identification is a preset identification of the runtime environment, such as android. The component running environment identifier carried in the component acquisition request is used for configuring the component running environment corresponding to the component running environment identifier in a platform service module for component publishing service in advance, and then the component is run, so that the running process and the running result of the component in running can be previewed in advance. Such as whether the component is operating smoothly to achieve a predetermined effect, etc. Therefore, the success rate of component release can be ensured.
In one implementation of this example, the method further comprises:
acquiring monitoring data of the target assembly;
generating a component monitoring report according to the monitoring data of the target component;
and acquiring a quality monitoring result of the target assembly according to the assembly monitoring report.
The monitoring data of the target component is the data of the historical publishing success rate, the calling condition and the like of a certain component, and the quality of the component can be effectively reflected.
The preset data service module is a preset component data transfer center node and records monitoring data of all components, such as historical publishing success rate, calling condition and the like.
The component quality monitoring module is a module which is arranged for periodically monitoring the quality of the component.
The component quality monitoring module sends a component quality monitoring request of the target component to the preset data service module periodically, so that periodic monitoring data of the target component can be acquired. Then, the quality monitoring module automatically adds data with different attributes in the regular monitoring data into a preset blank report template, and can accurately generate a component monitoring report according to the monitoring data of the target component. Then, the component quality monitoring module inquires the score of the data of each attribute according to the data of each attribute in the component monitoring report and a preset data scoring table for scoring the component quality, and then sums each score to obtain the quality monitoring result of the target component, so that the quality of the component can be effectively monitored, and the component is reasonably maintained.
The present disclosure also provides a component management apparatus. Referring to fig. 4, the component management apparatus may include a platform service module 410, a data service module 420, a persistent integration module 430, and a storage module 440. Wherein:
the platform service module 410 may be configured to receive the components uploaded to the component management system and corresponding component information;
the data service module 420 may be configured to process the received component and the corresponding component information into pre-stored data;
the persistent integration module 430 may be configured to generate an integration policy of the component according to the current component storage data of the component and the pre-stored data;
the storage module 440 may be configured to integrate the pre-stored data with the current component storage data of the component according to the integration policy of the component, obtain the storage data of the component, and store the storage data in a predetermined location.
The specific details of each module in the component management apparatus have been described in detail in the corresponding component management method, and therefore are not described herein again.
It should be noted that although in the above detailed description several modules or units of the device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit, according to embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into embodiments by a plurality of modules or units.
Moreover, although the steps of the methods of the present disclosure are depicted in the drawings in a particular order, this does not require or imply that the steps must be performed in this particular order, or that all of the depicted steps must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions, etc.
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which may be a personal computer, a server, a mobile terminal, or a network device, etc.) to execute the method according to the embodiments of the present disclosure.
In an exemplary embodiment of the present disclosure, an electronic device capable of implementing the above method is also provided.
As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or program product. Thus, various aspects of the invention may be embodied in the form of: an entirely hardware embodiment, an entirely software embodiment (including firmware, microcode, etc.) or an embodiment combining hardware and software aspects that may all generally be referred to herein as a "circuit," module "or" system.
An electronic device 500 according to this embodiment of the invention is described below with reference to fig. 5. The electronic device 500 shown in fig. 5 is only an example and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.
As shown in fig. 5, the electronic device 500 is embodied in the form of a general purpose computing device. The components of the electronic device 500 may include, but are not limited to: the at least one processing unit 510, the at least one memory unit 520, and a bus 530 that couples various system components including the memory unit 520 and the processing unit 510.
Wherein the storage unit stores program code that is executable by the processing unit 510 to cause the processing unit 510 to perform steps according to various exemplary embodiments of the present invention as described in the above section "exemplary methods" of the present specification. For example, the processing unit 510 may execute step S110 as shown in fig. 1: receiving the components uploaded to the component management system and corresponding component information; s120: processing the received components and the corresponding component information into pre-stored data; step S130: generating an integration strategy of the component according to the current component storage data and the pre-stored data of the component; step S140: and integrating the pre-stored data with the current assembly stored data of the assembly according to the assembly integration strategy to obtain the stored data of the assembly, and storing the stored data to a preset position.
The memory unit 520 may include a readable medium in the form of a volatile memory unit, such as a random access memory unit (RAM)5201 and/or a cache memory unit 5202, and may further include a read only memory unit (ROM) 5203.
Storage unit 520 may also include a program/utility 5204 having a set (at least one) of program modules 5205, such program modules 5205 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may comprise an implementation of a network environment.
Bus 530 may be one or more of any of several types of bus structures including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.
The electronic device 500 may also communicate with one or more external devices 700 (e.g., keyboard, pointing device, bluetooth device, etc.), with one or more devices that enable a client to interact with the electronic device 500, and/or with any devices (e.g., router, modem, etc.) that enable the electronic device 500 to communicate with one or more other computing devices. Such communication may occur via input/output (I/O) interfaces 550. Also, the electronic device 500 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the internet) via the network adapter 560. As shown, the network adapter 560 communicates with the other modules of the electronic device 500 over the bus 530. It should be appreciated that although not shown in the figures, other hardware and/or software modules may be used in conjunction with the electronic device 500, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which may be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the embodiments of the present disclosure.
In an exemplary embodiment of the present disclosure, there is also provided a computer-readable storage medium having stored thereon a program product capable of implementing the above-described method of the present specification. In some possible embodiments, aspects of the invention may also be implemented in the form of a program product comprising program code means for causing a terminal device to carry out the steps according to various exemplary embodiments of the invention described in the above section "exemplary methods" of the present description, when said program product is run on the terminal device.
Referring to fig. 6, a program product 600 for implementing the above method according to an embodiment of the present invention is described, which may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited in this regard and, in the present document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
A computer readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the client computing device, partly on the client device, as a stand-alone software package, partly on the client computing device and partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the client computing device over any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., over the internet using an internet service provider).
Furthermore, the above-described figures are merely schematic illustrations of processes involved in methods according to exemplary embodiments of the invention, and are not intended to be limiting. It will be readily understood that the processes shown in the above figures are not intended to indicate or limit the chronological order of the processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, e.g., in multiple modules.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
Claims (10)
1. A method for component management, the method comprising:
receiving the components uploaded to the component management system and corresponding component information;
processing the received components and the corresponding component information into pre-stored data;
generating an integration strategy of the component according to the current component storage data and the pre-stored data of the component;
and integrating the pre-stored data with the current assembly stored data of the assembly according to the assembly integration strategy to obtain the stored data of the assembly, and storing the stored data to a preset position.
2. The method of claim 1, wherein after the pre-stored data is integrated with the stored data of the current component of the component according to the integration policy of the component and then saved to a predetermined location, the method further comprises:
receiving a component acquisition request of a target component;
generating a data acquisition message of the target component according to the component acquisition request;
acquiring the storage data of the target component according to the data acquisition message;
processing the stored data of the target component into release data;
and sending the release data to the demander of the target component.
3. The method of claim 2, wherein said processing said stored data of said target component into published data comprises:
analyzing the stored data to obtain pre-release data;
and setting a publishing parameter for the pre-publishing data according to the configuration requirement in the component acquisition request to obtain the publishing data.
4. The method of claim 1, wherein the processing the received component and the corresponding component information into pre-stored data comprises:
processing the component into first pre-stored data of the current storage format according to the current storage format of the current component storage data of the component;
and processing the component information into second pre-stored data of the preset component information storage format according to the preset component information storage format of the component.
5. The method of claim 1, wherein the integrating the pre-stored data with the current component stored data of the component according to the integration policy of the component to obtain the stored data of the component, and storing the stored data in a predetermined location comprises:
integrating the pre-stored data of the component source data type with the current component storage data of the component source data type according to the integration strategy of the component to obtain storage data of the component source data type, and storing the storage data in a component source data management database;
and integrating the pre-stored data of the document type with the stored data of the current component of the document type according to the integration strategy of the component to obtain the stored data of the document type, and storing the stored data in a document type data management database.
6. The method of claim 2, wherein after the stored data of the target component is processed into published data, the method further comprises:
configuring a component operating environment corresponding to the component operating environment identifier for the platform service module according to the component operating environment identifier carried in the component acquisition request;
and operating the component in the component operating environment, and displaying the operating process and the operating result of the component.
7. The method of claim 1, further comprising:
acquiring monitoring data of the target assembly;
generating a component monitoring report according to the monitoring data of the target component;
and acquiring a quality monitoring result of the target assembly according to the assembly monitoring report.
8. A component management apparatus, comprising:
the platform service module is used for receiving the components uploaded to the component management system and corresponding component information;
the data service module is used for processing the received components and the corresponding component information into pre-stored data;
the continuous integration module is used for generating an integration strategy of the component according to the current component storage data and the pre-stored data of the component;
and the storage module is used for integrating the pre-stored data with the current component storage data of the component according to the integration strategy of the component to obtain the storage data of the component and storing the storage data to a preset position.
9. A computer-readable storage medium having stored thereon a component management program, wherein the component management program, when executed by a processor, implements the method of any of claims 1-7.
10. An electronic device, comprising:
a processor; and
a memory for storing a component manager of the processor; wherein the processor is configured to perform the method of any of claims 1-7 via execution of the component manager.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910818621.3A CN110727457A (en) | 2019-08-30 | 2019-08-30 | Component management method, device, storage medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910818621.3A CN110727457A (en) | 2019-08-30 | 2019-08-30 | Component management method, device, storage medium and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110727457A true CN110727457A (en) | 2020-01-24 |
Family
ID=69218758
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910818621.3A Pending CN110727457A (en) | 2019-08-30 | 2019-08-30 | Component management method, device, storage medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110727457A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112631573A (en) * | 2020-12-25 | 2021-04-09 | 平安银行股份有限公司 | Component adding method, device, equipment and computer readable storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120089976A1 (en) * | 2010-10-08 | 2012-04-12 | Microsoft Corporation | Integrating Software Components |
| US20170214737A1 (en) * | 2016-01-25 | 2017-07-27 | Vmware, Inc. | Integrated application-aware load balancer incorporated within a distributed-service-application-controlled distributed computer system |
| CN109783155A (en) * | 2018-12-27 | 2019-05-21 | 北京奇安信科技有限公司 | Service Component management method, device, electronic equipment and storage medium |
| CN110058860A (en) * | 2019-03-16 | 2019-07-26 | 平安城市建设科技(深圳)有限公司 | A kind of automatic delivery method of code, device, equipment and computer storage medium |
-
2019
- 2019-08-30 CN CN201910818621.3A patent/CN110727457A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120089976A1 (en) * | 2010-10-08 | 2012-04-12 | Microsoft Corporation | Integrating Software Components |
| US20170214737A1 (en) * | 2016-01-25 | 2017-07-27 | Vmware, Inc. | Integrated application-aware load balancer incorporated within a distributed-service-application-controlled distributed computer system |
| CN109783155A (en) * | 2018-12-27 | 2019-05-21 | 北京奇安信科技有限公司 | Service Component management method, device, electronic equipment and storage medium |
| CN110058860A (en) * | 2019-03-16 | 2019-07-26 | 平安城市建设科技(深圳)有限公司 | A kind of automatic delivery method of code, device, equipment and computer storage medium |
Non-Patent Citations (1)
| Title |
|---|
| SUSAN L. NORN’S;MICHAEL M. ENGELGAU;PATRICK J. O’CONNOR;DAVID MCCULLOCH;RUSSELL E. GLASGOW: "Chronic Disease Management A Definition And Systematic Approach To Component Interventions", 《JOURNA《DISEASE MANAGEMENT AND HEALTH OUTCOMES》, vol. 11, no. 08, 31 August 2003 (2003-08-31), pages 477 - 488 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112631573A (en) * | 2020-12-25 | 2021-04-09 | 平安银行股份有限公司 | Component adding method, device, equipment and computer readable storage medium |
| CN112631573B (en) * | 2020-12-25 | 2024-05-10 | 平安银行股份有限公司 | Component adding method, device, equipment and computer readable storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107506451B (en) | Abnormal information monitoring method and device for data interaction | |
| CN110069572B (en) | HIVE task scheduling method, device, equipment and storage medium based on big data platform | |
| CN110807067B (en) | Data synchronization method, device and equipment for relational database and data warehouse | |
| CN111309550A (en) | Data acquisition method, system, equipment and storage medium of application program | |
| CN111190888A (en) | Method and device for managing graph database cluster | |
| CN104537015A (en) | Log analysis computer implementation method, computer and system | |
| CN103345386A (en) | Software production method, device and operation system | |
| CN112711581A (en) | Medical data verification method and device, electronic equipment and storage medium | |
| KR20200046769A (en) | Method for providing business process management system based on automatic report generation | |
| CN111125064A (en) | Method and device for generating database mode definition statement | |
| CN116126950A (en) | Real-time materialized view system and method | |
| CN110716804A (en) | Method and device for automatically deleting useless resources, storage medium and electronic equipment | |
| CN117271584A (en) | Data processing method and device, computer readable storage medium and electronic equipment | |
| US10129328B2 (en) | Centralized management of webservice resources in an enterprise | |
| CN110727457A (en) | Component management method, device, storage medium and electronic equipment | |
| CN110716763B (en) | Automatic optimization method and device for web container, storage medium and electronic equipment | |
| CN111159237B (en) | System data distribution method and device, storage medium and electronic equipment | |
| CN114547106A (en) | Data query method and device, storage medium and computer system | |
| CN110471708B (en) | Method and device for acquiring configuration items based on reusable components | |
| CN114189457A (en) | Cloud resource display and processing method, equipment and storage medium | |
| CN108874625B (en) | Information processing method and device, electronic equipment and storage medium | |
| CN113076343A (en) | Data query method, device, equipment and storage medium | |
| CN112817953A (en) | Data verification method and device, computer equipment and computer-readable storage medium | |
| CN110750563A (en) | Multi-model data processing method, system, device, electronic equipment and storage medium | |
| CN110716949A (en) | Method, device, medium and electronic equipment for automatically optimizing structured query statement |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |