Device driver synthesis and verification

<p><a href="/facts/Device_driver/rDYnHU1G">Device drivers</a> are programs which allow <a href="/facts/Software/RP79lVSW">software</a> or higher-level <a href="/facts/Computer_program/e38jH9N9">computer programs</a> to interact with a <a href="/facts/Computer_hardware/8jSjsCNv">hardware</a> device. These software components act as a link between the devices and the <a href="/facts/Operating_system/8XTuvMh2">operating systems</a>, communicating with each of these systems and executing commands. They provide an <a href="/facts/Abstraction_layer/EV8c84SY">abstraction layer</a> for the software above and also mediate the communication between the operating system kernel and the devices below. 
</p><p>Usually the operating systems comes with a support for the common device drivers and usually the hardware vendors provide the device driver for their hardware devices for most platforms. The aggressive scaling of the hardware devices and the complex software components has made the device driver development process cumbersome and complex. When the size and <a href="/facts/Function_(engineering)/kUQFAh2o">functionality</a> of the drivers started increasing the <a href="/facts/Device_driver/rDYnHU1G">device drivers</a> became a key factor in defining the <a href="/facts/Reliability_(engineering)/cd6AS5w3">reliability</a> of the system. This has created an incentive towards automatic synthesis and <a href="/facts/Software_verification/PczD7lsh">verification</a> of device drivers. This article sheds some light into some approaches in synthesis and verification of device drivers.
</p>

Device driver synthesis and verification open-in-new

Device driver synthesis and verification