Sparx Systems Forum
Enterprise Architect => General Board => Topic started by: zalbina on July 02, 2013, 11:44:40 pm
-
Hello,
I have really weird question: is it possible to link two function in EA and see their relationship in the Relationship Matrix?
Thanks.
-
I mean two classes operations.
-
Helle,
it isn't possible to see dependencies between operations by means of Relationship matrix.
However you can draw a dependency between operations/attributes. To do this make a dependency between the two classes. Then right click on the dependency and choose "Link to an element feature".
Best regards,
Helmut
-
WOW, thanks a lot. I'm just wondering where are those relations saved in EA database? I can use it for my addin in order to built my own relationship matrix between operations.
Thanks.
-
Hello,
there are some ways to find out:
- Thomas Kilian's eBook InsideEA or ScriptingEA
- Make a new repository with just the problem at hand modelled
Usually you quickly find the database field the connection is saved in
- Addin EnarSpy (from LieberLieber, free)
In case of operation its:
- t_connector, StyleEx
LFSP={GUID} LFEP={GUID}
Best regards,
Helmut
-
Thank you again.
-
Another one Thought according to Relationship Matrix. I can run a Model Search on it, but when I do it, my matrix is empty. I suppose that my queries are in "wrong style". For example: select Name from t_object where bla-bla. What am I missing? I wanted to link 2 operation using Model Searches. You told me it's not possible, but...
Thanks.
-
I guess you must be more specific in term of your SQL and the applied RDBMS.
q.
-
The search is stright forward:
SELECT Name
FROM t_object
WHERE Name LIKE '#WC#<Search Term>'
But I assume in this case the query returns strings, but the Matrix requiries objects.
Thanks.
-
Hello,
the Apply Model Search feature looks weird. With Simple it works. With my own SQL search with the same output it doesn't work.
I haven't found any documentation regarding search in Relationship Matrix.
The conventions should be according to CLASSGUID and CLASSTYPE (see SQL search documentation).
Example:
select ea_guid as CLASSGUID, object_type AS CLASSTYPE, Name, object_Type As Type from t_object
where Name like "<Search Term>#WC#"
Beside: Operations, Attributes are not supported elements.
You may file a bug report about not supporting SQL queries for classes or so.
Kind regards,
Helmut
-
It's very clear what you said. So, my solution could be a conversion of operations into classes or to write some addin for my own needs.
Thanks.
-
Hello,
you may consider:
- Define Behavior of Operation by Activity or Interaction
- Activities, Interaction,.. are supported in Relationship Matrix
Helmut Ortmann
-
100%. I'll discuss this option with my boss.
Thank you very much for so quick response.
-
There is a short discussion of using Model Searches to locate source and/or target elements in the Help topic:
Navigate, Search and Trace > Trace: Tracking Dependencies > Relationship Matrix > Set Source and Target Package.
-
Hello,
@Roy Thanks for your feedback and also thanks for the quick and valuable response to my bug report.
The important thing about using SQL Searches in Relationship Matrix is:
Write 'AS CLASSGUID, AS CLASSTYPE' in capitals
Example which works:
select ea_guid AS CLASSGUID, object_type AS CLASSTYPE, Name, object_Type As Type from t_object
where Name like "<Search Term>#WC#"
Helmut Ortmann
-
Hello,
After yesterday's discussion, I've been told to check if it's possible to see relationships between operations in the Relationships View and I did not find them over there :(, but a relationship between a class and an operation does appear.
Some suggestions?
Thanks.
-
Hello,
to visualize the dependency between operations I see the following possibilities:
- Diagram
- Search (general or for package and subpackages)
- Search + little script to visualize the connected operations to a selected operation
- Addin
Best regards,
Helmut
-
That's right, but I'm not sure if your solutions are acceptable for our needs.
Thanks a lot.
-
The Help makes it clear that the Link to Element Feature is a visual aid only and the actual links are between the Elements, not the Features.
Is there any good reason why the traceability could not be implemented by Sparx at the Feature level?
-
Probably the same reason why God has set Pi to be 3.1415...
;)
q.
-
I've submitted a feature request (to Sparx, not God).
-
I've submitted a feature request (to Sparx, not God).
I would try both, to increase you chances ;D
Geert