Author Topic: Import Requirements from 3rd party tools (EAIDs) (Read 6410 times)

struppimoppi · « **on:** September 22, 2009, 12:37:04 am »

Hi,

I'm looking for a way to import requirements from a 3rd party tool, in my case Trac. My idea is to write a little tool myself what creates XMI files I can import into the ea-model. So I first exported some objects to XMI to get to know the xml structure. So far so good. The question which arises now is how do I generate EAIDs for the new objects or what are the constraints for such ids (uniqueness probably...but what else)?

Thanks for any hints and help...

Regards, Frank

Makulik · « **Reply #1 on:** September 22, 2009, 02:35:45 am »

Hi Frank,

I think you don't necessarily have to provide the EAIDs for XMI data to be imported. I am not 100% sure about this, but I think the import facility will generate them for you.
The IDs used by EA are basically GUIDs, in XMI they have a special format.

WBR
Günther

Geert Bellekens · « **Reply #2 on:** September 22, 2009, 04:36:32 pm »

Frank,

If I were you I would stay far away from xmi and import the requirements using the EA API.
I think that is much easier and a lot less error prone. Plus you don't have to worry about GUID's and their format as EA will take care of that for you.

Geert

struppimoppi · « **Reply #3 on:** September 22, 2009, 07:52:19 pm »

Quote

Frank,

If I were you I would stay far away from xmi and import the requirements using the EA API.

This is an excellent hint! I will go for it. Thanks.

umesan · « **Reply #4 on:** September 24, 2009, 04:58:51 pm »

Using RaQuest is one of the options for importing Requirements as well.
Please try the trial version.

struppimoppi · « **Reply #5 on:** September 24, 2009, 06:45:29 pm »

Quote

Using RaQuest is one of the options for importing Requirements as well.

But this assumes that I would use RaQuest for managing the requirements too, right? In my situation I already have a fully productive tool for that purpose (trac.edgewall.org) and I only want to import the requirements into EA.
At the moment I'm happy with the EA API. It is quite pleasent to create new elements (requirements) and link them to other elements (to use cases for instance).

Thanks, Frank.

umesan · « **Reply #6 on:** September 25, 2009, 05:13:24 pm »

>But this assumes that I would use RaQuest for managing the requirements too, right?
I wasn't assuming that situation.
I thought csv import of RaQuest would be easier than using EA API, but in that case, csv import function of EA would be a better suggestion.

If EA API would settle the issue, that is certainly good.

Sparx Systems Forum

News: