Traceability Matrix document generation

[user_368285]

Hi all,
I need to generate a traceability Matrix, or my requirements.

I have tree level of requirements:
1) Customer requirements
2) System requirements
3) Segments requirements

I have the "satisfy" relationship for requirements:
a) System satisfy Customer
b) Segments satisfy System

Relationship are 1 to n.

I want a Matrix with the following items:
[/td][/td]

Customer[td]System[td]Segments

and

[/td][/td]

Segments[td]System[td]Customer

I used template for document generation, but I don't know how indicate

"target element" of "target element"

Can anyone help me?

Thanks all.

[Robert Sheridan]

I suspect you will have to do that via the Automation Interface from a macro enable spread sheet.

[OpenIT Solutions]

There will be a number of ways to achieve this. The simple way is to structure your model to work with the document generator. This means nesting your requirements as child elements:

Customer Requirement with Child System requirements with child segment requirements...this falls over when a system/segment requirement is shared. But in your template you would just include a <child elements> section...

Another way is to create a traceability diagram. Place your Customer Requirement on a diagram, then right mouse click and use the Insert Related feature... then just include the diagram in your report...

Hows your SQL ? You could create a template that includes your top level customer requirement then uses a diagram fragment with custom SQL to retrieve and display all related elements and there related elements etc...I use SQL Server so I achieve this by creating a view on the server that uses the SQL Server CTE capability, then include the view in a simple select statement within my fragment...

[user_368285]

I suspect you will have to do that via the Automation Interface from a macro enable spread sheet.

I'm not able to think that a tool as Enterprise Architect oblige a buyer user to create a Macro with Excel to realize a simple operation as above descripted.

I think this operation is a common operation in requirement management, then for all buyer users of Enterprise architect.