There is generally an implicit assumption at this stage
that there need only be one transformation written fromUMLto Java, say, and allDSM
languages could use that same transformation. Had that been true, then UML would
have provided what its hype implied: full applications from models.
Unfortunately, the model to code transformations for two different languages,
even closely-related object-oriented languages, are rarely so similar that they could
be considered the same transformation with just a few differences in syntax. Give
the same problem description to a Java programmer and a C++ programmer, and the
resulting programs will be distinctly different. Good programmers will take
advantage of the features of the language??”and have to work around its foibles
and shortcomings. Automatic translation between object-oriented languages is a nice
pipe dream, but not a practical approach; the same is true for universal intermediate
formats.
11.5 PROCESS
Although Chapter 13 will discuss how generator creation ?¬?ts into the overall DSM
de?¬?nition process, it seems useful here to examine a fewdetails and pass on some tips.
You can view Chapter 13 as the strategy or game plan for the whole DSM solution
team, while this section looks at tactics and instructions for the generator builder.
11.5.1 Creating and Testing Generators
As we mentioned at the start of this chapter, an important part of the process of
creating a generator is knowing when to start.
Pages:
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569