Reuse. The quality of the created applications can be expected to improve since
reuse can be better enforced across the company (Griss andWentzel, 1994). TheDSM
solution can prevent developers from making designs that reinvent the wheel or
create an alternative implementation of the same functionality. These are
very common in manually written code and their testing and maintenance can be
time consuming and error prone. DSM can enforce reuse by automatically using
design information from available models or refering to an existing library or platform
code.
Validation at the Domain Level. ADSMlanguage may also be designed to support
the validation of desirable properties at the domain level. Validation is usually a lot
simpler at the domain level than verifying code in a general-purpose modeling
language or via a general-purpose programming language. Let??™s consider here a
desirable property of mobile applications: that all selection dialogs must offer the
possibility to cancel.With DSM, this property is built in to the modeling language:
if no explicit cancel navigation is de?¬?ned, the generator provides the default
behavior.
In?¬‚uence of Changes and Refactoring. Studies comparing DSM to manual
practices (for example, Kieburtz et al., 1996) suggest that changes to the speci?¬?cations
are easier to do at the domain-speci?¬?c level than at the code level.
Pages:
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78