EETimes

Embedded Systems October 2000 Vol13_11

Issue link: http://dc.ee.ubm-us.com/i/71842

Contents of this Issue

Navigation

Page 140 of 181

GREGORY EAKMAN Strategies for Debugging Embedded Systems TIle best time to detect bugs is early in the development process. If you instrument your UML. you can even find them during analysis and design. ntegration and testing of software is difficult, and embedded systems pro- vide the additional challenges of limited manipulation and visibility of the system through a small number of inputs and outputs. Abnormal sys- tem states, in parti culal~ are difficult to test, because the system must be driven in to the state before its behavior in that state can be determined. This article introduces the idea of instrumentation code injected in to the implementation of UML models for the purposes of increasing the control- labiUty, observabili ty, and testability of the system. The instrumentation is used in both the development and the target environments, and allows interactive system debugging at the model level. In batch mode, the instrumentation serves as the basis for data collection, initialization, and test automation. My goals are to: • Provide a brief overview of model-based software engineering and implemen- tation of these models I • Outline approaches fo r integration testing of model-based software • Identify the in teresting run-time data and execution poin ts within modeled systems • Define alternatives for collecting and manipulating mode l data at runtime • Integrate the instrumentatio n with test automation Integration testing According to Roger S. Pressman, in Software Engineering-A Practitioner's Ajlproach, "Integration testing is a systematic technique for constructing the program struc- ture while at the same time conducting tests to uncover the errors associated with Embedded Systems Programming OCTOBER 2000 139

Articles in this issue

Archives of this issue

view archives of EETimes - Embedded Systems October 2000 Vol13_11