The main dif?¬?culty for people in stepping up to DSM is to
leave the code world behind when building the modeling language. Since the bene?¬?ts
of DSM are largely due to the raise in the level of abstraction in the modeling
language, it is best to avoid the risk of a familiar area such as the framework dragging
the level back down toward the code.
Similarly for the generator: take the time to learn the newmindset required for using
a generator language, rather than trying to take a ???shortcut??? by doing everything in the
familiar language of the framework. After all, the generator language itself is
(hopefully)domain-speci?¬?c, honed for the task of generation. So, do not be in a hurry to
return to the familiar world of code: DSM involves learning some new things, but a
little abstinence fromcoding will whet your appetite for it. At the proper time, building
the framework will more than satisfy that appetite, as you get to use all the skills of your
trade. Best of all, as you update the generator to take advantage of the framework, your
framework will for once have the discerning user you have always longed for.
328 DOMAIN FRAMEWORK
CHAPTER 13
DSM DEFINITION PROCESS
In this chapter, we will look at the process of creating, introducing, and evolving the
whole Domain-Speci?¬?c Modeling (DSM) solution.
Pages:
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617