The modeling language and process should be designed to
make this possible. With a DSM environment that has taken multiuser access into
account in its meta-metamodel, achieving this tends to be relatively easy: the hard
work has already been done. Any issues caused by the particular metamodel made for
the modeling language should be revealed by the pilot project.
As with most multiuser databases, the repository will probably be stored physically
as a set of ?¬?les on a server. Although there are multiple ?¬?les, the division into ?¬?les is
determined more by internal details of the tool, repository, or operating system than by
any perceived semantic borders in the models. The ?¬?les are thus treated as forming a
single conceptual whole.
15.2.3 Multiple Repositories
For the smallest projects, or areas where only a little simple reuse of whole models is
used, disjoint ?¬?les may prove suitable. For larger projects, or where more reuse is
required between models in the project, multiuser repositories are ideal. For the
largest projects, or large projects with disconnected teams, the project can be split into
disjoint multiuser repositories.
In the simplest case, each repository only contains the models made by its team.
Each team works on its models, releasing the results as code and documentation to a
central version control system, from where they are replicated to other teams.
Pages:
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779