Glossary per project root

[beginner]

The glossary had recently been upgraded slightly by adding custom types (besides Technical and Business). Though this might have helped others in our case it doesn't. We do have multiple project roots where each root represents a real project. And each project does have its own glossary. There are of course a lot of terms on model level common to all projects (the current project glossary). But we also have the need for sub-glossaries per project root.

Currently we have a workaround with xml-like glossary entries. This works but is far from an optimum.

Any ideas?

b.

[Paolo F Cantoni]

After thinking about it a long time and trying all sorts of options over the years, I've come to the conclusion that the ONLY viable solution is to have ONE root node:  "Repository" and have everything else subordinate to it.  As it happens, this is in line with a feature request to have a top level "Reposioty" node I made many years ago.

This just moves everything down one level.  The arbitrary distinctions between Project Roots, Model Views, and Packages is actually, in my view a chimera (given the current state of EA development).

Since I've done this I've suffered a lot less problems.

Moving an existing models down one level is not a hard task for anyone prepared to perform surgery on the DB. Just switch a couple of parent IDs and you're half way there...

HTH,
Paolo

[beginner]

Do I understand you correctly that (in other words) there should be one level introduced above the current root levels which is then called Repository? That would make sense. However, this is only part of the whole truth since you have to introduce model elements (like the glossary, stereotypes, etc.) on different levels with different meaning. Me thinks that EA will not do such a shift. It would impose a re-design of the whole product. And this is something we haven't seen in all the years. They always put new stuff on load of their truck. This is nice and easy with an empty truck (as in the past) but when it's fully loaded you need to think about a new way. They haven't got the balls to do that step. Probably only when it's too late. I've seen similar development elsewhere.

Cassandra b.

[Paolo F Cantoni]

Do I understand you correctly that (in other words) there should be one level introduced above the current root levels which is then called Repository? That would make sense.
[size=18]...[/size]
Cassandra b.

I'm saying I did it manually...  I advise my customers to use only the one root node "Repository" - then everybody is descended from it...

The problem you mention of stuff needed in some places and not in others is a generic problem - not just at the project root level - that's just the minimum partitioning that you might need.

I'm working on ways to solve the more generic problem - with additional processing (and metadata).

Interesting you signed yourself Cassandra today...  I, too, have been disparagingly called Cassandra - to my face!  The person who was "dissing" me obviously didn't know that Cassandra's predictions turned out to be correct...  (as in that case they also did...)

Paolo

[beginner]

Si tacuisses...
We can't probably help other than telling the obvious truth. I always feel wretched to be right in the end...

b.

[mperry247]

I'd like to be able to create a glossary per project and extend hat is held against each. For example a single record that holds, internal term, external term, meaning.

I'd then really like some way of checking the project for terms used.

[Sue Maurizio]

We also had a similar problem, and we solved it by creating a new add-in for managing multiple projects and resources in Enterprise Architect: http://projectweaver.soluta.net/

Sue Maurizio - Soluta.Net