Book a Demo

Author Topic: 1 or many metaclasses  (Read 3241 times)

Modesto Vega

  • EA Practitioner
  • ***
  • Posts: 1183
  • Karma: +30/-8
    • View Profile
1 or many metaclasses
« on: March 12, 2019, 08:20:25 pm »
I have noticed that when creating a profile I can drop a metaclass and connect to it as many stereotypes as I need or add a metaclass per stereotype. For example, I can add a Class metaclass to the profile and connect to it 2 stereotypes, plane and helicopter or I can add 2 Class metaclasses and connect the plane stereotype to one and the helicopter stereotype to the other. Does it actually make a difference?

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: 1 or many metaclasses
« Reply #1 on: March 12, 2019, 08:51:44 pm »
There is no difference (in most cases; see Geert's following answer). In fact I use a package for the metaclasses already in use to re-use them.

q.
« Last Edit: March 12, 2019, 09:23:19 pm by qwerty »

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: 1 or many metaclasses
« Reply #2 on: March 12, 2019, 08:57:31 pm »
Yes, a number of properties of your stereotype are stored on the metaclass element
(e.g. meaningForwards and meaningBackwards for connectors)

In order to avoid running into issues I recommend using one metaclass per stereotype (the profile helper does it this way as well)

Geert

Modesto Vega

  • EA Practitioner
  • ***
  • Posts: 1183
  • Karma: +30/-8
    • View Profile
Re: 1 or many metaclasses
« Reply #3 on: March 13, 2019, 04:36:31 am »
Thanks qwerty and Geert