CN112988222B - Method and system for checking information system integration project interface version compatibility - Google Patents
Method and system for checking information system integration project interface version compatibility Download PDFInfo
- Publication number
- CN112988222B CN112988222B CN202110446941.8A CN202110446941A CN112988222B CN 112988222 B CN112988222 B CN 112988222B CN 202110446941 A CN202110446941 A CN 202110446941A CN 112988222 B CN112988222 B CN 112988222B
- Authority
- CN
- China
- Prior art keywords
- version
- interface
- product
- compatibility
- provider
- 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
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention relates to the technical field of interface compatibility management, in particular to a method and a system for checking the compatibility of an information system integration project interface version, which comprises the following steps: constructing a main product association table, a first sub provider product association table and a second sub caller product association table which are mutually dependent on an interface between a provider and a caller, and storing the main product association table, the first sub provider product association table and the second sub caller product association table in a database; according to the deployment and/or version upgrading requirements of field products, a field associated product set is constructed, each product is used as a calling party to obtain a calling party product version, a calling interface and an interface version, the field interface product is used as a product provider, and the interface version of the corresponding provider is inquired from a database; and performing compatibility check on the calling party interface version and the providing party interface version according to the interface version compatibility standard. The invention is based on the compatibility management of the interface version, can find the version compatibility problem in the product deployment and upgrade process in time, reduces the product deployment and upgrade risk, and has better application prospect.
Description
Technical Field
The invention relates to the technical field of interface compatibility management, in particular to a method and a system for checking the interface version compatibility of an information system integration project.
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. Compatibility verification is conventionally performed using a compatibility test. For small-scale engineering, the product is less and the problem is not great. However, if there are multiple project sites, and there are more products deployed at each site and the versions are not very consistent, the portfolio of product versions expands catastrophically. So that sufficient and effective testing cannot be performed to perform the necessary compatibility verification.
Disclosure of Invention
Therefore, the invention provides the method and the system for checking the interface version compatibility of the information system integration project, which are based on the compatibility management of the interface version, are convenient for the test and verification of the interface compatibility, can find the version compatibility problem in the product deployment and upgrade processes in time and reduce the product deployment and upgrade risks.
According to the design scheme provided by the invention, the method for checking the information system integration project interface version compatibility comprises the following steps:
constructing a product main association table, a provider product first sub-association table and a caller product second sub-association table which are mutually dependent on interfaces between a provider and a caller, and storing the product main association table, the first sub-association table and the second sub-association table into a database, wherein each product version and corresponding interface version are respectively stored in the first sub-association table and the second sub-association table;
constructing a field associated product set according to the field product deployment and/or version upgrading requirements; taking each product in the field associated product set as a caller, acquiring the product version, a calling interface and an interface version of the caller, taking the field interface product as a product provider, and inquiring the interface version of the corresponding provider from a database;
and performing compatibility check on the calling party interface version and the providing party interface version according to the interface version compatibility standard.
As the information system integration project interface version compatibility checking method, further, the field associated product set at least comprises two products, the product version to be deployed and/or upgraded of each product is respectively determined, and each product is used as a calling party to obtain the product version, the interface and the interface version of the calling party.
As the information system integration project interface version compatibility checking method, the interface version number of the developed new version product is marked according to the version number declaration principle aiming at the developed new version product, and the related data in the database is updated based on the interface version number of the new version product.
The method for checking the compatibility of the interface version of the information system integration project further comprises the step of selecting the self-adaptive interface and the interface version step by step according to the product, the product version, the interface and the interface version which provide interface service for the developed new version product.
As the information system integration project interface version compatibility checking method of the invention, further, the version number declaration principle comprises the following contents: if the new version product does not change the interface, the major version number and the minor version number of the interface are kept unchanged; if the new version product changes the interface and is compatible forward, the major version number of the interface is not changed, and the minor version number is upgraded; and if the new version product changes the interface and is not forward compatible, upgrading the major version number of the interface and resetting the minor version number.
As the information system integration project interface version compatibility checking method, further, when the corresponding interface version of the developed new version product is not forward compatible, other products depending on the interface are obtained by inquiring in a database according to the new version interface, and the inquired other products are subjected to upgrading adaptation processing.
As the information system integration project interface version compatibility checking method of the invention, further, the interface version compatibility standard comprises the following contents: and if the main version number of the provider interface version is the same as the main version number of the caller interface version, and the current version number of the caller interface version is less than or equal to the minor version number of the provider interface version, judging that the provider interface version and the caller interface version are compatible, otherwise, judging that the provider interface version and the caller interface version are incompatible.
As the information system integration project interface version compatibility checking method, further, compatibility checking is carried out by traversing all deployed and/or upgraded products on site; in each product compatibility check of deployment and/or upgrade, each product in a field-associated product set is taken as a caller, all the caller calling interfaces are traversed, whether the field contains a product providing the interface is judged according to the caller calling interface and the interface version, if the field contains the product providing the interface, the product providing the interface is taken as a provider, the provider interface version is obtained by inquiring a database through the provider product version, and whether the provider interface version is compatible with the caller interface version is judged based on the interface version compatibility standard.
The information system integration project interface version compatibility checking method is characterized in that the field product is deployed and/or version upgraded according to the condition that the compatibility check is passed, and the version deployment state of the field product is updated after the deployment and/or version upgrade is completed.
Further, the present invention also provides an information system integration project interface version compatibility checking system, which comprises: a database construction module, a field engineering deployment module, and a compatibility check module, wherein,
the database construction module is used for constructing a product main association table, a provider product first sub-association table and a caller product second sub-association table which are interdependent between a provider and a caller based on interfaces, and storing the product main association table, the first sub-association table and the second sub-association table to a database, wherein each product version and corresponding interface version are respectively stored in the first sub-association table and the second sub-association table;
the field engineering deployment module is used for constructing a field associated product set according to the requirements of field product deployment and/or version upgrading; taking each product in the field associated product set as a caller, acquiring the product version, a calling interface and an interface version of the caller, taking the field interface product as a product provider, and inquiring the interface version of the corresponding provider from a database;
and the compatibility checking module is used for carrying out compatibility checking on the calling party interface version and the providing party interface version according to the interface version compatibility standard.
The invention has the beneficial effects that:
the invention verifies the version compatibility of the associated product in an interface management mode, realizes the compatibility check of the product version deployed or upgraded in the field engineering, can find the version compatibility problem in the product deployment or upgrading process in time, and avoids the field accident caused by the compatibility problem; in addition, the development team can realize compatibility check among products as long as knowing and inputting the own product interface requirements, so that a product responsible person can conveniently make corresponding coordination according to the compatibility check result, the product interface compatibility detection, verification, deployment and upgrade efficiency is improved, and the method has a good application prospect.
Description of the drawings:
FIG. 1 is a flow chart of a method for checking compatibility of an information system integration project interface version in an embodiment;
fig. 2 is a schematic diagram of a compatibility checking process for a certain field engineering product in the embodiment.
The specific implementation mode is as follows:
in order to make the objects, technical solutions and advantages of the present invention clearer and more obvious, the present invention is further described in detail below with reference to the accompanying drawings and technical solutions.
The embodiment of the invention provides a method for checking the compatibility of an information system integration project interface version, which comprises the following steps:
constructing a product main association table, a provider product first sub-association table and a caller product second sub-association table which are mutually dependent on interfaces between a provider and a caller, and storing the product main association table, the first sub-association table and the second sub-association table into a database, wherein each product version and corresponding interface version are respectively stored in the first sub-association table and the second sub-association table;
constructing a field associated product set according to the field product deployment and/or version upgrading requirements; taking each product in the field associated product set as a caller, acquiring the product version, a calling interface and an interface version of the caller, taking the field interface product as a product provider, and inquiring the interface version of the corresponding provider from a database;
and performing compatibility check on the calling party interface version and the providing party interface version according to the interface version compatibility standard.
Version compatibility verification of the associated products is carried out in an interface management mode, compatibility check of the versions of the products deployed or upgraded in the field engineering is achieved, the problem of version compatibility in the product deployment or upgrade process can be found in time, and field accidents caused by the compatibility problem are avoided.
Referring to fig. 1, a main association table of two products that are dependent to each other is established based on corresponding interfaces, one of the two products that are dependent to each other is used as a provider, the other is used as a caller, a first sub-association table between each product version of the provider and the corresponding interface version and a second sub-association table between each product version of the caller and the corresponding interface version are respectively established, and then the main association table, the first sub-association table and the second sub-association table are stored in a database in an association manner; based on the requirements of field engineering deployment or product version upgrading, a field associated product set is pre-constructed, the field associated product set at least comprises two products, and the product version to be deployed or upgraded of each product is respectively determined; and taking each product to be deployed or upgraded in the field associated product set as a calling party, respectively obtaining a product version, an interface and an interface version of the calling party, then obtaining a product providing the interface on the field as a provider, inquiring and obtaining the interface version of the provider from the database based on the product version of the provider, and finally carrying out compatibility check on the interface version of the calling party and the interface version of the provider according to an interface version compatibility standard.
Further, the versions in this embodiment may be distinguished by version numbers, where the version number is composed of a major version number MajorVersion and a minor version number MinorVersion, for example, if the interface version number is 1.2, "1" is the interface major version number, "2" is the interface minor version number, and the major version number and the minor version number may be separated by a symbol ". times".
Further, the specific characterization of the interface version compatibility standard in the embodiment of the present disclosure may be described as follows:
if the interface version of the provider is the same as the major version number of the interface version of the caller, and the minor version number of the interface version of the caller is less than or equal to the minor version number of the interface version of the provider, judging that the two are compatible; otherwise, judging that the two are incompatible.
Further, based on the foregoing method, an embodiment of the present invention further provides an information system integration project interface version compatibility checking system, including: a database construction module, a field engineering deployment module, and a compatibility check module, wherein,
the database construction module is used for constructing a product main association table, a provider product first sub-association table and a caller product second sub-association table which are interdependent between a provider and a caller based on interfaces, and storing the product main association table, the first sub-association table and the second sub-association table to a database, wherein each product version and corresponding interface version are respectively stored in the first sub-association table and the second sub-association table;
the field engineering deployment module is used for constructing a field associated product set according to the requirements of field product deployment and/or version upgrading; taking each product in the field associated product set as a caller, acquiring the product version, a calling interface and an interface version of the caller, taking the field interface product as a product provider, and inquiring the interface version of the corresponding provider from a database;
and the compatibility checking module is used for carrying out compatibility checking on the calling party interface version and the providing party interface version according to the interface version compatibility standard.
To further explain the scheme of the present application, the association relationship among the product, the product version, the interface and the interface version is specifically described below with the product a, the product B, the product C and the product D.
Table 1 shows the dependency relationship between products and interfaces of product a, product B, product C, and product D; as can be seen from Table 1, product A and product B are dependent, and the corresponding interface is JABUnder the dependency relationship, the product A is used as an interface JABProduct B as interface JABThe calling party of (2); the product B and the product C are in a dependency relationship, and the corresponding interface is JBC1、JBC2Under this dependency, product B acts as interface JBC1、JBC2Product C as interface JBC1、JBC2The calling party of (2); the product C and the product D are in a dependency relationship, and the corresponding interface is JCDUnder this dependency, product C acts as interface JCDProduct D as interface JCDThe caller of (1).
Table 1:
| product B | Product C | Product D | |
| Product A | JAB | ||
| Product B | JBC1、JBC2 | ||
| Product C | JCD |
Table 2 shows a first sub-association table for product A, and Table 3 shows a second sub-association table for product B, which can be obtained from tables 2 and 3, and the provider interface J for each product version A and providerABVersion number of version, and connection of calling party to each product B versionMouth JABVersion number of the version.
Table 2:
table 3:
it will be appreciated that so-called invokers are opposed to providers, and that the same product may switch between invokers and providers in different scenarios. Specifically, in one scenario, if product B calls interface 1 to access product a, product B is the caller and product a is the provider. In another scenario, if product C calls interface 2 to access product B, then in this scenario, product B will be the provider and product C the caller.
In the embodiment of the scheme, for developing a new version product, an interface version number of the new version product can be marked according to a version number declaration principle, and then relevant data in the database is updated based on the interface version number of the new version product, wherein the version number declaration principle can be specifically characterized as follows:
if the new version product does not change the interface, the major version number MajorVersion and the minor version number MinorVersion of the interface are kept unchanged;
if the new version product changes the interface but is forward compatible, the major version number MajorVersion of the interface is unchanged, and the minor version number MinorVersion is increased;
if the new version product changes the interface and is not forward compatible, the major version number majorvision of the interface is increased, and the minor version number minorvision clear 0.
Specifically, for example: the original product version is 1.0, the interface version is 1.1, and the product version is upgraded from 1.0 to 2.0.
If the first case is followed, the interface is not changed when the product version 1.0 is upgraded to 2.0, and the interface version of the product version 2.0 is still 1.1 and remains unchanged.
If the second situation is followed, upgrading product version 1.0 to 2.0 has changed the interface, but is forward compatible, at this time, the interface version of product version 2.0 may become 1.2, interface version 1.2 is compatible with interface version 1.1, and changing interface version 1.1 to interface version 1.2 indicates forward compatibility.
If the second case is followed, upgrading product version 1.0 to 2.0 has changed the interface and is not forward compatible, at which point the interface version of product version 2.0 may become 2.0 and interface version 2.0 is incompatible with interface version 1.1.
According to the embodiment of the invention, when a new version product is developed, the interface and the interface version which need to be called can be selected step by step through the product, the product version, the interface and the interface version which provide interface service.
For example, if a developer needs to develop a product a according to a requirement (the requirement here already knows what product needs to be developed), the product a first selects a product B that depends on the product a according to an interface service, selects a corresponding product version according to the selected product B, and then determines a called interface and an interface version according to the product version.
According to the embodiment of the invention, if a new version product is developed and the corresponding interface version is not forward compatible, other products depending on the interface can be obtained through database query according to the interface, and the responsible persons of other products are notified to perform upgrade adaptation processing.
It will be appreciated that various products, product versions, interfaces provided by the product versions, and interface versions, other products that rely on the interfaces, are stored in the database. When a new version of a product causes the version of the interface provided to be incompatible forward, for example: the interface version of the new version product is changed from original 1.2 to 2.0, at this time, other products originally depending on the interface version 1.2 may not be adapted to the interface version 2.0 of the new version product, and in order to enhance the interoperability among a plurality of products, the interface version 2.0 may be notified to the responsible person of other products, so as to make corresponding coordination.
As shown in fig. 2, the process of compatibility checking may be designed to include the following:
step 3-1, reading a product to be deployed or upgraded next and a product version thereof, and taking the product as a calling party;
step 3-2, reading a calling interface of a calling party and an interface version thereof;
3-3, judging whether the field engineering contains a product for providing the interface, if so, entering the step 3-4, and if not, failing to detect the compatibility;
step 3-4, taking the product providing the interface as a provider, and querying the database through the product version of the provider to obtain the interface version of the provider;
step 3-5, judging whether the interface version of the provider is compatible with the interface version of the caller or not based on the interface version compatibility standard, if so, entering step 3-6, and if not, failing to detect the compatibility;
step 3-6, judging whether all the calling interfaces of the calling party are traversed or not, if so, entering step 3-7, and if not, returning to step 3-2;
3-7; and judging whether all deployed or upgraded products of the field project are traversed, if so, passing the compatibility check, otherwise, returning to the step 3-1.
Further, according to the embodiment of the present invention, after the compatibility check is passed, the product deployment or version upgrade of the field engineering is implemented, and after the deployment or version upgrade is performed, the product version deployment state of the field engineering is updated.
It is to be appreciated that the field engineer is responsible for managing the products deployed by the project and their version status. When field deployment and field upgrade are implemented, a field engineer adjusts the version of a deployed product in a tool, and the following version compatibility check is triggered. After the version compatibility check is passed, deployment or upgrading can be implemented; and after the deployment and the upgrade are finished, updating the product version deployment state of the project. The standard for judging the compatibility of the interface version of the provider and the interface version of the caller is as follows: major version numbers MajorVersion are equal, and the minor version number MinorVersion of the caller is less than or equal to the minor version number MinorVersion of the provider.
The invention verifies the compatibility of the associated product version by an interface management mode, and realizes the compatibility check of the field engineering deployment or the upgrade product version. The method can find the version compatibility problem in the product deployment or upgrading process in time, and avoid field accidents caused by the compatibility problem. In addition, as long as a development team knows and inputs own product interface requirements, compatibility check among products can be carried out by the tool, so that product responsible persons can conveniently make corresponding coordination according to compatibility check results, the efficiency is improved, and the cost is reduced.
Unless specifically stated otherwise, the relative steps, numerical expressions, and values of the components and steps set forth in these embodiments do not limit the scope of the present invention.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the system and the apparatus described above may refer to the corresponding processes in the foregoing system embodiments, and are not described herein again.
In all examples shown and described herein, any particular value should be construed as merely exemplary, and not as a limitation, and thus other examples of example embodiments may have different values.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, 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 and/or flowchart illustration, and combinations of blocks in the block diagrams and/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.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a non-volatile computer-readable storage medium executable by a processor. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the system according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
Finally, it should be noted that: the above-mentioned embodiments are only specific embodiments of the present invention, which are used for illustrating the technical solutions of the present invention and not for limiting the same, and the protection scope of the present invention is not limited thereto, although the present invention is described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: any person skilled in the art can modify or easily conceive the technical solutions described in the foregoing embodiments or equivalent substitutes for some technical features within the technical scope of the present disclosure; such modifications, changes or substitutions do not depart from the spirit and scope of the embodiments of the present invention, and they should be construed as being included therein. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (10)
1. An information system integration project interface version compatibility checking method is characterized by comprising the following steps:
constructing a product main association table, a provider product first sub-association table and a caller product second sub-association table which are mutually dependent on interfaces between a provider and a caller, and storing the product main association table, the first sub-association table and the second sub-association table into a database, wherein each product version and corresponding interface version are respectively stored in the first sub-association table and the second sub-association table;
constructing a field associated product set according to the field product deployment and/or version upgrading requirements; taking each product in the field associated product set as a caller, acquiring the product version, a calling interface and an interface version of the caller, taking the field interface product as a product provider, and inquiring the interface version of the corresponding provider from a database;
and performing compatibility check on the calling party interface version and the providing party interface version according to the interface version compatibility standard.
2. The information system integration project interface version compatibility checking method according to claim 1, characterized in that the field-associated product set comprises at least two products, respectively determines the product version to be deployed and/or upgraded for each product, and uses each product as a calling party to obtain the calling party product version, the interface and the interface version.
3. The method for checking the interface version compatibility of the information system integration project according to claim 1, wherein for a new version product, the interface version number of the new version product is marked according to a version number declaration principle, and related data in the database is updated based on the interface version number of the new version product.
4. The method as claimed in claim 3, wherein the interface and the interface version are selected from the product, the product version, the interface and the interface version providing the interface service step by step according to the new version of the product.
5. The method for checking the compatibility of the interface versions of the information system integration project according to claim 3, wherein the version number declaration rule comprises the following contents: if the new version product does not change the interface, the major version number and the minor version number of the interface are kept unchanged; if the new version product changes the interface and is compatible forward, the major version number of the interface is not changed, and the minor version number is upgraded; and if the new version product changes the interface and is not forward compatible, upgrading the major version number of the interface and resetting the minor version number.
6. The information system integration project interface version compatibility checking method of claim 5, wherein when the corresponding interface version of the developed new version product is not forward compatible, other products depending on the interface are obtained by querying the database according to the new version interface, and the queried other products are upgraded and adapted.
7. The method for checking the interface version compatibility of an information system integration project according to claim 1, wherein the interface version compatibility standard comprises the following contents: and if the main version number of the provider interface version is the same as the main version number of the caller interface version, and the current version number of the caller interface version is less than or equal to the minor version number of the provider interface version, judging that the provider interface version and the caller interface version are compatible, otherwise, judging that the provider interface version and the caller interface version are incompatible.
8. The information system integration project interface version compatibility checking method according to claim 1 or 7, characterized in that the compatibility checking is performed by traversing all deployed and/or upgraded products in the field; in each product compatibility check of deployment and/or upgrade, each product in a field-associated product set is taken as a caller, all the caller calling interfaces are traversed, whether the field contains a product providing the interface is judged according to the caller calling interface and the interface version, if the field contains the product providing the interface, the product providing the interface is taken as a provider, the provider interface version is obtained by inquiring a database through the provider product version, and whether the provider interface version is compatible with the caller interface version is judged based on the interface version compatibility standard.
9. The information system integration project interface version compatibility checking method according to claim 1, wherein, for a situation that the compatibility check passes, the field product is deployed and/or version-upgraded, and after the deployment and/or version-upgrade is completed, a version deployment state of the field product is updated.
10. An information system integration project interface version compatibility checking system, comprising: a database construction module, a field engineering deployment module, and a compatibility check module, wherein,
the database construction module is used for constructing a product main association table, a provider product first sub-association table and a caller product second sub-association table which are interdependent between a provider and a caller based on interfaces, and storing the product main association table, the first sub-association table and the second sub-association table to a database, wherein each product version and corresponding interface version are respectively stored in the first sub-association table and the second sub-association table;
the field engineering deployment module is used for constructing a field associated product set according to the requirements of field product deployment and/or version upgrading; taking each product in the field associated product set as a caller, acquiring the product version, a calling interface and an interface version of the caller, taking the field interface product as a product provider, and inquiring the interface version of the corresponding provider from a database;
and the compatibility checking module is used for carrying out compatibility checking on the calling party interface version and the providing party interface version according to the interface version compatibility standard.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110446941.8A CN112988222B (en) | 2021-04-25 | 2021-04-25 | Method and system for checking information system integration project interface version compatibility |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110446941.8A CN112988222B (en) | 2021-04-25 | 2021-04-25 | Method and system for checking information system integration project interface version compatibility |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112988222A CN112988222A (en) | 2021-06-18 |
| CN112988222B true CN112988222B (en) | 2022-04-08 |
Family
ID=76341680
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110446941.8A Active CN112988222B (en) | 2021-04-25 | 2021-04-25 | Method and system for checking information system integration project interface version compatibility |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112988222B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104216724A (en) * | 2013-06-03 | 2014-12-17 | 阿里巴巴集团控股有限公司 | Method and system for updating network application program interface |
| CN107977223A (en) * | 2017-11-20 | 2018-05-01 | 杭州迪普科技股份有限公司 | One kind configuration compliance check method and device |
| CN109446069A (en) * | 2018-09-26 | 2019-03-08 | 平安普惠企业管理有限公司 | Compatibility test method, device, computer equipment and medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8539475B2 (en) * | 2009-09-29 | 2013-09-17 | Oracle America, Inc. | API backward compatibility checking |
-
2021
- 2021-04-25 CN CN202110446941.8A patent/CN112988222B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104216724A (en) * | 2013-06-03 | 2014-12-17 | 阿里巴巴集团控股有限公司 | Method and system for updating network application program interface |
| CN107977223A (en) * | 2017-11-20 | 2018-05-01 | 杭州迪普科技股份有限公司 | One kind configuration compliance check method and device |
| CN109446069A (en) * | 2018-09-26 | 2019-03-08 | 平安普惠企业管理有限公司 | Compatibility test method, device, computer equipment and medium |
Non-Patent Citations (1)
| Title |
|---|
| 组件系统接口匹配识别方案和应用;陈宏君等;《计算机技术与发展》;20160228(第02期);第130-133页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112988222A (en) | 2021-06-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9218169B2 (en) | Callpath finder | |
| US20060020937A1 (en) | System and method for extraction and creation of application meta-information within a software application repository | |
| CN102804133B (en) | Method and device for managed system extensibility | |
| CN111414739B (en) | Excel data entry component, entry method and device | |
| CN110851207B (en) | State transition management method and device, electronic equipment and storage medium | |
| JP2004118850A (en) | Adequacy inspection system and method | |
| CN107168866B (en) | Parameter analysis method and device for configuration file | |
| CN112988222B (en) | Method and system for checking information system integration project interface version compatibility | |
| CN115525534A (en) | Test case generation method and platform based on swagger interface test | |
| CN106095511A (en) | A kind of server updating method and apparatus | |
| US8689200B1 (en) | Method and system for optimizing an executable program by generating special operations for identical program entities | |
| CN109144620B (en) | Skipping method and device for suspension window permission setting interface | |
| US10438011B2 (en) | Information processing apparatus and non-transitory computer readable medium | |
| CN115018621A (en) | Contract changing method, device, equipment and medium | |
| CN110727537B (en) | Method, device, computer equipment and storage medium for uniformly processing response message | |
| US8683455B1 (en) | Method and system for optimizing an executable program by selectively merging identical program entities | |
| CN113379501A (en) | Message pushing method and device, electronic equipment and storage medium | |
| US20100241485A1 (en) | Claims Based Factory Pattern for Creating Objects | |
| CN105988866B (en) | Information processing unit and its control method | |
| CN116301758B (en) | Rule editing method, device, equipment and medium based on event time points | |
| CN113327167B (en) | Block chain data processing method | |
| CN112882721B (en) | Software package compiling method and device | |
| CN112035119B (en) | Data deleting method and device | |
| JP7492451B2 (en) | Data control system and data control method | |
| CN106990997B (en) | Service calling method and device |
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 |