David
Its unlikely that I would be able to give you code but I will ask "the management" and see what they say.
I just modelled both the requirement hierarchy (as seen in the ReqPro browser) and any explicit "trace-to" relationships attached to the requirements, with EA connectors (dependency relationships). This is time consuming to construct but once you have done it, you can do silly things like (for example) create an EA diagram with all the requirements on it, and see how they relate to one another or, for each design component, create a diagram with your classes on it and paste-as-link the relevent requirement objects and create dependency links between the requirements to your classes, etc. From those links we can document our requirement-to-design traceability.
Modelling hierarchy and inter-relationships is a fairly complex thing to do. When importing the ReqPro content, I build in memory a representation of it as a kind of graph-like structure. Each node in the graph represents either a ReqPro package or requirement, and each node can have as many links to other nodes as needed. From this I can create a facsimile of the ReqPro database in EA. The code to do this is highly recursive in places and my mind is often bent trying to understand it, even though I wrote it
Because the requirements in EA are marked with tagged values of the GUIDs of their counterparts in ReqPro, when a new import occurs, the add-in updates existing requirement objects in EA, so your traceability links remain intact. New requirements are obviosly created as needed, and requirements that have been deleted in the ReqPro database lead to warnings to the EA user to delete their counterparts manually in EA, once the design impacts have been assessed. Each import creates a fully detailed change report displayed in the output tab (and persisted in the model). This report can help the designer figure out what design elements have been affected by the requirement changes, assuming that before the latest import, they established requirement-to-design traceability, either diagrammatically, or using the relationship matrix editor in EA.
