CN118502814B - Software modification evaluation method, device, equipment and medium based on byte codes - Google Patents

Abstract

The invention discloses a software modification evaluation method, device, equipment and medium based on byte codes. The method comprises the following steps: acquiring a target byte code file of a software target version and a byte code file to be evaluated of a to-be-online version; determining the change content of the on-line version to be compared with the target version according to the target byte code file and the byte code file to be evaluated; a potential impact of the modified content is determined and an evaluation report is generated based on the potential impact and the modified content. The embodiment of the invention can improve the evaluation efficiency of byte code modification.

Description

A bytecode-based software modification assessment method, device, equipment and medium

Technical Field

The present invention relates to the technical field of software development, and in particular to a bytecode-based software modification evaluation method, device, equipment and medium.

Background Art

During software development and maintenance, code changes are inevitable, especially when code at the interface level changes.

Traditional static analysis technology often adopts the method of full analysis, that is, comprehensive parsing and analysis of the entire bytecode. However, this method is inefficient and consumes a lot of computing resources when dealing with large or frequently changing code bases, and cannot meet the requirements of modern software development for rapid iteration and continuous integration.

Summary of the invention

The present invention provides a bytecode-based software modification evaluation method, device, equipment and medium to improve the evaluation efficiency of bytecode modifications.

According to one aspect of the present invention, a bytecode-based software modification assessment method is provided, comprising:

Obtain the target bytecode file of the target version of the software and the bytecode file to be evaluated of the version to be launched;

Determine the changes of the to-be-released version relative to the target version according to the target bytecode file and the to-be-evaluated bytecode file;

Determine the potential impact of the modified content, and generate an assessment report based on the potential impact and the modified content.

According to another aspect of the present invention, there is provided a bytecode-based software modification assessment device, comprising:

Obtain the target bytecode file of the target version of the software and the bytecode file to be evaluated of the version to be launched;

Determine the changes of the to-be-released version relative to the target version according to the target bytecode file and the to-be-evaluated bytecode file;

Determine the potential impact of the modified content, and generate an assessment report based on the potential impact and the modified content.

According to another aspect of the present invention, a computer program product is provided, comprising a computer program, wherein when the computer program is executed by a processor, the bytecode-based software modification assessment method according to any embodiment of the present invention is implemented.

According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

at least one processor; and

a memory communicatively connected to the at least one processor; wherein,

The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the bytecode-based software modification assessment method described in any embodiment of the present invention.

According to another aspect of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, wherein the computer instructions are used to enable a processor to implement the bytecode-based software modification assessment method described in any embodiment of the present invention when executed.

The embodiment of the present invention analyzes the modified content and its impact in the bytecode dimension and generates an evaluation report, thereby greatly improving the modification evaluation efficiency compared to the existing manual evaluation method while ensuring the accuracy of the modification evaluation.

It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

FIG1 is a flow chart of a bytecode-based software modification assessment method according to an embodiment of the present invention;

FIG2 is a flow chart of a bytecode-based software modification assessment method according to another embodiment of the present invention;

FIG3 is a schematic diagram of the structure of a bytecode-based software modification assessment method according to another embodiment of the present invention;

FIG. 4 is a schematic diagram of the structure of an electronic device implementing an embodiment of the present invention.

DETAILED DESCRIPTION

In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

FIG1 is a flow chart of a bytecode-based software modification evaluation method provided by an embodiment of the present invention. This embodiment is applicable to the situation where the evaluator inputs the target bytecode file and the bytecode file to be evaluated, and the system automatically analyzes the content of the modification and its impact and then outputs an evaluation report. The method can be executed by a bytecode-based software modification evaluation device, which can be implemented in the form of hardware and/or software. The device can be configured in an electronic device with corresponding data processing capabilities, such as a software development management system. As shown in FIG1 , the method includes:

S110 , obtaining a target bytecode file of the target version of the software and a bytecode file to be evaluated of the version to be launched.

Among them, bytecode files include but are not limited to .class files, .jar packages, .war files, and compilation products of other JVM programming languages.

Specifically, during the software iteration and version control process, the online version or the baseline version of the software is used as the target version. The target bytecode file compiled from the target version of the software and the bytecode file to be evaluated compiled from the version to be launched input by the evaluator are received.

S120: Determine the changes of the to-be-released version relative to the target version according to the target bytecode file and the to-be-evaluated bytecode file.

The changes include changes to key content and changes to non-key content.

Specifically, use a special difference comparison tool or algorithm to compare the different bytecode files of the two versions, so as to accurately identify the changes in the version to be launched relative to the target version, such as the changed methods, instructions or interface elements. The purpose of the comparison is to identify what changes have been made in the version to be launched, so as to evaluate the impact of these changes on system behavior, performance and stability. This is crucial for ensuring software quality, performing regression testing, and identifying potential risks and problems.

S130: Determine the potential impact of the modified content, and generate an assessment report based on the potential impact and the modified content.

Specifically, based on pre-configured evaluation rules, the potential impact of these changes on system performance, functional logic, security, compatibility, etc. is evaluated according to the changes and their types.

In terms of system performance: evaluate whether the changes may lead to performance degradation or improvement, such as optimization of loop structure, changes in memory allocation, etc.

In terms of functional logic: evaluate whether the changes may introduce new logical errors, dead loops, exception handling, etc.

In terms of security: Assess whether the changes may increase security risks, such as unchecked user input, exposure of sensitive information, etc.

In terms of compatibility: evaluate whether the changes may break compatibility with older versions or affect other code that depends on this part.

After determining the content of the change and its potential impact, the system will generate an assessment report based on these two parts and other necessary reference information. For this assessment report, the system will push it to the corresponding assessor or display it directly on the operation terminal.

The embodiment of the present invention analyzes the modified content and its impact in the bytecode dimension and generates an evaluation report, thereby greatly improving the modification evaluation efficiency compared to the existing manual evaluation method while ensuring the accuracy of the modification evaluation.

FIG2 is a flowchart of a bytecode-based software modification evaluation method provided by another embodiment of the present invention. This embodiment is optimized and improved on the basis of the above embodiment. As shown in FIG2, the method includes:

S210: Obtain the target bytecode file of the target version of the software and the bytecode file to be evaluated of the version to be launched.

S220: Based on the recognition results of the key parts in the target bytecode file, establish a first index mapping table of the target bytecode file; based on the recognition results of the key parts in the bytecode file to be evaluated, establish a second index mapping table of the bytecode file to be evaluated.

S230: Determine changes in key parts of the to-be-released version relative to the target version according to the first index mapping table and the second index mapping table.

The key part is the part of the bytecode of the software that is considered to have a significant impact on the software function and performance, including but not limited to method definitions, class definitions, key fields, strings in the constant pool, and class references in the bytecode. The index mapping table contains at least the identifier of each key part and the specific location of the key part in the bytecode file.

Specifically, the present invention provides three key part recognition schemes, namely manual recognition, static recognition and dynamic recognition. These three recognition methods can be used one by one or in combination:

In manual identification, experienced developers or architects determine which parts are the skeleton and core of the program based on the structure and design patterns of the code, and input the identification results into the system.

In static identification, the system uses static code analysis tools to identify key classes, methods, variables and other parts, and obtains the identification results of key parts. These tools can analyze the complexity, dependencies and other indicators of the code to help locate the key parts.

In dynamic identification, the system monitors and debugs the performance of the software at runtime to observe which code parts are frequently called or consume a lot of resources during execution, so as to determine whether they are critical and obtain the identification results of the critical parts.

For the current bytecode file (the current bytecode file or the bytecode file to be identified), the system creates a unique identifier for each key part based on its identification results, and associates the identifier of the key part with its position information in the current file one by one to form an index mapping table of the current bytecode file (the first index mapping table or the second index mapping table), and the preprocessing is completed.

If there is no index of the key part, the comparison process may be performed byte by byte or line by line, which is very time-consuming. However, if there is an index of the key part, the system can directly locate the key part in the bytecode and compare the changes in the key part of the two bytecode files without comparing the changes in the non-key part of the two bytecode files, which greatly improves the speed of difference detection.

Optionally, determining the changes in the key part of the to-be-released version relative to the target version according to the first index mapping table and the second index mapping table includes:

Determine a non-common key portion according to the first index mapping table and the second index mapping table;

Determine a common key portion according to the first index mapping table and the second index mapping table and a first position of the common key portion in the target bytecode file and a second position of the bytecode file to be evaluated;

Determining the modified content of the common key part according to the bytecode at the first position in the target bytecode file and the bytecode at the second position in the bytecode file to be evaluated;

The modified content of the shared key part and the non-shared key part are determined as the modified content of the to-be-released version in the key part relative to the target version.

The shared key part is a key part that appears in both the first index mapping table and the second index mapping table. The non-shared key part is a key part that appears only in the first index mapping table or only in the second index mapping table, and is divided into two categories: a newly added key part and a deleted key part.

Specifically, when detecting differences, the first and second index mapping tables are queried to determine the common and non-common key parts of the two bytecodes. For the latter, it can be determined without a doubt that it is the change in the key part of the version to be launched relative to the target version. For the former, further analysis is required:

The first index mapping table and the second index mapping table are queried to determine that the common key part is at the first position of the target bytecode file, such as lines 2-4 of the target bytecode file, and the common key part is at the second position of the bytecode file to be evaluated, such as lines 5-6 of the bytecode file to be evaluated. The bytecode at the first position is compared with the bytecode at the second position. If the comparison result shows that the bytecodes are completely consistent, it is determined that the common key part has not been improved and is not a modified content; if the comparison result shows that the bytecodes are not completely consistent, it is determined that the common key part has been improved and is a modified content.

In addition, basic indexing provides the precise location of changes, allowing assessors to quickly understand which specific lines of code or instructions have changed, for example:

1. Directly locate the change point:

When the modified bytecode section is identified, the system uses the location information in the index to directly locate the specific line of code or instruction that was modified and displays it to the evaluator, so that the evaluator can quickly see which code has been modified.

2. Compare the content before and after the change:

The system can quickly extract code snippets before and after the changes through indexing and display them to the evaluator so that the evaluator can clearly see which codes have been added, deleted or modified, and accurately understand the specific content of the changes.

3. Visual display changes:

Using basic indexes, the system can highlight the changed parts or display them in other forms in the code editor, so that evaluators can intuitively see the changed points and improve the accuracy of the analysis.

S240. Obtain auxiliary evaluation metadata corresponding to the changed content from the first index mapping table and the second index mapping table; input the changed content, the auxiliary evaluation metadata and other reference data into a change impact prediction model to obtain a potential impact degree and potential impact type of the changed content.

The potential impact levels include minor impact, medium impact, and severe impact. Potential impact types include performance degradation, functional errors, and security issues. Other reference data include historical change data, error records, etc. The auxiliary evaluation metadata includes at least one of the following: method call relationships, method dependency information, and class inheritance relationships.

Specifically, the index not only contains the location information of the key part, but also other auxiliary evaluation metadata that helps with difference detection, such as the hash value of the key part, modification time, method call relationship, method dependency information, and class inheritance relationship. In the process of change detection, these metadata can be used to further optimize the comparison strategy and subsequent impact assessment. For example, by comparing the hash value, you can quickly determine whether a key part has changed without the need for actual bytecode comparison. In the impact assessment process, the historical change records and error logs recorded in the auxiliary evaluation metadata can help predict potential problems that may be introduced by the current change, so as to prevent risks in advance; the previous test information and the impact range of the change point recorded in the auxiliary evaluation metadata can help determine which test cases need to be re-executed to ensure that the change does not introduce new problems; when a method is improved, the call relationship and dependency information recorded in the auxiliary evaluation metadata can help quickly understand which other methods this method is called by, and which methods it calls, so as to quickly assess the possible impact of the change.

Generate training samples and their impact labels and impact type labels based on historical changes and their actual impact levels and types. Select a suitable machine learning model (such as decision tree, random forest, neural network, etc.), train it with training samples, and use cross-validation and other techniques to evaluate the performance of the model. After training, obtain the change impact prediction model. In practical applications, the model can be used to predict the potential impact of new changes on the system, thereby assisting the development team in making more informed decisions. During actual prediction, the change content, the auxiliary evaluation metadata and other reference data are input into the impact prediction model, and the model predicts and outputs the potential impact level and potential impact type on the change content.

S250, obtaining a dependency network diagram and a diffusion path diagram of the modified content; and obtaining historical repair measures corresponding to the potential impact.

S260. Based on a preset report template, generate a graphic assessment report according to the dependency network diagram, the diffusion path diagram, the changed content, the auxiliary assessment metadata, the potential impacts and the historical repair measures.

Among them, diffusion paths and dependency networks can help evaluators quickly understand which other methods the modified method is called by and which methods it calls. In this way, evaluators can assess the possible impact of the change.

Specifically, the auxiliary evaluation metadata of the changed content is obtained according to the first index mapping table and the second index mapping table, and the dependency network and diffusion path of the changed content are determined according to the auxiliary evaluation information such as the method call relationship, method dependency information, class inheritance relationship, etc. recorded in the auxiliary evaluation metadata, and the corresponding dependency network diagram and diffusion path diagram are generated. Search the database for historical changes that are similar or consistent with the current changes, and determine the historical repair measures for the historical changes. Fill in the dependency network diagram, diffusion path diagram, changed content, auxiliary evaluation metadata, potential impacts and historical repair measures into the corresponding positions of the report template one by one to generate a graphic evaluation report.

The embodiment of the present invention combines a variety of information data to generate a graphic evaluation report, thereby improving the reference value of the graphic evaluation report and facilitating evaluators to quickly understand the modified content and make decisions.

FIG3 is a schematic diagram of the structure of a bytecode-based software modification assessment device provided by another embodiment of the present invention. As shown in FIG3 , the device includes:

The file acquisition module 310 is used to acquire the target bytecode file of the target version of the software and the bytecode file to be evaluated of the version to be launched;

A change determination module 320, configured to determine the changes of the to-be-released version relative to the target version according to the target bytecode file and the to-be-evaluated bytecode file;

The report generation module 330 is used to determine the potential impact of the modified content and generate an evaluation report based on the potential impact and the modified content.

The bytecode-based software modification evaluation device provided in the embodiment of the present invention can execute the bytecode-based software modification evaluation method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

Optionally, the modification determination module 320 includes:

A first index establishing unit, configured to establish a first index mapping table of the target bytecode file based on the recognition results of each key part in the target bytecode file;

A second index establishing unit, configured to establish a second index mapping table of the bytecode file to be evaluated based on the recognition results of each key part in the bytecode file to be evaluated;

A change determination unit is used to determine the changes in the key parts of the version to be launched relative to the target version according to the first index mapping table and the second index mapping table.

Optionally, the change determination unit is specifically used to: determine the non-common key part according to the first index mapping table and the second index mapping table;

Determine a common key portion according to the first index mapping table and the second index mapping table and a first position of the common key portion in the target bytecode file and a second position of the bytecode file to be evaluated;

Determining the modified content of the common key part according to the bytecode at the first position in the target bytecode file and the bytecode at the second position in the bytecode file to be evaluated;

The modified content of the shared key part and the non-shared key part are determined as the modified content of the to-be-released version in the key part relative to the target version.

Optionally, the report generation module 330 includes;

An analysis data acquisition unit, configured to acquire auxiliary evaluation metadata corresponding to the modified content from the first index mapping table and the second index mapping table;

The impact determination unit is used to input the modified content, the auxiliary evaluation metadata and other reference data into the modification impact prediction model to obtain the potential impact degree and potential impact type of the modified content.

Optionally, the report generation module 330 includes:

An analysis diagram acquisition unit, used to acquire a dependency network diagram and a diffusion path diagram of the modified content;

A measure acquisition unit, used to acquire historical repair measures corresponding to the potential impact;

A report generation unit is used to generate a graphic evaluation report based on a preset report template, according to the dependency network diagram, the diffusion path diagram, the changed content, the auxiliary evaluation metadata, the potential impact and the historical repair measures.

Optionally, the auxiliary evaluation metadata includes at least one of the following: method calling relationship, method dependency information, and class inheritance relationship.

The bytecode-based software modification assessment device further described can also execute the bytecode-based software modification assessment method provided by any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

FIG4 shows a block diagram of an electronic device 40 that can be used to implement an embodiment of the present invention. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and/or required herein.

As shown in FIG4 , the electronic device 40 includes at least one processor 41, and a memory connected to the at least one processor 41 in communication, such as a read-only memory (ROM) 42, a random access memory (RAM) 43, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 41 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 42 or the computer program loaded from the storage unit 48 to the random access memory (RAM) 43. In the RAM 43, various programs and data required for the operation of the electronic device 40 can also be stored. The processor 41, the ROM 42, and the RAM 43 are connected to each other via a bus 44. An input/output (I/O) interface 45 is also connected to the bus 44.

A number of components in the electronic device 40 are connected to the I/O interface 45, including: an input unit 46, such as a keyboard, a mouse, etc.; an output unit 47, such as various types of displays, speakers, etc.; a storage unit 48, such as a disk, an optical disk, etc.; and a communication unit 49, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 49 allows the electronic device 40 to exchange information/data with other devices through a computer network such as the Internet and/or various telecommunication networks.

The processor 41 may be a variety of general and/or special processing components with processing and computing capabilities. Some examples of the processor 41 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 41 executes the various methods and processes described above, such as the bytecode-based software modification assessment method.

In some embodiments, the bytecode-based software modification assessment method may be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 48. In some embodiments, part or all of the computer program may be loaded and/or installed on the electronic device 40 via the ROM 42 and/or the communication unit 49. When the computer program is loaded into the RAM 43 and executed by the processor 41, one or more steps of the bytecode-based software modification assessment method described above may be performed. Alternatively, in other embodiments, the processor 41 may be configured to execute the bytecode-based software modification assessment method in any other appropriate manner (e.g., by means of firmware).

Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and/or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

Computer programs for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when the computer program is executed by the processor, the functions/operations specified in the flow chart and/or block diagram are implemented. The computer program may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

In the context of the present invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, device, or equipment. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

To provide interaction with a user, the systems and techniques described herein may be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or trackball) through which the user can provide input to the electronic device. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).

The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

A computing system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services.

It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the present invention can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution of the present invention can be achieved, and this document does not limit this.

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

Claims (7)

1. A bytecode-based software modification assessment method, characterized in that the method comprises: Obtain the target bytecode file of the target version of the software and the bytecode file to be evaluated of the version to be launched; Determine the changes of the to-be-released version relative to the target version according to the target bytecode file and the to-be-evaluated bytecode file; Determine the potential impact of the changes and generate an assessment report based on the potential impact and the changes; The step of determining the changes of the to-be-released version relative to the target version according to the target bytecode file and the to-be-evaluated bytecode file includes: Based on the recognition results of the key parts in the target bytecode file, establishing a first index mapping table of the target bytecode file; Based on the recognition results of the key parts in the bytecode file to be evaluated, a second index mapping table of the bytecode file to be evaluated is established; Determine, according to the first index mapping table and the second index mapping table, the changes in the key part of the version to be launched relative to the target version; the key part is the part of the bytecode of the software that is considered to have a significant impact on the software function and software performance; The determining, according to the first index mapping table and the second index mapping table, the changes in the key parts of the to-be-released version relative to the target version includes: Determine a non-shared key part according to the first index mapping table and the second index mapping table; the non-shared key part is a key part that only appears in the first index mapping table or only appears in the second index mapping table; Determine a common key portion according to the first index mapping table and the second index mapping table and the common key portion at a first position in the target bytecode file and at a second position in the bytecode file to be evaluated; the common key portion is a key portion that appears in both the first index mapping table and the second index mapping table; Determining the modified content of the common key part according to the bytecode at the first position in the target bytecode file and the bytecode at the second position in the bytecode file to be evaluated; The modified content of the shared key part and the non-shared key part are determined as the modified content of the to-be-released version in the key part relative to the target version. 2. The method according to claim 1, wherein determining the potential impact of the modified content comprises: Acquire auxiliary evaluation metadata corresponding to the modified content from the first index mapping table and the second index mapping table; The modified content, the auxiliary evaluation metadata and other reference data are input into a modification impact prediction model to obtain the potential impact degree and potential impact type of the modified content. 3. The method according to claim 2 is characterized in that the auxiliary evaluation metadata includes at least one of the following: method calling relationship, method dependency information and class inheritance relationship. 4. The method according to claim 2, wherein generating an assessment report according to the potential impact and the modified content comprises: Obtaining a dependency network diagram and a diffusion path diagram of the modified content; Obtain historical remediation measures corresponding to the potential impacts; Based on a preset report template, a graphic assessment report is generated according to the dependency network diagram, the diffusion path diagram, the changed content, the auxiliary assessment metadata, the potential impact and the historical repair measures. 5. A bytecode-based software modification assessment device, characterized in that the device comprises: A file acquisition module is used to acquire the target bytecode file of the target version of the software and the bytecode file to be evaluated of the version to be launched; A change determination module, used to determine the changes of the to-be-released version relative to the target version according to the target bytecode file and the to-be-evaluated bytecode file; A report generation module, used to determine the potential impact of the modified content and generate an evaluation report based on the potential impact and the modified content; Wherein, the modification determination module includes: A first index establishing unit, configured to establish a first index mapping table of the target bytecode file based on the recognition results of each key part in the target bytecode file; A second index establishing unit, configured to establish a second index mapping table of the bytecode file to be evaluated based on the recognition results of each key part in the bytecode file to be evaluated; a change determination unit, configured to determine the changes of the to-be-released version in a key part relative to the target version according to the first index mapping table and the second index mapping table; the key part is a part of the bytecode of the software that is considered to have a significant impact on the software function and software performance; Among them, the change determination unit is specifically used to: determine the non-common key part according to the first index mapping table and the second index mapping table; the non-common key part is the key part that only appears in the first index mapping table or only in the second index mapping table; determine the common key part and the common key part at the first position of the target bytecode file and the second position of the bytecode file to be evaluated according to the first index mapping table and the second index mapping table; the common key part is the key part that appears in both the first index mapping table and the second index mapping table; determine the changed content of the common key part according to the bytecode at the first position in the target bytecode file and the bytecode at the second position in the bytecode file to be evaluated; determine the changed content of the common key part and the non-common key part as the changed content of the key part of the version to be launched relative to the target version. 6. An electronic device, characterized in that the electronic device comprises: at least one processor; and a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can perform the bytecode-based software modification assessment method according to any one of claims 1 to 4. 7. A computer-readable storage medium, characterized in that the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the bytecode-based software modification assessment method according to any one of claims 1 to 4 when executed.