Microsoft Technology Licensing, LLC

Rajesh Bangalore Gururaj

Augustus Javier Tertzakian

Sergii Viktorovych Liashenko

A method for objective code branch verification executes code branch annotations to assess developer-specified pass conditions for each code branch that are indicative of whether or not the code branch is functioning as originally intended by the author of the code. The method includes maintaining and dynamically updating both a counter value and a pass indicator status in association with each of multiple annotated code branches defined within a code body during execution of the code body. The counter value for each annotated code branch represents a number of times the annotated code branch has executed within a current run-time environment, and the pass indicator status indicates satisfaction or non-satisfaction of a pass condition identified within the code branch that is determined based on the counter value for the associated code branch.

Executable code branch annotations for objective branch verification

A driver module framework enables the creation and execution of drivers. The modules in a driver compatible with the framework can expose data structures, device driver specific programming patterns, devices, or hardware buses. The modules share a common interface and can include callback functions, public methods, private methods, attributes, a module-specific configuration, and a private context. Driver-specific code in a driver can cause the framework to instantiate the modules and can consume functionality provided by the modules contained therein. The framework can also enforce the use of good programming practices, including preventing the use of improper module dependencies and enforcing data hiding. The framework can also provide callbacks received from an operating system to all of the modules in a driver, which allows modules to be fully self-contained and easily reusable.

Growing community of inventors

Redmond, WA, United States of America

Rajesh Bangalore Gururaj