Unless you know the input and output
required for a program, you are unlikely to be successful in building it. It is thus
important to ?¬?rst wait until the modeling language is in an acceptable state. All the
major concepts should be there and you should have made a few example models.
These example models will show that the modeling language works from the point
of view of the modeler, which is the most important factor. You should also make sure
when making the example models that the modeling language allows you to capture
all the information you would need to build the application. In fact, it is suf?¬?cient to
have enough information to be able to build an application corresponding to the
example model: there are always choices involved when hand coding.
Next you need a matching pair of an example model and the corresponding
working code. We looked at this in more detail in Section 11.1: either model an
existing application or write the code for an examplemodel. If you have the existing
framework code, you will of course use that; otherwise, do not worry too much
if you ?¬?nd repeating sections of code. Breaking those out into a domain framework
is the subject of the next chapter; for now it is ?¬?ne to do a little light refactoring as
you go, but also acceptable to have larger pieces of code as boilerplate in the
generators.
Pages:
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570