Discouraged to use stereotypes in SysML models

[jmarzouki]

Dear All,
I have been discouraged to use stereotypes in EA SysML models because I will end up with hundreds of them. Rather, I was recommended to use element properties.
I don't want to get into all stereotype rationale but aren't they the base of SysML. This does not make sense as nothing prevents their use especially in Systems Engineering modeling. How can one end up with hundreds of stereotypes?
I am a freshman to EA (not to SysML) and used other competitor tools on big projects where stereotypes were a core artifact for SysML models. I was wondering if this is particular to EA?
Any comment is very much appreciated!!
Many thanks in advance,
Best Regards,

[qwerty]

I'm not sure what you're idea about stereotypes is. But to me it sounds a bit weird.

q.

[Geert Bellekens]

I agree with q. Stereotypes and element properties are not interchangeable at all.

Maybe if you describe your issue in more detail we might give you some advice.

Geert

[jmarzouki]

Thank you q. thank you Geert,
Agreed for stereotype and property!  I am for using stereotypes!

I think you said it and I fully agree: it is weird!
The recommendation was instead of using stereotype such <<electrical>>, <<mechanical>>, <<fluidic>>, <<data>> applied to block, use an associated attribute of type enum (electrical, mechanical, fluidic, data).

This was also the case for Part Number as it was recommended to use an attribute. I switched it to a tag!

Thank you much,
J.

[Geert Bellekens]

Stereotypes are for indicating different metatypes.

This is usually done in order to add additional properties or relations to such a metatype.

So if for electrical components, you need to register the voltage, you could create a stereotype that extends an existing SysML stereotype and add Voltage as a property of that stereotype.

If it's only to make the difference in subtype, you are probably better of storing the subtype in a tagged value.

Anyway, if you decide to use stereotype, you should definitely define them in a UML profile and distribute them with an MDG technology.
"Wild" stereotypes are a menace.

Geert

[qwerty]

Just one remark: "tagged values" should be "stereotype properties". The first are what had been used with those "wild" stereotypes not belonging to a profile.

q.