Sparx Systems Forum
Enterprise Architect => Automation Interface, Add-Ins and Tools => Topic started by: Saul on December 14, 2010, 04:36:27 pm
-
I have an association between a use-case elemnt and a requirement element. I can change the connector type between them from 'Association' to 'Realization' using the COM API, however the requirement doesn't show up in the use-case as an 'External Requirement' as I would hope.
Looking at the API documentation there doesn't seem to be any way to add an existing requirement element as an external requirement to a use-case.
Am I missing something?
-
Which element is the Source (Client) and which is the Target (Supplier) of the connector? I think the Use Case should be at the Client end and the Requirement should be at the Supplier end. Also might be worth confirming that Connector.Direction is set to "Source -> Destination".
-
Yes, the source is the use-case and the target is the requirement.
I didn't have direction specified, but I've fixed that now...no change.
The "realization" I create in the UI looks identical to the one created via the API...except for the fact that nothing shows up in the Use-Case External Requirements list.
-
OK, I've found the solution.
You need to set the connector type to 'Realisation' *not* 'Realization' as described in the API spec (under Connector).
I think this might be a bug - at least a documentation bug.
Regards,
Saul
-
OK, I've found the solution.
You need to set the connector type to 'Realisation' *not* 'Realization' as described in the API spec (under Connector).
I think this might be a bug - at least a documentation bug.
Regards,
Saul
Hi Saul,
Which version & build of EA are you running?
The Realization/Realisation dichotomy should have been fixed as of 850 or so... See: Dear Geoffrey... (http://www.sparxsystems.com/cgi-bin/yabb/YaBB.cgi?num=1253503550)
Paolo