The only real solution is that the
tool be able to handle these issues, but current evidence shows this to be too much to
expect: sadly, it is the ???version 1.0??? tools that use disjoint ?¬?les. While some do not yet
offer links between ?¬?les, most of these say they are considering it.
For now, then, if you are stuck in a tool that offers intermodel links between disjoint
?¬?les, but not the tool support for protecting you from the problems this may cause, our
advice would be to avoid reuse by direct reference across model boundaries. This is a
shame, as such reuse, when supported by a true repository, is something we have used
to good effect in almost all cases of DSM we have worked on.
15.2.2 Multiuser Repositories
In a multiuser repository, all models are available in one coherent space. Models and
their elements can be freely browsed and reused by direct reference. User permissions
402 DSM IN USE
and modeling language rules can be layered on top of this basic freedom to limit it
where necessary. The repository and tool take care of the consistency of links between
model elements. Elements are not deleted from the repository while others refer to
them, so situations such as those in the previous section are avoided. In most cases,
referring to an object that has been removed from another model can still generate
good code.
Pages:
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777