Finally, the build process for compiling and packaging
a MIDP application required a number of extra steps and several new ?¬?les.
In spite of these differences, extending theWatch DSMsolution to support this new
platformwas possible mainly by simply building versions of the AbstractWatchApplet
and WatchCanvas classes for the phone MIDP framework. Only minor changes were
necessary to the code generation, to work in the more restricted MIDP environment.
No changes were necessary to the modeling language or models. Altogether, the
changes took four man-days: 2 for the MIDP framework code, 0.5 for the MIDP
build script, 1 for refactoring existing framework code, and 0.5 for adapting the code
generation.
Later, the generators and framework were further extended to take advantage of
the MetaEdit+ API to provide visual tracing of model execution. As the watch
application ran, it would make WebServices calls back to MetaEdit+ when control
TABLE 9.1 Productivity Improvements of DSM Modeling versus Manual Coding
Modeling Coding
Modeling:Coding
Time (s) Functions/hr Time (s) Functions/hr Productivity Ratio
Senior developer 38 94.7 200 18.0 5.2 : 1
Junior developer 160 22.5 639 5.6 4.0 : 1
Total 117.2 23.6 5.0 : 1
MAIN RESULTS 223
passed to a new state, and MetaEdit+ would highlight that state. Again, these
changes only affected the framework and generators.
Pages:
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407