Simple Requirements Reporting Question

[paddler]

Hi,

I have been away from EA for 18 months and am "re-wrapping" my head around reporting and requirements. Before I get to far into modeling requirements I want to make sure the reporting capabilities are in place.

Here is my question:

I use two types of "connectors" in any requirements models; "realizes" and "aggregation/composition" . The former is used when something like a use case "realizes" an original client requirement. The latter connector I use when a high-level requirement can be broken down into smaller, more specific ones. Diagramatically it looks great but reporting on this is a bugger.

The requirement element has a "Realizes" field which I can report on in RTF but how does one report (in RTF) on the relationship between those requirements where aggregation connectors are used?

Why do I care about this?Essentially, I want to produce a report that I can run at a root requirements package level which will run through all sub packages and pull out the requirements, their attributes and relationships in one shot.

Another way of saying this.... I would like to show, in an exported document, what the impact of changing Reqt X would be assuming it is "realized" by something else or is a "parent" or "child" in an aggregation/composition relationship.

 

[philchudley]

Hi

In the RTF template editor you will have to use the Connector checkbox, and below that the Source and its Element checkboxes, and the Target and its Element checkboxes (depending upon whether you wish the parent, child or both)

To ensure that only aggregation connectors are reported on use   Document Options... and exclude all connectors except Aggregation

This works OK, although when reporting on your children / parents you only have access to the basic properties such as Name, Notes etc

Cheers

Phil

[paddler]

Thanks, Phil!

PT