Merging multiple versions of the same
?¬?le into one version containing all changes is a dif?¬?cult task and has given rise to a
whole mini-industry of diff and merge tools. None of these is as intuitive and
informative as developers would like, but almost all of them are better than
attempting the same task manually.
With a model repository, this problem simply does not occur: elements are locked
when changed and no other user can change them until he has loaded the committed
version of the user who obtained the lock. While normal modularization is good
practice in DSM too, in a good tool it is perfectly possible for several users to edit
different objects in the same model at the same time: each object is locked separately,
so everyone can obtain the lock on just the object they need.
15.3.4 Where Do the Version Comments Go?
Version comments are an important part of development. In our experience, we refer
frequently to version comments in both code- and model-based development. They
provide information about why something changed, rather than just what changed,
and allow a much quicker overview than even the best diff tool.
In a version of a multiuser repository, the number of changes made by all
developers across all models will be too large and too disparate for some of the normal
uses of version comments.
Pages:
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785