Requirements stereotypes for SysML in EA 7.5

[deefer]

Hi
I'm evaluating EA 7.5 SysML version

I have noted that the stereotypes for the sysml requirements no longer include the functional requirement, extended requirement, interface requirement, performance requirement, design requirement and physical requirement.

I have a model developed with EA 7.1 with SysML where I've used these kind of reqs.

Is it possible to get these missing stereotypes back?

Thanks a lot!
Davide

[«Midnight»]

First, make sure you are using one of the new high-end EA editions. The SysML add-in has been integrated into these. Check the Sparx Web site for details on which two editions include the add-in. [I think it is the Systems Engineering and Ultimate editions, but you should verify that yourself.]

Take a look at the tagged values. I suggest opening and docking the Tagged Values window, then selecting several of these elements in one of your models.

Note that you might have to create a new SysML model from scratch, then build a (simple) requirement element. See if any of the tagged values is a list type. If you click on the value space for each tagged value, you might then see a drop-down indicator. [Note that the value might or might not be empty up to this point, depending on whether Sparx has defined a default value.] See if any of the lists provides the values you want. If so, choose a (non-default) value and see if the element redraws itself as one of the specialized types you are seeking.

I'd do this for you, but I have not upgraded my EA 7.5 production license (I don't want to throw away my investment in a partial year of a corporate license).

Please let us know what you find.

David

[deefer]

Thank you David

I'm using the 7.5 Systems Engineering version.

Let's put it in this way... I open the EAexample project provided by Sparx.
If i go to the requirements model of the SysML example I can see some requirements. The only thing that I can change in their properties (the tags contain only the ID) is the stereotype which can be "Performance", "Functional" or simple "requirement".

The mentioned stereotypes present in the 7.1 version of SysML add-on are no longer present.

So, I've decided to build the stereotypes by myself and put them in a custom profile...

Everything now seems ok (I can select the stereotype of the requirements from the req stereotypes that I've created).   [smiley=2vrolijk_08.gif]

The only thing that is annoying a little bit is that when I drop down let's say the functionalRequirement that I've created, the default display mode of the requirement doesn't show the req stereotype (<<functionalRequirement>>), so I have to change the view of the req to Rectangle notation. This behaviour is different compared to the built-in SysML requirement stereotype, which is immediately drawn in the rectangle notation as soon as I drop it... not a big issue, but a little annoying expecially for other people that will use the modl and that doesn't know that.

By the way... is there any possibility to reuse the SysML stereotypes and to derive from them other custom stereotypes? [smiley=rolleyes.gif]

Thank you very much!
Davide

[«Midnight»]

I'm not sure...

As an experiment, what happens if you prefix one of the stereotypes with SysML:: (punctuation included; there are 2 colons)?

You might have to play around a bit. Remember that stereotypes are case sensitive, so you may need to try several combinations of upper and lower case (for both the prefix and the rest of the stereotype). Do any of the 'qualified' stereotypes make a difference?

[deefer]

Hi David
I've tried your suggestions but no success... I would expect some extra tags to appear in the requirements stereotyped by SysML::functionalRequirement and so on (the ones defined in the SysML spec 1.1, appendix C), as it was in ea 7.1, but no extra tags appear...

It seems that, since these kind of requirements are non-normative, Sparx has decided to remove them...
Thanx anyway!

P.s.
do you know how to recycle SysML stereotypes (see my initial post)?

[«Midnight»]

Ouch!

Let's hope the Sparxians chime in with some enlightenment on this.

In the meantime, here's an experiment you can try. Make sure to use copies of your models though.

If possible use EA 7.1 to open an older project, one that shows the additional stereotypes. Export the stereotype reference data. Open one of your newer SysML projects in EA 7.5 and import the reference data from the older project. Did EA transfer the 'old' stereotypes?

Please post back either way and let us know what happens.

If you now see the stereotypes, make sure you include this fact on the bug report you will send to Sparx regardless of the outcome here. [Note the subtle hint!]

David

[deefer]

Hi
I've tried your experiment but, since the SysML requirements are not part of the gerenal types, the export/import reference data doesn't transfer them...

Many thanx
Davide

[«Midnight»]

Well, get a bug report or a support request in to Sparx. Perhaps they can shed some light on this, or even resolve the problem.