How to extract Glossary, issues, Test cases etc.,

[John Brand]

It would often be helpful to extract entered objects to a spread sheet or text object without having to create an HTML/RTF report. A good example is an added Glossary; is this possible?

[Graham_Moir]

It would often be helpful to extract entered objects to a spread sheet or text object without having to create an HTML/RTF report. A good example is an added Glossary; is this possible?

From the help  "You can transport glossary definitions between models, using Export Reference Data and Import Reference Data".  The entry you need is "Project Glossary", but this does create an XML file rather than a spreadsheet.

[John Brand]

Yeah, thanks Graham but I realised that; its getting the information out of EA to Excel or Word or whatever I require. Better example perhaps are test cases which I can import into EA but getting them out again?

[Graham_Moir]

Well the Glossary XML opens OK in Excel 2007 although you'd probably want to delete some of the columns.

Also have you tried the CSV export ?  The help says "Enterprise Architect enables you to import and export information about Enterprise Architect elements to and from CSV text files".  Otherwise you probably need an add-in.

[Stefan Bolleininger]

Well the CSV Export doesn't give you the possibilities for that kind of export.

BUT you can get your information with an SQL-Search from "Edit -> Model Search" and Create an SQL-Query.

For Example:

"SELECT * FROM t_glossary"

Gets all Information from the Glossary. Possible Columns for * are: Term, Meaning, Type, GlossaryID( not really needed for your query)

AND Than you can EXPORT to CSV by using "Options ->Export to CSV"

Other Tables for you:
t_issues; t_objecttests - and many others if you define your searches.

Have fun!

Stefan

[John Brand]

Thanks Stephan, that's a possibility but then I have to ask the question: Why bother? What are the advantages over a Glossary model using packages - technical glossary, testing glossary, business term glossary etc., Am I missing something obvious here?

[Graham_Moir]

Agreed you can't use csv import/export for glossary entries, but an additional requirement seemed to be test cases.  If these are distinct elements then csv export is a possibility.

[Stefan Bolleininger]

I don't get your question. The model glossary is that what it should do - establish a glossary for the whole model.

Why should you create packages for that?

If you have an package you can create an object in it which fulfills your desires and use taggedvalues. Than you can export it as well.

I don't get your idea about it.

Greetings

Stefan

[John Brand]

Hi Stefan,

If my glossaries are on the model project browser I can edit/report them as I choose. In the Glossary I'm limited to changing type, name and definition. Say I want to add owner or add a sort. Its difficult to explain!  :-/ Let me come back after some thought. Thanks for discussing, John