This approach is similar to DSM
sinceMOFdescribes the concepts of a language and howmodels of those concepts are
to be stored and interchanged. Although the MOF speci?¬?cation is large, use of it to
model languages describes little about those aspects that are of direct interest to its
user: what models in the language actually look like or how the user interacts with
them. MOF also lacks an explicit language concept and does not support language
integration or n-ary relationships between model elements.
3.3.5 Other Domain-Speci?¬?c Approaches
Developers may also use some readily available DSM solutions. For example, entityrelationship
modeling is a widely known and used technique to design schemas,
especially for relational databases. Although this is a relatively small domain, there
are multiple different languages available. Standardization has not been prioritized
here; the capability of each language to support the speci?¬?c characteristics of a
58 DSM DEFINED
particular database has been seen as more important. The same applies for GUI design
and the design of protocols which can also be characterized as domain-speci?¬?c
solutions. Similarly, tools that come with model-based code generation, like Labview
or Matlab/Simulink, can also be considered as domain-speci?¬?c solutions. The main
difference from DSM is that these are often ?¬?xed so that no users, not even the
experienced developers in a company, can change them.
Pages:
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132