It can be a traditional programming language, a scripting language, data
de?¬?nitions, or a con?¬?guration ?¬?le.
WHAT IS DSM? 17
1.4.3 DSM Solution Evolves
Changes to the DSM language and generators are more the norm than an exception.
A DSM solution should never be considered ready unless all the applications for
that domain are already known. The DSM solution needs to be changed because
the domain itself and related requirements change over time. Usually this leads to
changes in the modeling language and related generators. If a change occurs only on
the implementation side, like a new version of the programming language to be
generated or using a new library, changes to just the code generators can be
adequate. This keeps the design models untouched and hides implementation details
from developers using DSM.
A DSM solution also needs to be updated because your understanding of a
domain, even if you are an expert in it, will improve while de?¬?ning languages and
generators for it. Even after your language is used, your understanding of your
domain will improve through modeling or from getting feedback from others that
model with the language you de?¬?ned. Partly you will understand the domain better
and partly you will see possible improvements for your language.
1.5 WHEN TO USE DSM?
Languages and tools that are made to solve the particular task that we are working
with always perform better than general-purpose ones.
Pages:
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53