Dynamic Component Safety Analysis: A Regression Based Code Coverage Approach

In dynamic software updates there exists a different level of possible behavior change. The easiest way of transforming an application is to modify the implementation of a whole method body, i.e., updating the method body to a new version without disturbing the overall application. A next step regarding arbitrary updates is the ability to change the signature of a method, along with the internals of a method signature of a method also gets changed, i.e., includes the number of parameters and types of parameters, the return type of the method name get changed. The final step regarding random changes and fully dynamically updateable systems is the support for changing global fields and fields inside of structures, global fields suppose in the case of classbased systems, the fields of objects as defined by their respective classes. In this proposal a semi-automated runtime analysis version consistency is proposed to evaluate the impact of the dynamic software updates.