CN112559373B - Software compatibility management method and system - Google Patents
Software compatibility management method and system Download PDFInfo
- Publication number
- CN112559373B CN112559373B CN202011549225.4A CN202011549225A CN112559373B CN 112559373 B CN112559373 B CN 112559373B CN 202011549225 A CN202011549225 A CN 202011549225A CN 112559373 B CN112559373 B CN 112559373B
- Authority
- CN
- China
- Prior art keywords
- product
- product set
- version
- field
- combination
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/368—Test management for test version control, e.g. updating test cases to a new software version
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Stored Programmes (AREA)
Abstract
The invention belongs to the technical field of system integration project management and discloses a software compatibility management method which comprises the following steps: establishing a plurality of related product sets at a remote working end; according to the product version compatibility requirement, the remote working end tests to obtain a compatible version combination of each associated product set; binding each associated product set and the corresponding compatible version combination and storing the combined product set and the corresponding compatible version combination in a database of a remote working end system; the remote working end receives a deployment or version upgrading request of a field product set sent by a certain field server end; the remote working end carries out compatibility check on the product versions in the field product set by using the compatible version combination bound with the associated product set; the field service end upgrades the deployment or version of the field product set; and the remote working end updates the product version deployment state of the field service end. The invention can simplify the complexity of field product deployment and product version upgrading and reduce the risk of product deployment and upgrading.
Description
Technical Field
The invention relates to the technical field of integrated project management, in particular to a software compatibility management method and system.
Background
At present, in an information system integration project, a plurality of interdependent software products are often deployed. When a certain product needs to be upgraded, if the product depending on the product or the product depending on the product does not perform necessary upgrading, compatibility problems are often caused, upgrading is failed, and field accidents are caused.
These interdependent products are often not developed by the same research and development organization; the person performing the upgrade on-site is typically not a developer. Therefore, when upgrading products, it is necessary to establish an effective management mechanism to clear the compatibility relationship between product versions and ensure the safe implementation of field upgrading.
Disclosure of Invention
The invention aims to provide a software compatibility management method and a software compatibility management system, which solve the problem of compatibility among product versions.
In order to achieve the purpose, the invention adopts the following technical scheme:
the invention provides a software compatibility management method, which comprises the following steps:
step 1: establishing a plurality of associated product sets at a remote working end, wherein each associated product set at least comprises two products, and the products in each associated product set respectively correspond to different product versions;
step 2: according to the product version compatibility requirement, the remote working end tests to obtain a compatible version combination of each associated product set;
and step 3: binding each associated product set and the corresponding compatible version combination and storing the combined product set and the corresponding compatible version combination in a database of a remote working end system;
and 4, step 4: the remote working end receives a deployment or version upgrading request of a field product set sent by a certain field server end;
and 5: the remote working end searches out a related product set matched with the field product set from the database, and performs compatibility check on product versions in the field product set by using a compatible version combination bound with the related product set;
step 6: after the compatibility check is passed, the field service end upgrades the deployment or version of the field product set;
and 7: and after the deployment or version upgrade of the field product set is finished, the remote working end updates the product version deployment state of the field service end.
Further, the step 2 specifically includes:
step 201: obtaining the product version combination number of each associated product set according to the version number of each product in each associated product set;
step 202: judging whether the product version combination number of the associated product set is smaller than a preset threshold value, if so, directly testing the product version combination in the product version combination of the associated product set to obtain a compatible version combination; and if the product version combination is larger than or equal to the preset threshold, selecting the product version combination containing the live server product active version in the product version combination of the associated product set to perform compatibility test, so as to obtain the compatible version combination of the associated product set.
Further, the preset threshold value is 5-20.
Further, the step 5 specifically includes:
step 501: the remote working end reads any associated product set in the database;
step 502: judging whether the associated product set is contained in the field product set, if so, entering a step 503; if not, returning to the step 501;
step 503: judging whether the product version combination deployed or upgraded by the field product set belongs to the compatible version combination of the associated product set, if so, passing the compatibility check; if not, the compatibility check fails, returning to step 501 until all the associated product sets in the database are traversed.
Further, after step 7, the method further comprises:
collecting the deployment states of all product versions in the field service end, monitoring whether the number of compatible version combinations of each associated product set exceeds a set threshold value, if so, triggering an alarm, prompting to merge the active compatible version combinations in the field service end, and updating the corresponding compatible version combinations bound with each associated product set in the database.
Further, the set threshold is 3-5.
Further, after step 7, the method further comprises: and supplementing the field product set serving as a new associated product set into the database so as to carry out compatibility check on product versions in other subsequent field product sets.
The invention also provides a software compatibility management system for realizing the software compatibility management method, wherein the system comprises a related product set building module, a test module, a binding module, a receiving module and a compatibility checking module;
the system comprises a related product set building module, a remote working end and a product processing module, wherein the related product set building module is used for building a plurality of related product sets at the remote working end, each related product set at least comprises two products, and the products in each related product set respectively correspond to different product versions;
a test module: according to the product version compatibility requirement, the remote working end tests to obtain a compatible version combination of each associated product set;
a binding module: binding each associated product set and the corresponding compatible version combination and storing the combined product set and the corresponding compatible version combination in a database of a remote working end system;
a receiving module: the remote working end receives a deployment or version upgrading request of a field product set sent by a certain field server end;
a compatibility checking module: and the remote working end searches out a related product set matched with the field product set from the database, and performs compatibility check on the product versions in the field product set by using the compatible version combination bound with the related product set.
Further, the test module further comprises:
a calculation module: obtaining the product version combination number of each associated product set according to the version number of each product in each associated product set;
a first judgment module: judging whether the product version combination number of the associated product set is smaller than a preset threshold value, if so, directly testing the product version combination in the product version combination of the associated product set to obtain a compatible version combination; and if the product version combination is larger than or equal to the preset threshold, selecting the product version combination containing the live server product active version in the product version combination of the associated product set to perform compatibility test, so as to obtain the compatible version combination of the associated product set.
Further, the compatibility check module further comprises:
a reading module: the remote working end reads any associated product set in the database;
a second judging module: judging whether the associated product set is contained in the field product set, if so, entering a third judgment module; if not, returning to the reading module;
a third judging module: judging whether the product version combination deployed or upgraded by the field product set belongs to the compatible version combination of the associated product set, if so, passing the compatibility check; if not, the compatibility check fails, and the read module is returned until all the associated product sets in the database are traversed.
Compared with the prior art, the invention has the beneficial effects that:
the software compatibility management method can timely find out the problem of incompatibility of product versions in the process of field product deployment or upgrading, avoid field engineering accidents, and ensure the safe implementation of field product deployment or version upgrading.
The invention degrades the high-dimensional problem into the low-dimensional problem through the associated product set; the low-dimensional problem is further projected as a one-dimensional problem by "compatible version combining": for a field engineer to only touch a compatible version combination, rather than individually touching a new version of a product, the upgrade process is embodied as a migration from one compatible version combination to a new compatible version combination. Therefore, the invention can simplify the complexity of field product deployment and product version upgrading and reduce the risk of product deployment and upgrading.
Drawings
Fig. 1 is a flowchart of a software compatibility management method according to embodiment 1 of the present invention.
Fig. 2 is a flowchart of a software compatibility management method according to embodiment 2 of the present invention.
Fig. 3 is a flowchart of a software compatibility management method according to embodiment 3 of the present invention.
Fig. 4 is a schematic structural diagram of a software compatibility management system according to embodiment 4 of the present invention.
Detailed Description
The following examples are intended to illustrate the invention, but are not intended to limit the scope of the invention. Unless otherwise specified, the technical means used in the examples are conventional means well known to those skilled in the art. The test methods in the following examples are conventional methods unless otherwise specified.
Example 1
Fig. 1 shows a flow chart of a software compatibility management method of the present invention. Referring to fig. 1, the software compatibility management method of the present invention includes the following steps:
step S101: establishing a plurality of associated product sets at a remote working end, wherein each associated product set at least comprises two products, and the products in each associated product set respectively correspond to different product versions;
step S102: according to the product version compatibility requirement, the remote working end tests to obtain a compatible version combination of each associated product set;
step S103: binding each associated product set and the corresponding compatible version combination and storing the combined product set and the corresponding compatible version combination in a database of a remote working end system;
step S104: the remote working end receives a deployment or version upgrading request of a field product set sent by a certain field server end;
step S105: the remote working end searches out a related product set matched with the field product set from the database, and performs compatibility check on product versions in the field product set by using a compatible version combination bound with the related product set;
step S106: after the compatibility check is passed, the field service end upgrades the deployment or version of the field product set;
step S107: and after the deployment or version upgrade of the field product set is finished, the remote working end updates the product version deployment state of the field service end.
In practical application, the remote working end not only includes a computer, but also includes related equipment and personnel such as a product planner, a software developer, a deployment personnel, a tester and the like. The field service end comprises a computer, a field engineer and other related equipment and personnel. And (4) the product planners input the products and establish a related product set by combining the requirements of field integration projects based on a high-cohesion low-coupling principle. The associated product set is the core of the software compatibility management of the present invention. For example: a, b, c, d, e, f, g, h, i, which are common products, may be divided into the following sets of related products:
S1（a，b，c，d，e，f）；
S2（e，f，g，h，i）；
S3（a，b，h，i）。
product developers are responsible for development and version management of respective products, and one product (e.g., product a) generally has multiple versions. Each version may have version compatibility requirements for other products in the associated product set. The tester is responsible for verifying and entering compatible version combinations of each associated product set, and one associated product set generally has a plurality of compatible version combinations. The field engineer of the field service end is responsible for managing the project and the product version deployment state thereof, and one field service end can only be in the product version deployment state. When field deployment and field upgrade are implemented, various products and versions thereof deployed by a field server are input, and the system can perform compatibility check. After the compatibility check is passed, the deployment or the upgrade of the field product set can be implemented; after deployment and upgrade are completed, the product version deployment state of the field server side needs to be updated.
In a specific embodiment, the step S102 specifically includes:
step 1021: obtaining the product version combination number of each associated product set according to the version number of each product in each associated product set;
step 1022: judging whether the product version combination number of the associated product set is smaller than a preset threshold value, if so, directly testing the product version combination in the product version combination of the associated product set to obtain a compatible version combination; and if the product version combination is larger than or equal to the preset threshold, selecting the product version combination containing the live server product active version in the product version combination of the associated product set to perform compatibility test, so as to obtain the compatible version combination of the associated product set.
Specifically, there are 6 products, P, per associated product set1、P2、P3、P4、P5、P6Product P1With 4 versions, product P2With 4 versions, product P3There are 4 versions, …, product P6If there are 4 versions, the number Q of version combinations of the associated product set is 4 × 4 × 4 × 4 × 4 × 4 × 4=4096, so for the associated product set with a large version combination space, it is obvious that a tester cannot examine all version combinations. According to the embodiment of the invention, after the active versions of the products are obtained, in practice, on one hand, the method can be communicated with developers and field engineers, select necessary version combinations to perform compatibility testing, and obtain compatible version combinations, so that unnecessary version combinations can be eliminated, and the difficulty in the version compatibility testing of each associated product set is reduced; on the other hand, a preset threshold value can be directly set, and the preset threshold value is 5-20. But not limited thereto, in other embodiments, the preset threshold may be set to be enlarged or reduced according to actual needs.
It is understood that the compatible version combinations passing the test will generally be some latest version combinations of each product, as shown in fig. 2, it is preset that some associated product set includes a, b, h, i, and product a includes version a4、a5Product b includes version b2Product h includes version h6、h7Product i includes version i3、i4Then, the active version a of each product is obtained from the product version deployment state of the field server5、b2、h6、h7、i4Selecting two version combinations (a)5→b2→h6→i4And a5→b2→h7→i4) And carrying out compatibility test.
In another specific embodiment, the step 501 specifically includes:
step 5011: the remote working end reads any associated product set in the database;
step 5012: judging whether the associated product set is contained in the field product set, if so, entering a step 5013; if not, return to step 5011;
step 5013: judging whether the product version combination deployed or upgraded by the field product set belongs to the compatible version combination of the associated product set, if so, passing the compatibility check; if not, the compatibility check fails, returning to step 5011 until all the associated product sets in the database are traversed.
Specifically, assuming a field product set T (a, b, d, e, f, g, h, i), the associated product sets of the database include the following:
S1（a，b，c，d，e，f）；
S2（e，f，g，h，i）；
S3（a，b，h，i）；
reading the associated product set S1. Judging the associated product set S1Whether the product is included in the field product set T or not can be known by comparison, because the product set S is related1Including product c, but not product c, the on-site product set T, so the associated product set S can be determined1Not included in the field product set T and not based on the associated product set S1The compatible version combination of (2) performs compatibility check on the versions of the field product set T. Then, the reading of the associated product set S is continued2Judging the associated product set S2The product set S can be related by comparison2Contained in the field product set T and based on the associated product set S2The compatible version combination of (2) performs compatibility checking on the versions of the field product set. Finally, judging whether the product version combination (e, f, g, h, i) in the field product set T (a, b, d, e, f, g, h, i) belongs to the related product set S2In a compatible version combination, it can continue to traverse the database in the manner described aboveHis associated product set (e.g. S)3) Until all the associated product sets T are traversed, and the deployed or upgraded product version combinations of the field product set T all satisfy all the associated product sets (e.g., S) included in the field product set T2、S3) The compatibility check passes if compatible versions of (1) are combined. In other words, a product version combination once a deployment or upgrade of a field product set fails to satisfy any one of the associated product sets (e.g., S) contained in the field product set T2Or S3) The compatibility check fails if the compatible versions are combined.
Example 2
FIG. 2 is a flow chart illustrating another software compatibility management method of the present invention. Referring to fig. 2, the software compatibility management method of the present invention includes the following steps:
step S201: establishing a plurality of associated product sets at a remote working end, wherein each associated product set at least comprises two products, and the products in each associated product set respectively correspond to different product versions;
step S202: according to the product version compatibility requirement, the remote working end tests to obtain a compatible version combination of each associated product set;
step S203: binding each associated product set and the corresponding compatible version combination and storing the combined product set and the corresponding compatible version combination in a database of a remote working end system;
step S204: the remote working end receives a deployment or version upgrading request of a field product set sent by a certain field server end;
step S205: the remote working end searches out a related product set matched with the field product set from the database, and performs compatibility check on product versions in the field product set by using a compatible version combination bound with the related product set;
step S206: after the compatibility check is passed, the field service end upgrades the deployment or version of the field product set;
step S207: after the deployment or version upgrading of the field product set is completed, the remote working end updates the product version deployment state of the field service end;
step S208: collecting the deployment states of all product versions in the field service end, monitoring whether the number of compatible version combinations of each associated product set exceeds a set threshold value, if so, triggering an alarm, prompting to merge the active compatible version combinations in the field service end, and updating the corresponding compatible version combinations bound with each associated product set in the database.
It can be appreciated that by collecting all product version deployment states in the field service, monitoring the number of compatible version combinations for each associated product set, one-dimensional problems can be avoided from expanding over time.
Specifically, the threshold value is set to be 3-5.
Example 3
FIG. 3 is a flow chart illustrating another software compatibility management method of the present invention. Referring to fig. 3, the software compatibility management method of the present invention includes the following steps:
step S301: establishing a plurality of associated product sets at a remote working end, wherein each associated product set at least comprises two products, and the products in each associated product set respectively correspond to different product versions;
step S302: according to the product version compatibility requirement, the remote working end tests to obtain a compatible version combination of each associated product set;
step S303: binding each associated product set and the corresponding compatible version combination and storing the combined product set and the corresponding compatible version combination in a database of a remote working end system;
step S304: the remote working end receives a deployment or version upgrading request of a field product set sent by a certain field server end;
step S305: the remote working end searches out a related product set matched with the field product set from the database, and performs compatibility check on product versions in the field product set by using a compatible version combination bound with the related product set;
step S206: after the compatibility check is passed, the field service end upgrades the deployment or version of the field product set;
step S307: after the deployment or version upgrading of the field product set is completed, the remote working end updates the product version deployment state of the field service end;
step S308: and supplementing the field product set serving as a new associated product set into the database so as to carry out compatibility check on product versions in other subsequent field product sets.
It should be noted that, when the field product set is supplemented into the database as a new associated product set, each product version in the field product set is determined first, and a compatible version combination is formed based on each product version, and then the field product set is used as a new associated product set and supplemented into the database with the corresponding compatible version combination, so that the database is continuously perfected in this way, and the version compatibility checking accuracy of the subsequent field product set is further improved.
Example 4
Fig. 4 is a schematic diagram illustrating a software compatibility management system according to the present invention. Referring to fig. 4, the software compatibility management system of the present invention includes an associated product set building module 401, a testing module 402, a binding module 403, a receiving module 404, and a compatibility checking module 405;
the related product set building module 401 is configured to build a plurality of related product sets at the remote working end, where each related product set includes at least two products;
the test module 402: according to the product version compatibility requirement, the remote working end tests to obtain a compatible version combination of each associated product set;
the binding module 403: binding each associated product set and the corresponding compatible version combination and storing the combined product set and the corresponding compatible version combination in a database of a remote working end system;
the receiving module 404: the remote working end receives a deployment or version upgrading request of a field product set sent by a certain field server end;
compatibility checking module 405: and the remote working end searches out a related product set matched with the field product set from the database, and performs compatibility check on the product versions in the field product set by using the compatible version combination bound with the related product set.
In one embodiment, the test module 402 further comprises:
the calculation module 4021: obtaining the product version combination number of each associated product set according to the version number of each product in each associated product set;
the first judging module 4022: judging whether the product version combination number of the associated product set is smaller than a preset threshold value, if so, directly testing the product version combination in the product version combination of the associated product set to obtain a compatible version combination; and if the product version combination is larger than or equal to the preset threshold, selecting the product version combination containing the live server product active version in the product version combination of the associated product set to perform compatibility test, so as to obtain the compatible version combination of the associated product set.
In a specific embodiment, the compatibility check module 405 further includes:
the reading module 4051: the remote working end reads any associated product set in the database;
second determination module 4052: judging whether the associated product set is contained in the field product set, if so, entering a third judgment module; if not, returning to the reading module;
third judging module 4053: judging whether the product version combination deployed or upgraded by the field product set belongs to the compatible version combination of the associated product set, if so, passing the compatibility check; if not, the compatibility check fails, and the read module is returned until all the associated product sets in the database are traversed.
The above-mentioned embodiments are merely preferred embodiments of the present invention, which are merely illustrative and not restrictive, and it should be understood that other embodiments may be easily made by those skilled in the art by replacing or changing the technical contents disclosed in the specification, and therefore, all changes and modifications that are made on the principle of the present invention should be included in the scope of the claims of the present invention.
Claims (8)
1. A software compatibility management method is characterized by comprising the following steps:
step 1: establishing a plurality of associated product sets at a remote working end, wherein each associated product set at least comprises two products, and the products in each associated product set respectively correspond to different product versions;
step 2: according to the product version compatibility requirement, the remote working end tests to obtain a compatible version combination of each associated product set;
and step 3: binding each associated product set and the corresponding compatible version combination and storing the combined product set and the corresponding compatible version combination in a database of a remote working end system;
and 4, step 4: the remote working end receives a deployment or version upgrading request of a field product set sent by a certain field server end;
and 5: the remote working end searches out a related product set matched with the field product set from the database, and performs compatibility check on product versions in the field product set by using a compatible version combination bound with the related product set;
step 6: after the compatibility check is passed, the field service end upgrades the deployment or version of the field product set;
and 7: and after the deployment or version upgrade of the field product set is finished, the remote working end updates the product version deployment state of the field service end.
2. The software compatibility management method according to claim 1, wherein the step 2 specifically includes:
step 201: obtaining the product version combination number of each associated product set according to the version number of each product in each associated product set;
step 202: judging whether the product version combination number of the associated product set is smaller than a preset threshold value, if so, directly testing the product version combination in the product version combination of the associated product set to obtain a compatible version combination; and if the product version combination is larger than or equal to the preset threshold, selecting the product version combination containing the live server product active version in the product version combination of the associated product set to perform compatibility test, so as to obtain the compatible version combination of the associated product set.
3. The software compatibility management method according to claim 1, wherein the step 5 specifically includes:
step 501: the remote working end reads any associated product set in the database;
step 502: judging whether the associated product set is contained in the field product set, if so, entering a step 503; if not, returning to the step 501;
step 503: judging whether the product version combination deployed or upgraded by the field product set belongs to the compatible version combination of the associated product set, if so, passing the compatibility check; if not, the compatibility check fails, returning to step 501 until all the associated product sets in the database are traversed.
4. The software compatibility management method according to claim 1, further comprising, after step 7:
collecting the deployment states of all product versions in the field service end, monitoring whether the number of compatible version combinations of each associated product set exceeds a set threshold value, if so, triggering an alarm, prompting to merge the active compatible version combinations in the field service end, and updating the corresponding compatible version combinations bound with each associated product set in the database.
5. The software compatibility management method according to claim 1, further comprising, after step 7: and supplementing the field product set serving as a new associated product set into the database so as to carry out compatibility check on product versions in other subsequent field product sets.
6. The software compatibility management system for realizing the software compatibility management method according to any one of claims 1 to 5, wherein the system comprises an associated product set building module, a testing module, a binding module, a receiving module and a compatibility checking module;
the system comprises a related product set building module, a remote working end and a product processing module, wherein the related product set building module is used for building a plurality of related product sets at the remote working end, each related product set at least comprises two products, and the products in each related product set respectively correspond to different product versions;
a test module: according to the product version compatibility requirement, the remote working end tests to obtain a compatible version combination of each associated product set;
a binding module: binding each associated product set and the corresponding compatible version combination and storing the combined product set and the corresponding compatible version combination in a database of a remote working end system;
a receiving module: the remote working end receives a deployment or version upgrading request of a field product set sent by a certain field server end;
a compatibility checking module: and the remote working end searches out a related product set matched with the field product set from the database, and performs compatibility check on the product versions in the field product set by using the compatible version combination bound with the related product set.
7. The software compatibility management system of claim 6, wherein said testing module further comprises:
a calculation module: obtaining the product version combination number of each associated product set according to the version number of each product in each associated product set;
a first judgment module: judging whether the product version combination number of the associated product set is smaller than a preset threshold value, if so, directly testing the product version combination in the product version combination of the associated product set to obtain a compatible version combination; and if the product version combination is larger than or equal to the preset threshold, selecting the product version combination containing the live server product active version in the product version combination of the associated product set to perform compatibility test, so as to obtain the compatible version combination of the associated product set.
8. The software compatibility management system of claim 6, wherein said compatibility checking module further comprises:
a reading module: the remote working end reads any associated product set in the database;
a second judging module: judging whether the associated product set is contained in the field product set, if so, entering a third judgment module; if not, returning to the reading module;
a third judging module: judging whether the product version combination deployed or upgraded by the field product set belongs to the compatible version combination of the associated product set, if so, passing the compatibility check; if not, the compatibility check fails, and the read module is returned until all the associated product sets in the database are traversed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011549225.4A CN112559373B (en) | 2020-12-24 | 2020-12-24 | Software compatibility management method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011549225.4A CN112559373B (en) | 2020-12-24 | 2020-12-24 | Software compatibility management method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112559373A CN112559373A (en) | 2021-03-26 |
| CN112559373B true CN112559373B (en) | 2022-04-08 |
Family
ID=75033268
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011549225.4A Active CN112559373B (en) | 2020-12-24 | 2020-12-24 | Software compatibility management method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112559373B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114328270B (en) * | 2022-01-20 | 2024-05-03 | 重庆长安汽车股份有限公司 | OTA upgrade detection method based on SOA service and readable storage medium |
| CN116737208B (en) * | 2023-08-16 | 2023-10-24 | 深圳市德兰明海新能源股份有限公司 | Software maintenance upgrade management method and device and electronic equipment |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101169749A (en) * | 2007-11-20 | 2008-04-30 | 中兴通讯股份有限公司 | Software edition upgrading management device and software edition upgrading management method |
| CN102495733A (en) * | 2011-12-08 | 2012-06-13 | 方正国际软件有限公司 | Methods for detecting compatibility of application program and relevant database script and performing upgrading maintenance on application program and relevant database script |
| CN103282843A (en) * | 2010-12-28 | 2013-09-04 | 恩德斯+豪斯流量技术股份有限公司 | Field device having long-erm firmware compatibility |
| US9063748B1 (en) * | 2013-03-19 | 2015-06-23 | Amdocs Software Systems Limited | System, method, and computer program for allowing a plurality of application programming interface (API) versions to interact with a single version of implementation code |
| CN107291457A (en) * | 2017-06-08 | 2017-10-24 | 重庆长安汽车股份有限公司 | The long-range renewal computing system and method for entire car controller software |
| CN110635994A (en) * | 2019-09-30 | 2019-12-31 | 郑州信大捷安信息技术股份有限公司 | Heterogeneous interconnection system and method based on self-adaptive detection |
-
2020
- 2020-12-24 CN CN202011549225.4A patent/CN112559373B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101169749A (en) * | 2007-11-20 | 2008-04-30 | 中兴通讯股份有限公司 | Software edition upgrading management device and software edition upgrading management method |
| CN103282843A (en) * | 2010-12-28 | 2013-09-04 | 恩德斯+豪斯流量技术股份有限公司 | Field device having long-erm firmware compatibility |
| CN102495733A (en) * | 2011-12-08 | 2012-06-13 | 方正国际软件有限公司 | Methods for detecting compatibility of application program and relevant database script and performing upgrading maintenance on application program and relevant database script |
| US9063748B1 (en) * | 2013-03-19 | 2015-06-23 | Amdocs Software Systems Limited | System, method, and computer program for allowing a plurality of application programming interface (API) versions to interact with a single version of implementation code |
| CN107291457A (en) * | 2017-06-08 | 2017-10-24 | 重庆长安汽车股份有限公司 | The long-range renewal computing system and method for entire car controller software |
| CN110635994A (en) * | 2019-09-30 | 2019-12-31 | 郑州信大捷安信息技术股份有限公司 | Heterogeneous interconnection system and method based on self-adaptive detection |
Non-Patent Citations (3)
| Title |
|---|
| Component-Based Software Update Process in Collaborative Software Development;Tien N.Nguyen;《2008 15th Asia-Pacific Software Engineering Conference》;20081222;全文 * |
| 国产基础软件应用平台的兼容性测试研究;郭军 等;《计算机科学》;20120731;第39卷(第6期);全文 * |
| 基于网络外部性的产品升级与兼容选择分析;潘小军 等;《系统工程理论方法应用》;20060606;第15卷(第2期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112559373A (en) | 2021-03-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7522978B2 (en) | Method and device of generating logic control units for railroad station-based vital computer apparatuses | |
| CN102934114B (en) | For the checkpoint of file system | |
| CN100541489C (en) | External metadata is handled | |
| CN101542445B (en) | Apparatus and methods of a zero single point of failure load balancer | |
| CN101268620B (en) | Device management system and method for managing device management object | |
| CN112559373B (en) | Software compatibility management method and system | |
| CN109074362A (en) | Fractionation and moving range in distributed system | |
| ITTO980722A1 (en) | PROCEDURE FOR INSTALLING AND / OR VERIFYING THE SOFTWARE FOR A COMPUTER SYSTEM MADE TO ORDER, AND COMPUTER SYSTEM FOR | |
| CN104090776A (en) | Software development method and system | |
| CN103019718A (en) | Use of distributed source control in centralized source control environment | |
| CN100392651C (en) | Universal constraining realizing method for real-time internal memory database | |
| US7386579B2 (en) | System, method, and computer program product for storing test results in a database | |
| CN106415539A (en) | Artifact correlation between domains | |
| CN112567375A (en) | Format verification method, information identification method, device and storage medium | |
| JPH11177655A (en) | Device and method for automatically verifying communication software | |
| CN109582334A (en) | The upgrade method and device of programmable logic device | |
| CN101436157A (en) | Method for processing program BUG in program test process flow | |
| CN101295314A (en) | File management system, file management method, support device thereof, and program thereof | |
| JP2008112229A (en) | Update data application method for software product | |
| Parkhomenko | Complex requirements analysis for the high-level design of Embedded Systems | |
| JP4379158B2 (en) | Parts ordering system, scrap information processing apparatus, parts ordering apparatus, scrap information processing method, and parts ordering method | |
| CN109032660A (en) | A kind of generation method of VersionCode, device, electronic equipment and storage medium | |
| CN112948480B (en) | Data extraction method, device, electronic equipment and storage medium | |
| CN109002287B (en) | Management method and device for software in cloud data system | |
| CN112988555B (en) | Interface testing method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |