WhilecorewatchbehaviorinCwouldhavebeenplatformindependent,theGUIwidgets
and graphics library in C tend to be platform speci?¬?c. Also, the majority of commonly
usedCcompilers and IDEs that users were likely to have are commercial products. The
installationanduseof the freelyavailablecompilers aregenerally suf?¬?cientlydif?¬?cult to
deter someone whose only motive would be to see an example application.
While other languages with freely available compilers and runtime environments
existed, the mainstream choice??”and hence most likely to already exist on users??™
computers??”was Java. The resulting Java applications would also be small enough to
be easily passed to other users, and availability of at least a Java runtime environment
192 DIGITAL WRISTWATCH
on a PC is virtually guaranteed. While Java was not the current language of choice for
embedded development, it was originally developed for such devices and would be
familiar to a large number of users.
9.2 DEVELOPMENT PROCESS
The development of the watch modeling language was carried out by Steven Kelly
and Risto Pohjonen of MetaCase over a couple of weeks. As this was an example
rather than a real-world case, therewas no outside customer: as both developers had
owned digital watches in the 1980s, they felt quali?¬?ed to play the role of domain
expert.
Pages:
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356