Phil,
What I find interesting is the list of products Mr. Bush listed for requirements. In my opinion, it is NOT the duty of EA to be modified to integrate with those products; rather, the duty of those products (if they see the need) to integrate with EA (or any other UML tool). You can ask Geoff that we worked with what was provided in EA and built EPG-RequirementControl (name change). Moreover, when Mr. Bush mentioned "RequistePro" he is being disingenuous. That product is built to integrate with only the Rational suite and quite frankly, IT DOESN'T INTEGRATE well at all. For example, Use Case diagrams can not be inserted in a Use Case document directly between Rose and RequistePro: you need to buy yet another tool (SoDA). RequistePro does NOT have a feature in it to connect to any other UML tool AT ALL and to take it further, there is NO CONNECTION between RequistePro and, let's say, Together!
As far as the reporting and roundtrip life cycle comments he made, well... that's what EPG-TraceControl, -VersionControl, -TestControl, et cetera are all about. Describe, for example, relies on other tools to complete the cycle. Rational does this as well. Together, prior to the purchase by Borland, didn't have a complete cycle either. To suggest that EA is lacking on a point that is equally lacking in their own tool and Rose, for example, is again, in my opinion, insincere and without merit.
Bottom line, in my opinion, not only was Mr. Bush disingenuous, but inaccurate with his comparisons and statements reqarding EA and other requirement gathering tools. And this, I'm afraid, reflects on the company he appears to represent.
Just my .02...
Steve