Source Code Revision Retrieval from Multiple History Datasets
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
As software development progresses, managing and retrieving revisions from large revision history data sets becomes increasingly time-consuming, hindering the efficiency of problem-solving tasks during code development.
Innovation Solution
A computer-implemented method that extracts and displays specific revision history data, including link information and version information, allowing users to specify function units and version ranges, facilitating the identification of relevant code changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If the revision history data set is large, then the completeness of revision information is improved, but the time required to check the revision history increases
Solution Approach 1:
The patent extracts only the necessary revision history data related to the specific function unit and version range from the large revision history data set. By using the version information and link information to filter and extract relevant revisions, the system reduces the amount of data that needs to be manually checked while maintaining complete information about the targeted function unit's evolution.
Solution Approach 2:
The patent segments the revision history data by function unit and version range, allowing users to check revisions in manageable portions rather than reviewing the entire history at once. This segmentation enables focused examination of specific code changes while maintaining the ability to access complete revision information when needed.
2Measurement precision
If the revision history is examined in detail, then the accuracy of problem identification is improved, but the productivity of problem-solving decreases
Solution Approach 1:
The system extracts and presents only the revision history data relevant to the specified function unit and version range, eliminating unnecessary data that would slow down the problem-solving process. This allows developers to quickly identify problems in the specific code areas of interest without being overwhelmed by irrelevant revision information from other parts of the codebase.
Solution Approach 2:
The patent allows users to pre-specify the function unit and version range before examining revision history, performing a preliminary filter to narrow down the data scope. This preliminary action ensures that only the most relevant revisions are presented, enabling rapid and accurate problem identification without sacrificing productivity.
Data Source
AI summary
Embodiments includes techniques for retrieving revisions in source code from a plurality of revision history data sets including link information to the source code and version information. The revision history data includes a function unit specified by a user is extracted from the plurality of revision history data sets, and a list of the extracted revision history data is displayed on the display device. Also, the display of this list includes displaying on the display device or creating in a storage area source code or information associated with the source code corresponding to at least two different revision history data sets in this first list.