Proposed decomposition of the driver software

The driver software for the MCB will be divided into upper and lower parts. The bottom half driver will be tied closely to the hardware, and will need to be re-written if the software is moved to another machine or operating system. The upper half driver should be written in a device independent manner, so that it can stay the same even if the hardware or operating system changes underneath. There will be a library of access functions to allow client programs to deal with the hardware in an abstract manner. These three sections of code as shown in figure 1 are called the SIB Driver, the MCB Software, and the SIB Interface Library, respectively.

  

Figure 1: GBT MCB Software Architecture

1#1