A software system detection method, device, electronic device and storage medium

Abstract

The present application discloses a detection method, device, electronic device and computer-readable storage medium for a software system. The method comprises: if some software modules of the software system change, updating the hash value of the changed software module; calculating the chain hash value of the unchanged software module according to the call relationship corresponding to each software module; judging whether the chain hash value of the unchanged software module is the same as the corresponding historical chain hash value, if the chain hash value of any unchanged software module is different from the historical chain hash value, determining that the unchanged software module is disturbed; the method can characterize the impact of the change of any software module in the software system through the chain hash value, and quickly and accurately determine the unchanged software module that is disturbed.

Description

Technical Field

[0001] The present application relates to the field of software technology, and in particular to a software system detection method, a software system detection device, an electronic device and a computer-readable storage medium. Background Art

[0002] Generally, a software system is composed of multiple software modules, each of which has mutual calls and dependencies, and together constitutes several software. In the modular software design process, a module is called through an API (Application Programming Interface), or sends / receives information to use the functions of another or multiple modules. According to the calling relationship between modules, each module can be logically divided into multiple levels. The upper module calls the service or API provided by the lower module. In order to track the changes of modules, currently, an independent version number is set for each module, and when the software module changes, its version number is also upgraded accordingly. Developers and testers determine the changes of the software according to the version number of the module and carry out corresponding development and arrange testing. However, a software system usually includes multiple software, each of which includes multiple software modules. The calling relationship between each software module is complex. The version number can only determine the software module that has changed, and whether the change of the software module will affect the function realization of another software module requires developers to judge by themselves according to the calling relationship between the modules, which takes a long time.

[0003] Therefore, how to solve the problem that related technologies cannot quickly detect interference with software systems is a technical problem that technical personnel in this field need to solve. Summary of the invention

[0004] In view of this, the purpose of the present application is to provide a software system detection method, a software system detection device, an electronic device and a computer-readable storage medium, which can characterize the impact of changes in any software module in the software system and detect the software system quickly and accurately.

[0005] In order to solve the above technical problems, the present application provides a software system detection method, comprising:

[0006] If some software modules of the software system are changed, the hash value of the changed software module is updated;

[0007] According to the calling relationship corresponding to each software module, the chain hash value of the unchanged software module is calculated;

[0008] It is determined whether the chain hash value of the unchanged software module is the same as the corresponding historical chain hash value. If the chain hash value of any unchanged software module is not the same as the historical chain hash value, it is determined that the unchanged software module is interfered with.

[0009] Optionally, if some software modules of the software system are changed, it includes:

[0010] If it is detected that the header file and / or source file of any software module is edited, it is determined that the software module is changed.

[0011] Optionally, updating the hash value of the changed software module includes:

[0012] Using the header file and source file of the changed software module for splicing, to obtain intermediate data;

[0013] Perform hash calculation on the intermediate data to obtain the hash value.

[0014] Optionally, the calculating the chain hash value of the unchanged software module according to the call relationship corresponding to each software module includes:

[0015] According to the calling relationship, obtaining a target chain hash value of a target software module called by the unchanged software module;

[0016] The chain hash value of the unchanged software module is calculated using the hash value of the unchanged software module and the target chain hash value.

[0017] Optionally, the calculating the chain hash value of the unchanged software module by using the hash value of the unchanged software module and the target chain hash value includes:

[0018] An AND operation is performed using the hash value of the unchanged software module and the target chain hash value to obtain the chain hash value of the unchanged software module.

[0019] Optionally, it also includes:

[0020] Get call relationship information;

[0021] The target calling relationship information corresponding to the identity information in the calling relationship information is extracted by using the identity information of each software module respectively as the calling relationship corresponding to the software module.

[0022] Optionally, after determining whether the chain hash value of the unchanged software module is the same as the corresponding historical chain hash value, the method further includes:

[0023] The calculated chain hash value is used to update the historical chain hash value of the unchanged software module.

[0024] The present application also provides a software system detection device, comprising:

[0025] A first generating module, used for updating the hash value of the changed software module when some software modules of the software system are changed;

[0026] A second generation module is used to calculate the chain hash value of the unchanged software module according to the call relationship corresponding to each software module;

[0027] A determination module is used to determine whether the chain hash value of the unchanged software module is the same as the corresponding historical chain hash value. If the chain hash value of any unchanged software module is not the same as the historical chain hash value, it is determined that the unchanged software module is disturbed.

[0028] The present application also provides an electronic device, including a memory and a processor, wherein:

[0029] The memory is used to store the computer program;

[0030] The processor is used to execute the computer program to implement the above-mentioned software system detection method.

[0031] The present application also provides a computer-readable storage medium for storing a computer program, wherein the computer program implements the above-mentioned software system detection method when executed by a processor.

[0032] The software system detection method provided by the present application updates the hash value of the changed software module if some software modules of the software system change; calculates the chain hash value of the unchanged software module according to the calling relationship corresponding to each software module; determines whether the chain hash value of the unchanged software module is the same as the corresponding historical chain hash value; if the chain hash value of any unchanged software module is different from the historical chain hash value, it is determined that the unchanged software module is interfered with.

[0033] It can be seen that when the method detects that a software module has changed, it means that a software module has been updated. By updating the hash value of the changed software module, the changed status of these software modules can be determined. Each software module has its own calling relationship, which refers to the relationship between the software module calling other software modules, that is, which other software modules are called by this module. Based on the calling relationship, the chain hash value of each unchanged software module can be recalculated. The chain hash value of each software module can characterize the status of itself and other software modules called by it. After the calculation is completed, it is determined whether the new chain hash value is the same as the historical chain hash value before the update. If not, it means that the changed software module has interfered with the unchanged software module. Through the chain hash value, the impact of the change of any software module can be characterized in the software system, and the unchanged software module that has been disturbed can be quickly and accurately determined.

[0034] In addition, the present application also provides a detection device, electronic device and computer-readable storage medium for a software system, which also have the above-mentioned beneficial effects. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related technologies, the drawings required for use in the embodiments or the related technical descriptions are briefly introduced below. Obviously, the drawings described below are merely embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0036] Figure 1 A flow chart of a detection method for a software system provided in an embodiment of the present application;

[0037] Figure 2 A software system structure diagram provided for an embodiment of the present application;

[0038] Figure 3 A specific software system structure diagram provided for an embodiment of the present application;

[0039] Figure 4 A schematic diagram of the structure of a detection device for a software system provided in an embodiment of the present application;

[0040] Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0041] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0042] Please refer to Figure 1 , Figure 1 A flow chart of a detection method for a software system provided in an embodiment of the present application. The method includes:

[0043] S101: If some software modules of the software system are changed, the hash values ​​of the changed software modules are updated.

[0044] Among them, a software system refers to a system with multiple software modules that can build several software. A software module refers to a set of software codes that can be called directly. If changes are detected in some software modules in the software system, the hash values ​​of these changed software modules are updated. Generally, the function of a software module is affected by its header file and source file. If any change in either of the two files changes, the state of the software module is changed. Therefore, if changes are detected in the header file and / or source file of any software module, it is determined that the software module has changed. The new hash value generated during the update needs to represent the state of the entire software module, and the software module is usually composed of a header file and a source file. Therefore, in one embodiment, the process of updating the hash value may include:

[0045] Step 11: Use the header file and source file of the changed software module to splice and obtain the intermediate data.

[0046] Step 12: Perform hash calculation on the intermediate data to obtain a hash value.

[0047] This embodiment does not limit the specific splicing method, for example, the header file and the source file can be directly spliced, or they can be split and then mixed and spliced. After obtaining the intermediate data, the hash value is calculated using it. The specific calculation method is not limited, and reference can be made to related technologies.

[0048] S102: Calculate the chain hash value of the unchanged software module according to the calling relationship corresponding to each software module.

[0049] The calling relationship refers to the relationship in which the software module calls other software modules. It should be noted that, for any software module, the software module can be called the current module, and other software modules are software modules other than the current module.

[0050] The calling relationship of any software module indicates which other software modules are called by this module. Therefore, the data required to generate the chain hash value corresponding to this module can be obtained based on the calling relationship. Specifically, it is necessary to calculate the chain hash value (ChainHASH) of each unchanged software module. The chain hash value can indicate whether the unchanged software module is affected by any changed software module. The specific process of generating the chain hash value can include the following steps:

[0051] Step 21: According to the calling relationship, obtain the target chain hash value of the target software module called by the unchanged software module:.

[0052] Step 22: Calculate the chain hash value of the unchanged software module using the hash value of the unchanged software module and the target chain hash value.

[0053] Since the hash value is used to characterize the state of each software module itself, and the chain hash value can characterize the common state of itself and other software modules called by itself, it can be understood that when generating the chain hash value required by this module, the chain hash values ​​of other software modules need to be used. Therefore, it can be determined that the chain hash values ​​of each software module in the software system are not generated at the same time, but are generated layer by layer from the bottom layer to the top layer of the calling relationship according to the calling relationship of the entire software system. The software module that does not call any software module is located at the bottom layer of the calling relationship, and the software module that is not called by any software module is located at the top layer of the calling relationship. Specifically, for a software module that has not changed, when calculating its corresponding chain hash value, it is necessary to obtain the chain hash value of the target software module called by it, that is, the target chain hash value, and use the hash value of this software module and the target chain hash value to calculate the chain hash value of this software module. This embodiment does not limit the specific calculation method of the chain hash value. In one implementation, the hash value of the unchanged software module and the target chain hash value can be used to perform an AND operation using the hash value and the target chain hash value to obtain the chain hash value of the unchanged software module. In addition, other calculations, such as other logical operations, can also be performed.

[0054] To generate the chain hash value of an unchanged software module, its own hash value and the chain hash values ​​of all target software modules called by it are required. Moreover, when a software module changes, other software modules that call it will also be affected. The status of any software module can be reflected by its own chain hash value, and the impact on any software module can also be reflected by its chain hash value, which in turn affects the chain hash values ​​of other modules. In this way, the scope of impact caused by any change in a software module can be reflected in the chain hash values ​​of other unchanged software modules by means of a chain hash value. For details, please refer to Figure 2 , Figure 2 A software system structure diagram provided for an embodiment of the present application.

[0055] If a software module does not call other software modules, it means that it is at the bottom of the calling relationship, such as module A1, module A2, module A3 and module A4, and its corresponding chain hash value is equal to its own hash value, that is, A1 hash is equal to A1 chain hash, A2 hash is equal to A2 chain hash, A3 hash is equal to A3 chain hash, and A4 hash is equal to A4 chain hash. If the unchanged software module calls other software modules, the target chain hash values ​​of the other software modules called by it are obtained, and the chain hash values ​​are generated using them. For example, for module B2, it calls module A2, module A3 and module A4, then its corresponding target chain hash value B2 chain hash is B2 hash value & A2 chain hash & A3 chain hash & A4 chain hash, where & represents an AND operation. It should be noted that the above-mentioned chain hash value generation method is an exemplary specific method, and other chain hash value generation methods can also be selected as needed.

[0056] It is understandable that before using the call relationship to generate the chain hash value, it is also necessary to generate the call relationship. Specifically, the call relationship generation process includes:

[0057] Step 31: Get call relationship information.

[0058] Step 32: Using the identity information of each software module, extract the target calling relationship information corresponding to the identity information in the calling relationship information as the calling relationship corresponding to the software module.

[0059] Among them, the call relationship information includes the call relationship between each software module in the software system, and the identity information of each software module. Specifically, the call relationship information describes the relationship between the identity information of each software module to represent the call relationship between each software module. After obtaining the call relationship information, the call relationship is filtered using the identity information of each software module, and the part related to the software module is extracted to generate the call relationship of the software module. Identity information refers to information that can uniquely identify a software module, and illustratively, it can be a module number, module name, etc.

[0060] S103: Determine whether the chain hash value of the unchanged software module is the same as the corresponding historical chain hash value. If the chain hash value of any unchanged software module is different from the historical chain hash value, it is determined that the unchanged software module is disturbed.

[0061] The historical chain hash value refers to the chain hash value corresponding to each unchanged software module before recording the chain hash value of the unchanged software module. By comparing the chain hash value with the historical chain hash value, it can be determined whether the change of the software module affects the target software module.

[0062] If the chain hash value of the unchanged software module is the same as the historical chain hash value, it means that the unchanged software module has not been disturbed and can still operate normally. In this case, the preset operation can be performed. The specific content of the preset operation is not limited. For example, it can be no operation, that is, no operation is performed. It is understandable that after determining whether the chain hash value of the target software module is the same as the corresponding historical chain hash value, the chain hash value should be determined as the new historical chain hash value, so as to provide the historical chain hash value for the next judgment.

[0063] If the chain hash value of at least one unchanged software module is different from the historical chain hash value, it means that the changed software module has affected the operation of the unchanged software module. In this case, it cannot be guaranteed that the unchanged software module can still operate normally, and it is determined that it has been interfered with. Please refer to Figure 3 , Figure 3A specific software system structure diagram provided for an embodiment of the present application. A series of modular basic services (i.e., software modules) are provided on a software system called the Legato platform, and users can develop software based on these services. The eCall (emergency Call) APP used in the user-developed on-board TBOX (Telematics BOX, on-board network terminal) needs to pass the operator's certification test. The eCall certification process will last for several weeks, while other software in the entire system is also undergoing certification tests in parallel. Problems may be found in other certification processes and certain software modules in the Legato platform need to be updated. Legato needs to update the version number to reflect these changes, that is, it needs to be recompiled. This has raised questions from the eCall certification agency as to whether the eCall APP is affected and needs to be retested.

[0064] The problem can be solved by using the software system detection method provided by this application. Specifically, if the abstract hardware service module in the Legato platform is affected by other problems and the software code of the module needs to be updated, the entire software system needs to be recompiled after the update. After the compilation is completed, it can be determined that the chain hash values ​​of all software modules used by the eCall APP are the same as the historical chain hash values, so it is not disturbed and there is no need to restart the certification test.

[0065] By using the detection method of the software system provided by the embodiment of the present application, when a software module is detected to have changed, it is indicated that a software module has been updated. By updating the hash value of the software module that has changed, the changed state of these software modules can be determined. Each software module has its own calling relationship, which refers to the relationship between the software module calling other software modules, that is, which other software modules are called by this module. Based on the calling relationship, the chain hash value of each unchanged software module can be recalculated, and the chain hash value of each software module can characterize the state of itself and other software modules called by it. After the calculation is completed, it is determined whether the new chain hash value is the same as the historical chain hash value before the update. If not, it means that the changed software module has caused interference to the unchanged software module. Through the chain hash value, the change impact of any software module can be characterized in the software system, and the unchanged software module that has been disturbed can be quickly and accurately determined.

[0066] The following is an introduction to a detection device for a software system provided in an embodiment of the present application. The detection device for a software system described below and the detection method for a software system described above can be referenced to each other.

[0067] Please refer to Figure 4 , Figure 4A schematic diagram of a detection device for a software system provided in an embodiment of the present application includes:

[0068] A first generating module 110 is used to update the hash value of the changed software module if some software modules of the software system are changed;

[0069] The second generation module 120 is used to calculate the chain hash value of the unchanged software module according to the call relationship corresponding to each software module;

[0070] The determination module 130 is used to determine whether the chain hash value of the unchanged software module is the same as the corresponding historical chain hash value. If the chain hash value of any unchanged software module is different from the historical chain hash value, it is determined that the unchanged software module is disturbed.

[0071] Optionally, the first generating module 110 includes:

[0072] The edit detection unit is used to determine that a software module has been changed if it is detected that a header file and / or a source file of any software module has been edited.

[0073] Optionally, the first generating module 110 includes:

[0074] A splicing unit, used for splicing the header file and the source file of the changed software module to obtain intermediate data;

[0075] A computing unit is used to perform hash calculation on the intermediate data to obtain the hash value.

[0076] Optionally, the second generating module 120 includes:

[0077] A target determination unit, configured to obtain, according to the calling relationship, a target chain hash value of a target software module called by the unchanged software module;

[0078] The chain hash calculation unit is used to calculate the chain hash value of the unchanged software module by using the hash value of the unchanged software module and the target chain hash value.

[0079] Optionally, the chain hash calculation unit includes:

[0080] The AND calculation subunit is used to perform an AND operation using the hash value of the unchanged software module and the target chain hash value to obtain the chain hash value of the unchanged software module.

[0081] Optionally, it also includes:

[0082] An information acquisition module, used to obtain call relationship information;

[0083] The identity filtering module is used to respectively use the identity information of each software module to extract the target calling relationship information corresponding to the identity information in the calling relationship information as the calling relationship corresponding to the software module.

[0084] Optionally, it also includes:

[0085] The history update module is used to update the history chain hash value of the unchanged software module using the calculated chain hash value.

[0086] The electronic device provided in the embodiment of the present application is introduced below. The electronic device described below and the detection method of the software system described above can be referenced to each other.

[0087] Please refer to Figure 5 , Figure 5 The electronic device 100 may include a processor 101 and a memory 102 , and may further include one or more of a multimedia component 103 , an information input / information output (I / O) interface 104 , and a communication component 105 .

[0088] The processor 101 is used to control the overall operation of the electronic device 100 to complete all or part of the steps in the detection method of the software system described above; the memory 102 is used to store various types of data to support the operation of the electronic device 100, and these data may include, for example, instructions for any application or method used to operate on the electronic device 100, and data related to the application. The memory 102 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0089] The multimedia component 103 may include a screen and an audio component. The screen may be, for example, a touch screen, and the audio component is used to output and / or input audio signals. For example, the audio component may include a microphone, which is used to receive external audio signals. The received audio signal may be further stored in the memory 102 or sent through the communication component 105. The audio component also includes at least one speaker for outputting audio signals. The I / O interface 104 provides an interface between the processor 101 and other interface modules, and the above-mentioned other interface modules may be keyboards, mice, buttons, etc. These buttons may be virtual buttons or physical buttons. The communication component 105 is used for wired or wireless communication between the electronic device 100 and other devices. Wireless communication, such as Wi-Fi, Bluetooth, Near Field Communication (NFC), 2G, 3G or 4G, or a combination of one or more of them, so the corresponding communication component 105 may include: Wi-Fi components, Bluetooth components, NFC components.

[0090] The electronic device 100 can be implemented by one or more application specific integrated circuits (ASIC), digital signal processors (DSP), digital signal processing devices (DSPD), programmable logic devices (PLD), field programmable gate arrays (FPGA), controllers, microcontrollers, microprocessors or other electronic components to execute the detection method of the software system given in the above embodiment.

[0091] The computer-readable storage medium provided in the embodiments of the present application is introduced below. The computer-readable storage medium described below and the detection method of the software system described above can be referenced to each other.

[0092] The present application also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the above-mentioned software system detection method are implemented.

[0093] The computer-readable storage medium may include: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and other media that can store program codes.

[0094] In this specification, each embodiment is described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the embodiments can be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part.

[0095] Those skilled in the art may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented with electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0096] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0097] Finally, it should be noted that, in this article, relationships such as first and second, etc. are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms include, include or any other variations are intended to cover non-exclusive inclusion, so that a process, method, article or device that includes a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device.

[0098] Specific examples are used herein to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea. At the same time, for those skilled in the art, according to the idea of ​​the present application, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. A software system detection method, characterized in that: include: If some software modules of the software system are changed, the hash value of the changed software module is updated; The hash value is used to characterize the status of each software module itself; According to the calling relationship corresponding to each software module, the chain hash value of the unchanged software module is calculated; the chain hash value is used to represent the common state of itself and other software modules called by itself; Determine whether the chain hash value of the unchanged software module is the same as the corresponding historical chain hash value, and if the chain hash value of any unchanged software module is not the same as the historical chain hash value, determine that the unchanged software module is interfered; The step of calculating the chain hash value of the unchanged software module according to the call relationship corresponding to each software module includes: According to the calling relationship, obtaining a target chain hash value of a target software module called by the unchanged software module; The chain hash value of the unchanged software module is calculated using the hash value of the unchanged software module and the target chain hash value.

2. The software system detection method according to claim 1, characterized in that: If some software modules of the software system are changed, it includes: If it is detected that the header file and / or source file of any software module is edited, it is determined that the software module is changed.

3. The software system detection method according to claim 2, characterized in that: The updating of the hash value of the changed software module includes: Using the header file and source file of the changed software module for splicing, to obtain intermediate data; Perform hash calculation on the intermediate data to obtain the hash value.

4. The software system detection method according to claim 1, characterized in that: The calculating the chain hash value of the unchanged software module by using the hash value of the unchanged software module and the target chain hash value includes: An AND operation is performed using the hash value of the unchanged software module and the target chain hash value to obtain the chain hash value of the unchanged software module.

5. The software system detection method according to claim 1, characterized in that: Also includes: Get call relationship information; The target calling relationship information corresponding to the identity information in the calling relationship information is extracted by using the identity information of each software module respectively as the calling relationship corresponding to the software module.

6. The software system detection method according to claim 1, characterized in that: After determining whether the chain hash value of the unchanged software module is the same as the corresponding historical chain hash value, the method further includes: The calculated chain hash value is used to update the historical chain hash value of the unchanged software module.

7. A detection device for a software system, characterized in that: include: A first generating module, used for updating the hash value of the changed software module when some software modules of the software system are changed; The hash value is used to characterize the status of each software module itself; The second generation module is used to calculate the chain hash value of the unchanged software module according to the calling relationship corresponding to each software module; the chain hash value is used to represent the common state of the software module itself and other software modules called by the software module; A determination module, used to determine whether the chain hash value of the unchanged software module is the same as the corresponding historical chain hash value, and if the chain hash value of any unchanged software module is not the same as the historical chain hash value, it is determined that the unchanged software module is interfered; Wherein, the second generation module includes: A target determination unit, configured to obtain, according to the calling relationship, a target chain hash value of a target software module called by the unchanged software module; The chain hash calculation unit is used to calculate the chain hash value of the unchanged software module by using the hash value of the unchanged software module and the target chain hash value.

8. An electronic device, characterized in that: comprising a memory and a processor, wherein: The memory is used to store the computer program; The processor is used to execute the computer program to implement the software system detection method according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that: Used to store a computer program, wherein when the computer program is executed by a processor, the detection method of the software system according to any one of claims 1 to 6 is implemented.

Images