CN110688096B - Method and device for constructing application program containing plug-in, medium and electronic equipment - Google Patents
Method and device for constructing application program containing plug-in, medium and electronic equipment Download PDFInfo
- Publication number
- CN110688096B CN110688096B CN201910854862.3A CN201910854862A CN110688096B CN 110688096 B CN110688096 B CN 110688096B CN 201910854862 A CN201910854862 A CN 201910854862A CN 110688096 B CN110688096 B CN 110688096B
- Authority
- CN
- China
- Prior art keywords
- function component
- plug
- description
- functional
- function
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 45
- 238000009434 installation Methods 0.000 claims abstract description 53
- 238000004806 packaging method and process Methods 0.000 claims abstract description 10
- 230000006870 function Effects 0.000 claims description 236
- 238000004590 computer program Methods 0.000 claims description 2
- 230000008569 process Effects 0.000 abstract description 7
- 238000011161 development Methods 0.000 description 14
- 238000012545 processing Methods 0.000 description 8
- 238000010586 diagram Methods 0.000 description 7
- 238000010276 construction Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 238000004422 calculation algorithm Methods 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 239000013307 optical fiber Substances 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000008520 organization 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
- 230000001360 synchronised effect Effects 0.000 description 1
- 230000002123 temporal effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The disclosure relates to the field of software development, and discloses a method, a device, a medium and electronic equipment for constructing an application program containing a plug-in. The method comprises the following steps: acquiring a demand document in a preset format of a first application program; according to the function component description in the requirement document, determining a function component identifier to be developed in a plug-in mode from function component identifiers corresponding to the function component description as a plug-in function component identifier; the plug-in function component identification and the corresponding function component description are sent to a developer terminal, so that the developer can develop a function component plug-in installation package; after the engineering codes corresponding to the descriptions of other functional components are developed, packaging all the engineering codes into an engineering installation package; and loading the functional component plug-in installation package into the engineering installation package to obtain the first application program. Under the method, the efficiency of selecting the functional components to be plugged in the whole software development process is improved, so that the efficiency of the software development is improved as a whole.
Description
Technical Field
The disclosure relates to the technical field of software development, and in particular relates to a method, a device, a medium and electronic equipment for constructing an application program containing a plug-in.
Background
With the advent of the internet, especially the mobile internet, the functions of the application program are more and more complex, the version of the application program needs to be updated and iterated continuously, the development of the plug-in software package can improve the updating efficiency of the version of the application program, and when the user does not need to use the functions of the plug-in, the plug-in does not occupy the storage space of the user equipment. However, since the integration level of an application program is high, the functional components are complex, so that when the functional components are selected to develop the plug-ins, the selection process is complex, the development efficiency is low, and how to efficiently select the appropriate functional components in the highly integrated application program to realize plug-ins is a problem to be solved by those skilled in the art.
Disclosure of Invention
In order to solve the above technical problems in the technical field of software development, an object of the present disclosure is to provide a method, an apparatus, a medium, and an electronic device for constructing an application program including a plug-in.
According to an aspect of the present application, there is provided a method for constructing an application program including a plug-in, the method including:
Before a first application program is developed, acquiring a requirement document in a preset format corresponding to the first application program, wherein the requirement document comprises a plurality of function component descriptions, and the function component descriptions correspond to identifications of the function components;
according to the description of the functional components in the requirement document, determining the identification of the functional components required to be developed in a plug-in mode from the identifications of the functional components corresponding to the description of each functional component as plug-in functional component identifications;
the plug-in function component identification and the function component description corresponding to the plug-in function component identification are sent to a developer terminal, so that a developer develops a function component plug-in installation package corresponding to the plug-in function component identification according to the function component description corresponding to the plug-in function component identification;
when the engineering codes corresponding to the function component descriptions except the function component description corresponding to the plug-in function component identifier in the function component descriptions are developed, packaging all the engineering codes into an engineering installation package;
and loading the functional component plug-in installation package to the engineering installation package to obtain the first application program.
According to another aspect of the present application, there is provided a construction apparatus for an application program including a plug-in, the apparatus including:
a required document acquisition module configured to acquire a required document in a preset format corresponding to a first application program before the first application program is developed, the required document including a plurality of function component descriptions, the function component descriptions corresponding to identifications of the function components;
the determining module is configured to determine the identification of the functional component to be developed according to the plug-in mode from the identifications of the functional components corresponding to each functional component description according to the functional component description in the requirement document, and the identification is used as the plug-in functional component identification;
the sending module is configured to send the plug-in function component identifier and the function component description corresponding to the plug-in function component identifier to a developer terminal, so that the developer develops a function component plug-in installation package corresponding to the plug-in function component identifier according to the function component description corresponding to the plug-in function component identifier;
the packaging module is configured to package all the engineering codes into one engineering installation package after the engineering codes corresponding to the functional component descriptions except the functional component description corresponding to the plug-in functional component identifier in the functional component descriptions are developed;
And the loading module is configured to load the functional component plug-in installation package to the engineering installation package to obtain the first application program.
According to another aspect of the present application, there is provided a computer readable program medium storing computer program instructions which, when executed by a computer, cause the computer to perform the method as described above.
According to another aspect of the present application, there is provided an electronic device including:
a processor;
a memory having stored thereon computer readable instructions which, when executed by the processor, implement a method as described above.
The technical scheme provided by the embodiment of the invention can comprise the following beneficial effects:
the method for constructing the application program comprising the plug-in comprises the following steps: before a first application program is developed, acquiring a requirement document in a preset format corresponding to the first application program, wherein the requirement document comprises a plurality of function component descriptions, and the function component descriptions correspond to identifications of the function components; according to the description of the functional components in the requirement document, determining the identification of the functional components required to be developed in a plug-in mode from the identifications of the functional components corresponding to the description of each functional component as plug-in functional component identifications; the plug-in function component identification and the function component description corresponding to the plug-in function component identification are sent to a developer terminal, so that a developer develops a function component plug-in installation package corresponding to the plug-in function component identification according to the function component description corresponding to the plug-in function component identification; when the engineering codes corresponding to the function component descriptions except the function component description corresponding to the plug-in function component identifier in the function component descriptions are developed, packaging all the engineering codes into an engineering installation package; and loading the functional component plug-in installation package to the engineering installation package to obtain the first application program.
According to the method, the detail of the development task of the application program can be truly reflected by the requirement document, which functional components are to be developed into plug-ins can be accurately determined according to the description of the functional components in the requirement document, so that efficient selection of the functional components to be plugged is realized, and on the basis, the application can be quickly realized by loading the developed functional component plug-in installation package onto the engineering installation package, and the development efficiency of the application program containing plug-ins is 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 invention as claimed.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.
FIG. 1 is an application scenario diagram illustrating a method of building an application program including a plug-in, according to an example embodiment;
FIG. 2 is a flowchart illustrating a method of building an application containing plug-ins, according to an example embodiment;
FIG. 3 is a flowchart illustrating details of step 220 according to one embodiment shown in the corresponding embodiment of FIG. 2;
FIG. 4 is a flowchart showing details of step 220 according to another embodiment shown in the corresponding embodiment of FIG. 2;
FIG. 5 is a block diagram illustrating a build device for an application containing plug-ins, according to an example embodiment;
FIG. 6 is an exemplary block diagram of an electronic device implementing a method of building an application containing plug-ins as described above, according to an exemplary embodiment;
fig. 7 is a computer-readable storage medium embodying a construction method of the above-described application program including a plug-in, according to an exemplary embodiment.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the invention. Rather, they are merely examples of apparatus and methods consistent with aspects of the invention as detailed in the accompanying claims.
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 a repetitive description thereof 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.
The present disclosure first provides a method for building an application program including a plug-in. An application may be any collection of program code that utilizes a computer to solve a certain class of problems, where the application is not a plug-in host application, but rather a combination of plug-in and host applications. Plug-in is a program written by an application program interface conforming to a certain specification, a Plug-in cannot be executed by an application program containing the Plug-in, a Plug-in can assist an application program in realizing functions not possessed by some application programs, and an application program can contain various objects such as calling codes, function libraries, data and the like, and the objects can be used for the Plug-in to execute specific functions. The construction of the application program including the plug-in means that the organization generates an application program including the plug-in, and when the generated application program is installed in the corresponding terminal and executed, the function of the application program itself can be executed, or the function of the plug-in can be executed.
The implementation terminal of the present disclosure may be any device having an operation and processing function, which may be connected to an external device, for receiving or transmitting data, and may specifically be a portable mobile device, such as a smart phone, a tablet computer, a notebook computer, PDA (Personal Digital Assistant), or a fixed device, such as a computer device, a field terminal, a desktop computer, a server, a workstation, or the like, or may be a collection of multiple devices, such as a physical infrastructure of cloud computing.
Preferably, the implementation terminal of the present disclosure may be a server or a physical infrastructure of cloud computing.
Fig. 1 is an application scenario diagram illustrating a method of building an application program including a plug-in according to an exemplary embodiment. As shown in fig. 1, the system includes a server 110, a database 120, and a development terminal 130, where the database 120 and the development terminal 130 are respectively connected to the server 110 through a communication link, in this embodiment, the server 110 is an implementation terminal of the disclosure, and the development terminal 130 is a terminal used by an application developer, and may be any device with an operation and processing function, which may be the same type of terminal as the implementation terminal of the disclosure, or may be a different type of terminal, or may be the same terminal as the implementation terminal of the disclosure, or may be a different terminal, for example, the development terminal may be a notebook computer or a desktop computer. When a software developer needs to use the development terminal 130 to develop a project, for example, develop an App (Application) under a client or a mobile operating system such as Android and IOS, if the developed project is a large-scale project, it is necessary to integrate numerous functions, and it may be necessary to develop components of one or more functions into plug-ins, but how to select components of appropriate functions from the projects integrating numerous functions for plug-ins is a problem of the developer. In this embodiment, the database 120 stores the requirement document of the application program to be developed, and the implementation terminal-server 110 of the present disclosure, after obtaining the requirement document of the application program to be developed from the database 120, can automatically and accurately feed back which functional components need to be plugged into the developer according to the requirement document, so as to help the developer to quickly locate the development object, thereby improving the development efficiency.
It should be noted that, although in the present embodiment, the implementation terminal of the present disclosure is a server and the requirement document of the application program is stored in the database, in other embodiments or specific applications, various terminals may be selected as implementation terminals of the present disclosure as required, and the requirement document of the application program may be stored on any same or different terminals, which is not limited in any way, and the protection scope of the present disclosure should not be limited in any way.
FIG. 2 is a flowchart illustrating a method of building an application containing plug-ins, according to an example embodiment. The embodiment may be executed by the foregoing server, as shown in fig. 2, and may include the following steps:
step 210, before developing a first application program, obtaining a requirement document corresponding to a preset format of the first application program.
The requirements document includes a plurality of function component descriptions corresponding to identifications of the function components.
The first application may be a program written in any one or more languages, such as Java, C++, etc.
The preset format may be any format capable of recording text information, for example, a Json format. xml format, word format, excel format, etc.
The requirement document is a document which is artificially written and used for guiding the development and design of the software, and can be called as a software requirement specification, and can contain various contents for guiding the development of the software, such as development principles, design standards, functional module definition and outline.
By setting the preset format for the demand document, the format of the content in the demand document can be kept fixed, so that specific content can be conveniently and accurately extracted from the demand document.
In one embodiment, the step of obtaining a requirement document in a preset format corresponding to the first application is performed according to a request sent by a developer to obtain an identification of a functional component that needs to be developed in a plug-in manner, wherein the request is sent before the first application is developed.
In one embodiment, the request sent by the developer to obtain the identifier of the functional component to be developed according to the plug-in mode carries the identifier of the first application program, and the obtaining the requirement document corresponding to the preset format of the first application program includes: after receiving a request for acquiring the identification of the functional component required to be developed in a plug-in mode from the developer, acquiring the identification of the first application program in the request; and inquiring a demand document in a preset format corresponding to the identification in a preset database by using the identification, wherein the demand document is used as the demand document in the preset format corresponding to the first application program.
In one embodiment, the implementation terminal of the present disclosure is a terminal used by the developer.
In one embodiment, the developer sends a request to obtain an identification of the functional component that needs to be developed in a plug-in manner is sent using a terminal other than the implementation terminal of the present disclosure.
Functional components are program modules or units capable of performing a particular function, and are the basic units divided in functions throughout an application. Functional component descriptions are listing of one or more of the functional component's principles, implementation purposes, technical details, technical flow, actions, etc., typically in text format, and may contain letters, numbers, words, etc. When a developer reads a description of a functional component, the developer can generally understand how the functional component is developed, what functions the developed functional component can specifically perform, the standards or requirements of the developed functional component, and the like.
In one embodiment, before the first application program is developed, the obtaining the requirement document corresponding to the preset format of the first application program includes:
before a first application program is developed, judging whether a requirement document corresponding to the first application program is in a preset format or not;
If the demand document is not in the preset format, acquiring the demand document and converting the demand document into the preset format to obtain the demand document in the preset format;
and if the demand document is in the preset format, acquiring the demand document in the preset format.
For example, the requirement document may be in json format, and the preset format may be word format, and then the json format may be converted into word format.
Step 220, determining the identification of the functional components to be developed according to the plug-in mode from the identifications of the functional components corresponding to each functional component description according to the functional component descriptions in the requirement document, and taking the identification as the plug-in functional component identification.
The identity of the functional component is an identity for uniquely determining the identity of the functional component.
In one embodiment, the identification of the functional component is a string specific to the functional component. The string may be composed of letters, numbers, underlines, etc.
In one embodiment, the identification of the functional component is the name of the functional component.
In one embodiment, the function component descriptions and the identities of the function components corresponding to each function component description are stored in a requirements document corresponding to a preset format of the first application program.
In one embodiment, the function component descriptions and the identities of the function components corresponding to each function component description are stored in a preset function component description and function component identity correspondence table, and the identities of the function components corresponding to each function component description can be obtained by querying the table.
In one embodiment, the specific steps of step 220 may be as shown in FIG. 3. FIG. 3 is a flowchart diagram of details of step 220 according to one embodiment shown in the corresponding embodiment of FIG. 2, as shown in FIG. 3, may include the steps of:
step 221, determining the number of characters contained in each functional component description in the requirements document.
In one embodiment, each functional component in the requirement document is described as a first character string, and each first character string has a one-to-one correspondence with a preset second character string, and before determining the number of characters contained in each functional component description in the requirement document, the method may further include: and acquiring each first character string corresponding to the preset second character string as a functional component description in the requirement document.
In one embodiment, a counter is embedded in the implementation terminal of the present disclosure, and the number of characters contained in each functional component description in the requirement document can be calculated by using the counter.
Step 222, obtaining the plug-in function component identification from the identifications of the function components corresponding to the function component descriptions based on the number of characters contained in the function component descriptions.
In one embodiment, the obtaining the plug-in function component identifier based on the number of characters contained in each function component description in the identifier of the function component corresponding to each function component description includes:
acquiring the function component description with the largest number of contained characters;
and the identification of the functional component corresponding to the acquired functional component description is used as the plug-in functional component identification.
The functional components are software components, consisting of multiple lines of code. Because the larger the number of characters described by one functional component is, the more code quantity contained by the corresponding functional component described by the functional component is indicated, and the more memory space of the user equipment is occupied when the corresponding functional component is integrated on the application program, by using the identification of the functional component corresponding to the functional component description with the largest number of contained characters as the plug-in functional component identification, a developer can plug-in the functional component with the larger code quantity when developing, so that a part of the larger memory space occupied in the application program is realized in a plug-in mode, and when the user does not need to execute the function of the plug-in, the codes and resources of the plug-in do not need to be stored in the local of the equipment, thereby improving the effect of saving the memory space of the plug-in; meanwhile, the higher the possibility of loopholes of the functional components with more code quantity, the higher the possibility of requirements for updating the functional components with more code quantity, and the convenience of updating and upgrading the software is further improved by inserting the functional components with more code quantity.
In one embodiment, the code amount is the number of lines of code.
In one embodiment, the obtaining the plug-in function component identifier based on the number of characters contained in each function component description in the identifier of the function component corresponding to each function component description includes:
sorting the descriptions of the functional components from large to small according to the number of the contained characters;
the identification of the functional components corresponding to the description of the functional components which are sequenced in the previous preset number is obtained and used as the identification of the plug-in functional components.
In one embodiment, the functional component descriptions are sorted from large to small by the number of characters contained using a bubble sorting algorithm.
The preset number may be an arbitrarily set value, for example, when the predetermined number is 5, the identification of the functional component corresponding to the functional component description of the preceding 5 ordered from large to small in terms of the number of contained characters is the plug-in functional component identification.
Since the number of characters included in the descriptions of the functional components in the previous sequence from large to small according to the number of the characters included is generally large, this means that the functions of the corresponding functional components described by the functional components may be complex, and when the functional components are developed, the code amount for implementing the functional components is increased due to the complex functions, so that the memory space occupied by the functional components is large. The embodiment has the advantages that on one hand, a plurality of functional components which possibly occupy larger storage when being developed into the functional components are realized by means of the plug-in, so that the effect of saving the storage space of the plug-in is further improved; on the other hand, the preset number is set to enable the number of the selected plug-in function component identifiers to be stable, and therefore the number of plug-ins developed for the first application program can be kept in a stable range.
In one embodiment, the obtaining the plug-in function component identifier based on the number of characters contained in each function component description in the identifier of the function component corresponding to each function component description includes:
acquiring a functional component description of which the number of contained characters is larger than a preset character number threshold;
and the identification of the functional component corresponding to the acquired functional component description is used as the plug-in functional component identification.
As described above, the number of characters contained in the description of the functional component is generally in positive correlation with the amount of code used for developing the corresponding functional component and the storage space occupied by developing the corresponding functional component, when the number of characters contained in one description of the functional component is sufficiently small, it is indicated that the amount of code used for developing the corresponding functional component is generally not large, and accordingly, the storage space occupied by the corresponding functional component is not large, in this case, the number of characters contained in the description of the functional component is filtered by using the preset character number threshold, so that the functional components corresponding to the descriptions of the functional components can be integrated in an application program when being implemented, and it is ensured that the number of characters contained in the description of the functional component corresponding to the obtained plug-in functional component identifier is sufficiently large, so that the storage space of the user equipment can be saved to a large extent, and meanwhile, the larger the storage space occupied by the functional component is also more likely to need to be updated, the update efficiency of the whole application software is improved, and the convenience of updating the application software is ensured.
In one embodiment, the obtaining the plug-in function component identifier based on the number of characters contained in each function component description in the identifier of the function component corresponding to each function component description includes:
sorting the descriptions of the functional components from large to small according to the number of the contained characters;
if the number of characters contained in the ordered function component description with the sequence number being the preset value is larger than a preset character number threshold value, taking the identification of the function component corresponding to the function component description with the sequence number being smaller than the preset value as a plug-in function component identification;
if the number of the characters contained in the ordered function component description with the sequence number of the preset value is smaller than the preset character number threshold value, acquiring the function component description with the number of the characters contained reaching the preset character number threshold value;
and taking the identification of the functional component corresponding to the acquired functional component description as the plug-in functional component identification.
In one embodiment, the feature descriptions are sorted from large to small by the number of characters contained using a fast sort or merge sort algorithm.
It is easy to understand that any two of the description of the functional component, the identification of the functional component and the functional component to be developed are in a one-to-one correspondence relationship, and as described above, the number of characters contained in the description of the functional component is generally in a positive correlation relationship with the code amount corresponding to the functional component to be developed and the storage space occupied by the corresponding functional component to be developed, in this embodiment, on one hand, when the number of characters contained in the description of the ordered functional component with the sequence number of the predetermined value is smaller than the threshold value of the predetermined number of characters, the identification of the functional component corresponding to the description of the functional component with the number of the characters contained reaching the threshold value of the predetermined number of characters is used as the identification of the pluggable functional component, that is, the functional component to be developed with a larger code amount is pluggable, so that the functional component to be pluggable has a sufficient code amount, and therefore the developed pluggable unit can save the storage space of the user equipment to a large extent, and the updating efficiency of the whole application software is improved; on the other hand, when the number of characters contained in the sorted functional component description with the sequence number of the predetermined value is smaller than the predetermined character number threshold, the number of the selected plug-in functional component identifiers is limited by using the sorted sequence number, so that the number of the selected plug-in functional component identifiers is stable, and further, the number of plug-ins developed for the first application program can be maintained within a stable range, so that the balance between the number of the plug-in functional components and the code quantity of the functional components to be plugged in is considered in the embodiment.
Continuing back to fig. 2, it can be seen that the following steps are also included:
and step 230, the plug-in function component identifier and the function component description corresponding to the plug-in function component identifier are sent to a developer terminal, so that the developer develops a function component plug-in installation package corresponding to the plug-in function component identifier according to the function component description corresponding to the plug-in function component identifier.
In one embodiment, the function component plug-in installation package is an android package developed by java language, the format is apk, the plug-in function component identifier is the name of the class interface, and when a developer obtains the plug-in function component identifier and the corresponding function component description, specific implementation of the class can be developed according to the name of the class interface and the corresponding function component description, so that the android package is obtained, namely the function component plug-in installation package.
And step 240, packaging all the engineering codes into an engineering installation package after the engineering codes corresponding to the functional component descriptions except the functional component description corresponding to the plug-in functional component identifier in the functional component descriptions are developed.
The engineering code which does not need to be developed in a plug-in mode is the code of the host engineering of the application program and is the main code of the application program.
In one embodiment, the engineering code which does not need to be developed in a plug-in manner is android program code developed in java language, and the engineering code corresponding to the functional component corresponding to each functional component description is packaged into a package in jar format, wherein the packaging all the engineering code into one engineering installation package comprises:
and packaging all the program packages in the jar format into an engineering installation package.
In one embodiment, after the engineering codes corresponding to the other function component descriptions except the function component description corresponding to the plug-in function component identifier in the plurality of function component descriptions are developed, the engineering codes corresponding to the other function component descriptions are synchronized to the local terminal, and the local terminal packages all the engineering codes into an engineering installation package.
And step 250, loading the functional component plug-in installation package into the engineering installation package to obtain the first application program.
Loading the function component plug-in installation package into the engineering installation package means that the function component plug-in installation package is embedded into the engineering installation package, and the whole obtained by combining the function component plug-in installation package and the engineering installation package is the first application program, so that codes in the engineering installation package can be called by codes in the function component plug-in installation package in an interface calling mode.
In one embodiment, the function component plug-in installation package and the engineering installation package are android program installation packages, the engineering installation package loads class and resource files in the function component plug-in installation package respectively, and invokes an Activity component and a Service component of the function component plug-in installation package to load the function component plug-in installation package.
In summary, according to the method for constructing the application program including the plugin shown in the embodiment of fig. 2, efficient selection of the functional components to be plugin is achieved, and efficiency of selecting the functional components to be plugin in the whole software development process is improved, so that efficiency of software development is improved as a whole.
Fig. 4 is a flowchart showing details of step 220 according to another embodiment shown in the corresponding embodiment of fig. 2. In the embodiment of fig. 4, the requirement document corresponding to the preset format of the first application program is a first requirement document, and the functional components in the requirement document are described as first functional components, as shown in fig. 4, including the following steps:
step 221' obtains a requirement document corresponding to the second application as a second requirement document.
Wherein the second requirements document includes a plurality of second functional component descriptions.
The second application is a program that has been developed and updated before the first application.
In one embodiment, the preset database stores the requirement document of each application program which is developed and updated, and the requirement document of one application program is taken from the preset database as the second requirement document by querying the preset database.
Step 222' obtains an update log for the second application.
The update log contains a plurality of update records, each update record corresponding to a second functional component description in the second requirements document.
In one embodiment, a script is embedded in the implementation terminal of the present disclosure, and the update log of the second application program may be crawled by running the script.
Step 223', determining the identification of the first functional component to be developed according to the plug-in mode from the identifications of the first functional components corresponding to each first functional component description according to the first functional component description in the first requirement document and the second functional component description corresponding to each update record in the update log of the second application program, and taking the identification as the plug-in functional component identification.
In one embodiment, step 223' may include the steps of:
the second function component descriptions corresponding to each update record in the update log of the second application program are sequenced from large to small according to the number of the update records corresponding to each second function component description;
acquiring a second function component description ordered in a preset number;
for each second function component description which is ordered in a previous preset number, acquiring a first function component description with the maximum similarity with the second function component description from the first function component descriptions of the first requirement document;
in the identification of the first functional component corresponding to each first functional component description, the identification of the first functional component corresponding to the first functional component description acquired correspondingly to each second functional description is acquired as a plug-in functional component identification.
The more the number of update records of the second function component description similar to the first function component description is, the more frequently the corresponding first function component is updated according to the first function component description, and in this embodiment, the identifier of the first function component corresponding to the second function component description similar to the second function component description with the number of update records is used as the plugin function component identifier, so that the function component most likely to be updated at high frequency can be plugin, and the update and upgrade of the plugin part in the application program do not need to be checked by the application market, thereby ensuring the update efficiency of the developed application program.
In one embodiment, the obtaining, for each of the first function component descriptions of the first requirement document, a first function component description having the greatest similarity with the second function component description, where the second function component description is ranked a predetermined number before, includes:
extracting keywords described by each of the first function components in a predetermined number;
extracting keywords described by each first functional component of the first requirement document;
determining, for each of a predetermined number of the second feature descriptions ranked in front, a similarity of the second feature description and each of the first feature descriptions in the first requirement document based on the extracted keywords for that second feature description and the extracted keywords for each of the first feature descriptions in the first requirement document;
and acquiring a first function component description with the maximum similarity with the second function component description from the first function component descriptions of the first requirement document.
In one embodiment, the similarity of two functional components is calculated from the keywords of the first functional component and the keywords of the second functional component using the following Jaccard similarity coefficient formula:
Wherein A is a set of keywords extracted by the first functional component description, B is a set of keywords extracted by the second functional component description, |A n B| is the number of keywords contained in the set of keywords extracted by the first functional component description and the set of keywords extracted by the second functional component description together, and|A n B| is the number of keywords in the set formed by the union of the set of keywords extracted by the first functional component description and the set of keywords extracted by the second functional component description.
The present disclosure also provides a device for building an application program including a plug-in, and the following is an embodiment of the device of the present disclosure.
FIG. 5 is a block diagram illustrating an apparatus for building an application containing plug-ins, according to an example embodiment. As shown in fig. 5, the apparatus 500 includes:
a required document acquiring module 510 configured to acquire a required document in a preset format corresponding to a first application program before the first application program is developed, the required document including a plurality of function component descriptions, the function component descriptions corresponding to identifications of the function components;
the determining module 520 is configured to determine, according to the description of the functional components in the requirement document, the identification of the functional component to be developed in a plug-in manner from the identifications of the functional components corresponding to each description of the functional components, as a plug-in functional component identification;
A sending module 530 configured to send the pluggable function component identifier and the function component description corresponding to the pluggable function component identifier to a developer terminal, so that the developer develops a function component plug-in installation package corresponding to the pluggable function component identifier according to the function component description corresponding to the pluggable function component identifier;
a packaging module 540 configured to package all the engineering codes into an engineering installation package after the engineering codes corresponding to the functional component descriptions other than the functional component description corresponding to the plug-in functional component identifier in the plurality of functional component descriptions are developed;
a loading module 550 configured to load the functional component plug-in installation package into the engineering installation package, resulting in the first application.
According to a third aspect of the present disclosure, there is also provided an electronic device capable of implementing the above method.
Those skilled in the art will appreciate that the various aspects of the invention may be implemented as a system, method, or program product. Accordingly, aspects of the invention may be embodied in the following forms, namely: an entirely hardware embodiment, an entirely software embodiment (including firmware, micro-code, etc.) or an embodiment combining hardware and software aspects may be referred to herein as a "circuit," module "or" system.
An electronic device 600 according to this embodiment of the invention is described below with reference to fig. 6. The electronic device 600 shown in fig. 6 is merely an example, and should not be construed as limiting the functionality and scope of use of embodiments of the present invention.
As shown in fig. 6, the electronic device 600 is in the form of a general purpose computing device. Components of electronic device 600 may include, but are not limited to: the at least one processing unit 610, the at least one memory unit 620, and a bus 630 that connects the various system components, including the memory unit 620 and the processing unit 610.
Wherein the storage unit stores program code that is executable by the processing unit 610 such that the processing unit 610 performs steps according to various exemplary embodiments of the present invention described in the above-described "example methods" section of the present specification.
The storage unit 620 may include readable media in the form of volatile storage units, such as Random Access Memory (RAM) 621 and/or cache memory 622, and may further include Read Only Memory (ROM) 623.
The storage unit 620 may also include a program/utility 624 having a set (at least one) of program modules 625, such program modules 625 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment.
Bus 630 may be a local bus representing one or more 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 using any of a variety of bus architectures.
The electronic device 600 may also communicate with one or more external devices 800 (e.g., keyboard, pointing device, bluetooth device, etc.), one or more devices that enable a user to interact with the electronic device 600, and/or any device (e.g., router, modem, etc.) that enables the electronic device 600 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 650. Also, electronic device 600 may communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the Internet, through network adapter 660. As shown, network adapter 660 communicates with other modules of electronic device 600 over bus 630. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with electronic device 600, including, but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.
From the above description of embodiments, those skilled in the art will readily appreciate that the example embodiments described herein may be implemented in software, or may be implemented in software in combination with the necessary hardware. Thus, 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 (may be a CD-ROM, a U-disk, a mobile hard disk, etc.) or on a network, including several instructions to cause a computing device (may be a personal computer, a server, a terminal device, or a network device, etc.) to perform the method according to the embodiments of the present disclosure.
According to a fourth aspect of the present disclosure, there is also provided a computer readable storage medium having stored thereon a program product capable of implementing the method described herein above. In some possible embodiments, the various aspects of the invention may also be implemented in the form of a program product comprising program code for causing a terminal device to carry out the steps according to the various exemplary embodiments of the invention as described in the "exemplary methods" section of this specification, when said program product is run on the terminal device.
Referring to fig. 7, a program product 700 for implementing the above-described 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 thereto, and in this 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. The readable storage medium can be, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium would include the following: an electrical connection having one or more wires, a portable disk, a hard disk, random Access Memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
The computer readable signal medium may include a data signal propagated in baseband or as part of a carrier wave with readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. 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 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 user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through 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., connected via the Internet using an Internet service provider).
Furthermore, the above-described drawings are only schematic illustrations of processes included in the method according to the exemplary embodiment of the present invention, and are not intended to be limiting. It will be readily appreciated that the processes shown in the above figures do not indicate or limit the temporal order of these processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, for example, among a plurality of modules.
It is to be understood that the invention is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the invention is limited only by the appended claims.
Claims (8)
1. A method of building an application program comprising a plug-in, the method comprising:
before a first application program is developed, acquiring a requirement document in a preset format corresponding to the first application program, wherein the requirement document comprises a plurality of function component descriptions, and the function component descriptions correspond to identifications of the function components;
according to the description of the functional components in the requirement document, determining the identification of the functional components required to be developed in a plug-in mode from the identifications of the functional components corresponding to the description of each functional component as plug-in functional component identifications;
The plug-in function component identification and the function component description corresponding to the plug-in function component identification are sent to a developer terminal, so that a developer develops a function component plug-in installation package corresponding to the plug-in function component identification according to the function component description corresponding to the plug-in function component identification;
when the engineering codes corresponding to the function component descriptions except the function component description corresponding to the plug-in function component identifier in the function component descriptions are developed, packaging all the engineering codes into an engineering installation package;
loading the functional component plug-in installation package to the engineering installation package to obtain the first application program;
the determining, according to the description of the functional components in the requirement document, the identification of the functional components to be developed according to the plug-in mode in the identifications of the functional components corresponding to each functional component description, as plug-in functional component identifications, includes:
determining a number of characters contained by each functional component description in the requirements document; based on the number of characters contained in each function component description, acquiring a plug-in function component identifier in the identifier of the function component corresponding to each function component description; or alternatively
Acquiring a requirement document corresponding to a second application program as a second requirement document, wherein the second requirement document comprises a plurality of second function component descriptions; acquiring an update log of a second application program, wherein the update log comprises a plurality of update records, and each update record corresponds to a second function component description in the second requirement document; according to the first function component description in the first requirement document and the second function component description corresponding to each update record in the update log of the second application program, determining the identification of the first function component needing to be developed in a plug-in mode from the identification of the first function component corresponding to each first function component description as a plug-in function component identification, wherein the requirement document corresponding to the preset format of the first application program is the first requirement document, and the function component description in the first requirement document is the first function component description.
2. The method according to claim 1, wherein the obtaining, based on the number of characters included in each functional component description, the plug-in functional component identifier from the identifiers of the functional components corresponding to each functional component description includes:
Sorting the descriptions of the functional components from large to small according to the number of the contained characters;
the identification of the functional components corresponding to the description of the functional components which are sequenced in the previous preset number is obtained and used as the identification of the plug-in functional components.
3. The method according to claim 1, wherein the obtaining, based on the number of characters included in each functional component description, the plug-in functional component identifier from the identifiers of the functional components corresponding to each functional component description includes:
sorting the descriptions of the functional components from large to small according to the number of the contained characters;
if the number of characters contained in the ordered function component description with the sequence number being the preset value is larger than a preset character number threshold value, taking the identification of the function component corresponding to the function component description with the sequence number being smaller than the preset value as a plug-in function component identification;
if the number of the characters contained in the ordered function component description with the sequence number of the preset value is smaller than the preset character number threshold value, acquiring the function component description with the number of the characters contained reaching the preset character number threshold value;
and taking the identification of the functional component corresponding to the acquired functional component description as the plug-in functional component identification.
4. The method according to claim 1, wherein the determining, according to the first function component description in the first requirement document and the second function component description corresponding to each update record in the update log of the second application program, the identifier of the first function component to be developed in a plug-in manner from the identifiers of the first function components corresponding to each first function component description, as the plug-in function component identifier includes:
the second function component descriptions corresponding to each update record in the update log of the second application program are sequenced from large to small according to the number of the update records corresponding to each second function component description;
acquiring a second function component description ordered in a preset number;
for each second function component description which is ordered in a previous preset number, acquiring a first function component description with the maximum similarity with the second function component description from the first function component descriptions of the first requirement document;
in the identification of the first functional component corresponding to each first functional component description, the identification of the first functional component corresponding to the first functional component description acquired correspondingly to each second functional description is acquired as a plug-in functional component identification.
5. The method according to claim 4, wherein, for each second function component description ranked in a predetermined number, the obtaining, from each first function component description of the first requirement document, a first function component description having a greatest similarity with the second function component description, includes:
extracting keywords described by each of the first function components in a predetermined number;
extracting keywords described by each first functional component of the first requirement document;
determining, for each of a predetermined number of the second feature descriptions ranked in front, a similarity of the second feature description and each of the first feature descriptions in the first requirement document based on the extracted keywords for that second feature description and the extracted keywords for each of the first feature descriptions in the first requirement document;
and acquiring a first function component description with the maximum similarity with the second function component description from the first function component descriptions of the first requirement document.
6. A build device for an application program containing plug-ins, the device comprising:
a required document acquisition module configured to acquire a required document in a preset format corresponding to a first application program before the first application program is developed, the required document including a plurality of function component descriptions, the function component descriptions corresponding to identifications of the function components;
The determining module is configured to determine the identification of the functional component to be developed according to the plug-in mode from the identifications of the functional components corresponding to each functional component description according to the functional component description in the requirement document, and the identification is used as the plug-in functional component identification;
the sending module is configured to send the plug-in function component identifier and the function component description corresponding to the plug-in function component identifier to a developer terminal, so that the developer develops a function component plug-in installation package corresponding to the plug-in function component identifier according to the function component description corresponding to the plug-in function component identifier;
the packaging module is configured to package all the engineering codes into one engineering installation package after the engineering codes corresponding to the functional component descriptions except the functional component description corresponding to the plug-in functional component identifier in the functional component descriptions are developed;
the loading module is configured to load the functional component plug-in installation package to the engineering installation package to obtain the first application program;
the determining, according to the description of the functional components in the requirement document, the identification of the functional components to be developed according to the plug-in mode in the identifications of the functional components corresponding to each functional component description, as plug-in functional component identifications, includes:
Determining a number of characters contained by each functional component description in the requirements document; based on the number of characters contained in each function component description, acquiring a plug-in function component identifier in the identifier of the function component corresponding to each function component description; or alternatively
Acquiring a requirement document corresponding to a second application program as a second requirement document, wherein the second requirement document comprises a plurality of second function component descriptions; acquiring an update log of a second application program, wherein the update log comprises a plurality of update records, and each update record corresponds to a second function component description in the second requirement document; according to the first function component description in the first requirement document and the second function component description corresponding to each update record in the update log of the second application program, determining the identification of the first function component needing to be developed in a plug-in mode from the identification of the first function component corresponding to each first function component description as a plug-in function component identification, wherein the requirement document corresponding to the preset format of the first application program is the first requirement document, and the function component description in the first requirement document is the first function component description.
7. A computer readable program medium, characterized in that it stores computer program instructions, which when executed by a computer, cause the computer to perform the method according to any one of claims 1 to 5.
8. An electronic device, the electronic device comprising:
a processor;
a memory having stored thereon computer readable instructions which, when executed by the processor, implement the method of any of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910854862.3A CN110688096B (en) | 2019-09-10 | 2019-09-10 | Method and device for constructing application program containing plug-in, medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910854862.3A CN110688096B (en) | 2019-09-10 | 2019-09-10 | Method and device for constructing application program containing plug-in, medium and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110688096A CN110688096A (en) | 2020-01-14 |
| CN110688096B true CN110688096B (en) | 2024-03-01 |
Family
ID=69107905
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910854862.3A Active CN110688096B (en) | 2019-09-10 | 2019-09-10 | Method and device for constructing application program containing plug-in, medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110688096B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111399810A (en) * | 2020-03-11 | 2020-07-10 | 杭州涂鸦信息技术有限公司 | iOS application program dynamic componentization development method, system and equipment thereof |
| CN111796802B (en) * | 2020-06-30 | 2023-09-12 | 北京字节跳动网络技术有限公司 | Function package generation method and device and electronic equipment |
| CN112130814A (en) * | 2020-08-06 | 2020-12-25 | 亿存(北京)信息科技有限公司 | Project construction method and device and electronic equipment |
| CN113296831B (en) * | 2021-06-11 | 2023-08-25 | 恒安嘉新（北京）科技股份公司 | Application identifier extraction method and device, computer equipment and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106775689A (en) * | 2016-12-05 | 2017-05-31 | 广发证券股份有限公司 | A kind of system and method for big data application and development |
| CN106873972A (en) * | 2016-12-30 | 2017-06-20 | 中国电力科学研究院 | Electric Power Network Planning emulation platform computing module cut-in method and system based on plug-in unit |
| CN108572813A (en) * | 2018-03-24 | 2018-09-25 | 深圳市前海安测信息技术有限公司 | Assembly type program development frame creates application system and method |
| CN109542445A (en) * | 2017-08-01 | 2019-03-29 | 北京京东尚科信息技术有限公司 | A kind of method and apparatus that Android plug-in unit melts hair |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070220479A1 (en) * | 2006-03-14 | 2007-09-20 | Hughes John M | Systems and methods for software development |
-
2019
- 2019-09-10 CN CN201910854862.3A patent/CN110688096B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106775689A (en) * | 2016-12-05 | 2017-05-31 | 广发证券股份有限公司 | A kind of system and method for big data application and development |
| CN106873972A (en) * | 2016-12-30 | 2017-06-20 | 中国电力科学研究院 | Electric Power Network Planning emulation platform computing module cut-in method and system based on plug-in unit |
| CN109542445A (en) * | 2017-08-01 | 2019-03-29 | 北京京东尚科信息技术有限公司 | A kind of method and apparatus that Android plug-in unit melts hair |
| CN108572813A (en) * | 2018-03-24 | 2018-09-25 | 深圳市前海安测信息技术有限公司 | Assembly type program development frame creates application system and method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110688096A (en) | 2020-01-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110688096B (en) | Method and device for constructing application program containing plug-in, medium and electronic equipment | |
| CN109766082B (en) | Method and device for application program page jump | |
| CN109062563B (en) | Method and device for generating page | |
| CN107506256B (en) | Method and device for monitoring crash data | |
| CN110858172A (en) | Automatic test code generation method and device | |
| US11934287B2 (en) | Method, electronic device and computer program product for processing data | |
| CN112769706B (en) | Componentized routing method and system | |
| CN110109983B (en) | Method and device for operating Redis database | |
| CN113076153A (en) | Interface calling method and device | |
| CN108845864B (en) | Spring frame-based JVM garbage recycling method and device | |
| CN110888972A (en) | Sensitive content identification method and device based on Spark Streaming | |
| CN108959294B (en) | Method and device for accessing search engine | |
| CN113779004A (en) | Data verification method and device | |
| CN113138768A (en) | Application package generation method and device, electronic equipment and readable storage medium | |
| CN110505289B (en) | File downloading method and device, computer readable medium and wireless communication equipment | |
| CN111949648B (en) | Memory data caching system and data indexing method | |
| CN108984221B (en) | Method and device for acquiring multi-platform user behavior logs | |
| CN116069725A (en) | File migration method, device, apparatus, medium and program product | |
| US20140136471A1 (en) | Rapid Provisioning of Information for Business Analytics | |
| CN110471708B (en) | Method and device for acquiring configuration items based on reusable components | |
| CN114780361A (en) | Log generation method, device, computer system and readable storage medium | |
| CN112988583A (en) | Method and device for testing syntax compatibility of database | |
| CN113282489A (en) | Interface testing method and device | |
| CN112882698A (en) | Development environment generation method and device, computer storage medium and electronic device | |
| CN112182085A (en) | Data export 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 | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20240131 Address after: No. 603, Building 3, Yinhai International Trade Garden, Chuncheng Road, Guandu District, Kunming City, Yunnan Province, 650000 Applicant after: Liu Aiyong Country or region after: China Applicant after: Huang Yunshu Applicant after: Yan Cong Applicant after: Shi Wenzhi Address before: Room 201, building a, No. 1, Qianwan 1st Road, Shenzhen Hong Kong cooperation zone, Shenzhen, Guangdong Province Applicant before: PING AN PUHUI ENTERPRISE MANAGEMENT Co.,Ltd. Country or region before: China |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |