Book a Demo

Author Topic: Type specification in MDG  (Read 2551 times)

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Type specification in MDG
« on: December 15, 2009, 02:57:16 pm »
When I create an instance of the TOGAF model (or Zachman) for that matter, I get a set of predefined objects.  An example of this might be ZFCell from Zachman or ADM_xxxx from TOGAF.  I presume these have been defined in an MDG environment like the ones we get to use when we're creating our MDG Technologies.

When I select one of these objects, and view the Properties Window I see: Stereotype=ZFCell and Type=ZFCell.  Another example (not a package) is an Artifact «Mission».  It, too, shows Stereotype=Mission and Type=Mission.  Further, when I open the Properties Dialog the caption shows: "Mission:".

However, when I create a stereotype with my MDG Technology (I extend Activity to create PM.Execution stereotype), I see: Stereotype=PM.Execution and Type=Activity.  Is there a secret handshake that Sparx use to get the type? I've had another look at the Help and I can't seem to find any direct reference.

TIA,
Paolo
« Last Edit: December 15, 2009, 03:05:26 pm by PaoloFCantoni »
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

Aaron B

  • EA Administrator
  • EA User
  • *****
  • Posts: 941
  • Karma: +18/-0
    • View Profile
Re: Type specification in MDG
« Reply #1 on: December 15, 2009, 03:19:27 pm »

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Type specification in MDG
« Reply #2 on: December 15, 2009, 05:45:03 pm »
Quote
You have to define your stereotype as a "Metatype".  See:
http://www.sparxsystems.com/uml_tool_guide/sdk_for_enterprise_architect/defining_a_stereotype_as_a_met.html
Thanks Aaron,
I thought it might be that, but since I never got that deep in the help I didn't fall across it.

Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!