Indirect Relationship Traceability Report

[Dorian Workman]

Hi,

In our requirments management process we trace Requirements to Use Cases and Use Cases to Screens, using Realizations.  There is no direct link between the Requirements and the Screens.

Is there a way for me to spit out a Report, RTF or otherwise, that shows the indirect relationships between the Requirements and the Screens?  I don't mind if the 'middle-man' Use Cases are shown on the report too.

I know the Hierarchy view shows me this, but I need to spit it out into a neato looking report, to distribute to the team.  I can't see any option like this in the Hierarchy view.

Thanks.

[nraponi]

This is something I really need too, not sure if anyone has any ideas?

[bioform]

In the short term a hack might be:

Export RTF view part 1 (Req to UC)
Export RTF view part 2 (UC to Screen)
the use excel and these two "sources" to format your new view using formulas.

Be aware though that you seem to be assuming that ALL rrequirements traced to a UC are then realized through the screens of the use case. Seems like big assumption to make...

[Dermot]

This is not any simple report as you are dealing with complex many-to-many relationships.  One thing you can look at is using the Advanced Search SQL query builder. A simple SQL for one level of "Implements" is:
SELECT t_package.Package_ID, t_package.Name AS Package, t_connector.End_Object_ID AS ObjectID, Object_1.Name AS ObjectName, Object_1.Object_Type AS ObjectType, t_connector.Connector_Type AS Connector, t_object.Object_ID AS ImplementedByID, t_object.Name AS ImplementorName, t_object.Object_Type AS ImplementorType, t_objecttypes.DesignObject
FROM (t_objecttypes INNER JOIN t_object ON t_objecttypes.Object_Type = t_object.Object_Type) INNER JOIN ((t_connector INNER JOIN t_object AS Object_1 ON t_connector.End_Object_ID = Object_1.Object_ID) INNER JOIN t_package ON Object_1.Package_ID = t_package.Package_ID) ON t_object.Object_ID = t_connector.Start_Object_ID
WHERE (((t_connector.Connector_Type)="Realisation"))
ORDER BY t_package.Package_ID;

Doing multiple levels starts to tax standard SQL, however if you are usng a .eap file then the SQL Query can include a reference to an existing SQL query saved in the repository (mdb file).
Note: the results can be output to RTF.
Good luck!

[philchudley]

Hi

If you do not mind a diagrammatic report, here is a suggestion.

1) After all realizations have been made
2) Create a new Custom/Requirements diagram
3) Drag a Requirement onto this diagram, then right click and select Add/Related Elements...
4) Choose a "depth level" and optionally filter to the specified link type etc (leaving at defaults will work fine)
5) Repeat the process for the use cases now added to the diagram
6) Repeat as necessary

Cheers

[bioform]

Hmmm, a feature I have not noticed or explored! So many buried nuggets!

One caveat, that does seem to "screw up" your existing diagram's layout, so might be best to try it on a new/blank diagram.

thanks Phil!

[Dorian Workman]

This is very helpful Phil, thanks!