Requirement Inheritance for External Requirements

[MichaelY]

I have approximately 1500 requirements that I loaded into EA as external requirements, some of which I need to move to Internal requirements under classes (or packages) that have been arranged in a hiearchy.  I don't see a mechanism to move requirements from External to Internal and I don't want to reload the requirements as they already have a TON of relationships established with other elements.

Anyone have some ideas on the best approach, as my understanding is that inheritence for requirements only works with internal requirements - argh... :-/

Thanks for any guidance on this...

[thomas.kilian]

With that amount you should dig the automation interface. Probably a SQL could do the same job, but then "you need to know what you're doing".

[MichaelY]

Ya, I took a look at the database directly at first and then realized there were quite a few gaps in database relationships - ugh.  

I then took a peak at the automation interface and realized that might be a long-term path for approach, but right now I need to finish modeling as much as possible by this weekend for presenting... (No time right now to learn the Automation interface) ...

However, if you know a fair amount about it, my main end concern after getting the relationships and inheritence correctly established is to do reporting beyond the RTF's capabilities (one example is creating a report for each 80+ components that Lists first the component name, description, but also then related actors, objects)