Book a Demo

Author Topic: DOORS table views  (Read 4884 times)

Gary

  • EA User
  • **
  • Posts: 84
  • Karma: +1/-0
    • View Profile
DOORS table views
« on: January 20, 2014, 08:44:35 pm »
I often get challenged when putting forward the view that EA can do requirements management (unique ids, tracability, requiement types etc) that viewing lots of requirements in a table view is easier in DOORS. You create a VCRI that has the text, type, verification method etc. in an easy to view table list and export to excel format for distribution.

What is the best way of recreating this from EA and what do you good people use?

Gary

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: DOORS table views
« Reply #1 on: January 20, 2014, 09:16:52 pm »
That very much depends ;-)

One way is to export requirements via csv and to import that into DOORS. However, if you are using DOORS anyway you should make that the primary RM system and just mirror the requirements from there into EA. There's an add-in available to do that. In a recent project I had more complex requirements so we wrote a dedicated exporter in DOORS and imported/synched that with a script inside EA. It was quite a bit of work, but no way around it. You should avoid any round-tripping. That is to make changes to requirements in EA and then move them to DOORS and later re-import. Choose one system to be the leading one.

q.

Gary

  • EA User
  • **
  • Posts: 84
  • Karma: +1/-0
    • View Profile
Re: DOORS table views
« Reply #2 on: January 20, 2014, 10:59:05 pm »
Thanks Qwerty

I love that it depends answer, I use that a lot. :)
 
What I am trying to do is move us from a DOORS to Powerpoint to Massive Word document, systems engineering process to MBSE. The last old school systems engineering hold out is the requirements management. The main sticking point is that a VCRI is very easy to read as you have all the information laid out in a table format. Whereas the model has tracability in a Relationship Matrix, type of requirement in a tag value etc.

What I would love to do is import from DOORS once using the MDG add-in (which i have used and found very helpful) and then never touch DOORs again.

Gary

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: DOORS table views
« Reply #3 on: January 20, 2014, 11:26:57 pm »
The trouble with DOORS is that it's (more or less) the only (more or less) valuable RM tool. It's GUI got stuck mid 90's, but it supports that break down process and can handle tons of requirements. EA is not really a RM tool (lack of unique numbering, only a half-breed of that) and the break down of Word docs (which are still the major source) works only manually (though in the end that's the way to go anyway). I never really used RaQuest for EA. It might be something in the middle but have not heard so much here on the forum.

I can only wish much luck when dealing with RM. Unfortunately everybody seems to be enabled to talk responsibly about requirements. I have seen so much grief...

q.