It hides
the platform details, and thus insulates the rest of the DSM solution from changes in a
platform. The insulation works equally well whether the change is to a new version of
the same platformor to a new platform altogether. This can also be applied when there
SUMMARY 327
is a desire to support several platforms in parallel: the same modeling language,
models, and generators can be used for all platforms, with just a new version of the
framework being written for each platform. As the size of the framework will almost
always be smaller than theamount of code thatwould be needed for a single application
in that domain without DSM, the cost of supporting an additional platform will be
comparable to the pre-DSM cost of building a single application. Furthermore,
whereas without DSM building a single application on the new platform would offer
precisely one application, with DSM every single application built for the previous
platform will now also be available for the new platform.
While it is good to be aware of such possibilities, the main focus for the domain
framework developer will be elsewhere. As in any framework, the domain framework
should provide the algorithms and functions required in that domain. In addition to
those, the domain framework should focus on matching well with the modeling
language where possible, and on providing a good interface for the generator.
Pages:
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615