While the bulk of work in an autobuild generator will be in creating and executing
the make?¬?le or build script, we must not forget the surrounding work. First, the
autobuild generator must run the other generators to actually produce the code, before
executing the build: the following sections will cover this. Finally, after a successful
build the autobuild should open the resulting program. If the program is a desktop
application intended to run on the same platform it is developed on, it can simply be
started. If it is targeted for a different platform, it can often be opened in an emulator or
simulator. As these are often slow to start up, it may be worth investigating if the
emulator itself can stay open, with each autobuild simply updating the application in
the emulator. If the generated program does not have a user interface, and hence there
is no point opening it, the ?¬?nal step of autobuild could also usefully be to run
automated tests against the program and display the results.
11.4.2 Generator per Modeling Language
A full DSM solution for a given domain will normally have more than one modeling
language. The kinds of information needed to describe an application will be divided
over a fewmodeling languages. These modeling languages, and the models madewith
them, should exhibit high cohesion and low coupling.
Pages:
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558