Author Topic: Marrying DOORS to EA  (Read 3223 times)

alicecbrown

  • EA User
  • **
  • Posts: 30
  • Karma: +0/-0
  • Silence condones.
    • View Profile
Marrying DOORS to EA
« on: July 12, 2007, 08:30:22 am »
 :) So, we now have the module in EA, and guess what?  It only imports the first cell in the table that's imported for each row.  OR, it skillfully hides all the rest of the info in the table.  And, since each cell in DOORS is an object, with its own Object ID, and the text is called 'Object text', that field should be filled, but isn't.
Do I have a bug, or am I not looking in the right place? ???
The larger goal still lies before me.  I have now chopped up the module into Views.....to fit each class of requirements in EA: So we have the Centrifuge requirements that correlate to the Centrifuge class diagram, etc.  But there has to be an easier way to drag n drop these requirements into the Requirements field in the pop-up for each Activity, Package, Diagram, etc.  The future of DOORS and EA use on this project is at stake.
We already fear that IBM will drop DOORS once it buys Telelogic in September (since they have Rational's Req Pro as a competitor already).
Unto him who is given much, much is required.