Issue Creating new Stereotype from Requirement

[Brian Selvy]

I'm trying to create a new stereotype, using the SysML Requirement stereotype as the point of extension.  I've followed the steps outlined on the page "Create Stereotypes Extending non-UML Objects" at:  http://www.sparxsystems.com/enterprise_architect_user_guide/10/extending_uml_models/non_uml_metatypes.html

However, I created a new set of attributes that I want to be part of the new stereotyped element, but when I create a new element stereotyped by my newly defined stereotype, none of the attributes come through.  The documentation on any needed linkages between attributes and Tagged Values for stereotypes extended from a SysML object is almost non-existent.  

Has anyone been successful in creating new stereotypes extended from SysML elements? If so, can you point me to a good reference on how to properly set them up or walk through the steps?

[qwerty]

The problem here is that Sparx lets you stand alone in the rain if your MDG is not 100% correct. There is no trace, no debug, no hint. Just it does not work. Thus it is difficult to support you via the forum. There are a couple of threads here that deal with extending existing profiles (not necessarily SysML but that does not matter).

Have you had success already to create a simple MDG and deploy that?

q.

[Brian Selvy]

I created an MDG Technology file and deployed it.  I checked to see if it's loaded, and it looks like it is.  I can access my new stereotype by selecting "New Element", clicking "Select Toolset", clicking on "Stereotype Profiles", and then I see the stereotype I created in the "Type" pulldown menu.

I was really hoping to create a new "type" of requirement with additional properties, but I don't know how to get my new stereotype to show up as a new "type" of the existing SysML requirement stereotype.

As of right now, when I create a new element with the new stereotype applied, none of the custom attributes show up.  All I see are the basic requirement attributes of "id" and "text".

[qwerty]

All I could say is that you need to <<extend>> some class metatype from the SysML profile. You need to look into the SysML MDG how the prefix is named. Either SysML or SysML2 or whatever. In the first case your metaclass would be names something like SysML::Block (for a SysML block).

Can't be of much help since it's too long ago and buried somewhere in my brain.

q.

[Brian Selvy]

I figured it out with the help of a coworker who was able to point me to a great resource - Enterprise Architect Product Demonstrations (http://www.sparxsystems.com.au/resources/demos/index.html)


This video explains exactly how to create a new stereotype:  http://www.sparxsystems.com.au/resources/demos/profile-helpers/profile-helpers.htm