Sparx Systems Forum
Enterprise Architect => General Board => Topic started by: Tehila1 on March 20, 2016, 07:54:17 pm
-
Hello,
Our model consists of several projects, where as a project is a branch.
Sometimes a project uses assets of another branch. In case of a problem we should reverse the project to a previous version along with its related packages.
I therefore would like to develop an add-in that recognizes relation among the projects, and here is my questions:
What are the parameters that EA rely on in order to recognize relations among packages?
According to Geert's great article (http://bellekens.com/2015/10/16/searching-for-real-orphans-in-enterprise-architect/) I found the following:
1. In case there is an object on my project, that its classifier is from another project, there is a relation between the package.
2. In case a diagram in my project contains an element from another package.
3. In case there is a relation between element in my project (as source) and an element from another package.
4. In case an attribute in my project is of type that defined in another package.
5. In case a returned type of an operation in my project is a type that defined in another package.
6. In case a parameter to an operation in my project is of type that defined in another package.
Do I cover all of the relation scenarios? any other ideas?
Thanks in advance!
-
Some things you might have forgotten:
- Relations between packages
- hyperlinks to elements or diagrams
Geert
-
Some things you might have forgotten:
- Relations between packages
- hyperlinks to elements or diagrams
Geert
Thanks.
What do you mean by "Relations between packages"?
-
A relation where one or two of the sides is a Package
Geert
-
Hi,
I would additional check the t_xref table. There are properties and more relations inside which you might forget.
Helmut
-
Ah, yes indeed.
And don't forget possible RefGUID tagged values.
A RefGUID tagged value can reference an element, package, diagram, operation or attribute using the GUID of that item.
Geert