Book a Demo

Author Topic: requirements management with RaQuest & EA  (Read 3607 times)

esra

  • EA Novice
  • *
  • Posts: 1
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
requirements management with RaQuest & EA
« on: January 25, 2005, 01:44:09 am »
Hello, we have a requirements management problem in our project.

We are using EA for analysis&design but haven't decided a requirements management tool yet. We need a req. mngm't tool that is compatible with EA, because we need to trace requirements to use-cases. If req. mngm't is done with a tool that is not compatible with EA (like RequisitePro) all things are messed up, because requirements and usecases are maintained in different environments.

I downloaded trial version of RaQuest, but it is very newly released, i don't know how much robust it is. Besides, i couldn't install the word add-in, which i need for sure. Because our project documentation will be MIL-STD-498 compatible, we will create a requirements document then we will import it to RaQuest. :-/

???Does anyone have previous experience on requirements management with EA, or on RaQuest (and word add-in), or on integration with other requirements management tools?

It is somewhat an unattractive :) issue, but we need it badly in the project, thank you.

thomaskilian

  • Guest
Re: requirements management with RaQuest & EA
« Reply #1 on: January 25, 2005, 06:04:51 am »
Hi,
please try to search the forum for "requirement", since there are a lot of posts regarding this issue. (Note: increase the search time limit to 999 days!)

Tjerk

  • EA User
  • **
  • Posts: 231
  • Karma: +1/-0
    • View Profile
Re: requirements management with RaQuest & EA
« Reply #2 on: January 26, 2005, 12:26:04 am »
Hi,

I have worked with EA and the Mil-Std-498 documentation for more than two years succesfully. What I do is to mirror the structure of the Mil documents (SSS, etc.) in EA view and package structures (each chapter and paragraph becomes a package).

Then I will be exporting RTF per chapter and replace the original chapters in a Mil document using the Word Master-Subdocument feature. Traceability is done by using the various relationships that EA (UML) offers and by exporting the relationship matrix (via CSV and Excel) to a Word table (not yet automated).

I have tweaked a RTF template in EA to match our format. After that I commonly run some self made macros in MS Word to tune the last details (e.g. removing technical terms from an SSS to hide some of the UML language for the customer).

We're still working on an automation interface to insert the EA Mil structure to a Mil template directly, but progress is slow (always short of time  :-/ ).