Safety of DSM Development. The safety of tool customization becomes crucial
in the longer run. If all the design speci?¬?cations are based on the language and
generators de?¬?ned by a few experts, then changes in the language must propagate to
all speci?¬?cations without deleting or corrupting them. In the worst tools, a change in
the modeling language can make it impossible to load design models made earlier.
Therefore, the tools should guide expert developers in both creating and maintaining
the DSM solution.
Current IDE environments are unlikely to be the best place for creating or using
a DSM solution as they originate from and focus on lower-level programming
constructs. Too close a link between the model and code worlds can drag the level of
abstraction ofmodels back downto the level of the code, as seen withUML.Ifwereally
want to raise the level of abstraction, then tools need to change too. Domain concepts
and rules are unlikely to be best expressed in code but rather in representations that are
closer to the actual domain representations and other forms already in use. For
instance, they can be pictorial with spatial information, diagrammatic where elements
are connected to each other, matrises, tables, spreadsheets and so on. Naturally,
integration with compilers, debuggers, and testing tools is still needed.
Pages:
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137