Heather Wallace

[Heather Wallace]

As far as the table structure goes I can recommend “Inside Enterprise Architect” by Thomas Killian, available from https://leanpub.com/InsideEA.

It was recommended to me and I’ve found it to be a really valuable resource. It can also be useful to browse the data in a database management tool to really understand how your data is held. I tend to use MS Access (needs to be 2010 or earlier for EA10 – don’t know about later EA versions) to look at a local copy of the project. I change the .eap extension to .mdb and can then use the linked table manager in MS Access to find the project file and link to all the tables. Only a few tables tend to be populated, so it is easy to get to grips with. There are a few complications, such as the handling of stereotypes – watch out for the t_xref table!

Heather

[Heather Wallace]

I’ve had to resort to this approach when I’ve run into version control issues i.e. some good profiles in one profile xml and others in another. It can be a quick way to achieve what you need, but definitely heed the warnings – it’s very easy to corrupt the xml.

Heather

[Heather Wallace]

Nice to have some support on this one, as it’s been on my wish-list for a while. I very recently had to transfer some model data from EA into MEGA. It was made much easier by an Excel-based matrix import facility that had been developed in an add-on. It reminded me how much I miss the feature when using EA.

Yes I know it’s difficult, but we can live in hope …

Heather

[Heather Wallace]

Did you receive the document and XMI? I assumed you were Ian and sent it to his address on 24th February. I sent the full doc without pictures as they were bumping up the size.

Regards,

Heather

[Heather Wallace]

Hmm. The document is full of pictures and comes in at 60MB. I could do a partial version when I get a chance (I’m in France on business at the moment). Are attachments here private? Or is there another address I can send the XMI and document to?

Heather

[Heather Wallace]

Unfortunately not, I have 37 headings in the later section that should be referenced from hyperlinks in the first section, but a much smaller number of BK_ bookmarks survive the cull.

Heather

[Heather Wallace]

How did I miss that? Many thanks,

Heather

[Heather Wallace]

Something to look forward to!

Heather

[Heather Wallace]

I saw that option. My point was more that in a single document there might be one “main” treatment of the stereotype, which would deal with lots of stuff and be handled via a normal profile, plus one or more supplementary treatments of the element type e.g. as a simple bullet list of hyperlinked names.

I need to look into this a bit further before I can say anything sensible, as I haven’t yet tried to create my document (the underlying Word template won’t turn up until tomorrow). What I essentially have it a need to display the element twice:

First: Parent element plus description plus bullet list of hyperlinked names of children
Then: each child with its name as heading and desrption plus lots of relationships and pictures (i.e. standard profile)

So I guess the element report wasn’t really the issue in this case, what I really need is the option to present a table of related attributes as a bulleted list, or the option to define an alternative presentation for a related element.

Hmm…

Heather

[Heather Wallace]

I am intrigued by your (Adrian’s) statement “when we added importing of relationships”. I have just re-checked the latest version 3.5.5.and the user guide is explicit that relationships are read-only. Am I missing something?

Heather

[Heather Wallace]

Very happy to be of assistance. Before I knew about the back end tables I had to write xslt scripts to convert the xmi int an xmi format that read a sensible set of columns into Excel, and then back again after updates were made (scripts now lost…). MS Access is much easier!

It would be good to have a standard section that simply adds the whole glossary table, or a glossary profile to accomodate sorting by type or term.

Best regards,

Heather

[Heather Wallace]

An easier way of getting the whole glossary out is just grabbing the contents from the t_glossary table.

I would do the following:
– Create a local model copy (as an eap file)
– change the extension to .mdb
– Open MS access and use the linked table manager to link to all the tables (or just pick t_glossary)
– Open the table in MS Access and copy the contents into Excel or Word

Of course, you could get this information out via SQL – the glossary fields are Term, Type and Meaning.

I also use Access to more efficiently update the glossary using a local copy. Once the updates are made, Ijust export as XMI and import tthe XMI into the master model.

Hope this helps,

Heather

[Heather Wallace]

I would second that. It’s not so easy to see TPos for just the set of things you’re interested in using Access, so it would be a very useful feature to adjust TPos in Excel within a package structure. Can’t think why I didn’t already ask!

Heather

[Heather Wallace]

It wouldn’t work in our case because the eaDocX content is inserted into documents that are far from blank, with title pages, headers, footers, main introductions, sometimes section introductions et. When updating the eaDocX-driven sections I may also notice other things not driven by eaDocX that need updating, so what I want is the final proved document without its generated content to use as a template for next time.

Heather

[Heather Wallace]

OK, that works well. Back down from 36 minuts to 13 using draft mode with no ill effects on the big docuemnt. Unfortunately some of our documents contain matrix reports. These are not formatted by the draft generation process. I guess it will be more time-effective to generate these in a dedicated run as formatting of just the matrices still occurs quickly.

Thanks again,

Heather

[Author]

Posts