Cross-project defect influence analysis method based on program dependency relationship and symbolic analysis

Abstract

The invention provides a cross-project defect influence analysis method based on a program dependency relationship and symbolic analysis. The cross-project defect influence analysis method comprises the following steps: 1) acquiring program source codes of different projects and multiple versions in the same software ecosystem; 2) extracting a calling relationship from a program source code of each project basic version, and constructing an ecosystem basic dependence network; 3) obtaining code changes from program source codes of other versions of each project, and constructing a version-sensitive ecosystem dependent network; 4) for a given cross-project defect, under the condition that an upstream error method of the cross-project defect is known, selecting a candidate downstream module;5) for each candidate downstream module, carrying out code preprocessing; 6) performing symbol coding on each preprocessed candidate downstream module; and 7) carrying out constraint solving on each downstream module after symbol coding, and if a solution exists, prompting a developer that the module is possibly influenced by a given cross-project defect. According to the method, the problems thatat present, cross-project defect influence analysis is lacked, and a downstream project affected module cannot be prompted are solved, so that the design of a cross-project defect repair scheme is guided, the quality of defect repair patches is improved, and healthy development of a software ecosystem can be better controlled and managed.

Description

technical field [0001] The invention belongs to the field of computer technology, especially the field of software maintenance. The invention provides a software ecosystem-oriented cross-project defect impact analysis method based on program dependencies and symbol analysis, which is used in the process of repairing cross-project defects to evaluate the severity of defects, set repair priorities and design defect repair Scenarios provide auxiliary information. Background technique [0002] Software ecosystem usually refers to "a collection of software products with a certain degree of symbiotic relationship". In the software ecosystem, different projects are related in code through dependencies, among which the projects that provide functions or services are called upstream projects, and the users are called downstream projects. Upstream and downstream projects are relative, and a project will play different roles in the software ecosystem. For example, in the Python scie...

AI Technical Summary

Problems solved by technology

The present invention aims to solve the existing problems such as lack of impact analysis for cross-project defects, failure to prompt the affected modules of downstream projects, etc., and then guide the repair plan design of cross-project defects, improve the quality of defect repair patches, so as to better control and Managing the Health of the Software Ecosystem

Images