Would you laugh if we said any architecture or model information that you require from Enterprise Architect models is just a click away?
Let’s take the example of use-case and requirements and see how it can be done.
To re-iterate, the goal is to let users see a specific list of requirements that are connected to a use-case on a click.
This is the normal view before adding the custom report:
Follow the steps to define the custom query:
SELECT distinct incomingObject.name as SourceName,
outgoingObject.object_type as basetype,
FROM t_object as tobject
LEFT JOIN t_connector connector on ( (connector.start_object_id = tobject.object_id) or
(connector.end_object_id = tobject.object_id ))
LEFT JOIN t_object as incomingObject on (incomingObject.object_id = connector.start_object_id and
tobject.object_id != connector.start_object_id)
LEFT JOIN t_object as outgoingObject on (outgoingObject.object_id = connector.end_object_id and
tobject.object_id != connector.end_object_id)
tobject.ea_guid = '<guid>' AND
outgoingObject.object_type IN ('Requirement')
The results are showing up and so, we know the query works fine.
Follow these steps to add the newly created query attribute to an object:
Now, open any use-case to see the list of requirements.
You can click on any of the requirements to get more details.
In the same way, you can create reports to get
We are just limited by our creativity!