Book a Demo

Author Topic: node vs deivce (EA bug or UML restriction)  (Read 12406 times)

kepNCI

  • EA User
  • **
  • Posts: 127
  • Karma: +1/-0
    • View Profile
node vs deivce (EA bug or UML restriction)
« on: September 28, 2012, 04:31:14 am »
I created a profile for generating network deployment diagrams. I created device stereotypes for all of the hardware including servers. This seems to be in agreement of what I read about devices in that it is just a stereotype for a node which represents a physical piece of hardware.

That being the case, why when I use the Advanced/Parnet... function only stereotypes derived from node are displayed as a choice. None of the device stereotypes are selectable. Is this an EA bug or is there a UNL rule that prohibits a device from being a parent?

Karl

kepNCI

  • EA User
  • **
  • Posts: 127
  • Karma: +1/-0
    • View Profile
Re: node vs deivce (EA bug or UML restriction)
« Reply #1 on: September 28, 2012, 04:39:17 am »
BTW: The Advanced/Instance Classifier... appears to be working the same as the Parent... function, that is, device stereotypes are not displayed as an option.    

Michael Proske

  • EA User
  • **
  • Posts: 72
  • Karma: +0/-0
    • View Profile
Re: node vs deivce (EA bug or UML restriction)
« Reply #2 on: September 28, 2012, 10:42:40 pm »
It is a bug i created a profile based on stereotypes of device but i can't used them with the parent instance classifier dialog. It is a registered bug now. I changed my profile to use only stereotypes derived from nodes. The bug is more than a yera old so don't think it will be solved soon.