It would
generally be better to let this second group have access to the models, but this is not a
perfect world.
The need for version control of generated code is thus the exception rather than
the rule. In real world cases, our experience has been that the improved quality and
consistency of generated code largely removes the need to worry about versioning??”
throughout the DSM solution. To a generation who have grown up believing in the
safety net of version control, this may seem hard to believe at ?¬?rst. The fact is
that current version control systems, practices, and requirements have grown out of
the needs of hand-coded programs, and DSM removes many of those problems.
Some parts of a DSM solution will still need to be versioned, but generally not the
generated code.
11.6 SUMMARY
The generator forms the keystone of a DSM solution: it must interface with the
modeling language, models, domain framework, and language to be generated. In
some ways, building the generator is the most challenging task in DSM, since it
requires a strong understanding of all of these areas and also of the generator facilities
offered by the DSM tool. To ameliorate these potential dif?¬?culties, it is important to
remember two things:
. Keep the generator simple: push complexity down into the domain framework.
Pages:
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578