CN114564934A - Software program version difference analysis method, device, equipment and storage medium - Google Patents
Software program version difference analysis method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN114564934A CN114564934A CN202210118545.7A CN202210118545A CN114564934A CN 114564934 A CN114564934 A CN 114564934A CN 202210118545 A CN202210118545 A CN 202210118545A CN 114564934 A CN114564934 A CN 114564934A
- Authority
- CN
- China
- Prior art keywords
- version
- software program
- file
- abstract
- digest
- 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.)
- Granted
Links
- 238000004458 analytical method Methods 0.000 title claims abstract description 27
- 238000000034 method Methods 0.000 claims abstract description 32
- 230000008569 process Effects 0.000 claims abstract description 14
- 238000012795 verification Methods 0.000 claims abstract description 10
- 238000004590 computer program Methods 0.000 claims description 10
- 238000012545 processing Methods 0.000 description 10
- 230000006870 function Effects 0.000 description 9
- 238000004891 communication Methods 0.000 description 8
- 238000010586 diagram Methods 0.000 description 8
- 230000003287 optical effect Effects 0.000 description 4
- 239000000835 fiber Substances 0.000 description 2
- 230000010365 information processing Effects 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000033764 rhythmic process Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/194—Calculation of difference between files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
- G06F16/9566—URL specific, e.g. using aliases, detecting broken or misspelled links
-
- 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)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Databases & Information Systems (AREA)
- Computer Security & Cryptography (AREA)
- Health & Medical Sciences (AREA)
- Artificial Intelligence (AREA)
- Audiology, Speech & Language Pathology (AREA)
- Computational Linguistics (AREA)
- General Health & Medical Sciences (AREA)
- Data Mining & Analysis (AREA)
- Stored Programmes (AREA)
Abstract
The application provides a software program version difference analysis method, which specifically comprises the following steps: acquiring each element contained in the release version of the software program, defining each element through URL to form element content, abstracting the defined element content by adopting a message abstraction algorithm to generate a version abstract of the release version of the software program; further acquiring abstract files of the standard versions of the software programs; executing a version verification process on a software program needing to be subjected to difference analysis through a version comparator; and recording the compared difference to form a difference list and storing the difference list. The method comprises the steps of clearly defining each element contained in a software program through a URI, simplifying the content of the element by adopting a message digest algorithm, generating a version digest of the running version, comparing the version digest with a release digest of a standard version item by item to obtain a difference list, getting rid of time and labor consumption of manually comparing version differences, and quickly analyzing the differences of the running version.
Description
Technical Field
The application belongs to the technical field of software program version difference analysis, and particularly relates to a software program version difference analysis method, device, equipment and storage medium.
Background
At present, most software programs mainly adopt version numbers, version description files and other modes when determining versions. However, in an actual production environment, because the incremental release mode is mostly adopted for release of version update, a part of changed files are updated each time, and in the long-term maintenance process, the production version gradually cannot correspond to the source code version, particularly, one product is applied to a plurality of clients, different clients may have respective release rhythms and requirements, and only a part of the content of the version may be released, so that a plurality of versions need to be compared when modification is performed at a later stage. And the configuration items of the product (including configuration files and configuration class information in the data table), the table structure of the database, the initialization data in the data table, etc. may also be inconsistent with the version requirements, causing problems. Therefore, a method for quickly and effectively analyzing the version difference and accurately positioning to a specific difference point is urgently needed.
In view of the above, it is very significant to provide a method, an apparatus, a device and a storage medium for analyzing software program version difference.
Content of application
In order to solve the problem that the version difference of the software program cannot be analyzed quickly and effectively in the prior art, the application provides a method, a device, equipment and a storage medium for analyzing the version difference of the software program, so as to solve the technical defect problem in the prior art.
In a first aspect, the present application provides a software program version difference analysis method, which specifically includes the following steps:
s1, acquiring each element contained in the software program release version, defining each element through URL to form element content, abstracting the defined element content by adopting a message abstraction algorithm, and generating a version abstract of the software program release version;
s2, further acquiring a summary file of the standard version of the software program;
s3, executing a version verification process on the software program needing to be subjected to difference analysis through a version comparator; and
and S4, recording the differences after comparison to form a difference list and storing the difference list.
The method comprises the steps of clearly defining each element contained in the running version of the software program through a URI, simplifying the content of the element by adopting a message digest algorithm, generating a version digest of the running version, and comparing the version digest with a release digest of a standard version item by item to obtain a difference list. By comparing the release abstracts of a plurality of standard versions, the difference between the running version and each version can be analyzed, the closest version is found, and the subsequent upgrade is carried out; the time and labor for comparing version differences manually can be avoided, the influence of misoperation caused by manual comparison can be avoided, the differences of the running versions can be analyzed rapidly, particularly the contents which are difficult to compare, such as configuration items, initialization data and the like, can be analyzed rapidly, and the difference list can be generated accurately in time.
Preferably, the version verification process in S3 specifically includes:
s31, the version comparator acquires the URL of each element of the software program version to be analyzed, searches in the abstract file of the standard software program version acquired in S2, and judges and marks the URL of each element to be in the existing, nonexistent or missing state;
s32, if the URL of the element belongs to the existing state, the element is abstracted by the message abstraction algorithm in the abstract file of the standard version of the software program, and then compared with the abstract file of the standard version of the software program, the element is judged and marked as the existing state and the existing state of inconsistency.
Preferably, the elements include release documents, configuration items, database table structures, and initialization data.
Further preferably, the published file includes a non-configuration file and a configuration file, and the URI format of the non-configuration file is: file/[ war packet name ]/file path/file name, and summarizing the full content of the published file; the URI format of the configuration file is: fileconfig:// [ war package name ]/file path/file name;
the URI format is as follows: configuring item names and abstracting configuration item values;
The URI formats of the tables, fields, indexes, storage processes and custom functions in the database are as follows: [ mysql | oracle | db2| sqlserver | … ]/[ table | field | index | sp | udf ]/name, abstract the full text of the corresponding database DDL statement;
the URI format of the initialization data is: record:// table name/primary key value, and converting all field values of corresponding records into character strings and then using "|" to splice and make abstract.
Preferably, the summary file of the standard version includes:
the first row displays the product name, version number, release date and message abstract algorithm name, and adjacent rows are separated by commas;
the second line begins one line for each of the elements, each line having the format: URL is digest value.
Preferably, the list of differences comprises: one row for each element, the format of each row being: URL, state mark, standard version abstract value and running version abstract value; the status flags include present consistency, present inconsistency, absence, and absence.
Preferably, the message digest algorithm includes MD2, MD4, and MD 5.
In a second aspect, the present application further provides an apparatus for analyzing version differences of a software program, including:
an acquisition module: configuring various elements and abstract files for acquiring the software program;
The definition module: configuring and defining each acquired element through a URL;
version abstract generator module: configured to digest the defined elements by a message digest algorithm;
a version comparator module: configured to perform an analysis and comparison of differences in versions of the software program;
a judging module: configured to determine and mark the discrepancy;
a recording module: configured to record the analyzed differences and form a list of differences.
In a third aspect, an embodiment of the present application provides an electronic device, including: one or more processors; storage means for storing one or more programs which, when executed by one or more processors, cause the one or more processors to carry out a method as described in any one of the implementations of the first aspect.
In a fourth aspect, the present application provides a computer-readable storage medium, on which a computer program is stored, which, when executed by a processor, implements the method as described in any implementation manner of the first aspect.
Compared with the prior art, the beneficial results of this application lie in:
(1) the method comprises the steps of clearly defining each element contained in the running version of the software program through a URI, simplifying the content of the element by adopting a message digest algorithm, generating a version digest of the running version, and comparing the version digest with a release digest of a standard version item by item to obtain a difference list.
(2) By comparing the release abstracts of a plurality of standard versions, the difference between the running version and each version can be analyzed, the closest version is found, and the subsequent upgrade is carried out; the time and labor for comparing version differences manually can be avoided, the influence of misoperation caused by manual comparison can be avoided, the differences of the running versions can be analyzed rapidly, particularly the contents which are difficult to compare, such as configuration items, initialization data and the like, can be analyzed rapidly, and the difference list can be generated accurately in time.
Drawings
The accompanying drawings are included to provide a further understanding of the embodiments and are incorporated in and constitute a part of this specification. The drawings illustrate embodiments and together with the description serve to explain the principles of the application. Other embodiments and many of the intended advantages of embodiments will be readily appreciated as they become better understood by reference to the following detailed description. The elements of the drawings are not necessarily to scale relative to each other. Like reference numerals designate corresponding similar parts.
FIG. 1 is an exemplary device architecture diagram in which one embodiment of the present application may be applied;
FIG. 2 is a flowchart illustrating a software program version difference analysis method according to an embodiment of the present application;
Fig. 3 is a schematic structural diagram of a software program version difference analysis method according to an embodiment of the present application;
fig. 4 is a schematic flowchart of S3 in the software program version difference analysis method according to the embodiment of the present application;
fig. 5 is a flowchart illustrating a software program version difference analysis apparatus according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of a computer device suitable for implementing an electronic apparatus according to an embodiment of the present application.
Detailed Description
In the following detailed description, reference is made to the accompanying drawings, which form a part hereof, and in which is shown by way of illustration specific embodiments in which the application may be practiced. In this regard, directional terminology, such as "top," "bottom," "left," "right," "up," "down," etc., is used with reference to the orientation of the figures being described. Because components of embodiments can be positioned in a number of different orientations, the directional terminology is used for purposes of illustration and is in no way limiting. It is to be understood that other embodiments may be utilized and logical changes may be made without departing from the scope of the present application. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope of the present application is defined by the appended claims.
It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Fig. 1 illustrates an exemplary system architecture 100 to which a method for processing information or an apparatus for processing information of embodiments of the present application may be applied.
As shown in fig. 1, the system architecture 100 may include terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 serves as a medium for providing communication links between the terminal devices 101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
The user may use the terminal devices 101, 102, 103 to interact with the server 105 via the network 104 to receive or send messages or the like. The terminal devices 101, 102, 103 may have various communication client applications installed thereon, such as a web browser application, a shopping application, a search application, an instant messaging tool, a mailbox client, social platform software, and the like.
The terminal devices 101, 102, 103 may be various electronic devices having communication functions, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.
The server 105 may be a server that provides various services, such as a background information processing server that processes check request information transmitted by the terminal apparatuses 101, 102, 103. The background information processing server may perform processing such as analysis on the received verification request information, and obtain a processing result (for example, verification success information used for representing that the verification request is a legal request).
It should be noted that the method for processing information provided in the embodiment of the present application is generally performed by the server 105, and accordingly, the apparatus for processing information is generally disposed in the server 105. In addition, the method for sending information provided by the embodiment of the present application is generally executed by the terminal equipment 101, 102, 103, and accordingly, the apparatus for sending information is generally disposed in the terminal equipment 101, 102, 103.
The server may be hardware or software. When the server is hardware, it may be implemented as a distributed server cluster formed by multiple servers, or may be implemented as a single server. When the server is software, it may be implemented as multiple pieces of software or software modules (e.g., to provide distributed services), or as a single piece of software or multiple software modules. And is not particularly limited herein.
In a first aspect, an embodiment of the present application discloses a software program version difference analysis method, with reference to fig. 2 and 3, the method specifically includes the following steps:
s1, acquiring each element contained in the release version of the software program, defining each element through URL to form element content, abstracting the defined element content by adopting a message abstraction algorithm, and generating a version abstract of the release version of the software program;
s2, further acquiring a summary file of the standard version of the software program;
s3, executing a version verification process to the software program needing to be subjected to the difference analysis through a version comparator;
specifically, with reference to fig. 4, in this embodiment, the version verification process in S3 specifically includes: s31, the version comparator acquires the URL of each element of the software program version to be analyzed, searches in the abstract file of the standard software program version acquired in S2, and judges and marks that the URL of each element belongs to the existing, nonexistent or missing three states;
and S32, if the URL of the element belongs to the existing state, abstracting the element content by using a message abstraction algorithm in an abstract file of the standard version of the software program, comparing the abstract file with the abstract file of the standard version of the software program, and judging and marking the two states of consistency and inconsistency.
And S4, recording the differences after comparison to form a difference list and storing the difference list.
Specifically, in the embodiment, the message digest algorithm includes MD2, MD4, and MD5, and in the embodiment, the MD5 digest algorithm is adopted.
In the present embodiment, the various elements included in the software program include, but are not limited to, release files, configuration items, database table structures, initialization data, and the like.
The publishing file comprises a non-configuration file and a configuration file, and the URI format of the non-configuration file is as follows: file/[ war packet name ]/file path/file name, abstract the full content of the published file; the URI format of the configuration file is: fileconfig:// [ war package name ]/file path/file name;
the URI format is: configuring item names and abstracting configuration item values;
the URI formats of the tables, fields, indexes, storage processes and custom functions in the database are as follows: [ mysql | oracle | db2| sqlserver | … ]/[ table | field | index | sp | udf ]/name, abstract the full text of the corresponding database DDL statement;
the URI format of the initialization data is: record:// table name/primary key value, converting all field values of corresponding records into character strings and then splicing with '|' to make an abstract;
the URI format of the configuration item data is: dbconfig:// table name/primary key value, abstracted with the key field value of the configuration item.
In addition, contents requiring version control, which are not within the above range, may perform a digest algorithm by defining a URI and then checking as needed.
Further, the standard version summary file includes:
the first row displays the product name, version number, release date and message abstract algorithm name, and adjacent rows are separated by commas;
the second line begins one line per element, the format of each line being: URL ═ digest value.
The difference list includes: one line for each element, the format of each line being: URL, state mark, standard version abstract value and running version abstract value; the status flags include present consistency, present inconsistency, absence, and absence.
According to the scheme, each element contained in the running version of the software program is clearly defined through a URI, the content of the element is simplified by adopting a message digest algorithm, the version digest of the running version is generated, the version digest is compared with the release digest of the standard version item by item, and a difference list is obtained. By comparing the release abstracts of a plurality of standard versions, the difference between the running version and each version can be analyzed, the closest version is found, and the subsequent upgrade is carried out; the time and labor for comparing version differences manually can be avoided, the influence of misoperation caused by manual comparison can be avoided, the differences of the running versions can be analyzed rapidly, particularly the contents which are difficult to compare, such as configuration items, initialization data and the like, can be analyzed rapidly, and the difference list can be generated accurately in time.
In a second aspect, an embodiment of the present application further provides an apparatus for analyzing a software program version difference, with reference to fig. 5, including:
the acquisition module 51: configuring various elements for acquiring the software program and a summary file;
the definition module 52: configuring and defining each acquired element through URL;
version digest generator module 53: configured to digest defined elements by a message digest algorithm;
version comparator module 54: configured to perform an analysis and comparison of differences in versions of the software program;
the judging module 55: configured to determine and mark the discrepancy;
the recording module 56: configured to record the analyzed differences and form a list of differences.
Referring now to fig. 6, a schematic diagram of a computer device 600 suitable for use in implementing an electronic device (e.g., the server or terminal device shown in fig. 1) according to an embodiment of the present application is shown. The electronic device shown in fig. 6 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present application.
As shown in fig. 6, the computer apparatus 600 includes a Central Processing Unit (CPU)601 and a Graphics Processing Unit (GPU)602, which can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)603 or a program loaded from a storage section 609 into a Random Access Memory (RAM) 606. In the RAM 604, various programs and data necessary for the operation of the apparatus 600 are also stored. The CPU 601, GPU602, ROM 603, and RAM 604 are connected to each other via a bus 605. An input/output (I/O) interface 606 is also connected to bus 605.
The following components are connected to the I/O interface 606: an input portion 607 including a keyboard, a mouse, and the like; an output section 608 including, for example, a Liquid Crystal Display (LCD), and a speaker; a storage section 609 including a hard disk and the like; and a communication section 610 including a network interface card such as a LAN card, a modem, or the like. The communication section 610 performs communication processing via a network such as the internet. The drive 611 may also be connected to the I/O interface 606 as needed. A removable medium 612 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 611 as necessary, so that a computer program read out therefrom is mounted into the storage section 609 as necessary.
In particular, according to an embodiment 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 embodiments, the computer program may be downloaded and installed from a network via the communication section 610, and/or installed from the removable media 612. The computer programs, when executed by a Central Processing Unit (CPU)601 and a Graphics Processor (GPU)602, perform the above-described functions defined in the methods of the present application.
It should be noted that the computer readable medium described herein can be a computer readable signal medium or a computer readable medium or any combination of the two. The computer readable medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor device, apparatus, or any combination of the foregoing. More specific examples of the computer readable 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 application, a computer readable medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution apparatus, device, or apparatus. In this application, 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 medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution apparatus, device, or apparatus. 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.
Computer program code for carrying out operations for aspects of the present application may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present application. 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 devices that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The modules described in the embodiments of the present application may be implemented by software or hardware. The modules described may also be provided in a processor.
As another aspect, the present application also provides a computer-readable medium, which may be contained in the electronic device described in the above embodiment; or may be separate and not incorporated into the electronic device. The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to perform the method for software program version difference analysis described above.
The foregoing description is only exemplary of the preferred embodiments of the application and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the invention herein disclosed is not limited to the particular combination of features described above, but also encompasses other arrangements formed by any combination of the above features or their equivalents without departing from the spirit of the invention. For example, the above features may be replaced with (but not limited to) features having similar functions disclosed in the present application.
Claims (10)
1. A software program version difference analysis method is characterized by comprising the following steps:
s1, acquiring each element contained in the software program release version, defining each element through URL to form element content, abstracting the defined element content by adopting a message abstraction algorithm, and generating a version abstract of the software program release version;
s2, further acquiring a summary file of the standard version of the software program;
s3, executing a version verification process to the software program needing to be subjected to the difference analysis through a version comparator; and
and S4, recording the differences after comparison to form a difference list and storing the difference list.
2. The software program version difference analysis method according to claim 1, wherein the version verification process in S3 specifically includes:
s31, the version comparator acquires the URL of each element of the software program version to be analyzed, searches in the abstract file of the standard software program version acquired in S2, and judges and marks that the URL of each element belongs to the existing, nonexistent or missing three states;
s32, if the URL of the element belongs to the existing state, the element is abstracted by the message abstraction algorithm in the abstract file of the standard version of the software program, and then compared with the abstract file of the standard version of the software program, the element is judged and marked as the existing state and the existing state of inconsistency.
3. The software program version difference analysis method according to claim 1, wherein the elements include release files, configuration items, database table structures, and initialization data.
4. The software program version difference analysis method according to claim 3, wherein the release file comprises a non-configuration file and a configuration file, and the URI format of the non-configuration file is as follows: file/[ war packet name ]/file path/file name, and summarizing the full content of the published file; the URI format of the configuration file is: fileconfig:// [ war package name ]/file path/file name;
the URI format is as follows: configuring item names and abstracting configuration item values;
the URI formats of the table, the field, the index, the storage process and the self-defined function in the database are as follows: [ mysql | oracle | db2| sqlserver | … ]/[ table | field | index | sp | udf ]/name, abstract the full text of the corresponding database DDL statement;
the URI format of the initialization data is: record:// table name/primary key value, all field values of corresponding records are converted into character strings and then spliced by '|' to be abstracted.
5. The software program version difference analysis method according to claim 1, wherein the digest file of the standard version comprises:
The first row displays the product name, version number, release date and message abstract algorithm name, and adjacent rows are separated by commas;
the second line begins one line per said element, the format of each line being: URL ═ digest value.
6. The software program version difference analysis method according to claim 1, wherein the difference list comprises: one line for each of said elements, the format of each line being: URL, state mark, standard edition abstract value and operation edition abstract value; the status flags include present consistency, present inconsistency, absence, and absence.
7. The software program version difference analysis method according to claim 1, wherein the message digest algorithm includes MD2, MD4, and MD 5.
8. An apparatus for analyzing version differences of a software program, comprising:
an acquisition module: configuring various elements and abstract files for acquiring the software program;
a definition module: configuring and defining each acquired element through a URL;
a version abstract generator module: configured to digest the defined elements by a message digest algorithm;
a version comparator module: configured to perform an analysis and comparison of differences in versions of the software program;
A judgment module: configured to determine and mark the discrepancy;
a recording module: configured to record the analyzed differences and form a list of differences.
9. An electronic device, comprising:
one or more processors;
storage means 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.
10. A computer-readable storage 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.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210118545.7A CN114564934B (en) | 2022-02-08 | 2022-02-08 | Software program version difference analysis method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210118545.7A CN114564934B (en) | 2022-02-08 | 2022-02-08 | Software program version difference analysis method, device, equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114564934A true CN114564934A (en) | 2022-05-31 |
| CN114564934B CN114564934B (en) | 2024-03-22 |
Family
ID=81713475
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210118545.7A Active CN114564934B (en) | 2022-02-08 | 2022-02-08 | Software program version difference analysis method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114564934B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130104115A1 (en) * | 2011-10-21 | 2013-04-25 | International Business Machines Corporation | Systems and methods for upgrading a version of software |
| CN110109840A (en) * | 2019-05-10 | 2019-08-09 | 重庆八戒电子商务有限公司 | Code audit method, audit device and the medium compared based on version number |
| CN110457628A (en) * | 2019-07-05 | 2019-11-15 | 平安国际智慧城市科技股份有限公司 | Webpage edition correcting method, device, equipment and storage medium |
| CN113157315A (en) * | 2021-04-30 | 2021-07-23 | 平安普惠企业管理有限公司 | Method, device, equipment and medium for identifying difference information of different versions of software |
| CN113225729A (en) * | 2020-01-21 | 2021-08-06 | 荣耀终端有限公司 | OTA (over the air) upgrading method and device and readable storage medium |
| CN113326058A (en) * | 2021-07-01 | 2021-08-31 | 苏州好玩友网络科技有限公司 | Method, device, equipment and medium for updating version of application |
| CN113778510A (en) * | 2021-08-17 | 2021-12-10 | 珠海西山居移动游戏科技有限公司 | Multi-version maintenance method and device for application program and readable storage medium |
-
2022
- 2022-02-08 CN CN202210118545.7A patent/CN114564934B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130104115A1 (en) * | 2011-10-21 | 2013-04-25 | International Business Machines Corporation | Systems and methods for upgrading a version of software |
| CN110109840A (en) * | 2019-05-10 | 2019-08-09 | 重庆八戒电子商务有限公司 | Code audit method, audit device and the medium compared based on version number |
| CN110457628A (en) * | 2019-07-05 | 2019-11-15 | 平安国际智慧城市科技股份有限公司 | Webpage edition correcting method, device, equipment and storage medium |
| CN113225729A (en) * | 2020-01-21 | 2021-08-06 | 荣耀终端有限公司 | OTA (over the air) upgrading method and device and readable storage medium |
| CN113157315A (en) * | 2021-04-30 | 2021-07-23 | 平安普惠企业管理有限公司 | Method, device, equipment and medium for identifying difference information of different versions of software |
| CN113326058A (en) * | 2021-07-01 | 2021-08-31 | 苏州好玩友网络科技有限公司 | Method, device, equipment and medium for updating version of application |
| CN113778510A (en) * | 2021-08-17 | 2021-12-10 | 珠海西山居移动游戏科技有限公司 | Multi-version maintenance method and device for application program and readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114564934B (en) | 2024-03-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11720418B2 (en) | Distillation of various application interface data structures distributed over distinctive repositories to form a data source of consolidated application interface data components | |
| US10282197B2 (en) | Open application lifecycle management framework | |
| EP2808790B1 (en) | Migration assessment for cloud computing platforms | |
| US9626368B2 (en) | Document merge based on knowledge of document schema | |
| US20120036397A1 (en) | Utilizing log event ontology to deliver user role specific solutions for problem determination | |
| US20140330745A1 (en) | Analytic solution integration | |
| US10360394B2 (en) | System and method for creating, tracking, and maintaining big data use cases | |
| US20160259831A1 (en) | Methodology supported business intelligence (BI) software and system | |
| US11675581B1 (en) | Automated creation, testing, training, adaptation and deployment of new artificial intelligence (AI) models | |
| CN110321544B (en) | Method and device for generating information | |
| CN111125064B (en) | Method and device for generating database schema definition statement | |
| US8775392B1 (en) | Revision control and configuration management | |
| CN108694172B (en) | Information output method and device | |
| CN112818026A (en) | Data integration method and device | |
| CN113377342B (en) | Project construction method and device, electronic equipment and storage medium | |
| US20140207830A1 (en) | Decomposing xml schema documents into subsets | |
| CN116414855A (en) | Information processing method and device, electronic equipment and computer readable storage medium | |
| CN114564934B (en) | Software program version difference analysis method, device, equipment and storage medium | |
| US20230089365A1 (en) | Data virtualization adapter in an integration platform | |
| CN110196803B (en) | Software defect training method and system | |
| CN113312053A (en) | Data processing method and device | |
| US20220114189A1 (en) | Extraction of structured information from unstructured documents | |
| CN113760949B (en) | Data query method and device | |
| CN118132153A (en) | Continuous integrated pipeline task execution method and device and related equipment | |
| McCampbell et al. | ATIS |
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 |