Perhaps the best known domainspeci
?¬?c modeling languages are those used in database design for specifying data
structures, normalizing them, and generating database schemas. Another well-known
area that uses speci?¬?cations made with a domain-speci?¬?c language and targets code
generation is GUI design.
If we inspect modeling languages that originate from coding, we can see that
most class diagrams fall into this category too. Although there is interaction
between the class instances, they are not usually described in the model. There are,
however, some class diagram versions that also capture method calls among
classes, taking a step into the behavioral side too. Other example languages here are
those producing cluster diagrams, feature diagrams, system diagrams, network
diagrams, component diagrams, process matrices, deployment diagrams, Venn
diagrams, inheritance models, and naturally entity-relationship diagrams with their
numerous dialects.
For DSM, static languages are often easier to specify than behavioral ones. Their
use of code generation is also simpler as they produce static properties of a system
but not howto compute them. Among the cases illustrated in Part III, we included only
one case out of?¬?ve that speci?¬?es pure static structures to generate declarative code. An
example of static modeling can be found from Chapter 6.
Pages:
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155