Modeling Concepts Should Also Support Editing Language de?¬?nition
should not focus only on the ?¬?nal static model but also cover the use of the modeling
language. This means thinking about the model editing process, how models can be
kept consistent, and howreuse of model elements can be supported. In our example of
button pressing, having different button objects for a long press and a short press
would make some model editing actions unnecessarily complex. Simple refactoring
actions, such as changing the name of the button, could mean editing the name twice:
for both button types when two different policies are used. It would also become more
dif?¬?cult to check the consistency of the models: what if only the short press button
name is changed from ???Mode??? to ???Set???? How could we inform the modeler that the
???Mode??? long press needs to be changed too? De?¬?ning the button with information
about its usage would limit reuse possibilities and increase modeling work: we could
not reuse the button speci?¬?cation so often anymore as it would always come with its
usage information. While modeling, we would then need to specify the button
multiple times if it is used differently in the same application. A closer mapping to the
behavior in the problem domain would lead to reuse and minimize modeling work.
Pages:
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445