In a few cases, an
individual repository grew too large to be managed by a single developer, and so
those cases simply moved to using multiuser access to that repository when extra
developers were added.
15.4 SUMMARY
DSM already offers large amounts of reuse and productivity through the work done in
the modeling language, generators, and domain framework. The amount of reuse can
be increased still further by reusing models and model elements. Storing models in a
multiuser repository allows the greatest scope for reuse, makes it easiest, and avoids
many of the problems familiar from reuse by name reference in code-based
development. Where necessary or desired, work can also be split over several
repositories, each used by a smaller team, or even one or more repositories per
developer. These more disjoint approaches inhibit reuse and make the process of using
DSM more like traditional programming. While this may not be a good ?¬?t, there may
be some transitional bene?¬?t from the more familiar process.
Attempting to force DSM into the ?¬?le-based model, with multiple ?¬?les per
developer and a single model per ?¬?le, appears to be a poor solution, at least with
current tools. The main expected bene?¬?t, better integration with code-oriented version
control systems and practices, seems not to be achieved if any reuse is allowed.
Pages:
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787