This distinguishes this from the other example cases, where the authors did
not have suf?¬?cient domain knowledge at the start of the project to create the
language on their own. This case thus brings the authors??™ positions closer to those of
readers thinking about their own application domains, and gives us a good
opportunity to examine the thought processes of a domain expert. As will be seen,
creating a DSM language is largely a question of determining what facts need to be
recorded about each application in that domain, and where in the modeling language
to store these facts.
The total time spent was approximately 10 man-days, including the modeling
language, a full set of models, the generator, and the domain framework. Since this
was the ?¬?rst Java project for either developer, the time also included learning the
language, its libraries, and development environment. Over the subsequent years, a
few more days have been spent on upgrading the framework and generator to work on
other desktop platforms, cope with later Java versions, produce watches that run on
mobile phones, and add support for model-level tracing of a running watch
application. None of these changes has required changing the models, and the result
has always been fully running applications, identical in behavior but with
environment-related differences in appearance and sometimes in code.
Pages:
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357