Book a Demo

Author Topic: Domain model and project glossary  (Read 13266 times)

mike08

  • EA User
  • **
  • Posts: 20
  • Karma: +0/-0
    • View Profile
Domain model and project glossary
« on: October 03, 2014, 10:42:22 pm »
Hi,

I'm trying to develop a domain model on an UML class diagram using class objects. Following the ICONIX process this model will eventually converge to (among other things) act as project glossary.
Now, EA has a glossary database but I seem to have the following issues when using it during the domain modelling:
- I can not enter the names of classes as terms in the project glossary (e.g. via right mouse click -> create glossary definition) which works for terms from within e.g. the notes field.
- Changes to the project glossary are not updated for all their occurances within my model.

Well, as changing the names of terms in the object model is one of the main activities it is difficult to keep track/sync with the glossary.
I also tried to skip the derivation of the glossary from the domain model during model updates and only do it at the end of the development. This still does not solve yet another issue:
I want to use the proper terms from my domain model in my use cases. Using the project glossary does not work (reason see above), inserting links to classes in the domain model does not work either as changing the name of an object in the domain model is not backpropagated to its link within the use case.

What am I doing wrong here? Is there a way to consistently use terms in an evolving domain model and some use cases simultanely in EA?

Many thanks for your hints!
Mike

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Domain model and project glossary
« Reply #1 on: October 03, 2014, 11:12:38 pm »
Regarding the issue to put class names into the glossary I think this would not make sense. Classes are on a higher level and they base on glossary terms coming from "outside".

I can't say much about your other issue. I did not use the glossary as it is but modeled my own glossary from <<term>> elements which allows a much more flexible handling. Especially if you combine it with a few scripts.

q.

mike08

  • EA User
  • **
  • Posts: 20
  • Karma: +0/-0
    • View Profile
Re: Domain model and project glossary
« Reply #2 on: October 07, 2014, 06:17:36 pm »
Thanks for your reply. Indeed, moving to <<term>> objects does simplify the scripting quite a bit.

The linking issues resolved itself: the link names within the scenario editor are updated according to the target objects only after you close and reopen it.

Best,
Mike