Application Architecture. Architectural rules will be enforced automatically at
the design stage. This is unlike in manual practices where individual developers
can make different choices and implement the software without following the
planned architecture. For example, in mobile phones, an architectural rule related
to the user interface is that there can only be one menu per form element. In DSM,
this can be directly enforced by simply not allowing the modeler to add more than
QUALITY 29
one menu. Later, this architectural rule doesn??™t need to be tested anymore: all
applications generated from the DSM models will follow it. This greatly eases the
development process and makes it more predictable. Further bene?¬?ts of this are
available in the maintenance phase as we now know how the applications are
implemented.
Coding. With generators many typical errors, like missing references, typos, or
forgotten initialization, simply don??™t exist anymore for application developers. A
generator and supporting domain framework may also prevent the creation of
incorrect or otherwise unwanted applications, like those leading to poor performance
or not following proven practices. Since the generator produces the code similarly for
each case, the maintenance becomes easier: All developers implement the code
similarly and there is no need to inspect and modify code implemented in different
styles.
Pages:
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77