Analysis method, device and analysis tool of application program module

Abstract

The invention relates to an application program module analysis method and device and an analysis tool. The application program module analysis method comprises the following steps: analyzing a source code of at least one file contained in an application program to obtain an analysis result of the at least one file of the application program, and obtaining analysis results of all files contained in a module; carrying out module dependency analysis on the module level to acquire a module forward dependency analysis result, and acquiring a module analysis result in combination with a module file analysis result; and finally, carrying out cross-module analysis to obtain a reverse dependency analysis result between the module and the file on the module level and the file level. Reverse dependency analysis results of the file level and the module level are provided, research and development personnel can clearly know the reverse dependency relationship in the module and the file in the application program, redundancy of the program is reduced, and maintenance and iteration cost of the program is reduced.

Description

technical field [0001] The present disclosure relates to the field of computer programs, in particular to an analysis method, device and analysis tool for application program modules. Background technique [0002] In order to develop a complex application in parallel, reduce development complexity, and improve development efficiency, the application usually contains multiple modules, one module contains one or more files, and one file contains one or more APIs. Modules are interdependent and collaborate through certain conventions. [0003] Adopting this method brings a new problem: the dependencies between modules are difficult to track, and in the process of application iteration, it is easy to change one module and affect multiple modules. Due to the large number of modules in the application and the high cost of manual retrieval, it is difficult for developers to know the reverse dependencies (dependence by other modules) between modules, that is, it is difficult to kno...

AI Technical Summary

Problems solved by technology

[0003] Using this method brings a new problem: the dependencies between modules are difficult to track, and in the process of application iteration, it is easy to change one module and affect multiple modules.

Due to the large number of modules in the application and the high cost of manual retrieval, it is difficult for developers to know the reverse dependencies (dependence by other modules) between modules, that is, it is difficult to know which other modules will be affected by the iteration of a module, for example When multiple modules depend on the same module, once the module is iterated or modified, it will inevitably have an impact on the dependent modules. However, it is difficult for developers to know the reverse dependencies between modules and files. In the process of maintenance and maintenance, the source code is redundant, the program becomes more and more bloated, and the iteration cost is getting higher and higher

Images