importing requirements from RTF doc

[ramosen]

  I'm new to EA and trying to attempt importing requrements from a Word document converted into RTF. I've read through some of the older threads and still have not found the solution I've been looking for. Any pointers?

[«Midnight»]

I'm not sure you'll be successful at this. You may be able to somehow import the text of requirements, but I do not think you can have EA automatically create requirement entities.

[I could be wrong on this; if so please jump in anyone...]

If you can convert the requirements information to a table and export that to Excel you could do an import. Use Excel to export the table to CSV format and EA will read the file.

You will have to ensure the correct information is in the table. To find out what you need look at this Sparx white paper: http://www.sparxsystems.com.au/downloads/whitepapers/Requirements_Management_in_Enterprise_Architect.pdf

David

[JohnWSaundersIII]

I have almost succeeded in doing just this, at least in the case of one particular requirements document. I saved it from Word 2003 in XML format, and was able to use an XSLT stylesheet to transform it into XMI, which I was able to import into EA.

Unfortunately, I'm a bit stuck at one point, and may need to post the details of the problem: EA creates the requirements for me, complete with the text, but won't show them as package contents if I move them into packages.

I'll post again if I make any progress on this, but I think I'm more or less on the right track. Note that I was only able to do this to the extent that the requirements document followed our requirements template properly. Having requirements text at different header and outline levels messed things up pretty badly, and had to be fixed first.

John

[Jan ´Bary´ Glas]

If I understand well, the problem is with displaying the content of packages.
If so, try in Diagram properites check Show Package Content.

[JohnWSaundersIII]

Thanks. That was set.

The problem is that my imported elements won't show up in package contents, whereas a newly-created element will show up in the same package. I've clearly missed setting something which allows ownership to be changed.

I haven't had any more time to look at this. Things keep happening in the world - other things.

John

[ramosen]

John, what did you use to convert xml to xslt?

[JohnWSaundersIII]

Sorry, I didn't convert XML to XSLT - I created an XSLT stylesheet which could convert the XML format saved by Word 2003 to XMI 2.1, which could be read by EA. The stylesheet I used depended on the particular requirements document I was converting - if the individual requirements had been at heading level 2 instead of 3, the stylesheet wouldn't have worked.

We're  meant to be using templates for requirements documents, going forward, so I'm hoping this will have the side effect of standardizing the resultant Word XML.

John

P.S. It's now looking like next week before I get back to this. "It never rains but it pours".