What is the Applies to Base Class list?

[Paolo F Cantoni]

In a related topic, [size=13]New Applies to Base Class list entries[/size] I imply that the only things that should appear in the Base Class list should be:
<connectors>,
<elements> and
<features>.

But comparing the list of such things (for example Change Type dropdowns for Elements and Connectors), there is only a passing resemblence between the two.

In addition, there are entries in the stereotype list that don't appear in the dropdown.

Can someone from Sparx (or anywhere) provide a list of the values that can appear there and what the value applies to...

Confused...
Paolo

[KP]

Can someone from Sparx (or anywhere) provide a list of the values that can appear there and what the value applies to...

The short answer: Drop a Metaclass element from the Profile toolbox onto a diagram. In the Create New Metaclass dialog, set the "Include Extended" option. You may use any of the values now shown in the Create New Metaclass dialog in the "Base Class" field on the Stereotypes dialog.

The longer answer will take longer to come up with...

[Paolo F Cantoni]

The short answer: Drop a Metaclass element from the Profile toolbox onto a diagram. In the Create New Metaclass dialog, set the "Include Extended" option. You may use any of the values now shown in the Create New Metaclass dialog in the "Base Class" field on the Stereotypes dialog.

The longer answer will take longer to come up with...

Thanks for that KP,

Perusing the list (on the left hand side) it would appear that by entering  Feature, Attribute or Operation I can almost solve the suggestion for [size=13]New Applies to Base Class list entries[/size].  Does the right hand "Connector" checkbox mean any Connector or a UML2 Connector (section 8.3.2)?

Assuming the latter, it would appear that adding <Elements> and <Connectors> (as synthetic entries in the Applies to list) should actually fix my problem.

Have I understood correctly?

Paolo

[KP]

Does the right hand "Connector" checkbox mean any Connector or a UML2 Connector (section 8.3.2)?

It's the specific UML metaclass named "Connector".

The word "Connector" also gets used as a synonym for the generic "Relationship". Confusing, but UML haven't left us many words to choose from...  

[Eve]

Feature applies to Feature elements (look in the requirements toolbox) not both Attributes and Operations.

[Paolo F Cantoni]

It's the specific UML metaclass named "Connector".

The word "Connector" also gets used as a synonym for the generic "Relationship". Confusing, but UML haven't left us many words to choose from...  

I happened to be thinking about that (UML not leaving us too many names) this morning.  In my own conceptual modelling tool which I developed, over 10 years ago now, I used the very pragmatic "shapes" and "lines" - however.  A model consisted of shapes connected by lines.

However, now that I'm a har-falutin' architect  

I'd use vertexes (for shapes) and edges (for lines).

In fact, to relieve confusion, Sparx might want to adopt it for their documentation...

Paolo

[size=0]©2006 Paolo Cantoni, -Semantica-[/size]

[Paolo F Cantoni]

Feature applies to Feature elements (look in the requirements toolbox) not both Attributes and Operations.

Thanks for that Simon, it slipped through...

Paolo