Using line-of-code behavior and relation models to anticipate impact of hardware changes

Abstract

Disclosed herein are techniques for analyzing hardware change impacts based on at least one functional line-of-code behavior and relation model. Techniques include identifying a new hardware component associated with a system; accessing a first line-of-code behavior and relation model representing execution of functions using the new hardware component; accessing a second line-of-code behavior and relation model representing execution of functions on a previous hardware component of the system; performing a functional differential comparison of the first line-of-code behavior and relation model to the second line-of-code behavior and relation model; determining, based on the functional differential comparison, a status of functional equivalence between the new hardware component and the previous hardware component; and generating, based on the determined difference, a report identifying the status of functional equivalence.

What is claimed is: 
     
         1 - 20 . (canceled) 
     
     
         21 . A non-transitory computer-readable medium including instructions that, when executed by at least one processor, cause the at least one processor to perform operations for analyzing hardware change impacts based on at least one model, comprising:
 accessing a first model representing first functional behavior of code, wherein the first model:
 was generated based on determining functional effects of a new hardware component not previously part of a system; and 
 comprises a plurality of symbols and relationships between at least some of the plurality of symbols, at least one symbol representing at least one of: a function, a variable, a buffer, a call, an object, a segment of code, a controller, the system, or another system; 
   accessing a second model representing second functional behavior of code and based on a previous hardware component previously in the system, the previous hardware component having been configured to execute within the system without the system having the new hardware component;   performing a functional differential comparison of at least a portion of the first model representing the first functional behavior to at least a portion of the second model representing the second functional behavior; and   determining, based on the functional differential comparison, at least one of:
 whether there is a functional difference between the previous hardware component and the new hardware component; or 
 an instance of functionality drift. 
   
     
     
         22 . The non-transitory computer-readable medium of  claim 21 , wherein the functional differential comparison is performed at a device separate from the system. 
     
     
         23 . The non-transitory computer-readable medium of  claim 21 , wherein the previous hardware component and the new hardware component are controllers. 
     
     
         24 . The non-transitory computer-readable medium of  claim 21 , wherein at least one of the first functional behavior or the second functional behavior includes execution of functions in the system. 
     
     
         25 . The non-transitory computer-readable medium of  claim 21 , wherein:
 a first portion of the first model is associated with the new hardware component; and   a second portion of the second model is associated with the previous hardware component.   
     
     
         26 . The non-transitory computer-readable medium of  claim 21 , the operations further comprising determining, based on the functional differential comparison, a degree of functional equivalence between the previous hardware component and the new hardware component. 
     
     
         27 . The non-transitory computer-readable medium of  claim 26 , the operations further comprising determining whether the degree of functional equivalence meets a threshold. 
     
     
         28 . The non-transitory computer-readable medium of  claim 21 , the operations further comprising determining, based on the functional differential comparison, that the new hardware component is unauthorized. 
     
     
         29 . The non-transitory computer-readable medium of  claim 28 , the operations further comprising blocking operation of the new hardware component based on the determination that the new hardware component is unauthorized. 
     
     
         30 . The non-transitory computer-readable medium of  claim 21 , wherein:
 the new hardware component includes a first controller;   the previous hardware component includes a second controller; and   the system includes at least one third controller.   
     
     
         31 . The non-transitory computer-readable medium of  claim 21 , wherein the operations are initiated in response to determining that the new hardware component is operating in the system or attempting to operate in the system. 
     
     
         32 . A computer-implemented method for analyzing hardware change impacts based on at least one model, the method comprising:
 accessing a first model representing first functional behavior of code, wherein the first model:
 was generated based on determining functional effects of a new hardware component not previously part of a system; and 
 comprises a plurality of symbols and relationships between at least some of the plurality of symbols, at least one symbol representing at least one of: a function, a variable, a buffer, a call, an object, a segment of code, a controller, the system, or another system; 
   accessing a second model representing second functional behavior of code and based on a previous hardware component previously in the system, the previous hardware component having been configured to execute within the system without the system having the new hardware component;   performing a functional differential comparison of at least a portion of the first model representing the first functional behavior to at least a portion of the second model representing the second functional behavior; and   determining, based on the functional differential comparison, at least one of:
 whether there is a functional difference between the previous hardware component and the new hardware component; or 
 an instance of functionality drift. 
   
     
     
         33 . The method of  claim 32 , wherein the functional differential comparison is performed at a device separate from the system. 
     
     
         34 . The method of  claim 32 , wherein the previous hardware component and the new hardware component are controllers. 
     
     
         35 . The method of  claim 32 , wherein at least one of the first functional behavior or the second functional behavior includes execution of functions in the system. 
     
     
         36 . The method of  claim 32 , wherein:
 a first portion of the first model is associated with the new hardware component; and   a second portion of the second model is associated with the previous hardware component.   
     
     
         37 . The method of  claim 32 , further comprising determining, based on the functional differential comparison, a degree of functional equivalence between the previous hardware component and the new hardware component. 
     
     
         38 . The method of  claim 37 , further comprising determining whether the degree of functional equivalence meets a threshold. 
     
     
         39 . The method of  claim 32 , wherein:
 the new hardware component includes a first controller;   the previous hardware component includes a second controller; and   the system includes at least one third controller.   
     
     
         40 . The method of  claim 32 , wherein the method is initiated in response to determining that the new hardware component is operating in the system or attempting to operate in the system.