Problems while Importing/Exporting Requirements wi

[Davide]

Hi,

I’m using EA version 7.0.813 and I had significant problem while exporting/importing requirements with extended attributes. :-/ In fact, after exporting/importing requirements, there was no data regarding the “requirements attributes” different from the default ones like “Difficulty” and “Priority”   In other words,
1)
Suppose that I’ve a set of requirements to import, saved in a CVS file, and this file includes a column named “Reviewer comments” (because the old requirement model included such an attribute), how can I import this data inside EA?
2)
Suppose that I’ve defined a new value tag called “Reviewer comments” and I’ve several requirements that include this added attribute, how can I export such requirement (by including also the data related to “Reviewer comments”)?
Unfortunately, I wasn’t able, while defining the CVS Import/Export specification, to select any “my defined tagged values” in the “element field” to Import/Export.
Is it possible that a great tool like EA does not support the importing/exporting of requirements with attributes that are different from the standard ones?  

Thanks,
Davide

[«Midnight»]

Are you talking about version control or CSV files?

[Davide]

Sorry   I meant CSV and not CVS.

[«Midnight»]

Thought that might be it...

I think you're out of luck. The CSV import and export works only for requirements. [At least it used to. There might have been one or two other things added lately, but I don't think they'll help you either.] Not only that, but the format is extremely limited. EA does not allow you much latitude for extension.

You might be able to do what you want via import and export of reference data. Of course this works best for transfer between projects. If you are defining requirements in some other environment you will have to do additional work.

Perhaps someone can shed light on a way to do this without jumping trough too many hoops.

David

[Eve]

CSV import/export is in no way limited to requirements, it never has been and I can't see anywhere in the documentation that suggests this.  The limitation is that only certain fields of elements are useable.

To import something into additional fields we would recommend that you generate some basic XMI for EA to import.

PS. I am moving this onto the General Board as it does not concern a bug report.

[Davide]

I need to import some reqiurements and according to the documentation I should use the CSV facility. You are talking about XMI, can you please indicate me the documentation where I can learn how to ues XMI to import requirement?
Thanks.

[RoyC]

To export reference data to an XML file, as David suggests, see:

http://www.sparxsystems.com.au/EAUserGuide/index.html?exportrefdata.htm

You select the Requirement Types item from the list in the dialog. This exports requirement types as defined on the Requirement tab of the General Types dialog:

http://www.sparxsystems.com.au/EAUserGuide/index.html?requirementtypes.htm

However, to export/import the requirements themselves via XMI, see:

http://www.sparxsystems.com.au/EAUserGuide/index.html?exporttoxmi.htm

I hope these help.

[Davide]

What if I do not have a XMI source file but I've a CSV with columns different from the standard requirement attributes A solution may be to import this CSV file into another requirement tool (acting as a proxy), then from this tool I will generate an XMI file that I will import into EA. Sounds good?  

[«Midnight»]

Simon brings up a good point.

When I last used this I wanted to do something with the Glossary. While I don't remember ever finding something that said CSV was limited to Requirements, I also did not find any information on using it for anything else. Nor did I find any way to initiate the transfer for anything other than Requirement data. I eventually built a utility that solved my problem - allowing people to maintain a general purpose glossary in Excel, then importing it into projects when needed, with filters etc. provided by the tool.

That was back in the EA 6.0 days (or so), and things may have changed since then. Still, I don't remember seeing anything about CSV for general data transfer. [That does not mean it is not there, just that I have not noticed it. However, I do actually read release notes for each build...]

Meanwhile, I think the point that David (E) is trying to make is that he cannot find any way to extend the data that the CSV file contains. He wants to be able to add new fields, and have EA capture that data someplace. The details are important, but only if EA supports the concept somehow.

David

[Babysittah]

To export reference data to an XML file, as David suggests, see:

http://www.sparxsystems.com.au/EAUserGuide/index.html?exportrefdata.htm

You select the Requirement Types item from the list in the dialog. This exports requirement types as defined on the Requirement tab of the General Types dialog:

http://www.sparxsystems.com.au/EAUserGuide/index.html?requirementtypes.htm

However, to export/import the requirements themselves via XMI, see:

http://www.sparxsystems.com.au/EAUserGuide/index.html?exporttoxmi.htm

I hope these help.

Well, lemme check it out if it helps