
Implementation and Testing 367
Once all of the tasks, timers, communications pathways, priority han-
dling, and error detection/ recovery systems have been built and tested,
it is time to start integration and testing of the complete system. While
this may seem like a simple enough task, it is typically one of the most
frustrating to accomplish. Why should this be? All of the components are
complete and working, so it should just be a simple matter of stringing
all the components together to create a whole. Well, yes, the individual
components are complete and tested, but they have not been tested with
one another. It is less a matter of whether ...