Book a Demo

Author Topic: Preserve relationships from imported model element  (Read 3211 times)

natvig

  • EA User
  • **
  • Posts: 65
  • Karma: +7/-0
  • I love YaBB 1G - SP1!
    • View Profile
Preserve relationships from imported model element
« on: May 20, 2008, 12:17:21 am »
We are working with multiple models in parallel, using Enterprise Architect. Some which are general (framework) and used as building blocks in more project specific models. The framework model is used by importing it to the project specific model as a root model (from XMI). The model is made read-only to the staff working on a specific project. When an updated version of the framework is released it is imported again into the project specific model. Relationships that originate from elements outside the framework root model are retained during update, also if the relationships have framework elements as target elements. Now, here is my two questions:

1. Relationships may be created from the framework elements even though this model is write protected using the EA-security mechanism. Should EA security mechanism allow this relationship to be created? I think it should not.

2. The relationships created from the framework elements are discarded when framework model is imported again with a new update. How can they be retained?

One typical relationship that we would like to model this way is the SysML <<Satisfy>> relationship. We want to use this relationship from Blocks in the framework to requirements in the project to model that the specific requirements are fulfilled.

Any ideas?

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
Re: Preserve relationships from imported model ele
« Reply #1 on: May 20, 2008, 08:24:56 am »
1. I know that there a number of people that take each side of this discussion.  It would create similar issues as the version control that someone was talking about here recently.  (Can't remember the exact thread, but being unable to work with a shared actors package because it was locked was the basic problem.)

2. You should be able to preserve them by creating something in the opposite direction.  EA considers that the connectors you have created are owned by the package being replaced and therefore removes them.  (Some connectors you will be able to achieve the same effect by creating it in reverse then setting the direction to 'Destination -> Source' in the properties.)