Even then, it can only apply to the
intersection of the sets of information recorded in the two different models. For
example, inUML tools you may have one class in a model mapping to one class in the
code. With suf?¬?ciently simple changes, a bit of luck, and a following wind, the best
UML tools today are capable of maintaining that simple mapping for the names of
classes, attributes, and operations. The actual code isn??™t kept in synch. Although tool
vendors tend to claim that UML models are kept in synch, this generally means only
some parts of class diagram elements. Synchronization is partial simply because the
details of the code are not in those models that the tool can keep synchronized. The
only way the synchronization can be made ???better??? is by moving the two languages
closer: for example, by allowing UML operations to contain the method body as text,
or the code to show things like ???boundary class??? as specially formatted comments.
Each move toward better synchronization is thus a move away from having the ?¬?rst
language on a higher level than the second language.
The DSM solution is to turn the question on its head and ask, ???OK, you showed me
the model, possibly based on a high-level modeling language, that doesn??™t yet capture
enough information to build full systems. And you showed me a second model and a
transformation into it.
Pages:
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465