CN113778476A - Method, device, equipment and computer readable medium for updating mobile application version - Google Patents

Method, device, equipment and computer readable medium for updating mobile application version Download PDF

Info

Publication number
CN113778476A
CN113778476A CN202010640057.3A CN202010640057A CN113778476A CN 113778476 A CN113778476 A CN 113778476A CN 202010640057 A CN202010640057 A CN 202010640057A CN 113778476 A CN113778476 A CN 113778476A
Authority
CN
China
Prior art keywords
mobile application
configuration table
component
version number
version
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202010640057.3A
Other languages
Chinese (zh)
Inventor
贾晓滨
王巍
王新红
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Jingdong Century Trading Co Ltd
Beijing Wodong Tianjun Information Technology Co Ltd
Original Assignee
Beijing Jingdong Century Trading Co Ltd
Beijing Wodong Tianjun Information Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Beijing Jingdong Century Trading Co Ltd, Beijing Wodong Tianjun Information Technology Co Ltd filed Critical Beijing Jingdong Century Trading Co Ltd
Priority to CN202010640057.3A priority Critical patent/CN113778476A/en
Publication of CN113778476A publication Critical patent/CN113778476A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/65Updates

Abstract

The invention discloses a method, a device, equipment and a computer readable medium for updating a mobile application version, and relates to the technical field of computers. One embodiment of the method comprises: setting a version number of the mobile application according to a development process of the mobile application, a component corresponding to a product requirement of the mobile application and a mobile application version configuration table, wherein the mobile application version configuration table comprises the version number of the mobile application and a corresponding relation between the development process of the mobile application and the component configuration table; constructing an installation package of the mobile application based on a component configuration table corresponding to the version number and the product requirement of the mobile application, wherein the component configuration table comprises the version number of the component; and 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 embodiment can improve the efficiency of developing mobile APPs.

Description

Method, device, equipment and computer readable medium for updating mobile application version
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a method, an apparatus, a device, and a computer-readable medium for updating a mobile application version.
Background
With the development of mobile internet, mobile terminals access the internet through mobile Applications (APP). In the development process of mobile applications, in order to deliver software products and services on time and with quality, various research and development teams form specific design, development, operation and maintenance habits and modes. The design, development, operation habits and modes of each research and development team are different.
In the process of implementing the invention, the inventor finds that at least the following problems exist in the prior art: according to existing habits and patterns, developing mobile APPs is inefficient.
Disclosure of Invention
In view of this, embodiments of the present invention provide a method, an apparatus, a device, and a computer-readable medium for updating a mobile application version, which can improve the efficiency of developing a mobile APP.
To achieve the above object, according to an aspect of an embodiment of the present invention, there is provided a method of updating a mobile application version, including:
setting a version number of the mobile application according to a development process of the mobile application, a component corresponding to a product requirement of the mobile application and a mobile application version configuration table, wherein the mobile application version configuration table comprises the version number of the mobile application and a corresponding relation between the development process of the mobile application and the component configuration table;
constructing an installation package of the mobile application based on the component configuration table corresponding to the version number and the component corresponding to the product requirement, wherein the component configuration table comprises the version number of the component;
and 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.
The setting of the version number of the mobile application according to the development process of the mobile application, the component corresponding to the product requirement of the mobile application and the mobile application version configuration table comprises the following steps:
acquiring a component configuration table in the mobile application configuration table according to the development process of the mobile application;
determining a component configuration table of the highest version based on the component corresponding to the product requirement in the obtained component configuration table;
and taking the version number of the mobile application corresponding to the component configuration table with the highest version as the version number of the mobile application.
The building of the installation package of the mobile application based on the component configuration table corresponding to the version number and the component corresponding to the product requirement comprises the following steps:
establishing a test component configuration table based on the component configuration table of the version number and the component corresponding to the product requirement;
and constructing an installation package of the mobile application according to the test component configuration table.
The establishing of the test component configuration table based on the component configuration table of the version number and the component corresponding to the product requirement comprises the following steps:
updating 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;
and taking a component configuration table comprising the version number of the component corresponding to the product requirement as the test component configuration table.
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 mobile application version configuration summary table, including:
the installation package of the mobile application passing the test is combined with other installation packages of the mobile application passing the test to form an integrated installation package;
and after the integrated installation package passes the test, updating the version number of the component corresponding to the installation package in the integrated installation package in the component configuration table, and updating the version number of the mobile application according to the component configuration table.
The method further comprises the following steps:
and judging to submit the installation package of the mobile application to the test according to the development process of the mobile application.
The method further comprises the following steps:
and according to the development process of the mobile application, judging the installation package which passes the test of the mobile application, and combining the installation package with other installation packages which pass the test of the mobile application to form an integrated installation package.
According to a second aspect of the embodiments of the present invention, there is provided an apparatus for updating a mobile application version, including:
the mobile application version configuration table comprises a mobile application version number and a corresponding relation between the mobile application development process and the mobile application version configuration table;
the building module is used for building an installation package of the mobile application based on a component configuration table corresponding to the version number and the product requirement of the mobile application, wherein the component configuration table comprises the version number of the component;
and the updating module is used for updating 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 updating the version number of the mobile application according to the component configuration table.
The setting module is specifically used for acquiring a component configuration table in the mobile application configuration table according to a development process of the mobile application;
determining a component configuration table of the highest version based on the component corresponding to the product requirement in the obtained component configuration table;
and taking the version number of the mobile application corresponding to the highest version as the version number of the mobile application.
The update module is specifically configured to combine the installation package that the mobile application passes the test with other installation packages that the mobile application passes the test to form an integrated installation package;
and after the integrated installation package passes the test, updating the version number of the component corresponding to the installation package in the integrated installation package in the component configuration table, and updating the version number of the mobile application according to the component configuration table.
According to a third aspect of the embodiments of the present invention, there is provided an electronic device for updating a mobile application version, including:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the method as described above.
According to a fourth aspect of embodiments of the present invention, there is provided a computer readable medium, on which a computer program is stored, which when executed by a processor, implements the method as described above.
One embodiment of the above invention has the following advantages or benefits: setting a version number of the mobile application according to a development process of the mobile application, a component corresponding to the product requirement of the mobile application and a mobile application version configuration table; constructing an installation package of the mobile application based on the component configuration table corresponding to the version number and the product requirement of the mobile application; and 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. The version number of the mobile application can be uniformly configured in the development process and can be updated in time after the installation package passes the test, so that the efficiency of developing the mobile APP can be improved.
Further effects of the above-mentioned non-conventional alternatives will be described below in connection with the embodiments.
Drawings
The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:
fig. 1 is a schematic diagram of a main flow of a method of updating a mobile application version according to an embodiment of the present invention;
FIG. 2 is a flowchart illustrating setting a version number of a mobile application according to an embodiment of the present invention;
FIG. 3 is a schematic flow chart of building an installation package for a mobile application according to an embodiment of the present invention;
FIG. 4 is a flow diagram illustrating the creation of a test component configuration table according to an embodiment of the invention;
FIG. 5 is a flowchart illustrating adding a version number of a component corresponding to an installation package to a component configuration table according to an embodiment of the present invention;
FIG. 6 is a diagram illustrating a platform architecture for implementing updating a mobile application version according to an embodiment of the present invention;
FIG. 7 is a schematic diagram of the status of product demand according to an embodiment of the present invention;
fig. 8 is a schematic diagram of a main structure of an apparatus for updating a mobile application version according to an embodiment of the present invention;
FIG. 9 is an exemplary system architecture diagram in which embodiments of the present invention may be employed;
fig. 10 is a schematic block diagram of a computer system suitable for use in implementing a terminal device or server according to an embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which various details of embodiments of the invention are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
Currently, research and development teams develop mobile APPs according to existing habits and patterns. Developing a mobile APP requires multiple research and development teams to develop simultaneously according to several aspects of product requirements.
For one aspect of product demand, research and development teams will quickly iterate to develop multiple versions. Meanwhile, the version number of the mobile APP is different in updating modes of different research and development teams, and the version number of the mobile APP is disordered due to the multi-aspect product requirements, so that the version number of the mobile APP is difficult to update in time, and the efficiency of developing the mobile APP is low.
In order to solve the problem that the version number of the mobile APP is difficult to update in time and the efficiency of developing the mobile APP is low, the following technical scheme in the embodiment of the invention can be adopted.
Referring to fig. 1, fig. 1 is a schematic diagram of a main flow of a method for updating a mobile application version according to an embodiment of the present invention, after an installation package of a mobile APP passes a test, a version number of a component corresponding to the installation package is updated in a component configuration table, so as to update the version number of the mobile APP. As shown in fig. 1, the method specifically comprises the following steps:
s101, setting a version number of the mobile application according to a development process of the mobile application, a component corresponding to a product requirement of the mobile application and a mobile application version configuration table, wherein the mobile application version configuration table comprises the version number and a corresponding relation between the development process of the mobile application and the component configuration table.
The development of mobile APP includes several phases, and as an example, the development process of mobile APP may include several phases: the method comprises a to-be-started stage, a development stage, an integration stage, a regression stage, an internal test stage, a release stage and a successful release stage.
The to-be-started phase is a phase in which the mobile APP is ready to start but is not started, such as: the to-be-started phase may schedule developers. The development phase is a phase in which the mobile APP writes code according to product requirements. The integration phase is the phase in which the mobile APP is in the integration test. The regression phase is the phase in which the mobile APP is in the regression test. The internal test phase is the phase in which the mobile APP is in internal testing. The release phase is the phase in which the mobile APP is in the release process. The release success phase is the phase in which the mobile APP is after the successful release.
It can be seen that the development process of mobile APP includes multiple stages, with different emphasis at each stage. The mobile APP is updated for multiple times at each stage, so that the version number of the mobile APP needs to be set according to the development process of the mobile APP.
It can be understood that the technical solution in the embodiment of the present invention is applicable to each stage in the development process of mobile APP. The technical scheme of the embodiment of the invention can be adopted to update the mobile APP version in each stage.
Referring to fig. 2, fig. 2 is a schematic flowchart of setting a version number of a mobile application according to an embodiment of the present invention, which specifically includes:
s201, acquiring a component configuration table in a mobile application configuration table according to the development process of the mobile application.
The mobile application version configuration table comprises a version number, and a corresponding relation between the development process of the mobile application and the component configuration table.
As an example, the development integration of a mobile application is the development phase, then the version number of the mobile application starts with 2; the development phase of the mobile application is the introspection phase, and the version number of the mobile application starts with 5.
Referring to table 1, table 1 is an example of a mobile application version configuration table.
TABLE 1
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 test phase 5.1.1 D1.1
Internal test phase 5.1.2 D1.2
Internal test phase 5.3.1 D3.1
It can be known that for the development phase, three version numbers are included, each version number corresponding to a component configuration table. The internal test stage comprises three version numbers, and each version number corresponds to a component configuration table. As an example, in the development phase, three component configuration tables are known, component configuration table B1.0, component configuration table B2.3, and component configuration table B2.4, respectively.
S202, determining the component configuration table of the highest version according to the components corresponding to the product requirements in the obtained component configuration table.
Each component configuration table has a version number, and the later the component configuration table is set up, the higher the version number. In the known component configuration table, the component configuration table of the highest version may be determined based on the product requirement corresponding component. That is, in the case where a plurality of component configuration tables are known, the component configuration table whose setup time is the latest can be determined because the component in the component configuration table whose setup time is the latest.
S203, the version number of the mobile application corresponding to the highest version is used as the version number of the mobile application.
As an example, when the mobile application is in a development phase, and the product requirement of the mobile application corresponds to the component a, the mobile application version configuration table is queried according to the development phase, it is known that only the component configuration table B1.0 includes the component a, and then the version number of the mobile application is set to 2.1.0.
As an example, when the mobile application is in a development phase, and the product requirement of the mobile application corresponds to the component a, querying a mobile application version configuration table according to the development phase to obtain that the component configuration table B1.0 includes the component a; component configuration table 2.3 includes component a; component configuration table 2.4 includes component a. Wherein, the component configuration table 2.4 is the highest version of the component configuration table, and then the version number of the mobile application can be set as: 2.2.4.
as an example, when the mobile application is in a development phase, a product requirement of the mobile application corresponds to a component a, the mobile application version configuration table is queried according to the development phase, it is known that no component configuration table includes the component a, a mobile application version number 2.2.4 corresponding to a component configuration table of a highest version in the development phase is set, and the version number of the mobile application is set to be 2.2.4.
In the embodiment of fig. 2, the version number of the mobile application may be set according to a development process of the mobile application, a product requirement corresponding component of the mobile application, and a mobile application version configuration table, so as to avoid confusion of the version number of the mobile application.
It is to be understood that the mobile application version configuration table is updated as the development process of the mobile application is updated. The component configuration table is known through the mobile application version configuration table, and the version number of the component is determined by the component configuration table.
TABLE 2
Identification of a component Version number of a component
a a1.1
b b1.2
c c1.5
Referring to table 2, table 2 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 being: a 1.1; the version number of component b is: b 1.2; the version number of component c is: c1.5.
in the embodiment of the invention, the mobile APP needs to be updated for one component by a research and development team. Then, the version number of the mobile APP can be set according to the development process of the mobile APP, the product requirement corresponding component of the mobile APP, and the mobile APP version configuration table. In this way, the mobile APP is developed on the basis of the version number of the mobile APP. It can be understood that the version number of the mobile APP can embody the development process of the mobile APP.
S102, building an installation package of the mobile application based on a component configuration table corresponding to the version number and the product requirement of the mobile application, wherein the component configuration table comprises the version number of the component.
The mobile APP is developed to build an installation package of the mobile APP. In view of the update for one component, it needs to be used with other components. Then, a corresponding component configuration table may be known based on the version number of the mobile APP, and the component configuration table includes the version number of the component.
Therefore, the component corresponding to the version number of the component can be obtained according to the corresponding component configuration table. And further constructing an installation package of the mobile APP by combining product requirements.
Among other things, product requirements are the description and planning of one function of the mobile APP. As one example, product requirements include: and the home page of the mobile APP displays the commodities browsed by the user for many times.
Referring to fig. 3, fig. 3 is a schematic flowchart of a process of building an installation package of a mobile application according to an embodiment of the present invention, which specifically includes:
s301, building a test component configuration table based on the component configuration table of the version number and the components corresponding to the product requirements.
The components in the component configuration table of the version number of the mobile application all pass the test, and in order to meet the product requirements of the mobile APP, the components in the component configuration table are established or updated, so that the component configuration table can be established for testing.
The test component configuration table is used for recording the version numbers of the components in the mobile APP, wherein one or more components are the components which are not submitted to test.
Referring to fig. 4, fig. 4 is a schematic flowchart of establishing a test component configuration table according to an embodiment of the present invention, which specifically includes:
s401, updating 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 of the mobile application and the component corresponding to the product requirement.
The component configuration table of the version number of the mobile APP comprises the version number of the component, and the component can be newly built or updated according to the product requirement of the mobile APP. Then, the version number of the component corresponding to the product requirement may be updated in the above-described component configuration table.
As an example, for the product requirements of 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 may be updated in the component configuration table to be a 1.2.
As another example, for the product requirements of mobile APP, component b needs to be newly created, and there is no version number of component b in the component configuration table. The version number of the installation package of the component b can be newly created in the component configuration table to be 1.1.
S402, taking a component configuration table comprising the version number of the component corresponding to the product requirement as a test component configuration table.
And taking the component configuration table comprising the version number of the component corresponding to the product requirement as a test component configuration table. The test component configuration table comprises the version number of the component corresponding to the product requirement, so that the test component configuration table can be used for constructing the installation package of the mobile APP.
In the embodiment of FIG. 4, the installation package of the mobile APP is built by building a test component configuration table. This enables new creation or updating of components in the mobile APP based on the version number of the mobile APP.
S302, according to the test component configuration table, an installation package of the mobile application is constructed.
And the test component configuration table comprises 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 achieved based on the installation package of the mobile APP.
In the above embodiment of fig. 3, 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.
S103, 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.
After the installation package of the mobile APP needs to pass the test, the component can be added to the mobile APP. Wherein the installation package of the mobile APP can be tested by a tester.
As an example, upon receiving a test report of an installation package of a mobile APP, the test report including a pass test, confirming that the installation package of the mobile APP passes the test; and if the test report comprises the failed test, confirming that the installation package of the mobile APP fails to pass the test.
After the installation package of removal APP passed through the test, it can be applicable to removal APP to explain the installation package of removal APP. And adding the version number of the component corresponding to the installation package in the component configuration table, namely adding the component corresponding to the product requirement to the mobile APP, and then updating the version number of the mobile application according to the component configuration table.
As an example, the mobile application version configuration table corresponds to the component configuration table B2.4 in version number 2.2.4. According to the component configuration table B2.4, component a, component B and component c are included. The version number of component a is a 1.1; the version number of component b is b 1.3; the version number of component c is c 1.5.
For the product requirements of the mobile APP, the component a needs to be updated, and the version number of the component a in the component configuration table B2.4 is: a1.1. the version number of component a may be updated in the component configuration table to be a 1.2.
If the installation package including the component a1.2 passes the test, the version number a1.2 of the component a can be added to the component configuration table, and then the version number of the mobile APP is updated to be B2.5 according to the component configuration table.
As another example, after the built installation package of the mobile APP passes the test based on the test component configuration table, the version number of the component corresponding to the product requirement may be added to the component configuration table, that is, the component configuration table is updated with the test component configuration table. The version number of the mobile APP is then updated according to the component configuration table.
Referring to fig. 5, fig. 5 is a schematic flowchart illustrating 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, specifically including:
in the application process of the invention, a plurality of research and development teams develop a plurality of components in the mobile APP in parallel aiming at various product requirements. Then, in case of updating and/or building multiple components, the version number of the mobile APP can be updated in the following way.
S501, combining the installation package of the mobile application passing the test with other installation packages of the mobile application passing the test to form an integrated installation package.
After a plurality of installation packages of removal APP pass through the test, can merge and constitute integrated installation package. That is, a plurality of installation packages that pass the test are included in the integrated installation package. The purpose of establishing the integrated installation package is to test whether a plurality of installation packages are integrated together and then have problems. If a problem occurs, a research and development personnel of the installation package can be reminded to modify; if no problem occurs, the internal test can be carried out.
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.
After the integrated installation package passes the test, it indicates that a plurality of installation packages are integrated together and can normally operate, and then the version number of the corresponding component in the integrated installation package can be added in the component configuration table, and the version number of the mobile application is updated according to the component configuration table.
As an example, the mobile application version configuration table corresponds to the component configuration table B2.4 in version number 2.2.4. According to the component configuration table B2.4, component a, component B and component c are included. The version number of component a is a 1.1; the version number of component b is b 1.3; the version number of component c is c 1.5.
For the product requirements of mobile APP, component a and component b need to be updated. The version number of component a in the component configuration table is: a 1.1; the version number of component b is: b1.3. the version number of component a may be updated in the component configuration table to be a1.2 and the version number of component b to be b 1.4.
And if the installation package of the component a passes the test and the installation package of the component b also passes the test, combining the installation package of the component a and the installation package of the component b 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 of the component a and the version number of the component corresponding to the installation package of the component b can be added into the component configuration table. And then updating the version number of the mobile APP to be 2.2.5 according to the component configuration table.
In the embodiment of FIG. 5, the version number of the mobile APP is updated by building an integrated installation package through merging, in the case of updating and/or building multiple components. The stability of removing APP is further guaranteed.
In an embodiment of the present invention, since the development process includes multiple stages, it may be determined to submit the installation package of the mobile APP to the test according to the development process of the mobile APP, so as to determine that the installation package of the mobile APP passes the test.
As one example, the installation package of the mobile APP may be submitted for testing during a development phase or an integration phase.
In an embodiment of the present invention, the installation packages that pass the test of the mobile APPs may be determined according to the development process of the mobile APPs, and combined to form an integrated installation package, so as to ensure the stability of the mobile APPs.
As an example, in the integration phase, installation packages for which multiple mobile APPs pass testing may be merged to form an integrated installation package,
in the above embodiment, the version number of the mobile APP is set according to the development process of the mobile APP, the component corresponding to the product requirement of the mobile APP, and the mobile APP version configuration table; constructing an installation package of the mobile APP 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 corresponding component of 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.
Because the version number of removing the APP can the unified configuration in the development process, remove the APP version number moreover and obtain timely renewal after the installation package passes through the test, a plurality of research and development teams can parallel update remove the APP and can not cause the confusion of removing the APP version number, therefore can improve the efficiency of development removal APP.
The technical solution in the embodiments of the present invention is exemplarily described below with reference to the accompanying drawings.
According to existing habits and modes, development efficiency of mobile APP is low for each research and development team. The existing habits and modes are certain, otherwise, a lot of uncertainty occurs in the completion of the daily research and development tasks.
The existing habits and modes are standardized in a specific mode, and nodes of all links in the APP development process are analyzed and optimized, so that the overall APP delivery quality and efficiency can be improved.
Devops is a generic term for a set of processes, methods, and systems. The system integrates a plurality of functional departments such as product definition, software research and development, software operation and maintenance, product operation, quality assurance and the like, groups and personnel with different backgrounds and functions are gathered together by using unified culture and practice, common language and thinking habits are defined, and the whole cyclic process of software development is more convenient, reliable and rapid.
In the current mobile APP development process, team collaborative methods and tools mostly generate a unified platform for gathering various development documents, research and development tools and system data if special combing, definition and modification are performed. The platform integrates the processes and tools used by various roles of a research and development team in daily work, and part of work flow is changed and automated, so that the work efficiency of all departments and personnel of the team is improved. The mode achieves the optimization of the research and development process on a certain energy degree.
The current mobile research and development platform is mainly the aggregation of a plurality of nodes in the research, development, operation and maintenance process, and the situation is formed for historical reasons.
In the early stage of mobile internet development, the mobile research and development team has limited staff, and only the focus can be put on the research and development of mobile APP, and it is basically impossible to do research, development, support and research and development services as a single business. At several key points of mobile APP development and operation and maintenance, several systems are respectively built or purchased according to the needs at the time. Such as: agile development project management systems, componentized systems, persistent integration/persistent deployment systems, crash analysis systems, performance data analysis systems, and the like.
If the mobile APP development platform is just a convergence of these several tools, several problems arise:
1. and (5) splitting of a research and development process.
Users need to switch frequently among these systems. After the output result of one system is taken, the output result is manually sent to the following system for processing.
2. The learning cost is high.
Most systems are designed for business rather than for the user's role, which results in the user needing to learn the business logic and usage of multiple systems simultaneously.
3. The functional point responsibility and ownership are unclear.
The tool aggregation mode does not consider what mobile development needs to be done from the macro flow integrally, and models the business, so that the whole system is lost on some nodes with less importance.
4. The team has poor compatibility and expansibility.
The research and development platform gradually serves a plurality of research and development teams with different businesses and different styles. The demands of the teams are very different, the research and development platform is not designed uniformly, and all the user demands and expansibility requirements cannot be met well.
5. The difficulty of data acquisition and analysis increases.
This way of tool aggregation results in the use of different computational indicators in the dimensionality and analysis algorithms of the data acquisition, such as: iteration in agile development and version number of APP package. There are also differences between the two concepts described above in relation to each other. If the two concepts are not unified, it will result in a bias in correspondence and computation when analyzing the actual line data of the version requirement implementation and the analysis requirement.
The method comprehensively considers the cooperation styles of various different mobile APP research and development operation and maintenance teams, covers the whole process from demand research to demand on-line research and development of mobile research and development, and also considers the requirements of mobile APP technology operation and data operation and maintenance. The platform in fig. 5 may be used to implement the solution in the embodiment of the present invention.
Referring to fig. 6, fig. 6 is a schematic structural diagram of a platform for implementing updating a mobile application version according to an embodiment of the present invention, which specifically includes: the system comprises a demand management subsystem, a version management subsystem, a construction integration subsystem, a test management subsystem, an application release subsystem and a technology and data operation and maintenance subsystem.
The six subsystems are connected in series through the scheduling bus, work independently on services, and are not dependent and coupled with each other. And interaction objects and interaction ranges during data interaction are defined between each subsystem and the scheduling bus, so that intermediate products of each stage in the development and operation and maintenance flow are defined and definite.
The time generated by the intermediate products, the basic information of related personnel and the like can be stored in the data reporting interface of the data operation and maintenance subsystem through a calling technology in the scheduling bus, and the whole data is displayed in a large-screen mode, so that a team can conveniently provide reference for a data layer when analyzing and optimizing the whole research and development process.
In addition, in the logic of the scheduling bus, a plurality of extension points are defined, and a user can flexibly define the processing flow by realizing the extension points.
The six systems are described below in turn.
Demand management subsystem
The demand management subsystem mainly serves product managers and interactive designers, and is mainly used for helping users to conduct team value mining, user research and demand management, and output intermediate products are product demands. It can be appreciated that the need management system can provide product requirements for mobile APPs.
Referring to fig. 7, fig. 7 is a schematic diagram of the status of a product requirement according to an embodiment of the present invention, wherein the status of the product requirement is classified into claim, definition, review completion, test pass, integration, and release. The flow logic of the first 4 states is in the demand management subsystem, and the flow of the last 4 states is automatically processed and fed back in the scheduling bus according to the processing logic of other subsystems.
Product needs are claimed by product designers. The protocol is given by product research. The research and development personnel are responsible for evaluation, and finally the evaluation is completed. And (4) carrying out requirement test and transferring to the test. And the test management subsystem performs test feedback. After the test is passed, the demand is integrated by the built integrated subsystem. The application release subsystem is responsible for release of the version and finally release of the mobile APP.
As can be seen from FIG. 7, a demand is initiated in building an integrated subsystem for a build operation, and a product demand in a review completion state is synchronized from the demand management subsystem to the dispatch bus via demand build.
Version management subsystem
The version management subsystem mainly serves project managers and project piping personnel, the main responsibility is to manage the life cycle, time planning and development infrastructure of the version, and the output product is a mobile application version configuration table.
The stages of each mobile APP version are divided into a stage to be started, a development stage, an integration stage, a regression stage, an internal test stage, a release stage and a release success stage. The above phases are manually changed by the project manager or project piping in the version management subsystem, so that the planning and planning of versions can be controlled and synchronized. The limitations on other subsystems at each stage are as follows:
a stage to be started: not testable, not integrable, component configuration table may be empty.
And (3) in a development stage: test may be raised, not integrated, component configuration table may not be empty.
An integration stage: the configuration table of the components can be lifted, can be integrated and can not be empty.
A regression stage, an internal test stage, a release stage and a successful release stage: not testable, not integrable, component configuration table may be empty.
It is appreciated that the installation package of the mobile APP may be submitted for testing during the development phase and the integration phase. In the integration stage, a plurality of installation packages of which the mobile APP passes the test can be combined to form an integrated installation package.
Building integrated subsystems
The building integrated subsystem is mainly used for packaging and testing scenes after development of research and development personnel is completed, and the main responsibility is to build a mobile APP installation package according to a mobile APP version configuration table and provide an entrance for submitting a test. The main functions of constructing the integrated subsystem are demand providing and demand integrating.
The requirement testing refers to the testing of the requirement of a certain product, a user needs to create a testing component configuration table aiming at the function based on a mobile APP version configuration table, then obtains corresponding requirements from a scheduling bus, associates the requirements together and submits a testing task to the scheduling bus.
Requirement 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 according to the product requirements, after integration is carried out, an integration task is submitted to the scheduling bus, and the version number of the component in the mobile application version configuration table is modified. In addition, after the scheduling bus receives the integration task, the integration construction operation is automatically triggered, the information of the installation package and the integration requirement information are updated, and regression is carried out.
It should be noted that, in the integration process, the building of the integration subsystem obtains the test information on the scheduling bus based on the information of the test component configuration table. If the test is finished and the test is passed, the integration can be carried out; otherwise, prompting the integration failure.
Test management subsystem
The test management subsystem mainly serves unit testers and regression testers, and mainly functions to display the test information list and provide a test result feedback inlet.
The output product of the test management subsystem synchronizing to the dispatch bus is a test report, including: unit test reports and version regression test reports. Constructing an integration subsystem to acquire a unit test report of product requirements from a scheduling bus for verification of requirement integration; and the application release subsystem acquires a regression test report of the mobile APP version and then uses the regression test report for release of the version.
Application publishing subsystem
The application release mainly serves APP operators, and the main responsibility is to upload corresponding APP installation packages according to regression test reports, open old versions of user update switches and the like.
Technology and data operation and maintenance subsystem
The technical and data operation and maintenance subsystem mainly has the functions of providing data classification storage and classification analysis. Data with different dimensions, such as requirements, versions, installation packages, test reports, crash data and performance data after the mobile APP is on line, generated in the platform operation process are stored in the subsystem according to a well-defined format. The users with different roles can inquire and download data at any time through the system.
In addition, an extension point may be added on the basis of the above 6 subsystems, see the outward extension point in fig. 5. An extension point is an extension and complement to the main flow. Illustratively, the user can implement the following two functions through the extension point: firstly, a new system is accessed, and functions and capabilities which are not provided are added; and secondly, accessing a new system to replace the functions and the capabilities of the original subsystem.
As one example, a demand quote extension point is established. Through the requirement lifting and testing extension point, the requirement lifting and testing information can be synchronized externally, and the external requirement lifting and testing information can be received.
As another example, a test feedback extension point is established. Through the test feedback extension point, the test report can be synchronized to the outside, and the external test report can be received.
As yet another example, a publish packet extension point is established. By the distribution packet extension point, the packet information can be synchronously pre-distributed to the outside, and security check, resource information check and the like can be performed. And receiving and sending the distribution packet through the distribution packet extension point to carry out a distribution process.
Referring to fig. 8, fig. 8 is a schematic diagram of a main structure of an apparatus for updating a mobile application version according to an embodiment of the present invention, where the apparatus for updating a mobile application version may implement a method for updating a mobile application version, and as shown in fig. 7, the apparatus for updating a mobile application version specifically includes:
a setting module 801, configured to set a version number of the mobile application according to a development process of the mobile application and a mobile application version configuration table, where the mobile application version configuration table includes the version number of the mobile application and a corresponding relationship between the development process of the mobile application and the component configuration table.
A building module 802, configured to build an installation package of the mobile application based on the component configuration table corresponding to the version number, the component corresponding to the product requirement of the mobile application, and the product requirement of the mobile application, where the component configuration table includes the version number of the component.
The updating module 803 is configured 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 update the version number of the mobile application according to the component configuration table.
In an embodiment of the present invention, the setting module 801 is specifically configured to learn a component configuration table in the mobile application configuration table according to a development process of a mobile application;
determining a component configuration table of the highest version based on the component corresponding to the product requirement in the obtained component configuration table;
and taking the version number of the mobile application corresponding to the component configuration table with the highest version as the version number of the mobile application.
In an embodiment of the present invention, the building module 702 is specifically configured to build a test component configuration table based on a component configuration table of a version number and a component corresponding to a product requirement;
and building an installation package of the mobile application according to the test component configuration table.
In an embodiment of the present invention, the constructing module 702 is specifically configured to update, in the component configuration table, the version number of the component corresponding to the product requirement based on the component configuration table with the version number and the component corresponding to the product requirement;
and taking the component configuration table comprising the version number of the component corresponding to the product requirement as a test component configuration table.
In an embodiment of the present invention, the update module 703 is specifically configured to combine the installation package that the mobile application passes the test with other installation packages that the mobile application passes the test to form an integrated installation package;
and after the integrated installation package passes the test, updating the version number of the component corresponding to the installation package in the integrated installation package in the component configuration table, and updating the version number of the mobile application according to the component configuration table.
In an embodiment of the present invention, the building module 702 is further configured to determine to submit the installation package of the mobile application for testing according to a development process of the mobile application.
In an embodiment of the present invention, the updating module 703 is further configured to determine, according to the development process of the mobile application, that the installation package that passes the test of the mobile application and other installation packages that pass the test of the mobile application are combined to form an integrated installation package.
Fig. 9 illustrates an exemplary system architecture 900 of a method of updating a mobile application version or an apparatus for updating a mobile application version to which embodiments of the present invention may be applied.
As shown in fig. 9, the system architecture 900 may include end devices 901, 902, 903, a network 904, and a server 905. Network 904 is the medium used to provide 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 fiber optic cables, to name a few.
A user may use the terminal devices 901, 902, 903 to interact with a server 905 over a network 904 to receive or send messages and the like. The terminal devices 901, 902, 903 may have installed thereon various messenger client applications such as, for example only, a shopping-like application, a web browser application, a search-like application, an instant messaging tool, a mailbox client, social platform software, etc.
The terminal devices 901, 902, 903 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.
The server 905 may be a server providing various services, such as a background management server (for example only) providing support for shopping websites browsed by users using the terminal devices 901, 902, 903. The backend management server may analyze and perform other processing on the received data such as the product information query request, and feed back a processing result (for example, target push information, product information — just an example) to the terminal device.
It should be noted that the method for updating the mobile application version provided by the embodiment of the present invention is generally performed by the server 905, and accordingly, the apparatus for updating the mobile application version is generally disposed in the server 905.
It should be understood that the number of terminal devices, networks, and servers in fig. 9 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Referring now to FIG. 10, a block diagram of a computer system 1000 suitable for use with a terminal device implementing an embodiment of the invention is shown. The terminal device shown in fig. 10 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.
As shown in fig. 10, the computer system 1000 includes a Central Processing Unit (CPU)1001 that 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 section 1008 into a Random Access Memory (RAM) 1003. In the RAM 1003, various programs and data necessary for the operation of the system 1000 are also stored. The CPU 1001, ROM 1002, and RAM 1003 are connected to each other via a bus 1004. An input/output (I/O) interface 1005 is also connected to bus 1004.
The following components are connected to the I/O interface 1005: an input section 1006 including a keyboard, a mouse, and the like; an output section 1007 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 1008 including a hard disk and the like; and a communication section 1009 including a network interface card such as a LAN card, a modem, or the like. The communication section 1009 performs communication processing via a network such as the internet. The driver 1010 is also connected to the I/O interface 1005 as necessary. A removable medium 1011 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 1010 as necessary, so that a computer program read out therefrom is mounted into the storage section 1008 as necessary.
In particular, according to the embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication part 1009 and/or installed from the removable medium 1011. The computer program executes the above-described functions defined in the system of the present invention when executed by the Central Processing Unit (CPU) 1001.
It should be noted that the computer readable medium shown in the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present invention, a computer 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. In the present invention, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer 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 computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The modules described in the embodiments of the present invention may be implemented by software or hardware. The described modules may also be provided in a processor, which may be described as: a processor includes a transmitting unit, an obtaining unit, a determining unit, and a first processing unit. The names of these units do not in some cases constitute a limitation to the unit itself, and for example, the sending unit may also be described as a "unit sending a picture acquisition request to a connected server".
As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to comprise:
setting a version number of the mobile application according to a development process of the mobile application, a component corresponding to a product requirement of the mobile application and a mobile application version configuration table, wherein the mobile application version configuration table comprises the version number of the mobile application and a corresponding relation between the development process of the mobile application and the component configuration table;
constructing an installation package of the mobile application based on the component configuration table corresponding to the version number and the component corresponding to the product requirement, wherein the component configuration table comprises the version number of the component;
and 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.
According to the technical scheme of the embodiment of the invention, the version number of the mobile application is set according to the development process of the mobile application, the component corresponding to the product requirement of the mobile application and the mobile application version configuration table; constructing an installation package of the mobile application based on the component configuration table corresponding to the version number and the product requirement of the mobile application; and 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. The version number of the mobile application can be uniformly configured in the development process and can be updated in time after the installation package passes the test, so that the efficiency of developing the mobile APP can be improved.
The above-described embodiments should not be construed as limiting the scope of the invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims (12)

1. A method of updating a mobile application version, comprising:
setting a version number of the mobile application according to a development process of the mobile application, a component corresponding to a product requirement of the mobile application and a mobile application version configuration table, wherein the mobile application version configuration table comprises the version number of the mobile application and a corresponding relation between the development process of the mobile application and the component configuration table;
constructing an installation package of the mobile application based on the component configuration table corresponding to the version number and the component corresponding to the product requirement, wherein the component configuration table comprises the version number of the component;
and 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.
2. The method for updating the version of the mobile application according to claim 1, wherein the setting the version number of the mobile application according to the development process of the mobile application, the product requirement corresponding component of the mobile application and the version configuration table of the mobile application comprises:
acquiring a component configuration table in the mobile application configuration table according to the development process of the mobile application;
determining a component configuration table of the highest version based on the component corresponding to the product requirement in the obtained component configuration table;
and taking the version number of the mobile application corresponding to the component configuration table with the highest version as the version number of the mobile application.
3. The method for updating a version of a mobile application according to claim 1, wherein the building an installation package of a mobile application based on the component configuration table corresponding to the version number and the component corresponding to the product requirement comprises:
establishing a test component configuration table based on the component configuration table of the version number and the component corresponding to the product requirement;
and constructing an installation package of the mobile application according to the test component configuration table.
4. The method of claim 3, wherein the creating a test component configuration table based on the component configuration table of the version number and the component corresponding to the product requirement comprises:
updating 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;
and taking a component configuration table comprising the version number of the component corresponding to the product requirement as the test component configuration table.
5. The method of claim 1, wherein 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 mobile application version configuration summary table, comprises:
the installation package of the mobile application passing the test is combined with other installation packages of the mobile application passing the test to form an integrated installation package;
and after the integrated installation package passes the test, updating the version number of the component corresponding to the installation package in the integrated installation package in the component configuration table, and updating the version number of the mobile application according to the component configuration table.
6. The method for updating a mobile application version of claim 1, further comprising:
and judging to submit the installation package of the mobile application to the test according to the development process of the mobile application.
7. The method for updating a mobile application version of claim 1 or 5, further comprising:
and according to the development process of the mobile application, judging the installation package which passes the test of the mobile application, and combining the installation package with other installation packages which pass the test of the mobile application to form an integrated installation package.
8. An apparatus for updating a mobile application version, comprising:
the mobile application version configuration table comprises a mobile application version number and a corresponding relation between the mobile application development process and the mobile application version configuration table;
the building module is used for building an installation package of the mobile application based on a component configuration table corresponding to the version number and the product requirement of the mobile application, wherein the component configuration table comprises the version number of the component;
and the updating module is used for updating 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 updating the version number of the mobile application according to the component configuration table.
9. The apparatus for updating a mobile application version according to claim 8, wherein the setting module is specifically configured to learn a component configuration table from the mobile application configuration table according to a development process of a mobile application;
determining a component configuration table of the highest version based on the component corresponding to the product requirement in the obtained component configuration table;
and taking the version number of the mobile application corresponding to the highest version as the version number of the mobile application.
10. The apparatus for updating a mobile application version according to claim 8, wherein the update module is specifically configured to combine the installation package that the mobile application passes the test with other installation packages that the mobile application passes the test to form an integrated installation package;
and after the integrated installation package passes the test, updating the version number of the component corresponding to the installation package in the integrated installation package in the component configuration table, and updating the version number of the mobile application according to the component configuration table.
11. An electronic device for updating a mobile application version, comprising:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-7.
12. A computer-readable medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-7.
CN202010640057.3A 2020-07-06 2020-07-06 Method, device, equipment and computer readable medium for updating mobile application version Pending CN113778476A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010640057.3A CN113778476A (en) 2020-07-06 2020-07-06 Method, device, equipment and computer readable medium for updating mobile application version

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010640057.3A CN113778476A (en) 2020-07-06 2020-07-06 Method, device, equipment and computer readable medium for updating mobile application version

Publications (1)

Publication Number Publication Date
CN113778476A true CN113778476A (en) 2021-12-10

Family

ID=78835109

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010640057.3A Pending CN113778476A (en) 2020-07-06 2020-07-06 Method, device, equipment and computer readable medium for updating mobile application version

Country Status (1)

Country Link
CN (1) CN113778476A (en)

Similar Documents

Publication Publication Date Title
CN113505520A (en) Method, device and system for supporting heterogeneous federated learning
US8856155B2 (en) Management of configuration data structures in multi-layer data models
CN113778486A (en) Containerization processing method, device, medium and equipment for code pipeline
US10417200B2 (en) Data migration for service upgrades
CN109828830B (en) Method and apparatus for managing containers
CN112817562A (en) Service processing method and device
CN110795331A (en) Software testing method and device
CN110119279A (en) A kind of method and apparatus applied and its upgrade
CN110443034B (en) Risk program file identification method and device, computing equipment and medium
CN112506771A (en) Message comparison method and device
CN115964302A (en) Data testing method and device
CN112825525A (en) Method and apparatus for processing transactions
CN115801873A (en) Service distribution method, system, electronic device and storage medium
CN110580216A (en) application extraction and detection method and device
CN113076186B (en) Task processing method, device, electronic equipment and storage medium
CN113778476A (en) Method, device, equipment and computer readable medium for updating mobile application version
CN115309558A (en) Resource scheduling management system, method, computer equipment and storage medium
CN113918525A (en) Data exchange scheduling method, system, electronic device, medium, and program product
CN114693131A (en) Fault processing method and device for accessory robot
CN113434382A (en) Database performance monitoring method and device, electronic equipment and computer readable medium
CN113011858A (en) Audit project configuration and execution method and device
CN113312900A (en) Data verification method and device
CN113296796A (en) Project release method, device, system, storage medium and electronic equipment
CN113378346A (en) Method and device for model simulation
CN112559001A (en) Method and device for updating application

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