CN117667078A - Component development method and device, storage medium and electronic equipment - Google Patents
Component development method and device, storage medium and electronic equipment Download PDFInfo
- Publication number
- CN117667078A CN117667078A CN202311698969.6A CN202311698969A CN117667078A CN 117667078 A CN117667078 A CN 117667078A CN 202311698969 A CN202311698969 A CN 202311698969A CN 117667078 A CN117667078 A CN 117667078A
- Authority
- CN
- China
- Prior art keywords
- component
- development
- request
- components
- sending
- 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
- 238000011161 development Methods 0.000 title claims abstract description 203
- 238000000034 method Methods 0.000 title claims abstract description 61
- 230000004044 response Effects 0.000 claims abstract description 9
- 230000015654 memory Effects 0.000 claims description 18
- 238000012795 verification Methods 0.000 claims description 11
- 230000006870 function Effects 0.000 description 13
- 230000008569 process Effects 0.000 description 6
- 238000010586 diagram Methods 0.000 description 5
- 238000012545 processing Methods 0.000 description 5
- 230000005291 magnetic effect Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000010354 integration Effects 0.000 description 2
- 238000006467 substitution reaction Methods 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- KLDZYURQCUYZBL-UHFFFAOYSA-N 2-[3-[(2-hydroxyphenyl)methylideneamino]propyliminomethyl]phenol Chemical compound OC1=CC=CC=C1C=NCCCN=CC1=CC=CC=C1O KLDZYURQCUYZBL-UHFFFAOYSA-N 0.000 description 1
- 238000009530 blood pressure measurement Methods 0.000 description 1
- 230000015556 catabolic process Effects 0.000 description 1
- 230000002354 daily effect Effects 0.000 description 1
- 238000007405 data analysis Methods 0.000 description 1
- 238000006731 degradation reaction Methods 0.000 description 1
- 201000001098 delayed sleep phase syndrome Diseases 0.000 description 1
- 208000033921 delayed sleep phase type circadian rhythm sleep disease Diseases 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000003203 everyday effect Effects 0.000 description 1
- 230000005294 ferromagnetic effect Effects 0.000 description 1
- 238000011990 functional testing Methods 0.000 description 1
- 238000007689 inspection Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Abstract
The application discloses a component development method, a device, a storage medium and electronic equipment, wherein the method comprises the following steps: in response to receiving the component acquisition request, determining component characteristics of the component to be acquired based on the component acquisition request; searching the components in the component library, and if the components matched with the characteristics of the components exist in the component library, sending the components to a request end corresponding to the component acquisition request; if the component library does not have the component matched with the component characteristic, generating a component development request; the component development request is sent to the component development terminal so that the target component matched with the component characteristics is obtained through the component development terminal. The method and the device can multiplex the existing components, effectively develop the components which do not exist, improve the component development efficiency and reduce the development cost.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a method and an apparatus for developing a component, a storage medium, and an electronic device.
Background
Currently, in order for various websites and various applications to meet increasingly rich use requirements, it is often necessary to develop various components for websites and applications; the component is a simple package of data and operation methods, the component can be provided with special attributes and methods, and the use of the component can realize the functions of rapidly processing access, designing a software development method and the like.
However, in the current component development process, because the service logic of different service departments has the same amount, similar components can be developed and obtained, the efficiency of component development is reduced, and meanwhile, the cost of component development is increased.
Disclosure of Invention
Aiming at the problems, the application provides a component development method, a device, a storage medium and electronic equipment, which achieve the purposes of improving the component development efficiency and reducing the component development cost.
In order to achieve the above purpose, the present application provides the following technical solutions:
a component development method, comprising:
in response to receiving a component acquisition request, determining component characteristics of a component to be acquired based on the component acquisition request;
searching the components in a component library, and if the components matched with the component characteristics exist in the component library, sending the components to a request end corresponding to the component acquisition request;
if the component library does not have the component matched with the component characteristics, generating a component development request;
and sending the component development request to a component development end so that a target component matched with the component characteristic is obtained through the component development end.
Optionally, the method further comprises:
responding to the component development request to a component development end, and generating component development progress information of the component to be acquired based on development information of the component by the component development end;
and sending the component development progress information to a request end corresponding to the component acquisition request.
Optionally, the sending the component development request to a component development end includes:
acquiring development characteristics of the development ends of all the components;
matching the component characteristics of the component to be acquired with the development characteristics, and determining a target component development end in the component development end based on a matching result;
and sending the component development request to the target component development end.
Optionally, the method further comprises:
and responding to the development of the component development end to obtain a target component matched with the component characteristics, verifying the target component, and if the verification is passed, sending the target component to a request end corresponding to the component acquisition request.
Optionally, the sending the target component to the request end corresponding to the component obtaining request includes:
generating configuration information matched with a target component based on verification information of the target component;
and sending the configuration information and the target component to a request end corresponding to the component acquisition request.
Optionally, the method further comprises:
responding to a request end corresponding to the component acquisition request sent to the target component, and obtaining feedback information of the request end aiming at the target component;
and sending the feedback information to the component development end, so that the component development end updates the target component based on the feedback information.
Optionally, the method further comprises:
acquiring the applied information of each component in the component library;
and generating rewarding information of a component development end corresponding to the component based on the applied information, so that the component development end applies for the component development rewarding based on the rewarding information.
A component development apparatus comprising:
a first determining unit, configured to determine, in response to receiving a component acquisition request, component characteristics of a component to be acquired based on the component acquisition request;
the first sending unit is used for searching the components in the component library, and if the components matched with the characteristics of the components exist in the component library, the components are sent to a request end corresponding to the component acquisition request;
the first generation unit is used for generating a component development request if no component matched with the component characteristics exists in the component library;
and the second sending unit is used for sending the component development request to a component development end so as to enable the component development end to develop and obtain the target component matched with the component characteristics.
A storage medium storing executable instructions which when executed by a processor implement a component development method as claimed in any one of the preceding claims.
An electronic device, comprising:
a memory for storing a program;
a processor for executing the program, the program being specifically for implementing the component development method as set forth in any one of the above.
Compared with the prior art, the application provides a component development method, a device, a storage medium and an electronic device, wherein the method comprises the following steps: in response to receiving the component acquisition request, determining component characteristics of the component to be acquired based on the component acquisition request; searching the components in the component library, and if the components matched with the characteristics of the components exist in the component library, sending the components to a request end corresponding to the component acquisition request; if the component library does not have the component matched with the component characteristic, generating a component development request; the component development request is sent to the component development terminal so that the target component matched with the component characteristics is obtained through the component development terminal. The method and the device can multiplex the existing components, effectively develop the components which do not exist, improve the component development efficiency and reduce the development cost.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required to be used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only embodiments of the present application, and that other drawings may be obtained according to the provided drawings without inventive effort to a person skilled in the art.
Fig. 1 is a schematic flow chart of a component development method according to an embodiment of the present application;
fig. 2 is a schematic diagram of an application scenario provided in an embodiment of the present application;
fig. 3 is a flowchart of participation of each role provided in the embodiment of the present application;
fig. 4 is a schematic structural diagram of a scaffold for component development according to an embodiment of the present disclosure;
fig. 5 is a schematic structural diagram of a component development device according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.
The terms first and second and the like in the description and in the claims of the present application and in the above-described figures are used for distinguishing between different objects and not for describing a particular sequential order. Furthermore, the terms "comprise" and "have," as well as any variations thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to the listed steps or elements but may include steps or elements not expressly listed.
The embodiment of the application provides a component development method, a device, a storage medium and electronic equipment, wherein the method can be applied to component multiplexing among business component development departments, for example, a system architecture applying the component development method of the application embodiment can provide a component application function, so that a project developer can propose component requirements. The scaffold for component development is provided, so that a component developer can conveniently develop the component according to the standard. The component management function is provided, so that the component developer can upload the component conveniently and can be used by the project developer after the component is authenticated by the component authenticator. Meanwhile, the system has a component statistics function, so that a manager knows the current component use condition and the brought benefits. Through the embodiment of the application, the full life cycle management function of the component is realized, so that a component application actively develops and uses the component, the development cost is reduced, and the development efficiency is improved.
Referring to fig. 1, a flowchart of a component development method according to an embodiment of the present application may include the following steps:
s101, in response to receiving the component acquisition request, determining component characteristics of the component to be acquired based on the component acquisition request.
When a component acquisition request of a component request end is received, component characteristics of a component to be acquired are determined, wherein the component characteristics can comprise the type of the component to be acquired, an application scene, an execution environment, version information of the component and the like.
S102, searching the components in the component library, and if the components matched with the characteristics of the components exist in the component library, sending the components to a request end corresponding to the component acquisition request.
The component library includes a plurality of types of components, and each component has associated component specification information so that it can be determined whether there is a component matching the component characteristics of the component to be acquired, and if so, the component can be sent to the requesting end. Each component in the component library is a component developed by the previous component development end, so that the multiplexing of the components can be facilitated, when the same service logic demands exist, the previous components matched with the service logic can be multiplexed, and the repeated development of the components is avoided.
S103, if no component matched with the component characteristics exists in the component library, generating a component development request.
And S104, sending the component development request to a component development end so that a target component matched with the component characteristics is obtained through the component development end.
If there are no components in the component library that match the component characteristics, a component development request may be generated. The component development request may be sent to an internal component development platform to enable the component development end to claim the component development request for component development. The component development request can also be directly sent to the component development end by determining the component development end suitable for development based on the characteristics of the component, so that the component development end can complete the development of the component.
In order to enable the component acquisition request corresponding request end to acquire development progress of the component of the requirement in real time. In one implementation manner of the embodiment of the present application, in response to sending the component development request to a component development end, generating component development progress information of the component to be acquired based on development information of the component by the component development end; and sending the component development progress information to a request end corresponding to the component acquisition request.
For example, the information of the business personnel developing the component, the development progress of the component, the architecture or configuration information of developing the component and the like can be used for generating the development progress information of the component, so that the request end can acquire the development progress of the component and related information in real time.
In an embodiment of the present application, the sending the component development request to the component development end includes:
acquiring development characteristics of the development ends of all the components;
matching the component characteristics of the component to be acquired with the development characteristics, and determining a target component development end in the component development end based on a matching result;
and sending the component development request to the target component development end.
In this embodiment, the development characteristics of the development end may be determined based on the fields in which the respective component development ends are good, the types of components that have been previously developed, or the current component development workload, etc., as a target component development end by which the development of the current component to be developed is completed for matching the component to be developed to the optimal component development end. For example, if there are two component development ends (such as business personnel) that can complete the development of the current component, the component development end with lower workload can be selected as the target component development end, so that the component development can be completed most efficiently.
In order to ensure that the developed components can be successfully applied, the method further comprises the following steps:
and responding to the development of the component development end to obtain a target component matched with the component characteristics, verifying the target component, and if the verification is passed, sending the target component to a request end corresponding to the component acquisition request.
After the development of the component is completed, the performance of the component needs to be verified, and the component can be stored in a component library after the verification is passed or sent to a request end corresponding to the component acquisition request.
Further, the sending the target component to the request end corresponding to the component obtaining request includes:
generating configuration information matched with a target component based on verification information of the target component;
and sending the configuration information and the target component to a request end corresponding to the component acquisition request.
When the component is published in the component library or before the component is sent to the request end corresponding to the component acquisition request, the configuration information of the component can be determined according to the development environment, the code type, the verification process and the like when the component is developed, for example, the configuration information can comprise the application environment, the execution architecture or some problems possibly existing in the component, so that the request end can accurately apply the component based on the configuration information.
In order to ensure the accuracy of the components in the application process, the components in the component library can be updated and perfected based on feedback information applied to the components in the component library. Correspondingly, the method further comprises the following steps:
responding to a request end corresponding to the component acquisition request sent to the target component, and obtaining feedback information of the request end aiming at the target component; and sending the feedback information to the component development end, so that the component development end updates the target component based on the feedback information.
In order to encourage service developers to develop components across departments, promote resource integration, and avoid waste of development resources, in one implementation manner of the embodiment of the application, the method further includes: acquiring the applied information of each component in the component library; and generating rewarding information of a component development end corresponding to the component based on the applied information, so that the component development end applies for the component development rewarding based on the rewarding information.
The information to be applied to the component may be determined according to the number of downloads for the component, the number of collections for the component, and the information of interest of the component. And setting a corresponding rewarding parameter for each type of applied information, thereby obtaining rewarding information. For example, if the component is downloaded 5 times and is collected once, the calculated bonus information is a bonus score of 17.
The component development method of the embodiment of the present application is described below with a specific application scenario. The application scene comprises three parts of component application, component development and component management. The project developer, namely, a user of the component, can apply for generating a component acquisition request through the component, the component developer performs component development, and a component manager (called a leader for short) realizes management and maintenance of the component.
Referring to fig. 2 and fig. 3, fig. 2 is a schematic diagram of an application scenario provided by an embodiment of the present application, and fig. 3 is a flowchart of participation of each character provided by an embodiment of the present application. In the process of doing project development, a project developer can search for a use function from the components in the component management module to find out whether components are available for the project. If yes, the component application function is directly used, and if no component application function can be applied through the component, the requirement description of the component is clear. The following component application information needs to be provided:
applicant name, applicant contact mailbox, application department, component name, application reason (main functional description of the component).
For example, the project developer can see the status of the self-applied component through the my component application module of the component development application of the component request end, and whether the corresponding component has been developed.
After the component developer sees the component application submitted by the project developer, the component developer can quickly develop the component through the component development scaffold. The purpose of the component development scaffold function is to provide standards for the development of components. Referring to fig. 4, a schematic structural diagram of a scaffold for component development is provided in an embodiment of the present application. Component scaffolds provide a complete infrastructure architecture such as journaling, link tracking, monitoring, continuous integration, continuous deployment, etc. The component scaffold provides coding specifications, and improves code quality, such as static code inspection, unit test specifications and coverage rate detection, basic language coding specifications, exception handling, pressure measurement and the like. Component scaffolding provides system stability support such as fault tolerance, fuse degradation, etc. Based on the assembly scaffold, the assembly can be developed quickly, stably and with high quality in a standardized way.
The component management comprises 5 modules of component loading, my component, component authentication, component search use and component statistics.
Specifically, when a component developer develops a component according to the requirements of a component application through a component scaffold, and after the component is tested and put on line, the component can be put on the shelf through a component put-on-shelf module. The following component information needs to be provided:
component classification, component code warehouse address, component name, component number, component coding language, component usage description document address, component code number, associated component application, upper carrier name, upper carrier head portrait, other component participation developer, upper carrier contact mailbox, upper carrier department, component main function description, component version information, component authentication state, cost and labor saving.
The status of the self-racking component can be seen through the My component module, including how many items are used, praise and collect the component. Saving cost and manpower. And meanwhile, the component information is updated along with the version updating iteration of the component.
After the components are put on shelf, professional component certification personnel are organized together to evaluate whether the components provide corresponding materials such as use documents, functional test documents, and pressing performance reports according to the standard, and simultaneously evaluate whether the saved cost and labor are real. After the component is successfully authenticated, the developer on behalf of the project can use the component with confidence.
After the authentication of the components is finished, a project developer can inquire the components needed to be used through the component searching and using module during project development and use the components according to the component using documents. The component search usage module scans the code repository (commonly known as gitlab) daily on a regular basis, analyzes which items the component is used by depending on the manner in which the component is introduced, and records it. For example, java items may scan a pon file and Golang items may scan a go.sum file.
To encourage component developers to develop more components, the component statistics module may time the component's praise, collection, and use leaderboards. And meanwhile, the leader can see the number of components developed by the component developer and the cost and manpower resource saved for the company.
Taking the development of wallpaper systems as an example, a project developer needs to analyze the project to use definition-related functions, and if the project developer develops the project by himself, the project developer spends a long period of time. Since sharpness-related functionality may be required for other projects as well, a decision is made to search the component development platform for related directly reusable components. And when no corresponding component is found after searching, the project developer submits a component application through a component application page. After the component application is submitted, the corresponding component application can be seen in the component application page, and editing can be performed, for example, information in the component application is modified.
After receiving the component application, the component developer develops the component through the component development scaffold module according to the functional description of the component application. And after the component developer develops the definition service component and goes on line through testing, the component is put on shelf. After the component is put on shelf, the component developer can see praise, collection and use times in the module of 'My component', calculate the total labor and cost saving, and also can carry out version update iteration. The assembly is put on shelf, and professional assembly reviewers can evaluate the assembly document completeness, labor and cost saving authenticity. After the certification is passed, the project developer can use the certified components with confidence. The component searches the code warehouse by the using module every day and scans the code warehouse regularly, and records the definition service used by the wallpaper item and adds one to the using frequency of the definition service component. The component statistics module calculates a ranking list of the number of developed components or the number of downloaded, praise and collection of the developed components for each component developer. And meanwhile, data analysis is carried out on all the components to lead and view the project. Such as total number of components, number of access items, cost saving and labor saving. The development of the wallpaper project can be rapidly completed by the project developer through the definition component, and meanwhile, if codes which can be commonly used exist in the development process of the wallpaper project, the codes can also be added through the component development platform to form a component, so that the subsequent use of other projects is facilitated.
Also provided in an embodiment of the present application is a component development apparatus, referring to fig. 5, the apparatus may include:
a first determining unit 201, configured to determine, in response to receiving a component acquisition request, component characteristics of a component to be acquired based on the component acquisition request;
a first sending unit 202, configured to perform component search in a component library, and send a component to a request end corresponding to the component obtaining request if a component matched with the component feature exists in the component library;
a first generating unit 203, configured to generate a component development request if no component matching the component feature exists in the component library;
and the second sending unit 204 is configured to send the component development request to a component development end, so that a target component matched with the component feature is obtained through the component development end.
Optionally, the apparatus further comprises:
the second generating unit is used for responding to the component development request and sending the component development request to a component development end, and generating component development progress information of the component to be acquired based on the development information of the component by the component development end;
and the third sending unit is used for sending the component development progress information to a request end corresponding to the component acquisition request.
Optionally, the second transmitting unit includes:
the first acquisition subunit is used for acquiring development characteristics of the development ends of the components;
the matching subunit is used for matching the component characteristics of the component to be acquired with the development characteristics and determining a target component development end in the component development ends based on a matching result;
and the first sending subunit is used for sending the component development request to the target component development end.
Optionally, the method further comprises:
and the verification unit is used for responding to the development of the component development end to obtain a target component matched with the component characteristics, verifying the target component, and if the verification is passed, transmitting the target component to a request end corresponding to the component acquisition request.
Optionally, the second sending unit is specifically configured to:
generating configuration information matched with a target component based on verification information of the target component;
and sending the configuration information and the target component to a request end corresponding to the component acquisition request.
Optionally, the method further comprises:
the feedback information acquisition unit is used for responding to a request end corresponding to the component acquisition request and sending the target component to acquire feedback information of the request end for the target component;
and the feedback information sending unit is used for sending the feedback information to the component development end so that the component development end updates the target component based on the feedback information.
Optionally, the method further comprises: a bonus information generation unit for:
acquiring the applied information of each component in the component library;
and generating rewarding information of a component development end corresponding to the component based on the applied information, so that the component development end applies for the component development rewarding based on the rewarding information.
Based on the foregoing embodiments, embodiments of the present application provide a storage medium storing executable instructions that when executed by a processor implement a component development method as described in any one of the foregoing.
The embodiment of the application also provides electronic equipment, which comprises:
a memory for storing a program;
a processor for executing the program, the program being specifically for implementing the component development method as set forth in any one of the above.
The processor or CPU may be at least one of an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a digital signal processor (Digital Signal Processor, DSP), a digital signal processing device (Digital Signal Processing Device, DSPD), a programmable logic device (Programmable Logic Device, PLD), a field programmable gate array (Field Programmable Gate Array, FPGA), a Central processing unit (Central ProcessingUnit, CPU), a controller, a microcontroller, and a microprocessor. It will be appreciated that the electronic device implementing the above-mentioned processor function may be other, and embodiments of the present application are not specifically limited.
It should be noted that the computer storage medium/Memory may be a Read Only Memory (ROM), a programmable Read Only Memory (Programmable Read-OnlyMemory, PROM), an erasable programmable Read Only Memory (Erasable Programmable Read-Only Memory, EPROM), an electrically erasable programmable Read Only Memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), a magnetic random access Memory (Ferromagnetic RandomAccess Memory, FRAM), a flash Memory (flash Memory), a magnetic surface Memory, an optical disk, or a Read Only optical disk (Compact Disc Read-Only Memory, CD-ROM), etc.; but may also be various terminals such as mobile phones, computers, tablet devices, personal digital assistants, etc., that include one or any combination of the above-mentioned memories.
In the several embodiments provided in this application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above described device embodiments are only illustrative, e.g. the division of the units is only one logical function division, and there may be other divisions in practice, such as: multiple units or components may be combined or may be integrated into another system, or some features may be omitted, or not performed. In addition, the various components shown or discussed may be coupled or directly coupled or communicatively coupled to each other via some interface, whether indirectly coupled or communicatively coupled to devices or units, whether electrically, mechanically, or otherwise.
The units described as separate units may or may not be physically separate, and units displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units; some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in each embodiment of the present application may be integrated in one processing module, or each unit may be separately used as one unit, or two or more units may be integrated in one unit; the integrated units may be implemented in hardware or in hardware plus software functional units. Those of ordinary skill in the art will appreciate that: all or part of the steps for implementing the above method embodiments may be implemented by hardware associated with program instructions, where the foregoing program may be stored in a computer readable storage medium, and when executed, the program performs steps including the above method embodiments; and the aforementioned storage medium includes: a mobile storage device, a Read-Only Memory (ROM), a random access Memory (RandomAccess Memory, RAM), a magnetic disk or an optical disk, or the like, which can store program codes.
The methods disclosed in the several method embodiments provided in the present application may be arbitrarily combined without collision to obtain a new method embodiment.
The features disclosed in the several product embodiments provided in the present application may be combined arbitrarily without conflict to obtain new product embodiments.
The features disclosed in the several method or apparatus embodiments provided in the present application may be arbitrarily combined without conflict to obtain new method embodiments or apparatus embodiments.
The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
In the present specification, each embodiment is described in a progressive manner, and each embodiment is mainly described in a different point from other embodiments, and identical and similar parts between the embodiments are all enough to refer to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant points refer to the description of the method section.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. A component development method, comprising:
in response to receiving a component acquisition request, determining component characteristics of a component to be acquired based on the component acquisition request;
searching the components in a component library, and if the components matched with the component characteristics exist in the component library, sending the components to a request end corresponding to the component acquisition request;
if the component library does not have the component matched with the component characteristics, generating a component development request;
and sending the component development request to a component development end so that a target component matched with the component characteristic is obtained through the component development end.
2. The method according to claim 1, wherein the method further comprises:
responding to the component development request to a component development end, and generating component development progress information of the component to be acquired based on development information of the component by the component development end;
and sending the component development progress information to a request end corresponding to the component acquisition request.
3. The method of claim 1, wherein the sending the component development request to a component development terminal comprises:
acquiring development characteristics of the development ends of all the components;
matching the component characteristics of the component to be acquired with the development characteristics, and determining a target component development end in the component development end based on a matching result;
and sending the component development request to the target component development end.
4. The method as recited in claim 1, further comprising:
and responding to the development of the component development end to obtain a target component matched with the component characteristics, verifying the target component, and if the verification is passed, sending the target component to a request end corresponding to the component acquisition request.
5. The method of claim 4, wherein the sending the target component to the requesting end corresponding to the component acquisition request comprises:
generating configuration information matched with a target component based on verification information of the target component;
and sending the configuration information and the target component to a request end corresponding to the component acquisition request.
6. The method as recited in claim 5, further comprising:
responding to a request end corresponding to the component acquisition request sent to the target component, and obtaining feedback information of the request end aiming at the target component;
and sending the feedback information to the component development end, so that the component development end updates the target component based on the feedback information.
7. The method as recited in claim 1, further comprising:
acquiring the applied information of each component in the component library;
and generating rewarding information of a component development end corresponding to the component based on the applied information, so that the component development end applies for the component development rewarding based on the rewarding information.
8. A component development apparatus, comprising:
a first determining unit, configured to determine, in response to receiving a component acquisition request, component characteristics of a component to be acquired based on the component acquisition request;
the first sending unit is used for searching the components in the component library, and if the components matched with the characteristics of the components exist in the component library, the components are sent to a request end corresponding to the component acquisition request;
the first generation unit is used for generating a component development request if no component matched with the component characteristics exists in the component library;
and the second sending unit is used for sending the component development request to a component development end so as to enable the component development end to develop and obtain the target component matched with the component characteristics.
9. A storage medium storing executable instructions which when executed by a processor implement the component development method of any one of claims 1 to 7.
10. An electronic device, comprising:
a memory for storing a program;
a processor for executing the program, in particular for implementing the component development method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311698969.6A CN117667078A (en) | 2023-12-11 | 2023-12-11 | Component development method and device, storage medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311698969.6A CN117667078A (en) | 2023-12-11 | 2023-12-11 | Component development method and device, storage medium and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117667078A true CN117667078A (en) | 2024-03-08 |
Family
ID=90073134
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311698969.6A Pending CN117667078A (en) | 2023-12-11 | 2023-12-11 | Component development method and device, storage medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117667078A (en) |
-
2023
- 2023-12-11 CN CN202311698969.6A patent/CN117667078A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107896244B (en) | Version file distribution method, client and server | |
| CN111723313A (en) | Page jump processing method, device, equipment and storage medium | |
| CN106844730B (en) | Method and device for displaying file content | |
| CN111045944A (en) | Regression testing method, device and system and computer readable storage medium | |
| CN111522738A (en) | Test method and device of micro-service system, storage medium and electronic equipment | |
| CN103246606A (en) | Method and system for testing performances of ESB (enterprises service bus) platform | |
| CN113448854A (en) | Regression testing method and device | |
| CN112835808A (en) | Interface testing method and device, computer equipment and storage medium | |
| CN112650688A (en) | Automated regression testing method, associated device and computer program product | |
| CN107368407B (en) | Information processing method and device | |
| CN111367531A (en) | Code processing method and device | |
| CN106557419B (en) | Program testing method and device | |
| CN111651342A (en) | HTTP interface automation testing framework based on Charles recording session | |
| CN112486833B (en) | Software testing system and method capable of dynamically reconstructing on demand and oriented to software defined satellite | |
| CN117493188A (en) | Interface testing method and device, electronic equipment and storage medium | |
| CN110134583B (en) | Software testing and data processing method and device | |
| CN109101408B (en) | Method and device for detecting service availability in joint debugging environment | |
| CN106484601B (en) | User data analysis method and system for client | |
| CN109542496B (en) | Method, device and system for determining incremental code | |
| CN111913880A (en) | Application software testing method and device | |
| CN117667078A (en) | Component development method and device, storage medium and electronic equipment | |
| CN113591079A (en) | Method and device for acquiring abnormal application installation package and electronic equipment | |
| CN114416546A (en) | Code coverage rate determining method and device | |
| CN113064814A (en) | Processing method and device of component reference data, storage medium and electronic device | |
| CN112433946A (en) | Interface test management method, device, equipment and storage medium |
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 |