Embedded Systems Design - June 2008 - (Page 42)

feature the changes in the code. Figure 4 shows uncovered until late in the development to move in any direction the team that the variable is now visible in the needs to go. cycle resulting in product delays. model and the operation name changed. For example, Figure 3 shows a snipA bidirectional IDE/MDD frameThe code and the documentation in pet of code for a temperature sensor and work offers developers the beneﬁt of the model remain in synch. It’s impora representation of the code in an MDD automatic documentation, keeping the tant to note that making changes such as environment. We may want to perform design and the code in synch with these get reﬂected in all references to the some refactoring in the code, renaming DMCA. Reducing the learning curve effected element within the model, in the data variable to clarify the purpose and increasing effectiveness by working other words, all diaat either the code or model grams that show the atlevel makes a bidirectional Keeping both the model and code tribute are updated to workﬂow possible by enin synch ensures that your documentation reﬂect the change. In a abling the developer to change one view and have all represented in the model accurately reﬂects similar fashion, performing an edit of the the other views change autothe actual implementation. model is also reﬂected matically. Since this happens in code. Keeping both automatically, the developer of the variable like temp for temperature the model and code in synch ensures need not change the way he wishes to work: the workﬂow environment works and change the name of the operation to that your documentation represented in the model accurately reﬂects the actual reﬂect reading the temperature variable. the way he does, at either the model or Once we’re done with the edits from implementation. the code level. As the work environwithin the Eclipse editor and save the ment automatically documents the deWORKING IN A TOTALLY INTEcode, the modeling environment autosign, the code and the documentation GRATED ENVIRONMENT matically detects the change and autoare always up to date, enabling embedBy integrating design (MDD), developded and real-time development projects matically updates the model to reﬂect Bluetooth Writer and Bluetooth Reader working with new code developed for a new application. Figure 2 42 JUNE 2008 | embedded systems design | www.embedded.com http://www.embedded.com

Table of Contents Feed for the Digital Edition of Embedded Systems Design - June 2008

Embedded Systems Design - June 2008 Contents #Include Party Bit Programmer's Toolbox Cover Feature: Virtual Hardware Platforms for Embedded Software Validation Allocating Memory in MATLAB-to-C Code MDD and IDEs: Making the Twain Meet in Embedded Systems Design Avoid a Thrashing Guest Editor Advertising Index Break Points Marketplace

Embedded Systems Design - June 2008

For optimal viewing of this digital publication, please enable JavaScript and then refresh the page. If you would like to try to load the digital publication without using Flash Player detection, please click here.