US 10,481,880 B2Granted

Code lineage tool

AssigneeBank of America Corporation

InventorsPrashant Wason, Vijaya Rudraraju

Life of this patent

Estimating the term…

Loading patent…

Abstract

A code lineage tool includes a scanner, a parser, and an integrator. The scanner identifies a plurality of elements in software code. The parser determines that a value of a first element is affected by a second element and a third element. The parser adds the first element to a parse tree and adds the second and third elements to the parse tree as sub-nodes of the first element. The parser determines that a value of the second element is affected by a fourth element and adds the fourth element to the parse tree as a sub-node of the second element. The integrator determines that a change to the fourth element will change the value of the first element and the value of the second element and generates a lineage for the first element.

Claims21

Dependent claims

A code lineage tool comprising:

a scanner configured to identify a plurality of elements in software code by scanning the software code;
a hardware processor configured to implement:
a parser configured to:
determine, based on a stored grammar file, that a first element of the plurality of elements is a function whose value is affected by a second element of the plurality of elements and a third element of the plurality of elements;
determine, based on the grammar file, that the second and third elements are variables and are used when calling the first element;
add the first element to a parse tree;
add the second and third elements to the parse tree as sub-nodes of the first element in response to the determination that the second and third elements are used when calling the first element;
determine, based on the stored grammar file, that a value of the second element is affected by a fourth element of the plurality of elements;
and
add the fourth element to the parse tree as a sub-node of the second element in response to the determination that the value of the second element is affected by the fourth element;
and
an integrator configured to:
determine that the third element is not needed when calling the first element when the second element is provided to the first element;
determine, based on the parse tree, that a change to the fourth element will change the value of the first element and the value of the second element;
generate a lineage for the first element, the lineage comprising an identification of the first element, the second element, and the fourth element and an indication that the first element is based on the second element and that the second element is based on the fourth element;
exclude the third element from the lineage in response to the determination that the third element is not needed when calling the first element when the second element is provided to the first element;
determine, based on the parse tree, that when a change to a fifth element of the software code occurs, no corresponding change occurs in the first, second, and third elements;
exclude the fifth element from the lineage in response to the determination that no corresponding change occurs when the change to the fifth element occurs;
determine, based on the parse tree, that a sixth element of the software code will not execute as a result of a switch statement;
exclude the sixth element from the lineage in response to the determination that the sixth element will not execute;
and
a delivery engine configured to email the lineage for presentation to a user who requested that the software code be scanned.

19 more elements

A method comprising:

identifying a plurality of elements in software code by scanning the software code;
determining, based on a stored grammar file, that a first element of the plurality of elements is a function whose value is affected by a second element of the plurality of elements and a third element of the plurality of elements;
determining, based on the grammar file, that the second and third elements are variables and are used when calling the first element;
adding the first element to a parse tree;
adding the second and third elements to the parse tree as sub-nodes of the first element in response to the determination that the second and third elements are used when calling the first element;
determining, based on the stored grammar file, that a value of the second element is affected by a fourth element of the plurality of elements;
adding the fourth element to the parse tree as a sub-node of the second element in response to the determination that the value of the second element is affected by the fourth element;
determining that the third element is not needed when calling the first element when the second element is provided to the first element;
determining, based on the parse tree, that a change to the fourth element will change the value of the first element and the value of the second element;
generating a lineage for the first element, the lineage comprising an identification of the first element, the second element, and the fourth element and an indication that the first element is based on the second element and that the second element is based on the fourth element;
excluding the third element from the lineage in response to the determination that the third element is not needed when calling the first element when the second element is provided to the first element;
determining, based on the parse tree, that when a change to a fifth element of the software code occurs, no corresponding change occurs in the first, second, and third elements;
excluding the fifth element from the lineage in response to the determination that no corresponding change occurs when the change to the fifth element occurs;
determining, based on the parse tree, that a sixth element of the software code will not execute as a result of a switch statement;
excluding the sixth element from the lineage in response to the determination that the sixth element will not execute;
and
emailing the lineage for presentation to a user who requested that the software code be scanned.

14 more elements

A system comprising:

a database configured to store software code;
and
a code lineage tool comprising a hardware processor configured to:
identify a plurality of elements in the software code by scanning the software code;
determine, based on a stored grammar file, that a first element of the plurality of elements is a function whose value is affected by a second element of the plurality of elements and a third element of the plurality of elements;
determine, based on the grammar file, that the second and third elements are variables and are used when calling the first element;
add the first element to a parse tree;
add the second and third elements to the parse tree as sub-nodes of the first element in response to the determination that the second and third elements are used when calling the first element;
determine, based on the stored grammar file, that a value of the second element is affected by a fourth element of the plurality of elements;
add the fourth element to the parse tree as a sub-node of the second element in response to the determination that the value of the second element is affected by the fourth element;
determine that the third element is not needed when calling the first element when the second element is provided to the first element;
determine, based on the parse tree, that a change to the fourth element will change the value of the first element and the value of the second element;
generate a lineage for the first element, the lineage comprising an identification of the first element, the second element, and the fourth element and an indication that the first element is based on the second element and that the second element is based on the fourth element;
exclude the third element from the lineage in response to the determination that the third element is not needed when calling the first element when the second element is provided to the first element;
determine, based on the parse tree, that when a change to a fifth element of the software code occurs, no corresponding change occurs in the first, second, and third elements;
exclude the fifth element from the lineage in response to the determination that no corresponding change occurs when the change to the fifth element occurs;
determine, based on the parse tree, that a sixth element of the software code will not execute as a result of a switch statement;
exclude the sixth element from the lineage in response to the determination that the sixth element will not execute;
and
email the lineage for presentation to a user who requested that the software code be scanned.

17 more elements

Dependencies are inferred from the claim text.

Facts

Application: 15/646,448Filed 11 Jul 2017
Published: US 2019/0018662 A117 Jan 2019
Granted: 19 Nov 2019
Term ends: Not estimatedThe source records don’t support an estimate.

Classification5 codes

G06F 8/427
Syntactic analysis: parsing
G06F 8/75
Software maintenance or management: structural analysis for program understanding
G06F 8/43
Compilation: checking; Contextual analysis
G06F 8/433
Checking; Contextual analysis: dependency analysis; Data or control flow analysis

Family

US 2019/0018662 A1Pre-grant publication · published 17 Jan 2019
US 10,481,880 B2This patent

From the US filing history. Foreign family members aren’t listed.

Timeline

Citations

Open elsewhere

Building an agent or pulling many patents? Use the API or MCP server instead of scraping pages. Get an API key