WO2022100032A1

WO2022100032A1 - System analysis visualization method and apparatus, electronic device, and computer readable storage medium

Info

Publication number: WO2022100032A1
Application number: PCT/CN2021/091439
Authority: WO
Inventors: 楚亚兵; 黑晓群
Original assignee: 平安普惠企业管理有限公司
Priority date: 2020-11-10
Filing date: 2021-04-30
Publication date: 2022-05-19
Also published as: CN112364107A

Abstract

The present application relates to big data technology. Disclosed is a system analysis visualization method, comprising: acquiring a system data set to be analyzed; constructing an interface call graph according to a reference relationship present in the system data set to be analyzed; searching for entity class files in the system data set to be analyzed, and constructing a data model diagram according to the entity class files; acquiring an updated system data set, and comparing same with the system data set to be analyzed to obtain a system file difference table; and displaying, according to the interface call graph, the data model diagram, and the system file difference table, system content corresponding to the system data set to be analyzed. Furthermore, the present application also provides a system analysis visualization apparatus, and a computer readable storage medium. In addition, the present application further relates to blockchain technology. The system data set to be analyzed can be stored in a blockchain node. The present application can implement more comprehensive and clear system analysis visualization.

Description

System analysis visualization method, apparatus, electronic device, and computer-readable storage medium

This application claims the priority of the Chinese patent application with the application number CN202011246852.0 and the title of "System Analysis Visualization Method, Device, Electronic Device and Computer-readable Storage Medium" filed with the China Patent Office on November 10, 2020, which The entire contents of this application are incorporated by reference.

technical field

The present application relates to the field of big data technologies, and in particular, to a system analysis and visualization method, apparatus, electronic device, and computer-readable storage medium.

Background technique

The back of a business system contains large-scale code files, data files, etc., and the business system is not static after it is put into use, and often requires later maintenance, updates, etc. Therefore, it is necessary to analyze and visualize the internal code files of the system, In order to facilitate the maintenance or update of subsequent systems.

technical problem

The current system analysis visualization mainly shows the main modules of the system according to the document records. The inventor realized that this method cannot clearly show the logical calling relationship between the internal codes of the system, and the content of the business system is not comprehensive enough and clearly displayed. , which is not conducive to subsequent maintenance or update of the system.

technical solutions

A system analysis and visualization method provided by this application includes:

Obtain the data set of the system to be analyzed;

Build an interface calling relationship diagram according to the reference relationship existing in the data set of the system to be analyzed;

Find the entity class file in the data set of the system to be analyzed, and build a data model diagram according to the entity class file;

Obtain and update the system data set, and compare it with the system data set to be analyzed to obtain a system file difference table;

According to the interface calling relationship diagram, the data model diagram and the system file difference table, the system content corresponding to the system data set to be analyzed is displayed.

The application also provides a system analysis visualization device, the device includes:

The data acquisition module is used to acquire the data set of the system to be analyzed;

an interface relation call graph module, configured to construct an interface call relation graph according to the reference relation existing in the data set of the system to be analyzed;

a data model diagram module, used for finding entity class files in the system data set to be analyzed, and constructing a data model diagram according to the entity class files;

A file difference table module, used to obtain and update the system data set, and compare it with the system data set to be analyzed to obtain a system file difference table;

The display output module is configured to display the system content corresponding to the to-be-analyzed system data set according to the interface call relationship diagram, the data model diagram and the system file difference table.

The present application also provides an electronic device, the electronic device comprising:

at least one processor; and,

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

The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the steps of:

Obtain the data set of the system to be analyzed;

The present application also provides a computer-readable storage medium, comprising a storage data area and a storage program area, wherein the storage data area stores created data, and the storage program area stores a computer program; wherein the computer program is The processor implements the following steps when executing:

Obtain the data set of the system to be analyzed;

Description of drawings

1 is a schematic flowchart of a system analysis visualization method provided by an embodiment of the present application;

FIG. 2 is a schematic block diagram of a system analysis visualization device provided by an embodiment of the present application;

3 is a schematic diagram of the internal structure of an electronic device for implementing a system analysis visualization method provided by an embodiment of the present application;

The realization, functional characteristics and advantages of the purpose of the present application will be further described with reference to the accompanying drawings in conjunction with the embodiments.

Embodiments of the present invention

It should be understood that the specific embodiments described herein are only used to explain the present application, but not to limit the present application.

The execution subject of the system analysis visualization method provided by the embodiment of the present application includes, but is not limited to, at least one of electronic devices such as a server and a terminal that can be configured to execute the method provided by the embodiment of the present application. In other words, the system analysis and visualization method can be executed by software or hardware installed in a terminal device or a server device, and the software can be a blockchain platform. The server includes but is not limited to: a single server, a server cluster, a cloud server or a cloud server cluster, and the like.

The present application provides a system analysis visualization method. Referring to FIG. 1 , a schematic flowchart of a system analysis and visualization method provided by an embodiment of the present application is shown. The method may be performed by an apparatus, which may be implemented in software and/or hardware.

In this embodiment, the system analysis visualization method includes:

S1. Obtain a system data set to be analyzed.

In the embodiment of the present application, the data set of the system to be analyzed is a complete set of source codes of a business system, including multiple class files, toolkits, configuration files, and the like.

Preferably, various programming languages are used during system development, and commonly used programming languages include java, C/C++, php, python, and the like. In object-oriented programming languages, based on classes and objects, all operations in the language are carried out through objects. Many functions can be defined in a class code file, and the functions can be implemented by instantiating the aforementioned class objects. The system data set to be analyzed in the embodiments of the present application is data in a business system based on class objects.

Specifically, the system data set to be analyzed may be obtained from a preset server.

Preferably, the system data set to be analyzed can also be obtained from a node of a blockchain, and the security of the system data set to be analyzed is improved by storing the system data set to be analyzed in the blockchain.

S2. Build an interface calling relationship diagram according to the reference relationship existing in the data set of the system to be analyzed.

Preferably, a business system contains a large number of class files, and there is a mutual calling relationship between various class files, and a system function is jointly implemented by a plurality of class files.

In this embodiment of the present application, the interface calling relationship diagram is a tree diagram, and objects are organized in a parent-child hierarchical structure. The interface call relationship diagram includes a plurality of root nodes and sub-nodes. The interface call relationship diagram can display the distribution of modules in the data set of the system to be analyzed and the calling relationship between each class file, and can also display the corresponding Detailed functions of the business system.

In detail, the construction of the interface calling relationship diagram according to the reference relationship between the various classes in the system data set to be analyzed includes:

Utilize the root class search method to find the root class file in the data set of the system to be analyzed, and use the root class file as the root node;

Find a class file that references the root class file in the system data set to be analyzed, and use the class file of the root class file as a child node of the root node;

Search and reference the class file class file corresponding to the child node in the system data set to be analyzed, and use the class file of the class file corresponding to the child node as the next child node of the child node;

The above steps are repeated until the searched class file is not referenced by other class files, and the interface calling relationship diagram corresponding to the system data set to be analyzed is obtained.

Preferably, the root class file refers to class files that are not referenced by other class files, such as interfaces, timed tasks, message entries, and abandoned orphan classes. Further, using the root class finding method to find the root class files in the system data set to be analyzed, including:

Traverse the class files in the system data set to be analyzed;

Extract the header data of the currently traversed class file;

If no other class file is referenced in the header data, the currently traversed class file is determined as the root class file.

The header data refers to data information such as a package name at the beginning of a class file, reference to other class files, and other data information, and the identification character "import" is used when referencing other class files.

Optionally, in an optional embodiment of the present application, the interface calling relationship diagram may also be improved, including: counting the number of times each class file is cited; obtaining annotations and annotations of the class files in the system data set to be analyzed. ; Add the above data information to the corresponding class file in the interface call graph.

Preferably, the user can quickly learn about the business system corresponding to the system data set to be analyzed through the interface calling relationship diagram, so as to perform further analysis. For example, it can quickly locate the external interface and the calling relationship of the internal interface, and can also analyze which classes are closely related and which are sparse. The rationality of module division in the business system provides a quantitative basis for module division; it can also analyze which classes in the business system are isolated and which call chains have been abandoned, so as to simplify and optimize the business system.

S3. Find the entity class file in the data set of the system to be analyzed, and construct a data model diagram according to the entity class file.

The types of class files in the system data set to be analyzed in the embodiments of the present application include various types, such as entity classes, service classes, tool classes, and configuration classes. The entity class is data describing objective things in the real world, which can refer to people, such as teachers, students, etc., or objects, such as books, warehouses, and the like.

Specifically, the searching for entity class files in the system data set to be analyzed includes:

Obtain a class file whose type is an entity class according to a preset mark in the class file in the data set of the system to be analyzed;

Collecting the class files whose type is entity class to obtain a plurality of entity class files.

The preset mark is a method mark used by the system developer to distinguish various class files when constructing the class file. For example, if a class file is an entity class, add "Entity" at the end of the name when naming, If the class file is a service class, add "Service" at the end of the name when naming.

Preferably, the data model diagram described in the embodiment of the present application may be an E-R diagram (Entity Relationship Diagram). Diagram, entity-relationship diagram), used to describe information requirements or types of information to be stored in the database, the data model diagram includes entities, attributes of entities and associations between entities.

In detail, the building a data model diagram according to the entity class file includes:

Determine the entity in the data model diagram according to the class name of the entity class file;

Determine the attribute of the corresponding entity in the data model diagram according to the member variable contained in the entity class file;

An association relationship is added to each entity in the data model diagram according to the annotation in the entity class file.

Wherein, the member variable is an attribute of the class file, which is defined in the class file and can be accessed in the whole class file. The annotation is a code-level description, which is declared in a class file and used to describe or annotate the class file, and the association between the class file and other class files can be obtained according to the annotation.

Preferably, in the actual business system development, various data are generally stored in the database in the form of data tables, and each data table and its attributes and the relationship between the data tables represent the data structure in the actual business system. In the application embodiment, the data table in the database and the entity class in the system have a one-to-one correspondence. Therefore, the data model diagram in the embodiment of the application can completely reflect the data structure relationship, and can also reflect the relationship between each entity class. relationship between them.

S4. Obtain the updated system data set, and compare it with the to-be-analyzed system data set to obtain a system file difference table.

In detail, after the development of a business system is completed, post-maintenance or function optimization needs to be performed. Therefore, the business system also needs to be updated. The update system data set described in the embodiment of the present application is a complete set of source codes after the business system is updated.

In detail, the S4 includes:

Get the update system dataset;

Dividing the update system data set according to type to obtain multiple subsystem data sets;

Traverse each of the subsystem data sets, adopt a preset comparison algorithm corresponding to the type according to the type of the subsystem data set, and compare each file in each of the subsystem data sets with those in the to-be-analyzed data set. Compare the files in the system data set with the same file name, and identify the modified part of the file in each of the subsystem data sets;

The modified part is identified in the subsystem data set, and the modified part is saved in a file difference table.

The types are classified according to the functions of each file, such as entity classes, service classes, tool classes, and configuration classes. The file types are different, and the data forms of the files are also different, so different comparison algorithms need to be used to compare the files in the update system data set. The preset comparison algorithms include feature vector comparison method, semantic analysis comparison method and similarity comparison method algorithm etc.

Further, comparing each file in each of the subsystem data sets with a file whose name is consistent with the file in the system data set to be analyzed includes:

Determine the type of the subsystem data set;

When the type of the subsystem data set is an entity class, obtain data of each file in the subsystem data set line by line, obtain comparison data, and obtain the file name consistent with the file name in the system data set to be analyzed. The data of the file, get the original data;

A similarity comparison algorithm is used to calculate the similarity between the comparison data and the original data, and when the similarity is lower than a preset threshold, the comparison data is marked. Wherein, the similarity comparison algorithm uses continuous strings as unit blocks, the larger the same unit blocks, the more similar they are, and the smaller and less similar unit blocks of different parts are, and the similarity value is calculated based on this algorithm. .

The file difference table can clearly display the content of each change, which is convenient for users to accurately assess the impact of each change on the business logic of the system, reduce the risks brought by unknown changes, ensure the stability of the system, and improve the security quality of the system.

S5. Display the system content corresponding to the system data set to be analyzed according to the interface calling relationship diagram, the data model diagram, and the system file difference table.

In detail, in the embodiment of the present application, the obtained interface call relationship diagram, data model diagram and file difference table are combined, and the obtained multiple diagrams are used as visualization schemes to display the system content corresponding to the system data set to be analyzed. The interface calling relationship diagram, the data model diagram and the file difference table in the visualization scheme are constructed according to the data set of the system to be analyzed, and can display the corresponding data sets of the system to be analyzed in a clear and intuitive way. System content, so that users do not need to face complex and large-scale code data. The visualization scheme is concise and easy to understand, which is convenient for further processing of the system in the follow-up, and improves the work efficiency.

Further, the user can view the modified file in the system through the file difference table, and can view the position and function of the modified file in the entire system in the interface call relationship diagram according to the modified file name, and can view the modified file through the data model diagram. The data structure of the file, and whether the modified file has an impact on other files after modification.

The visualization solution described in the embodiment of the present application shows, in the form of a chart, each module included in the complex system code package and the internal calling relationship, and also shows the overall data structure of the system and the changes of the system. Users, such as developers or maintainers, can quickly understand the basic situation of the business system by browsing the visualization solution, which is convenient for the user to maintain or optimize the business system in the future.

The embodiment of the present application presents the module division of the system and the logical calling relationship of internal codes by constructing an interface call relationship diagram; by constructing a data model diagram, it reflects the data structure relationship in the system and the association relationship between various entity classes in the system; The system file difference table clearly shows the content of each change in the system; it is displayed in the form of an interface call relationship diagram, a data model diagram and a system file difference table, which can comprehensively and intuitively display the system content, which is convenient for subsequent system changes. for maintenance or updates. Therefore, the system analysis visualization method, device and computer-readable storage medium proposed in this application can achieve the purpose of realizing more comprehensive and clear system analysis visualization.

As shown in FIG. 2 , it is a schematic diagram of a module of the system analysis and visualization device of the present application.

The system analysis and visualization apparatus 100 described in this application can be installed in an electronic device. According to the realized functions, the system analysis and visualization apparatus may include a data acquisition module 101 , an interface relationship call graph module 102 , a data model graph module 103 , a file difference table module 104 and a presentation output module 105 . The modules described in the present invention can also be called units, which refer to a series of computer program segments that can be executed by the electronic device processor and can perform fixed functions, and are stored in the memory of the electronic device.

In this embodiment, the functions of each module/unit are as follows:

The data acquisition module 101 is used to acquire the system data set to be analyzed.

The interface relation call graph module 102 is configured to construct an interface call relation graph according to the reference relation existing in the to-be-analyzed system data set.

In the embodiment of the present application, the interface calling relationship diagram is a tree diagram, and objects are organized in a parent-child hierarchical structure. The interface call relationship diagram includes a plurality of root nodes and sub-nodes. The interface call relationship diagram can display the distribution of modules in the system data set to be analyzed and the call relationship between each class file, and can also display the corresponding Detailed functions of the business system.

In detail, the interface relationship call graph module 102 is specifically used for:

Traverse the class files in the system data set to be analyzed;

Extract the header data of the currently traversed class file;

The data model diagram module 103 is configured to search for entity class files in the data set of the system to be analyzed, and construct a data model diagram according to the entity class files.

The types of class files in the system data set to be analyzed described in the embodiments of the present application include various types, such as entity classes, service classes, tool classes, and configuration classes. The entity class is data describing objective things in the real world, which can refer to people, such as teachers, students, etc., or objects, such as books, warehouses, and the like.

In detail, when searching for the entity class file in the data set of the system to be analyzed, the data model diagram module 103 specifically performs the following operations:

Wherein, the preset mark is a method mark used by system developers to distinguish various class files when building a class file. For example, if a class file is an entity class, add "Entity" at the end of the name when naming, If the class file is a service class, add "Service" at the end of the name when naming.

Preferably, the data model diagram described in the embodiment of the present application may be an E-R diagram (Entity Relationship Diagram, entity-relationship diagram), used to describe the information requirements or the type of information to be stored in the database, the data model diagram includes entities, attributes of entities and associations between entities.

In detail, when constructing a data model diagram according to the entity class file, the data model diagram module 103 specifically performs the following operations:

The file difference table module 104 is configured to acquire and update the system data set, and compare it with the system data set to be analyzed to obtain a system file difference table.

In detail, the file difference table module 104 is specifically used for:

Get the update system dataset;

The types are classified according to the functions of each file, such as entity classes, service classes, tool classes, and configuration classes. The file types are different, and the data forms of the files are also different. Therefore, different comparison algorithms need to be used to compare the files in the update system data set. The preset comparison algorithms include feature vector comparison methods, semantic analysis comparison methods, and similarity comparison methods. algorithm etc.

Determine the type of the subsystem data set;

The display output module 105 is configured to display the system content corresponding to the system data set to be analyzed according to the interface call relationship diagram, the data model diagram and the system file difference table.

In detail, in the embodiment of the present application, the obtained interface calling relationship diagram, data model diagram and file difference table are combined, and the obtained multiple diagrams are used as visualization schemes to display the system content corresponding to the system data set to be analyzed. The interface calling relationship diagram, the data model diagram and the file difference table in the visualization scheme are constructed according to the data set of the system to be analyzed, and can display the corresponding data sets of the system to be analyzed in a clear and intuitive way. System content, so that users do not need to face complex and large-scale code data. The visualization scheme is concise and easy to understand, which is convenient for further processing of the system in the follow-up, and improves the work efficiency.

As shown in FIG. 3 , it is a schematic structural diagram of an electronic device implementing the system analysis and visualization method of the present application.

The electronic device 1 may include a processor 10, a memory 11 and a bus, and may also include a computer program stored in the memory 11 and executable on the processor 10, such as a system analysis visualization program 12.

Wherein, the memory 11 includes at least one type of readable storage medium, and the readable storage medium includes flash memory, mobile hard disk, multimedia card, card-type memory (for example: SD or DX memory, etc.), magnetic memory, magnetic disk, CD etc. The memory 11 may be an internal storage unit of the electronic device 1 in some embodiments, such as a mobile hard disk of the electronic device 1 . In other embodiments, the memory 11 may also be an external storage device of the electronic device 1, such as a pluggable mobile hard disk, a smart memory card (Smart Media Card, SMC), a secure digital Digital, SD) card, flash memory card (Flash Card), etc. Further, the memory 11 may also include both an internal storage unit of the electronic device 1 and an external storage device. The memory 11 can not only be used to store application software installed in the electronic device 1 and various types of data, such as the code of the system analysis visualization program 12, etc., but also can be used to temporarily store data that has been output or will be output.

In some embodiments, the processor 10 may be composed of integrated circuits, for example, may be composed of a single packaged integrated circuit, or may be composed of multiple integrated circuits packaged with the same function or different functions, including one or more integrated circuits. Central Processing Unit (CPU), microprocessor, digital processing chip, graphics processor and combination of various control chips, etc. The processor 10 is the control core (Control Core) of the electronic device. Unit), using various interfaces and lines to connect various components of the entire electronic device, by running or executing programs or modules stored in the memory 11 (for example, executing a system analysis visualization program, etc.), and calling the memory 11 to perform various functions of the electronic device 1 and process data.

The bus may be a peripheral component interconnect (PCI for short) bus or an extended industry standard structure (extended). industry standard architecture, referred to as EISA) bus, etc. The bus can be divided into address bus, data bus, control bus and so on. The bus is configured to implement connection communication between the memory 11 and at least one processor 10 and the like.

FIG. 3 only shows an electronic device with components. Those skilled in the art can understand that the structure shown in FIG. 3 does not constitute a limitation on the electronic device 1, and may include fewer or more components than those shown in the figure. components, or a combination of certain components, or a different arrangement of components.

For example, although not shown, the electronic device 1 may also include a power source (such as a battery) for powering the various components, preferably, the power source may be logically connected to the at least one processor 10 through a power management device, so that the power source can be managed by the power source. The device implements functions such as charge management, discharge management, and power consumption management. The power source may also include one or more DC or AC power sources, recharging devices, power failure detection circuits, power converters or inverters, power status indicators, and any other components. The electronic device 1 may further include various sensors, Bluetooth modules, Wi-Fi modules, etc., which will not be repeated here.

Further, the electronic device 1 may also include a network interface, optionally, the network interface may include a wired interface and/or a wireless interface (such as a WI-FI interface, a Bluetooth interface, etc.), which is usually used in the electronic device 1 Establish a communication connection with other electronic devices.

Optionally, the electronic device 1 may further include a user interface, and the user interface may be a display (Display), an input unit (such as a keyboard (Keyboard)), optionally, the user interface may also be a standard wired interface or a wireless interface. Optionally, in some embodiments, the display may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, and an OLED (Organic Light-Emitting Diode, Organic Light Emitting Diode) Touch, etc. The display may also be appropriately called a display screen or a display unit, which is used for displaying information processed in the electronic device 1 and for displaying a visualized user interface.

It should be understood that the embodiments are only used for illustration, and are not limited by this structure in the scope of the patent application.

The system analysis visualization program 12 stored in the memory 11 in the electronic device 1 is a combination of multiple instructions, and when running in the processor 10, can realize:

Obtain the data set of the system to be analyzed;

The system content corresponding to the system data set to be analyzed is displayed according to the interface calling relationship diagram, the data model diagram and the system file difference table.

Further, if the modules/units integrated in the electronic device 1 are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium, and the computer-readable storage medium can be stored in a computer-readable storage medium. It is volatile and can also be non-volatile. The computer-readable storage medium may include: any entity or device capable of carrying the computer program code, a recording medium, a U disk, a removable hard disk, a magnetic disk, an optical disk, a computer memory, a read-only memory (ROM, Read-Only Memory) ).

Further, the computer-readable storage medium includes a storage data area and a storage program area, wherein the storage data area stores created data, and the storage program area stores a computer program; wherein, the computer program is processed The following steps are implemented when the device is executed:

Obtain the data set of the system to be analyzed;

In the several embodiments provided in this application, it should be understood that the disclosed apparatus, apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative. For example, the division of the modules is only a logical function division, and there may be other division manners in actual implementation.

The modules described as separate components may or may not be physically separated, and components shown as modules may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional module in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The above-mentioned integrated units can be implemented in the form of hardware, or can be implemented in the form of hardware plus software function modules.

It will be apparent to those skilled in the art that the present application is not limited to the details of the above-described exemplary embodiments, but that the present application can be implemented in other specific forms without departing from the spirit or essential characteristics of the present application.

Accordingly, the embodiments are to be regarded in all respects as illustrative and not restrictive, and the scope of the application is to be defined by the appended claims rather than the foregoing description, which is therefore intended to fall within the scope of the claims. All changes within the meaning and scope of the equivalents of , are included in this application. Any accompanying reference signs in the claims should not be construed as limiting the involved claims.

The blockchain referred to in this application is a new application mode of computer technologies such as distributed data storage, point-to-point transmission, consensus mechanism, and encryption algorithm. Blockchain, essentially a decentralized database, is a series of data blocks associated with cryptographic methods. Each data block contains a batch of network transaction information to verify its Validity of information (anti-counterfeiting) and generation of the next block. The blockchain can include the underlying platform of the blockchain, the platform product service layer, and the application service layer.

Furthermore, it is clear that the word "comprising" does not exclude other units or steps and the singular does not exclude the plural. Several units or means recited in the system claims can also be realized by one unit or means by means of software or hardware. Second-class terms are used to denote names and do not denote any particular order.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application rather than limitations. Although the present application has been described in detail with reference to the preferred embodiments, those of ordinary skill in the art should understand that the technical solutions of the present application can be Modifications or equivalent substitutions can be made without departing from the spirit and scope of the technical solutions of the present application.

Claims

A system analysis and visualization method, wherein the method comprises:

Obtain the data set of the system to be analyzed;

Build an interface calling relationship diagram according to the reference relationship existing in the data set of the system to be analyzed;

Find the entity class file in the data set of the system to be analyzed, and build a data model diagram according to the entity class file;

Obtain and update the system data set, and compare it with the system data set to be analyzed to obtain a system file difference table;

According to the interface calling relationship diagram, the data model diagram and the system file difference table, the system content corresponding to the system data set to be analyzed is displayed.
The system analysis and visualization method according to claim 1, wherein the building an interface calling relationship diagram according to the reference relationship between the various classes in the system data set to be analyzed comprises:

Utilize the root class search method to find the root class file in the data set of the system to be analyzed, and use the root class file as the root node;

Find a class file that references the root class file in the system data set to be analyzed, and use the class file of the root class file as a child node of the root node;

Find a class file that references the class file corresponding to the child node in the system data set to be analyzed, and use the class file of the class file corresponding to the child node as the next child node of the child node;

The above steps are repeated until the searched class file is not referenced by other class files, and the interface calling relationship diagram corresponding to the system data set to be analyzed is obtained.
The system analysis and visualization method according to claim 2, wherein, using a root class finding method to find root class files in the system data set to be analyzed, comprising:

Traverse the class files in the system data set to be analyzed;

Extract the header data of the currently traversed class file;

If no other class file is referenced in the header data, the currently traversed class file is determined as the root class file.
The system analysis visualization method according to claim 1, wherein the searching for entity class files in the system data set to be analyzed comprises:

Obtain a class file whose type is an entity class according to a preset mark in the class file in the data set of the system to be analyzed;

Collecting the class files whose type is entity class to obtain a plurality of entity class files.
The system analysis and visualization method according to claim 1, wherein the data model diagram includes entities, attributes of entities, and associations between entities, and the construction of the data model diagram according to the entity class file includes:

Determine the entity in the data model diagram according to the class name of the entity class file;

Determine the attribute of the corresponding entity in the data model diagram according to the member variable contained in the entity class file;

An association relationship is added to each entity in the data model diagram according to the annotation in the entity class file.
The system analysis and visualization method according to claim 1, wherein the acquiring and updating the system data set and comparing with the system data set to be analyzed to obtain a system file difference table, comprising:

Get the update system dataset;

Dividing the update system data set according to type to obtain multiple subsystem data sets;

Traverse each of the subsystem data sets, adopt a preset comparison algorithm corresponding to the type according to the type of the subsystem data set, and compare each file in each of the subsystem data sets with those in the to-be-analyzed data set. Compare the files in the system data set with the same file name, and identify the modified part of the file in each of the subsystem data sets;

The modified part is identified in the subsystem data set, and the modified part is saved in a file difference table.
The system analysis and visualization method according to claim 6, wherein the preset comparison algorithm includes a similarity comparison algorithm, and the comparison between each file in each of the subsystem data sets and the data in the system to be analyzed Focus on the files with the same name as the file, including:

Determine the type of the subsystem data set; when the type of the subsystem data set is an entity class, obtain the data of each file in the subsystem data set line by line, obtain the comparison data, and obtain the data line by line in the Describe the data of the file whose name is consistent with the file name in the data set of the system to be analyzed, and obtain the original data;

A similarity comparison algorithm is used to calculate the similarity between the comparison data and the original data, and when the similarity is lower than a preset threshold, the comparison data is marked.
A system analysis visualization device, wherein the device includes:

The data acquisition module is used to acquire the data set of the system to be analyzed;

an interface relation call graph module, configured to construct an interface call relation graph according to the reference relation existing in the data set of the system to be analyzed;

a data model diagram module, used for finding entity class files in the system data set to be analyzed, and constructing a data model diagram according to the entity class files;

A file difference table module, used to obtain and update the system data set, and compare it with the system data set to be analyzed to obtain a system file difference table;

The display output module is configured to display the system content corresponding to the to-be-analyzed system data set according to the interface call relationship diagram, the data model diagram and the system file difference table.
An electronic device, wherein the electronic device comprises:

at least one processor; and,

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

The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the steps of:

Obtain the data set of the system to be analyzed;

Build an interface calling relationship diagram according to the reference relationship existing in the data set of the system to be analyzed;

Find the entity class file in the data set of the system to be analyzed, and build a data model diagram according to the entity class file;

Obtain and update the system data set, and compare it with the system data set to be analyzed to obtain a system file difference table;

According to the interface calling relationship diagram, the data model diagram and the system file difference table, the system content corresponding to the system data set to be analyzed is displayed.
The electronic device according to claim 9, wherein the building an interface calling relationship graph according to the reference relationship between the various classes in the system data set to be analyzed comprises:

Utilize the root class search method to find the root class file in the system data set to be analyzed, and use the root class file as the root node;

Find a class file that references the root class file in the system data set to be analyzed, and use the class file of the root class file as a child node of the root node;

Find a class file that references the class file corresponding to the child node in the system data set to be analyzed, and use the class file of the class file corresponding to the child node as the next child node of the child node;

The above steps are repeated until the searched class file is not referenced by other class files, and the interface calling relationship diagram corresponding to the system data set to be analyzed is obtained.
The electronic device according to claim 10, wherein the searching for root class files in the data set of the system to be analyzed by using a root class finding method comprises:

Traverse the class files in the system data set to be analyzed;

Extract the header data of the currently traversed class file;

If no other class file is referenced in the header data, the currently traversed class file is determined as the root class file.
The electronic device according to claim 9, wherein the searching for entity class files in the system data set to be analyzed comprises:

Obtain a class file whose type is an entity class according to a preset mark in the class file in the data set of the system to be analyzed;

Collecting the class files whose type is entity class to obtain a plurality of entity class files.
The electronic device according to claim 9, wherein the data model diagram includes entities, attributes of entities, and associations between entities, and the construction of the data model diagram according to the entity class file includes:

Determine the entity in the data model diagram according to the class name of the entity class file;

Determine the attribute of the corresponding entity in the data model diagram according to the member variable contained in the entity class file;

An association relationship is added to each entity in the data model diagram according to the annotation in the entity class file.
The electronic device according to claim 9, wherein the acquiring and updating the system data set is compared with the system data set to be analyzed to obtain a system file difference table, comprising:

Get the update system dataset;

Dividing the update system data set according to type to obtain multiple subsystem data sets;

Traverse each of the subsystem data sets, adopt a preset comparison algorithm corresponding to the type according to the type of the subsystem data set, and compare each file in each of the subsystem data sets with those in the to-be-analyzed data set. Compare the files in the system data set with the same file name, and identify the modified part of the file in each of the subsystem data sets;

The modified part is identified in the subsystem data set, and the modified part is saved in a file difference table.
The electronic device according to claim 14, wherein the preset comparison algorithm includes a similarity comparison algorithm, and the comparison between each file in each of the subsystem data sets and the data set of the system to be analyzed with the The files with the same file name are compared, including:

Determine the type of the subsystem data set; when the type of the subsystem data set is an entity class, obtain the data of each file in the subsystem data set line by line, obtain the comparison data, and obtain the data line by line in the Describe the data of the file whose name is consistent with the file name in the data set of the system to be analyzed, and obtain the original data;

A similarity comparison algorithm is used to calculate the similarity between the comparison data and the original data, and when the similarity is lower than a preset threshold, the comparison data is marked.
A computer-readable storage medium, comprising a storage data area and a storage program area, wherein the storage data area stores created data, and the storage program area stores a computer program; wherein, when the computer program is executed by a processor Implement the following steps:

Obtain the data set of the system to be analyzed;

Build an interface calling relationship diagram according to the reference relationship existing in the data set of the system to be analyzed;

Find the entity class file in the data set of the system to be analyzed, and build a data model diagram according to the entity class file;

Obtain and update the system data set, and compare it with the system data set to be analyzed to obtain a system file difference table;

The system content corresponding to the system data set to be analyzed is displayed according to the interface calling relationship diagram, the data model diagram, and the system file difference table.
The computer-readable storage medium according to claim 16, wherein the building an interface calling relationship graph according to the reference relationship between the various classes in the system data set to be analyzed comprises:

Utilize the root class search method to find the root class file in the system data set to be analyzed, and use the root class file as the root node;

Find a class file that references the root class file in the system data set to be analyzed, and use the class file of the root class file as a child node of the root node;

Find a class file that references the class file corresponding to the child node in the system data set to be analyzed, and use the class file of the class file corresponding to the child node as the next child node of the child node;

The above steps are repeated until the searched class file is not referenced by other class files, and the interface calling relationship diagram corresponding to the system data set to be analyzed is obtained.
The computer-readable storage medium of claim 17, wherein the searching for root class files in the system data set to be analyzed by using a root class finding method comprises:

Traverse the class files in the system data set to be analyzed;

Extract the header data of the currently traversed class file;

If no other class file is referenced in the header data, the currently traversed class file is determined as the root class file.
The computer-readable storage medium of claim 16, wherein the searching for entity class files in the system data set to be analyzed comprises:

Obtain a class file whose type is an entity class according to a preset mark in the class file in the data set of the system to be analyzed;

Collecting the class files whose type is entity class to obtain a plurality of entity class files.
The computer-readable storage medium of claim 16, wherein the data model diagram includes entities, attributes of entities, and associations between entities, and the constructing the data model diagram according to the entity class file includes:

Determine the entity in the data model diagram according to the class name of the entity class file;

Determine the attribute of the corresponding entity in the data model diagram according to the member variable contained in the entity class file;

An association relationship is added to each entity in the data model diagram according to the annotation in the entity class file.