generating report for parts of a team repository

[Darth Vader]

Hi all.
We have a project repository in MySQL database. Inside the project we have several packages. Package A contains information about all our components. Packages B, C, D, etc. contain customer requirements, realized by one ore more components. A component from package A realizes requirements from many packages.
Is it possible to create a report template that shows only relations between components in package A and reqirements in current package?
F.E. report on package C with requirements REQ01-03 must contain following information:
- component CMP01
 - realizes REQ01
 - realizes REQ03
- component CMP02
 - realizes REQ02
even if CMP01-02 realize requirements in packages B & D.

[Uffe]

Shouldn't be too hard. Construct the template to list all requirements, then filter out the irrelevant packages using the "Except where Query excludes Package" option in the Generate Documentation dialog.

You can save sets of document generation options as "resource documents," which helps with repeated generations.

HTH,


/Uffe

[Darth Vader]

Thanks for the reply.
Requirements must be grouped by components. Is it possible to perform smth like "group by" on element list?

[Uffe]

There should be no need. If the template is degisned to be run on the component package, the Element section in the template will resolve to the component, and you list its requirements by selecting Connector -- Target -- Element.

Something like:
package>
element>
{Element.Name}   <-- This is the component
connector>
target>
element>
{Element.Name}   <-- This is the requirement
< element
< target
< connector
< element
< package

However, if you do need more fine-grained control, you can always use a template fragment with an SQL query.

/Uffe