Software visualization method for object-oriented programming language source code

Abstract

The invention relates to a software visualization method for an object-oriented programming language source code, belonging to the technical field of software visualization. The method comprises the following steps of: (1) extracting key information from the source code; (2) acquiring data information of an original graph; (3) acquiring data information of a directed graph; (4) designing a graph layout; and (5) performing visualization mapping. With the adoption of the novel software visualization method for the object-oriented programming language source code provided by the invention, the defect of a class graph for the soft visualization is made up, and the internal structure of software and the status and the effect of types in the software can be accurately and intuitively reflected, so that a user can rapidly understand a software design level.

Description

technical field [0001] The invention relates to a software visualization method for object-oriented programming language (Object-Oriented Programming Language, OOPL) source code, belonging to the technical field of software visualization. Background technique [0002] Based on the program source code to obtain the high-level design abstraction method of the software, the most primitive and direct solution is that the programmer reads the source code, after a series of mental analysis, and finally uses some highly abstract graphics or text expressions to explain the internals of a software structure and implementation logic. [0003] Software visualization usually uses software automation to summarize various attributes (including keywords, inter-class relationships, etc.) The internal structure of the system, the evolution information of the software, and the behavioral characteristics of the software realize the automatic analysis and abstraction of the source code, and ge...

AI Technical Summary

Problems solved by technology

[0010] ①Because the class diagram is mainly used in the forward development, when it is applied in the reverse process such as software source code visualization, it is difficult to express some semantically related relationships in the class diagram correctly;

[0011] ②In some existing automated testing software or some IDE integrated development tools, the implementation from source code to class diagram is provided, but the class diagram obtained from it is often composed of multiple connected subgraphs, and the layout of the class diagram There is a lot of randomness, so the expression is not concise, clear, and not unified, which is not conducive to users' quick understanding of the structural system of the software

[0012] ③The class diagram can only represent certain specific relationships between classes in the software system, and the representation of the software system structure is also reflected through these relationships, so when representing the system structure, it is also limited to the level of classes and class relationships. The description of the role and role played by a concrete class in the system also has the same limitations.

[0013] So class diagrams are not suitable for software visualization

Images