Applying Glossary terms to a subset of the Model

[aniforatos]

Hello All,

I have a question surrounding glossaries, and I really feel like I cant be the only one to desire this:

I am utilizing the model based glossary. I am creating Glossary entries for some definitions that I want to apply specific packages (not the entire model).

Example, I have a term called "Permission", I dont want to have the definition of "Permission" show up in a note, block, requirement, etc. in Package A but I DO want it to appear in Package B.

Right now, "permission" gets underlined and highlighted with my unique definition whenever I write it in the model.

Thanks in advance!!

[Modesto Vega]

You may be able to achieve the desired result by using the functionality described in https://sparxsystems.com/enterprise_architect_user_guide/16.1/modeling_fundamentals/glossary_package_struct.html. It is new to the latest version of Sparx EA but I have never tried it.

With the previous glossary functionality, what you describe in the OP was not possible.

[Geert Bellekens]

You may be able to achieve the desired result by using the functionality described in https://sparxsystems.com/enterprise_architect_user_guide/16.1/modeling_fundamentals/glossary_package_struct.html. It is new to the latest version of Sparx EA but I have never tried it.

With the previous glossary functionality, what you describe in the OP was not possible.

No, glossary entries are "global".

There is no way to limit them to a certain branch of the model.

You could send in a feature request, but I'm not sure if this would get much traction.

Geert

[aniforatos]

Sad news, but thank you for letting me know!

[Modesto Vega]

Thank you Geert, somehow I am not too surprised.

This takes us back to a conversation that we have had several times in this forum: how Sparx EA implements or does not implement the concept of "model"?

Glossaries should be model specific not repository specific, Sparx EA does not really have a concept of "model" as separate from a package or a repository.

[qwerty]

They probably respond: make model==repository.

q.

[Modesto Vega]

They probably respond: make model==repository.

q.

Thank you qwerty, you are most likely correct. Strictly speaking that means that an Enterprise Model is a repository, and a model for each application in the enterprise model (both "As Is" and "To Be") will need a dedicated repository. I am not sure if this is very elegant or manageable (think dependencies). I know Sparx EA is flexible enough not to currently require using this approach.