Method, device, apparatus and computer-readable medium for updating mobile application version

Abstract

The present invention discloses a method, device, equipment and computer-readable medium for updating a mobile application version, and relates to the field of computer technology. A specific implementation of the method includes: setting the version number of the mobile application according to the development process of the mobile application, the components corresponding to the product requirements of the mobile application and the mobile application version configuration table, wherein the mobile application version configuration table includes the corresponding relationship between the version number of the mobile application, the development process of the mobile application and the component configuration table; constructing the installation package of the mobile application based on the component configuration table corresponding to the version number and the product requirements of the mobile application, wherein the component configuration table includes the version number of the component; after the installation package of the mobile application passes the test, updating the version number of the component corresponding to the installation package in the component configuration table, and updating the version number of the mobile application according to the component configuration table. This implementation can improve the efficiency of developing mobile APPs.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a method, device, equipment and computer-readable medium for updating a mobile application version. Background Art

[0002] With the development of mobile Internet, mobile terminals access the Internet through mobile applications (APP). In the process of mobile application development, in order to deliver software products and services on time and with quality, each R&D team has formed specific design, development, operation and maintenance habits and models. The design, development, operation habits and models of each R&D team are different.

[0003] In the process of implementing the present invention, the inventors found that there are at least the following problems in the prior art: the efficiency of developing mobile apps according to existing habits and patterns is low. Summary of the invention

[0004] In view of this, embodiments of the present invention provide a method, apparatus, device and computer-readable medium for updating a mobile application version, which can improve the efficiency of developing mobile APPs.

[0005] To achieve the above object, according to one aspect of an embodiment of the present invention, a method for updating a mobile application version is provided, comprising:

[0006] Setting a version number of the mobile application according to the development process of the mobile application, components corresponding to product requirements of the mobile application, and a mobile application version configuration table, wherein the mobile application version configuration table includes a correspondence between the version number of the mobile application, the development process of the mobile application, and the component configuration table;

[0007] Building an installation package of the mobile application based on the component configuration table corresponding to the version number and the components corresponding to the product requirements, wherein the component configuration table includes the version number of the component;

[0008] After the installation package of the mobile application passes the test, the version number of the component corresponding to the installation package is updated in the component configuration table, and the version number of the mobile application is updated according to the component configuration table.

[0009] The step of setting the version number of the mobile application according to the development process of the mobile application, the components corresponding to the product requirements of the mobile application, and the mobile application version configuration table includes:

[0010] Obtaining a component configuration table in the mobile application configuration table according to the development process of the mobile application;

[0011] In the acquired component configuration table, determining the component configuration table with the highest version based on the component corresponding to the product requirement;

[0012] The version number of the mobile application corresponding to the component configuration table of the highest version is used as the version number of the mobile application.

[0013] The step of constructing the installation package of the mobile application based on the component configuration table corresponding to the version number and the components corresponding to the product requirements includes:

[0014] Based on the component configuration table of the version number and the components corresponding to the product requirements, a test component configuration table is established;

[0015] According to the test component configuration table, build the installation package of the mobile application.

[0016] The component configuration table based on the version number and the component corresponding to the product requirement, establishing a test component configuration table, includes:

[0017] Based on the component configuration table of the version number and the component corresponding to the product requirement, updating the version number of the component corresponding to the product requirement in the component configuration table;

[0018] A component configuration table including version numbers of components corresponding to the product requirements is used as the test component configuration table.

[0019] After the installation package of the mobile application passes the test, the version number of the component corresponding to the installation package is updated in the component configuration table, and the version number of the mobile application is updated according to the mobile application version configuration summary table, including:

[0020] The installation package of the mobile application that has passed the test is combined with other installation packages of the mobile application that have passed the test to form an integrated installation package;

[0021] After the integrated installation package passes the test, the version number of the component corresponding to the installation package in the integrated installation package is updated in the component configuration table, and the version number of the mobile application is updated according to the component configuration table.

[0022] The method further comprises:

[0023] According to the development process of the mobile application, it is determined whether to submit the installation package of the mobile application for testing.

[0024] The method further comprises:

[0025] According to the development process of the mobile application, it is determined that the installation package of the mobile application that has passed the test and other installation packages of the mobile application that have passed the test are combined to form an integrated installation package.

[0026] According to a second aspect of an embodiment of the present invention, there is provided a device for updating a mobile application version, including:

[0027] A setting module, used to set the version number of the mobile application according to the development process of the mobile application, the components corresponding to the product requirements of the mobile application and the mobile application version configuration table, wherein the mobile application version configuration table includes the corresponding relationship between the version number of the mobile application, the development process of the mobile application and the component configuration table;

[0028] A construction module, configured to construct an installation package of the mobile application based on a component configuration table corresponding to the version number and product requirements of the mobile application, wherein the component configuration table includes a version number of the component;

[0029] The update module is used to update the version number of the component corresponding to the installation package in the component configuration table after the installation package of the mobile application passes the test, and to update the version number of the mobile application according to the component configuration table.

[0030] The setting module is specifically used to obtain a component configuration table in the mobile application configuration table according to the development process of the mobile application;

[0031] In the acquired component configuration table, determining the component configuration table with the highest version based on the component corresponding to the product requirement;

[0032] The version number of the mobile application corresponding to the highest version is used as the version number of the mobile application.

[0033] The update module is specifically used to combine the installation package of the mobile application that has passed the test with other installation packages of the mobile application that have passed the test to form an integrated installation package;

[0034] After the integrated installation package passes the test, the version number of the component corresponding to the installation package in the integrated installation package is updated in the component configuration table, and the version number of the mobile application is updated according to the component configuration table.

[0035] According to a third aspect of an embodiment of the present invention, there is provided an electronic device for updating a mobile application version, including:

[0036] one or more processors;

[0037] a storage device for storing one or more programs,

[0038] When the one or more programs are executed by the one or more processors, the one or more processors implement the above method.

[0039] According to a fourth aspect of an embodiment of the present invention, there is provided a computer-readable medium on which a computer program is stored, and when the program is executed by a processor, the method as described above is implemented.

[0040] One embodiment of the above invention has the following advantages or beneficial effects: according to the development process of the mobile application, the components corresponding to the product requirements of the mobile application and the mobile application version configuration table, the version number of the mobile application is set; based on the component configuration table corresponding to the version number and the product requirements of the mobile application, the installation package of the mobile application is constructed; after the installation package of the mobile application passes the test, the version number of the component corresponding to the installation package is updated in the component configuration table, and the version number of the mobile application is updated according to the component configuration table. Since the version number of the mobile application can be uniformly configured in the development process and updated in time after the installation package passes the test, the efficiency of developing mobile APPs can be improved.

[0041] The further effects of the above-mentioned non-conventional optional manner will be described below in conjunction with the specific implementation manner. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] The accompanying drawings are used to better understand the present invention and do not constitute an improper limitation of the present invention.

[0043] Figure 1 is a schematic diagram of the main process of a method for updating a mobile application version according to an embodiment of the present invention;

[0044] Figure 2 is a schematic diagram of a process for setting a version number of a mobile application according to an embodiment of the present invention;

[0045] Figure 3 is a schematic diagram of a process of constructing an installation package of a mobile application according to an embodiment of the present invention;

[0046] Figure 4 is a schematic diagram of a flow chart for establishing a test component configuration table according to an embodiment of the present invention;

[0047] Figure 5 It is a schematic diagram of a process of adding a version number of a component corresponding to an installation package in a component configuration table according to an embodiment of the present invention;

[0048] Figure 6 is a schematic diagram of a platform structure for updating a mobile application version according to an embodiment of the present invention;

[0049] Figure 7 is a schematic diagram of the status of product requirements according to an embodiment of the present invention;

[0050] Figure 8 is a schematic diagram of the main structure of an apparatus for updating a mobile application version according to an embodiment of the present invention;

[0051] Fig. 9 is an exemplary system architecture diagram to which embodiments of the present invention may be applied;

[0052] Fig.10It is a schematic diagram of the structure of a computer system of a terminal device or a server suitable for implementing an embodiment of the present invention. DETAILED DESCRIPTION

[0053] The following is a description of exemplary embodiments of the present invention in conjunction with the accompanying drawings, including various details of the embodiments of the present invention to facilitate understanding, which should be considered as merely exemplary. Therefore, it should be recognized by those of ordinary skill in the art that various changes and modifications may be made to the embodiments described herein without departing from the scope and spirit of the present invention. Similarly, for clarity and conciseness, the description of well-known functions and structures is omitted in the following description.

[0054] At present, the R&D team develops mobile apps according to existing habits and patterns. Developing a mobile app requires multiple R&D teams to develop it simultaneously according to several product requirements.

[0055] In response to a product requirement, the R&D team will quickly iterate and develop multiple versions. At the same time, the version number of the mobile app is updated in different ways by different R&D teams. The multi-faceted product requirements lead to a chaotic and disordered version number of the mobile app, making it difficult to update the version number of the mobile app in a timely manner, and the efficiency of developing mobile apps is low.

[0056] In order to solve the problem that it is difficult to update the version number of the mobile APP in time and the efficiency of developing the mobile APP is low, the following technical solution in the embodiment of the present invention can be adopted.

[0057] See also Figure 1 , Figure 1 1 is a schematic diagram of the main process of the method for updating the mobile application version according to an embodiment of the present invention. After the installation package of the mobile APP passes the test, the version number of the component corresponding to the installation package is updated in the component configuration table, and then the version number of the mobile APP is updated. Figure 1 As shown, the specific steps include:

[0058] S101. Set the version number of the mobile application according to the development process of the mobile application, the components corresponding to the product requirements of the mobile application, and the mobile application version configuration table. The mobile application version configuration table includes the correspondence between the version number, the development process of the mobile application, and the component configuration table.

[0059] The development of a mobile app includes multiple stages. As an example, the development process of a mobile app may include the following stages: waiting to be launched, development, integration, regression, internal testing, release, and successful release.

[0060] The waiting stage is the stage when the mobile app is ready to start but has not yet started. For example, developers can be arranged in the waiting stage. The development stage is the stage when the mobile app writes code according to product requirements. The integration stage is the stage when the mobile app is in integration testing. The regression stage is the stage when the mobile app is in regression testing. The internal testing stage is the stage when the mobile app is in internal testing. The release stage is the stage when the mobile app is in the release process. The successful release stage is the stage when the mobile app is successfully released.

[0061] It can be seen that the development process of mobile APP includes multiple stages, and each stage has different focuses. Mobile APP will also be updated multiple times in each stage, so it is necessary to set the version number of mobile APP according to the development process of mobile APP.

[0062] It is understandable that the technical solution in the embodiment of the present invention is applicable to each stage in the development process of the mobile APP. In each stage, the technical solution in the embodiment of the present invention can be used to update the mobile APP version.

[0063] See also Figure 2 , Figure 2 1 is a flow chart of setting the version number of a mobile application according to an embodiment of the present invention, which specifically includes:

[0064] S201. Obtain a component configuration table from a mobile application configuration table according to the development process of the mobile application.

[0065] The mobile application version configuration table includes the correspondence between the version number, the development process of the mobile application and the component configuration table.

[0066] As an example, if the development integration of a mobile application is in the development phase, the version number of the mobile application starts with 2; if the development phase of the mobile application is in the internal testing phase, the version number of the mobile application starts with 5.

[0067] See Table 1, which is an example of a mobile application version configuration table.

[0068] Table 1

[0069] Development Process Version Number Component configuration table Development Phase 2.1.0 B1.0 Development Phase 2.2.3 B2.3 Development Phase 2.2.4 B2.4 Internal testing phase 5.1.1 D1.1 Internal testing phase 5.1.2 D1.2 Internal testing phase 5.3.1 D3.1

[0070] It can be learned that for the development stage, three version numbers are included, and each version number corresponds to a component configuration table. The internal testing stage includes three version numbers, and each version number corresponds to a component configuration table. As an example, in the development stage, three component configuration tables are obtained, namely component configuration table B1.0, component configuration table B2.3 and component configuration table B2.4.

[0071] S202. In the acquired component configuration table, determine the component configuration table with the highest version based on the corresponding components of the product requirements.

[0072] Each component configuration table has a version number. The later the component configuration table is established, the higher the version number is. Among the known component configuration tables, the component configuration table with the highest version can be determined based on the corresponding components of the product requirements. In other words, when multiple component configuration tables are known, the component configuration table with the latest establishment time can be determined, because the components in the component configuration table with the latest establishment time are the latest.

[0073] S203: Use the version number of the mobile application corresponding to the highest version as the version number of the mobile application.

[0074] As an example, the mobile application is in the development stage, and the product requirement of the mobile application corresponds to component a. Then, the mobile application version configuration table is queried according to the development stage, and it is found that only component configuration table B1.0 includes component a, and then the version number of the mobile application is set to 2.1.0.

[0075] As an example, the mobile application is in the development stage, and the product requirements of the mobile application correspond to component a. Then, according to the development stage, the mobile application version configuration table is queried to find out that component configuration table B1.0 includes component a; component configuration table 2.3 includes component a; component configuration table 2.4 includes component a. Among them, component configuration table 2.4 is the highest version of the component configuration table, so the version number of the mobile application can be set to: 2.2.4.

[0076] As an example, a mobile application is in the development stage, and the product requirement of the mobile application corresponds to component a. The mobile application version configuration table is queried according to the development stage, and it is found that no component configuration table includes component a. The highest version of the component configuration table in the development stage corresponds to the mobile application version number 2.2.4, and the version number of the mobile application is set to 2.2.4.

[0077] exist Figure 2 In an embodiment of the present invention, the version number of the mobile application can be set according to the development process of the mobile application, the components corresponding to the product requirements of the mobile application, and the mobile application version configuration table to avoid confusion in the version number of the mobile application.

[0078] It is understandable that the mobile application version configuration table is updated as the development process of the mobile application is updated. The component configuration table can be obtained through the mobile application version configuration table, and the version number of the component is determined by the component configuration table.

[0079] Table 2

[0080] Component identification The version number of the component a a1.1 b b1.2 c c1.5

[0081] See Table 2, which is a component configuration table B1.0. The component configuration table B1.0 includes component a, component b, and component c. The version number of component a is a1.1; the version number of component b is b1.2; and the version number of component c is c1.5.

[0082] In the embodiment of the present invention, since the R&D team needs to update the mobile APP for a component, the version number of the mobile APP can be set according to the development process of the mobile APP, the component corresponding to the product requirements of the mobile application, and the mobile application version configuration table. In this way, the mobile APP is developed based on the version number of the mobile APP. It can be understood that the version number of the mobile APP can reflect the development process of the mobile APP.

[0083] S102: Building an installation package of the mobile application based on a component configuration table corresponding to the version number and product requirements of the mobile application, wherein the component configuration table includes the version number of the component.

[0084] The purpose of developing a mobile app is to build an installation package for the mobile app. Considering that the update of a component needs to be used in conjunction with other components, the corresponding component configuration table can be obtained based on the version number of the mobile app, and the component configuration table includes the version number of the component.

[0085] In this way, according to the above corresponding component configuration table, the component version number corresponding to the component can be known. Combined with product requirements, the installation package of the mobile APP is further constructed.

[0086] Among them, product requirements are the description and planning of a function of a mobile app. As an example, product requirements include: the homepage of the mobile app displays the products that users browse many times.

[0087] See also Figure 3 , Figure 3 1 is a schematic diagram of a process of constructing an installation package of a mobile application according to an embodiment of the present invention, which specifically includes:

[0088] S301. Create a test component configuration table based on the component configuration table of the version number and the components corresponding to the product requirements.

[0089] The components in the component configuration table of the version number of the mobile application have all passed the test. In order to meet the product requirements of the mobile APP, the components in the component configuration table can be established or updated, and a test component configuration table can be established.

[0090] The test component configuration table is used to record the version numbers of components in the mobile app, one or more of which are components that have not been submitted for testing.

[0091] See also Figure 4 , Figure 41 is a flow chart of establishing a test component configuration table according to an embodiment of the present invention, which specifically includes:

[0092] S401. Based on the component configuration table of the version number of the mobile application and the component corresponding to the product requirement, the version number of the component corresponding to the product requirement is updated in the component configuration table.

[0093] The component configuration table of the mobile APP version number includes the component version number. A component can be newly created or updated according to the product requirements of the mobile APP. Then, the version number of the component corresponding to the product requirement can be updated in the above component configuration table.

[0094] As an example, for the product requirements of a mobile app, component a needs to be updated, and the version number of component a in the component configuration table is: a1.1. The version number of component a can be updated to a1.2 in the component configuration table.

[0095] As another example, for the product requirements of a mobile app, a new component b needs to be created, and there is no version number of component b in the component configuration table. The version number of the installation package of the new component b can be set to 1.1 in the component configuration table.

[0096] S402: Use the component configuration table including the version numbers of the components corresponding to the product requirements as the test component configuration table.

[0097] The component configuration table including the version number of the component corresponding to the product requirement is used as the test component configuration table. The test component configuration table includes the version number of the component corresponding to the product requirement, so that the installation package of the mobile APP can be built with the test component configuration table.

[0098] exist Figure 4 In the embodiment of the present invention, by establishing a test component configuration table, the installation package of the mobile APP is constructed. In this way, components in the mobile APP can be newly created or updated based on the version number of the mobile APP.

[0099] S302: Build an installation package for the mobile application according to the test component configuration table.

[0100] The test component configuration table includes the version number of the component corresponding to the product requirement. According to the version number of the component corresponding to the product requirement, the installation package of the mobile APP is constructed, and the product requirement can be realized based on the installation package of the mobile APP.

[0101] In the above Figure 3 In the embodiment of the present invention, the installation package of the mobile APP includes not only the existing components but also the updated or established components. Moreover, the installation package of the mobile APP is established based on the component configuration table and meets the requirements of the component configuration table.

[0102] S103: After the installation package of the mobile application passes the test, the version number of the component corresponding to the installation package is updated in the component configuration table, and the version number of the mobile application is updated according to the component configuration table.

[0103] The installation package of the mobile APP needs to pass the test before the component can be added to the mobile APP. Among them, the installation package of the mobile APP can be tested by a tester.

[0104] As an example, when a test report of an installation package of a mobile APP is received, if the test report includes passing the test, it is confirmed that the installation package of the mobile APP has passed the test; if the test report includes failing the test, it is confirmed that the installation package of the mobile APP has failed the test.

[0105] After the installation package of the mobile APP passes the test, it means that the installation package of the mobile APP is applicable to the mobile APP. Add the version number of the component corresponding to the installation package in the component configuration table, that is, add the component corresponding to the product requirement to the mobile APP, and then update the version number of the mobile application according to the above component configuration table.

[0106] As an example, the version number 2.2.4 in the mobile application version configuration table corresponds to the component configuration table B2.4. According to the component configuration table B2.4, it includes component a, component b and component c. The version number of component a is a1.1; the version number of component b is b1.3; and the version number of component c is c1.5.

[0107] In response to the product requirements of the mobile app, component a needs to be updated. In the component configuration table B2.4, the version number of component a is: a1.1. The version number of component a can be updated to a1.2 in the component configuration table.

[0108] If the installation package including component a1.2 passes the test, the version number a1.2 of component a can be added to the component configuration table, and then the version number of the mobile APP can be updated to B2.5 according to the component configuration table.

[0109] As another example, after the installation package of the mobile APP built based on the test component configuration table passes the test, the version number of the component corresponding to the product requirement can be added to the component configuration table, that is, the component configuration table is updated with the test component configuration table. Then, the version number of the mobile APP is updated according to the component configuration table.

[0110] See also Figure 5 , Figure 5 The present invention is a flowchart of adding a version number of a component corresponding to an installation package in a component configuration table according to an embodiment of the present invention, which specifically includes:

[0111] In the application process of the present invention, multiple R&D teams develop multiple components in the mobile APP in parallel according to various product requirements. Then, when updating and / or establishing multiple components, the version number of the mobile APP can be updated in the following manner.

[0112] S501. The installation package of the mobile application that has passed the test is combined with other installation packages of the mobile application that have passed the test to form an integrated installation package.

[0113] After multiple installation packages of a mobile app pass the test, they can be combined to form an integrated installation package. In other words, the integrated installation package includes multiple installation packages that have passed the test. The purpose of establishing an integrated installation package is to test whether there are any problems after multiple installation packages are integrated together. If there are any problems, the R&D personnel of the installation package can be reminded to make modifications; if there are no problems, internal testing can be carried out.

[0114] S502: After the integrated installation package passes the test, the version number of the component corresponding to the installation package in the integrated installation package is added to the component configuration table, and the version number of the mobile application is updated according to the component configuration table.

[0115] After the integrated installation package passes the test, it means that multiple installation packages can be integrated and run normally. Then you can add the version number of the corresponding component in the integrated installation package to the component configuration table, and update the version number of the mobile application according to the component configuration table.

[0116] As an example, the version number 2.2.4 in the mobile application version configuration table corresponds to the component configuration table B2.4. According to the component configuration table B2.4, it includes component a, component b and component c. The version number of component a is a1.1; the version number of component b is b1.3; and the version number of component c is c1.5.

[0117] In response to the product requirements of the mobile app, you need to update component a and component b. In the component configuration table, the version number of component a is: a1.1; the version number of component b is: b1.3. You can update the version number of component a to a1.2 and the version number of component b to b1.4 in the component configuration table.

[0118] If the installation package of component a passes the test and the installation package of component b also passes the test, the installation package of component a and the installation package of component b are combined to form an integrated installation package. After the above integrated installation package passes the test, the version number of the component corresponding to the installation package of component a and the version number of the component corresponding to the installation package of component b can be added to the component configuration table. Then, according to the above component configuration table, the version number of the mobile app is updated to 2.2.5.

[0119] exist Figure 5In the embodiment, when multiple components are updated and / or established, the version number of the mobile APP is updated by merging and building an integrated installation package, thereby further ensuring the stability of the mobile APP.

[0120] In one embodiment of the present invention, since the development process includes multiple stages, it can be determined according to the development process of the mobile APP whether the installation package of the mobile APP is submitted for testing, thereby determining whether the installation package of the mobile APP passes the test.

[0121] As an example, during the development phase or the integration phase, the installation package of a mobile app may be submitted for testing.

[0122] In one embodiment of the present invention, according to the development process of the mobile APP, it can be determined that the installation packages of multiple mobile APPs that have passed the test can be merged to form an integrated installation package to ensure the stability of the mobile APP.

[0123] As an example, in the integration stage, multiple mobile APPs that have passed the test can be combined to form an integrated installation package.

[0124] In the above embodiment, the version number of the mobile APP is set according to the development process of the mobile APP, the components corresponding to the product requirements of the mobile application, and the mobile application version configuration table; the installation package of the mobile APP is constructed based on the component configuration table corresponding to the version number and the product requirements of the mobile APP; after the installation package of the mobile APP passes the test, the version number of the component corresponding to the installation package is added to the component configuration table, and the version number of the mobile APP is updated according to the component configuration table.

[0125] Since the version number of the mobile APP can be uniformly configured during the development process, and the mobile APP version number is updated in a timely manner after the installation package passes the test, multiple R&D teams can update the mobile APP in parallel without causing confusion in the mobile APP version number, thereby improving the efficiency of mobile APP development.

[0126] The technical solutions in the embodiments of the present invention are exemplarily described below with reference to the accompanying drawings.

[0127] The efficiency of developing mobile apps by various R&D teams according to existing habits and patterns is low. The above existing habits and patterns must exist, otherwise there will be a lot of uncertainty in the completion of daily R&D tasks.

[0128] By using specific methods to standardize the above existing habits and patterns, and analyzing and optimizing each link and node in the APP development process, the overall APP delivery quality and efficiency can be improved.

[0129] Devops is a collective name for a group of processes, methods and systems. It integrates multiple functional departments such as product definition, software development, software operation and maintenance, product operation, quality assurance, etc., and brings together teams and personnel with different backgrounds and functions with a unified culture and conventions, defines a common language and thinking habits, and makes the entire software development cycle more convenient, reliable and rapid.

[0130] In the current mobile APP development process, if the team collaboration methodology and tools are specially sorted out, defined and transformed, most of them will produce a unified platform that integrates various development documents, R&D tools and system data. This platform integrates the processes and tools used by various roles in the R&D team in their daily work, and streamlines and automates some of the workflows to improve the work efficiency of various departments and personnel in the team. This approach can achieve the optimization of the R&D process to a certain extent.

[0131] The current mobile R&D platform is mainly an aggregation of multiple nodes in the R&D and operation and maintenance processes. The formation of this situation has historical reasons.

[0132] In the early days of mobile Internet development, the mobile R&D team had limited personnel and could only focus on the development of mobile apps. It was basically impossible to do R&D, support and R&D services as a separate business. At several key points in mobile app development and operation and maintenance, several systems were built or purchased based on the needs at the time. For example: agile development project management system, componentized system, continuous integration / continuous deployment system, crash analysis system and performance data analysis system.

[0133] If the mobile APP development platform is just an aggregation of these tools, it will cause the following problems:

[0134] 1. Fragmentation of R&D process.

[0135] Users need to frequently switch between these systems. After obtaining the output results of a certain system, they need to manually send them to the subsequent system for processing.

[0136] 2. The cost of learning is high.

[0137] Most systems are designed for business rather than user roles, which means users need to learn the business logic and usage of multiple systems at the same time.

[0138] 3. The responsibilities and ownership of functional points are not clear.

[0139] This tool aggregation method does not consider what mobile R&D needs to do from a macro-process perspective and does not model the business, resulting in the entire system being missing some less important nodes.

[0140] 4. Poor team compatibility and scalability.

[0141] The above R&D platform gradually serves multiple R&D teams with different businesses and styles. The needs of these teams vary greatly, and the R&D platform has no unified design and may not be able to meet all user needs and scalability requirements.

[0142] 5. Data collection and analysis become more difficult.

[0143] This tool aggregation method results in different calculation indicators being used in the dimensions of data collection and analysis algorithms, such as the two concepts of iteration in agile development and the version number of the APP package. The above two concepts are related to each other but also different. If the above two concepts are not unified, it will lead to deviations in correspondence and calculation when analyzing the implementation of version requirements and the actual online data of the requirements.

[0144] Comprehensively consider the collaboration styles of various mobile APP R&D and operation teams, cover the overall R&D process from demand research to demand launch, and also consider the needs of mobile APP technical operation and data operation. Figure 5 The platform in implements the technical solution in the embodiment of the present invention.

[0145] See also Figure 6 , Figure 6 It is a schematic diagram of the platform structure for updating the mobile application version according to an embodiment of the present invention, which specifically includes: a demand management subsystem, a version management subsystem, a build integration subsystem, a test management subsystem, an application release subsystem and a technology and data operation and maintenance subsystem.

[0146] The above six subsystems are connected in series through the dispatch bus, and work independently in terms of business, without dependence or coupling. The interaction objects and scopes of data interaction are defined between each subsystem and the dispatch bus, so as to define and clarify the intermediate products of each stage in the mobile R&D and operation and maintenance process.

[0147] The basic information of these intermediate products, such as the time when they were produced and the relevant personnel, will be stored in the scheduling bus by calling the data reporting interface of the technology and data operation and maintenance subsystem. The whole information will be displayed in the form of a large data screen, which will provide data-level reference for the team when analyzing and optimizing the overall R&D process.

[0148] In addition, multiple extension points are defined in the logic of the scheduling bus, and users can flexibly define the processing flow by implementing the extension points.

[0149] The six systems mentioned above are introduced one by one below.

[0150] Demand Management Subsystem

[0151] The demand management subsystem mainly serves product managers and interaction designers. Its main responsibility is to help users conduct team value mining, user research and demand management. The intermediate output is product demand. It is understandable that the demand management system can provide product demand for mobile apps.

[0152] See also Figure 7 , Figure 7 : is a schematic diagram of the status of product requirements according to an embodiment of the present invention, wherein the status of product requirements is divided into being claimed, being defined, being reviewed, having been reviewed, being tested, having passed the test, being integrated, and being released. The flow logic of the first four states is inside the demand management subsystem, and the flow of the last four states is automatically processed and fed back in the scheduling bus according to the processing logic of other subsystems.

[0153] Product designers claim product requirements. Product research provides solutions. R&D personnel are responsible for review, and the final review is completed. After the requirements are submitted for testing, they are transferred to testing. The test management subsystem provides test feedback. After the test passes, the construction integration subsystem integrates the requirements. The application release subsystem is responsible for version release and finally releases the mobile app.

[0154] Depend on Figure 7 It can be seen that in the construction integration subsystem, a demand is initiated for testing operation, and a product demand in the review completion state is synchronized from the demand management subsystem to the scheduling bus through demand testing.

[0155] Version management subsystem

[0156] The version management subsystem mainly serves project managers and project management personnel. Its main responsibilities are to manage the version life cycle, time plan and R&D infrastructure. The output product is the mobile application version configuration table.

[0157] The stages of each mobile APP version are divided into the waiting stage, development stage, integration stage, regression stage, internal testing stage, release stage and successful release stage. The above stages are manually changed by the project manager or project management in the version management subsystem, so as to control and synchronize the version planning and planning. The restrictions on other subsystems in each stage are as follows:

[0158] Waiting for startup phase: Testing and integration are not possible, and the component configuration table can be empty.

[0159] Development stage: Can be tested, cannot be integrated, component configuration table cannot be empty.

[0160] Integration stage: testable, integrable, component configuration table cannot be empty.

[0161] Regression stage, internal testing stage, release stage, and successful release stage: Testing and integration are not allowed, and the component configuration table can be empty.

[0162] It is understandable that the installation package of the mobile APP can be submitted for testing in the development stage and the integration stage. In the integration stage, multiple installation packages of the mobile APP that have passed the test can be merged to form an integrated installation package.

[0163] Building integrated subsystems

[0164] The construction and integration subsystem mainly serves the scenario where R&D personnel package and test after the development is completed. Its main responsibility is to build the mobile APP installation package according to the mobile APP version configuration table and provide an entry for submitting tests. The main functions of the construction and integration subsystem are demand testing and demand integration.

[0165] Demand testing refers to the testing of a product requirement. Users need to create a test component configuration table for the function based on the mobile APP version configuration table, and then obtain the corresponding requirements from the scheduling bus. After associating them together, submit the test task to the scheduling bus.

[0166] Demand integration refers to the merging of the test component configuration table of product requirements into the mobile application version configuration table. Because the test component configuration table is established based on product requirements, after integration, an integration task will be submitted to the scheduling bus to modify the version number of the component in the mobile application version configuration table. In addition, after receiving the integration task, the scheduling bus will automatically trigger the integration build operation, update the installation package information and integration requirement information, and perform regression testing.

[0167] It should be noted that during the integration process, the construction integration subsystem will obtain test information on the scheduling bus based on the information in the test component configuration table. If the test has been completed and passed, integration can be performed; otherwise, it will prompt that the integration has failed.

[0168] Test management subsystem

[0169] The test management subsystem mainly serves unit testers and regression testers. Its main responsibilities are to display the test information list and provide a test result feedback entry.

[0170] The output product of the test management subsystem synchronized to the scheduling bus is the test report, including: unit test report and version regression test report. The build integration subsystem obtains the unit test report of the product requirements from the scheduling bus for verification of the requirements integration; the application release subsystem obtains the regression test report of the mobile APP version and then uses it for version release.

[0171] Application publishing subsystem

[0172] Application release mainly serves APP operators, whose main responsibilities are to upload the corresponding APP installation package according to the regression test report, turn on the user update switch of the old version, etc.

[0173] Technology and data operation and maintenance subsystem

[0174] The main responsibility of the technology and data operation and maintenance subsystem is to provide data classification storage and classification analysis. Data of different dimensions such as requirements, versions, installation packages, test reports, and crash data and performance data after the mobile APP is launched during the operation of the platform will be saved in this subsystem in a defined format. Users of different roles can query and download data at any time through the system.

[0175] In addition, you can add extension points based on the above 6 subsystems, see Figure 5 The external extension point in the main process. The extension point is an extension and supplement to the main process. For example, users can achieve the following two functions through the extension point: one is to access a new system and add functions and capabilities that are not available; the other is to access a new system and replace the functions and capabilities of the original subsystem.

[0176] As an example, a demand reporting extension point is established. Through the demand reporting extension point, demand reporting information can be synchronized externally and external demand reporting information can be received.

[0177] As another example, a test feedback extension point is established. Through the test feedback extension point, test reports can be synchronized externally and external test reports can be received.

[0178] Another example is to establish a release package extension point. Through the release package extension point, you can synchronize pre-release package information externally, and perform security checks, resource information checks, etc. Through the release package extension point, receive the release package to carry out the release process.

[0179] See also Figure 8 , Figure 8 is a schematic diagram of the main structure of the device for updating the mobile application version according to an embodiment of the present invention. The device for updating the mobile application version can implement the method for updating the mobile application version, such as Figure 7 As shown, the device for updating the mobile application version specifically includes:

[0180] The setting module 801 is used to set the version number of the mobile application according to the development process of the mobile application and the mobile application version configuration table, wherein the mobile application version configuration table includes the correspondence between the version number of the mobile application, the development process of the mobile application and the component configuration table.

[0181] The construction module 802 is used to construct an installation package of the mobile application based on a component configuration table corresponding to the version number, components corresponding to product requirements of the mobile application, and product requirements of the mobile application, wherein the component configuration table includes the version number of the component.

[0182] The updating module 803 is used to update the version number of the component corresponding to the installation package in the component configuration table after the installation package of the mobile application passes the test, and to update the version number of the mobile application according to the component configuration table.

[0183] In one embodiment of the present invention, the setting module 801 is specifically used to obtain a component configuration table in the mobile application configuration table according to the development process of the mobile application;

[0184] In the acquired component configuration table, determining the component configuration table with the highest version based on the component corresponding to the product requirement;

[0185] The version number of the mobile application corresponding to the component configuration table of the highest version is used as the version number of the mobile application.

[0186] In one embodiment of the present invention, the construction module 702 is specifically used to establish a test component configuration table based on the component configuration table of the version number and the component corresponding to the product requirement;

[0187] Build the installation package of the mobile application according to the test component configuration table.

[0188] In one embodiment of the present invention, the construction module 702 is specifically used to update the version number of the component corresponding to the product requirement in the component configuration table based on the component configuration table of the version number and the component corresponding to the product requirement;

[0189] The component configuration table including the version numbers of the components corresponding to the product requirements is used as the test component configuration table.

[0190] In one embodiment of the present invention, the update module 703 is specifically used to merge the installation package of the mobile application that has passed the test with other installation packages of the mobile application that have passed the test to form an integrated installation package;

[0191] After the integrated installation package passes the test, the version number of the component corresponding to the installation package in the integrated installation package is updated in the component configuration table, and the version number of the mobile application is updated according to the component configuration table.

[0192] In one embodiment of the present invention, the construction module 702 is further used to determine whether to submit the installation package of the mobile application for testing according to the development process of the mobile application.

[0193] In one embodiment of the present invention, the update module 703 is further used to determine, according to the development process of the mobile application, to merge the installation package of the mobile application that has passed the test with other installation packages of the mobile application that have passed the test to form an integrated installation package.

[0194] Fig. 9 An exemplary system architecture 900 is shown to which the method for updating a mobile application version or the apparatus for updating a mobile application version according to the embodiments of the present invention can be applied.

[0195] like Fig. 9 As shown, system architecture 900 may include terminal devices 901, 902, 903, network 904 and server 905. Network 904 is used to provide a medium for communication links between terminal devices 901, 902, 903 and server 905. Network 904 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0196] Users can use terminal devices 901, 902, 903 to interact with server 905 through network 904 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 901, 902, 903, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only examples).

[0197] The terminal devices 901 , 902 , and 903 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, and desktop computers, etc.

[0198] The server 905 may be a server that provides various services, such as a backend management server (only an example) that provides support for shopping websites browsed by users using the terminal devices 901, 902, and 903. The backend management server may analyze and process the received data such as product information query requests, and feed back the processing results (such as target push information, product information - only an example) to the terminal device.

[0199] It should be noted that the method for updating the mobile application version provided in the embodiment of the present invention is generally executed by the server 905 , and accordingly, the device for updating the mobile application version is generally set in the server 905 .

[0200] It should be understood that Fig. 9 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0201] Reference below Fig.10 , which shows a schematic diagram of the structure of a computer system 1000 of a terminal device suitable for implementing an embodiment of the present invention. Fig.10 The terminal device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0202] like Fig.10As shown, the computer system 1000 includes a central processing unit (CPU) 1001, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage part 1008 into a random access memory (RAM) 1003. In the RAM 1003, various programs and data required for the operation of the system 1000 are also stored. The CPU 1001, the ROM 1002, and the RAM 1003 are connected to each other via a bus 1004. An input / output (I / O) interface 1005 is also connected to the bus 1004.

[0203] The following components are connected to the I / O interface 1005: an input section 1006 including a keyboard, a mouse, etc.; an output section 1007 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 1008 including a hard disk, etc.; and a communication section 1009 including a network interface card such as a LAN card, a modem, etc. The communication section 1009 performs communication processing via a network such as the Internet. A drive 1010 is also connected to the I / O interface 1005 as needed. A removable medium 1011, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1010 as needed, so that a computer program read therefrom is installed into the storage section 1008 as needed.

[0204] In particular, according to the embodiments disclosed in the present invention, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present invention include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 1009, and / or installed from the removable medium 1011. When the computer program is executed by the central processing unit (CPU) 1001, the above-mentioned functions defined in the system of the present invention are executed.

[0205] It should be noted that the computer-readable medium shown in the present invention may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present invention, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present invention, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0206] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present invention. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0207] The modules involved in the embodiments of the present invention may be implemented in software or hardware. The modules described may also be provided in a processor. For example, they may be described as follows: a processor includes a sending unit, an acquisition unit, a determination unit, and a first processing unit. The names of these units do not, in some cases, constitute limitations on the units themselves. For example, the sending unit may also be described as a "unit that sends a request for obtaining an image to a connected server."

[0208] As another aspect, the present invention further provides a computer-readable medium, which may be included in the device described in the above embodiment; or may exist independently without being assembled into the device. The above computer-readable medium carries one or more programs, and when the above one or more programs are executed by a device, the device includes:

[0209] Setting a version number of the mobile application according to the development process of the mobile application, components corresponding to product requirements of the mobile application, and a mobile application version configuration table, wherein the mobile application version configuration table includes a correspondence between the version number of the mobile application, the development process of the mobile application, and the component configuration table;

[0210] Building an installation package of the mobile application based on the component configuration table corresponding to the version number and the components corresponding to the product requirements, wherein the component configuration table includes the version number of the component;

[0211] After the installation package of the mobile application passes the test, the version number of the component corresponding to the installation package is updated in the component configuration table, and the version number of the mobile application is updated according to the component configuration table.

[0212] According to the technical solution of the embodiment of the present invention, the version number of the mobile application is set according to the development process of the mobile application, the components corresponding to the product requirements of the mobile application, and the mobile application version configuration table; the installation package of the mobile application is constructed based on the component configuration table corresponding to the version number and the product requirements of the mobile application; after the installation package of the mobile application passes the test, the version number of the component corresponding to the installation package is updated in the component configuration table, and the version number of the mobile application is updated according to the component configuration table. Since the version number of the mobile application can be uniformly configured in the development process and updated in time after the installation package passes the test, the efficiency of developing mobile APPs can be improved.

[0213] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may occur depending on design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A method for updating a mobile application version, characterized in that: include: Setting a version number of the mobile application according to the development process of the mobile application, components corresponding to product requirements of the mobile application, and a mobile application version configuration table, wherein the mobile application version configuration table includes a correspondence between the version number of the mobile application, the development process of the mobile application, and the component configuration table; Building an installation package of the mobile application based on the component configuration table corresponding to the version number and the components corresponding to the product requirements, wherein the component configuration table includes the version number of the component; After the installation package of the mobile application passes the test, the version number of the component corresponding to the installation package is updated in the component configuration table, and the version number of the mobile application is updated according to the component configuration table; The step of constructing the installation package of the mobile application based on the component configuration table corresponding to the version number and the components corresponding to the product requirements includes: Based on the component configuration table of the version number and the components corresponding to the product requirements, a test component configuration table is established; According to the test component configuration table, build the installation package of the mobile application.

2. The method for updating the mobile application version according to claim 1, characterized in that: The step of setting the version number of the mobile application according to the development process of the mobile application, the components corresponding to the product requirements of the mobile application, and the mobile application version configuration table includes: Obtaining a component configuration table in the mobile application configuration table according to the development process of the mobile application; In the acquired component configuration table, determining the component configuration table with the highest version based on the component corresponding to the product requirement; The version number of the mobile application corresponding to the component configuration table of the highest version is used as the version number of the mobile application.

3. The method for updating the mobile application version according to claim 1, characterized in that: The component configuration table based on the version number and the component corresponding to the product requirement, establishing a test component configuration table, includes: Based on the component configuration table of the version number and the component corresponding to the product requirement, updating the version number of the component corresponding to the product requirement in the component configuration table; A component configuration table including version numbers of components corresponding to the product requirements is used as the test component configuration table.

4. The method for updating a mobile application version according to claim 1, characterized in that: After the installation package of the mobile application passes the test, the version number of the component corresponding to the installation package is updated in the component configuration table, and the version number of the mobile application is updated according to the component configuration table, including: The installation package of the mobile application that has passed the test is combined with other installation packages of the mobile application that have passed the test to form an integrated installation package; After the integrated installation package passes the test, the version number of the component corresponding to the installation package in the integrated installation package is updated in the component configuration table, and the version number of the mobile application is updated according to the component configuration table.

5. The method for updating the mobile application version according to claim 1, characterized in that: The method further comprises: According to the development process of the mobile application, it is determined whether to submit the installation package of the mobile application for testing.

6. The method for updating a mobile application version according to claim 1 or 4, characterized in that: The method further comprises: According to the development process of the mobile application, it is determined that the installation package of the mobile application that has passed the test and other installation packages of the mobile application that have passed the test are combined to form an integrated installation package.

7. A device for updating a mobile application version, characterized in that: include: A setting module, used to set the version number of the mobile application according to the development process of the mobile application, the components corresponding to the product requirements of the mobile application and the mobile application version configuration table, wherein the mobile application version configuration table includes the corresponding relationship between the version number of the mobile application, the development process of the mobile application and the component configuration table; A construction module, configured to construct an installation package of the mobile application based on a component configuration table corresponding to the version number and a product requirement of the mobile application, wherein the component configuration table includes a version number of the component; and to establish a test component configuration table based on the component configuration table of the version number and the component corresponding to the product requirement; and to construct an installation package of the mobile application according to the test component configuration table; The update module is used to update the version number of the component corresponding to the installation package in the component configuration table after the installation package of the mobile application passes the test, and to update the version number of the mobile application according to the component configuration table.

8. The device for updating the mobile application version according to claim 7, characterized in that: The setting module is specifically used to obtain a component configuration table in the mobile application configuration table according to the development process of the mobile application; In the acquired component configuration table, determining the component configuration table with the highest version based on the component corresponding to the product requirement; The version number of the mobile application corresponding to the highest version is used as the version number of the mobile application.

9. The device for updating the mobile application version according to claim 7, characterized in that: The update module is specifically used to combine the installation package of the mobile application that has passed the test with other installation packages of the mobile application that have passed the test to form an integrated installation package; After the integrated installation package passes the test, the version number of the component corresponding to the installation package in the integrated installation package is updated in the component configuration table, and the version number of the mobile application is updated according to the component configuration table.

10. An electronic device for updating a mobile application version, characterized in that: include: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 6.

11. A computer readable medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 6 is implemented.

Images