The idea of DSM is to
come up with a minimal suf?¬?cient representation of systems, and this is the main
reason for its 5??“10 times productivity increases: code- or UML-based ways of
building systems involve lots of duplication??”the same information in several places.
People asking for model-to-model transformation say next that ???we want to be able
to change the ?¬?rst model still, and have those changes re?¬‚ected automatically in the
generated model.??? That means you are working with 1 + 2 pieces of information, and
also that you need to come up with some way to propagate the changes down to the
second model ???correctly.??? ???Correctly??? here means without destroying information
manually added there, updating the automatically generated parts, creating newly
generated parts, and updating manually added parts to re?¬‚ect changes in the ?¬?rst
model. This last case happens if the manually added part refers to the name of an
element originally from the ?¬?rst model and that element??™s name has now been
changed.
Next people say, ???and we want to change the generated model and have the ?¬?rst
model update automatically.??? This is even harder. The only cases when it can happen
are where you don??™t really have a ?¬?rst model and a second model but rather two
different representations at the same level.
Pages:
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464