Author Topic: Good ways to mark lost of elements visual as library elements  (Read 1805 times)

PeterHeintz

  • EA User
  • **
  • Posts: 812
  • Karma: +47/-17
    • View Profile
Good ways to mark lost of elements visual as library elements
« on: February 27, 2016, 03:22:52 am »
I have some kind of model library that is intended to be used in other EA repositories.

Basically several user will create content for this model libraries.

The users who use the libraries will import those libraries somehow to their model and use the library more or less as read only elements.

I think it would be good, when the users would be able to quickly find out (e.g. when looking on their diagrams) whether an element belongs to their own work or when it just is a library element or is classified by an element coming from the library.

Currently I belief I should stereotype all that library elements manually or by a script before distribution. So I would be able to define in addition, some visual effects on those elements.
Do any of you, have some better ideas how to achieve such an indication with low effort, maybe even working when the library element is used as an classifier in a project using the library?
Best regards,

Peter Heintz

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 9387
  • Karma: +258/-27
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Good ways to mark lost of elements visual as library elements
« Reply #1 on: February 27, 2016, 03:38:08 am »
Peter,

I think you should look into UML profiles and shapescripts.
You could give your library elements a specific stereotype and attach a shapescript to that stereotype.

Package all of that up in an MDG technology file and deploy it to your users.

Geert

PeterHeintz

  • EA User
  • **
  • Posts: 812
  • Karma: +47/-17
    • View Profile
Re: Good ways to mark lost of elements visual as library elements
« Reply #2 on: February 27, 2016, 04:01:24 am »
Hello Geert
I have already profiles packed in a MDG technology which e.g. introduces a non SysML requirements management language.

I am looking on something that is “cheaper” (low effort).
With uml profile a cheap solution would be, just to define a stereotype which I could use for anything. But I look as well for a solution where I can mark quick anything without treating each of “anything” (classes, activities, ....) individually.
Best regards,

Peter Heintz

qwerty

  • EA Guru
  • *****
  • Posts: 10503
  • Karma: +231/-190
  • I'm no guru at all
    • View Profile
Re: Good ways to mark lost of elements visual as library elements
« Reply #3 on: February 27, 2016, 07:41:13 pm »
I don't think there is any simpler method than using a MDG. The startup is high, true. But using it is very simple compared to anything else.

q.

Glassboy

  • EA Practitioner
  • ***
  • Posts: 1301
  • Karma: +103/-75
    • View Profile
Re: Good ways to mark lost of elements visual as library elements
« Reply #4 on: February 29, 2016, 07:04:16 am »
Also, remember that the MDG approach is the lowest cost approach for making fixes and changes.  You simply update the shared file and the users get the results.  Imported profiles et al quickly become a PITA.

PeterHeintz

  • EA User
  • **
  • Posts: 812
  • Karma: +47/-17
    • View Profile
Re: Good ways to mark lost of elements visual as library elements
« Reply #5 on: February 29, 2016, 07:50:41 pm »
Ok! Thank you!
Just I wanted to be sure that there is no low effort solution.
I will go the MDG way.
Best regards,

Peter Heintz