International Business Machines Corporation

Orna Raz-Pelleg

Aviad Zlotnick

Eitan D Farchi

Shmuel Ur

Yarden Nir-Buchbinder

Sergey Novikov

Shachar Fienblit

Dan S Pelleg

Michael E Gildein

Lawrence Carter Blount

Sheli Rahav

Rachel Tzoref

Dalit Tzafrir

Yoram Simha Adler

Richard D Prewitt, Jr

Aharon Brodie

Shay Gammer

Embodiments include method, systems and computer program products for identifying dependency relationships in a software product. Aspects include obtaining change history data for the software product and extracting a plurality of change elements from the change history data, each change element including an identifier of a code segment that was changed and a timestamp of the change. Aspects also include creating a dependency graph based on the plurality of change elements, wherein the dependency graph includes nodes that correspond to the code segments and edges that connect nodes that were both updated in a same logical grouping, calculating a weight for each of the edges based on probability that the nodes connected by the edge will be updated together, and outputting the dependency graph.

Identifying software dependency relationships

A method and apparatus for estimating coverage of a computer program from traces, the method comprising: receiving trace data generated by an execution of an executable unit; and estimating coverage of the executable unit from the trace data, wherein estimating coverage comprises estimating trace coverage.

Trace coverage analysis

Systems and methods for detecting faults in a system. The method comprising maintaining diagnostic history for one or more system components; receiving system information about operational state and relational interaction among system components; determining if one or more system components are to be examined, in response to performing an analysis of the diagnostic history, wherein the analysis is performed to determine if the diagnostic history includes any information that may indicate that certain system components or combinations of components are suspected of causing a problem detected in the system, wherein the diagnostic history is maintained based on an at least one examination performed on said one or more components when said one or more components were installed in a system other than the system in which the problem is detected.

Fault detection based on diagnostic history

A method for software processing includes extracting from software code under test respective items of meta-information pertaining to elements of the software code and receiving respective quality data regarding the elements of software code. The quality data and meta-information are processed in a computer so as to assign respective metrics to the items of the meta-information responsively to the quality data regarding the elements of the software code to which the items pertain. At least some of the meta-information is presented to a user in accordance with the assigned metrics.

Cross-concern code coverage assessment

Detecting locking discipline violations on shared resources. For example, a method of detecting locking discipline violations of shared resources of a computing platform, by a testing process to be executed concurrently with one or more other processes on said computing platform, the testing process comprising: locking a shared resource of said computing platform; reading a value of the shared resource; locally storing the value of the shared resource; rereading the value of the shared resource after a predefined time period; and generating a locking discipline violation report if the value of said shared resource as reread by said rereading is different from the value of said resource as locally stored by said locally storing.

Detecting locking discipline violations on shared resources

A method for software processing includes obtaining change information, which records changes that have been performed in respective locations in software code. The change information is processed so as to assign to at least some of the locations respective priorities, which are indicative of respective likelihoods that the locations contain program faults. The at least some of the locations are presented to a user in accordance with the assigned priorities.

Evaluation of software based on change history

A method for software processing in which software locations are assigned priorities indicative of respective likelihoods that the locations contain program faults, based on review information pertaining to reviews that have been conducted on respective locations in software code. In some methods, a software location is detected to be critical based on the priorities.

Evaluation of software based on review history

A method for evaluating a debugger script, the method includes: (i) receiving a debugger script that includes a first debugger breakpoint that is associated with a certain program line number; and determining a validity of the first debugger breakpoint in response to a comparison between expected content associated with the first debugger breakpoint and between an actual content of at least a portion of a certain program line group that comprises a certain program line identified by the certain program line number.

Device, method and computer program product for evaluating a debugger script

A method for software processing includes accepting quality information, which includes names of elements of software code and respective quality indications regarding tested acceptability of the elements. The names are processed to extract a list of substrings that occur in the names. Respective metrics are assigned to the substrings responsively to the quality indications of the elements in whose names the substrings occur. At least some of the substrings are presented to a user in accordance with the assigned metrics.

Growing community of inventors

Haifa, Israel

Orna Raz-Pelleg