In step 1, (on the extreme
left) the following units are linked together to form the DISPLAY STEP:
??? The driver (a piece of software which will be substituted by whichever units eventually call the
system) CALLING DRIVER
??? Three other stubs: STORE stub, LHCK MONITOR stub, and KEY ENTRY HANDLER stub
??? The ADA run-time-system (ADA RTS)
??? The 6 units which together comprise the DISPLAY: UPDATE_LOWER, UPDATE_UPPER
INT_LOWER, INT_UPPER, UPDATE_MESSAGE, and UPDATE_FAILED
The features represented by the Display can now be integration tested. In step 2, the following units are
linked together to form the STORE and KEY ENTRY HANDLER STEP:
??? The driver CALLING DRIVER
??? Integrated DISPLAY
??? Two other stubs; LHCK MONITOR STUB and KEY ENTRY HANDLER STUB, and the ADA
run-time-system (ADA RTS)
??? The 6 units which represent the STORE
??? INITIALIZE unit which is the only unit of the KEY ENTRY HANDLER
??? The ADA run-time-system (ADA RTS)
The logic behind the strategy has to do with the need to get the display working first so that users can get
some feedback on their actions. In practice not all of the features can be properly tested since they require
the KEY ENTRY HANDLER as well. However this is added in the next step along with the STORE feature.
The key parts of the raster display are thus integrated and the LHCK MONITOR and KEY BUFFER are
then added before the entire raster display controller is ready to be integrated as a component.
Pages:
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322