Method for analyzing software function change and influence thereof by using function diagram

Abstract

The invention discloses a method for analyzing a software function change and the influence thereof by using a function diagram, which comprises the following steps of: analyzing software to be tested, and constructing a software function diagram; analyzing a control change and a code change influence; mapping the control to codes, finding out the software function corresponding to change codes by using the code and interface control mapping method through analyzing source program codes, and converting the code change to a function change; and analyzing the domain of function change influence according to the software function condition influenced by the function change and the code change, and finding out all functions passing by the function change point. In the method, the code dependency relation is described by using a dependency diagram, and the influence on the software by the code change can be accurately reflected; the influence on the software function by the code change and the control change is fully considered, and comprehensive analysis is influenced; and the code change is converted into the function change according to the association relation between the control and the codes, and the analysis result of the change influence is visualized.

Description

technical field [0001] The invention relates to a software testing method, in particular to a method for analyzing software function change and its influence by using a function diagram. Background technique [0002] Software change is an unavoidable and very frequent behavior in the software life cycle. After software change, the original software will be affected to varying degrees. Recognition from the surface is called implicit influence. Software change impact analysis is to determine the explicit and especially implicit impact of these changes on the software, and provide technical support for software testing and maintenance. [0003] Since the 1980s, GUI (Graphical User Interface) technology has been widely used. GUI software not only brings users intuitive and simple, but also has its own graphical input / output, event-driven, event-triggered randomness, Features such as multitasking and message passing make software functions more and more complex. In addition, m...

AI Technical Summary

Problems solved by technology

[0003] Since the 1980s, GUI (Graphical User Interface) technology has been widely used. GUI software not only brings users intuitive and simple, but also has its own graphical input / output, event-driven, event-triggered randomness, Features such as multitasking and message passing make software functions more and more complex

Using these methods, it is possible to find out the domain affected by code changes. However, since software codes and functions are not in a simple correspondence, even if the codes affected by the changes are known, the affected functions cannot be known.

In order to cover the source code affected by the change, testers also need to spend a certain amount of energy reading the code in order to design regression test cases that cover the domain affected by the change, thus affecting the efficiency of regression testing

[0011] Software functions are the essence of software. Users complete specified tasks through the functions provided by the software. Compared with codes, software functions are more intuitive. Therefore, analyzing the impact domain of software changes from the functional level will be more intuitive and convenient. Existing methods It is difficult to effectively solve this problem

Images