This is unlike general-purpose
modeling languages where the semantics do not map to a particular problem domain,
but it is left to developers to map the semantics and concepts of a language to a given
problem domain. Research on modeling language use (e.g.,Wijers, 1991) shows that
each developer makes this mapping differently. It is no surprise that modelers using
general-purpose languages create different kinds of models for the same problem.
DSM is different as it aims to rely on concepts and semantics that come directly from
the problem domain.
Use of domain semantics in the language is not limited just to the concepts but also
covers the connections between the modeling constructs as well as related rules.
Following the car infotainment example, a menu in an infotainment system can
usually trigger an action or open a submenu. Accordingly, in the domain-speci?¬?c
language a menu can be connected only to an action or to another menu. The former
could be de?¬?ned with a ???transition??? relationship from a menu to an action and the
latter with a ???submenu??? relationship from a menu to another instance of a menu. To
follow the semantics closely, the modeling language also includes a constraint that
allows only one relationship, either the ???transition??? or the ???submenu,??? to be speci?¬?ed
from each menu.
Pages:
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151