recommend EA14.1 or EA15 with respect to Stereotypes?

[ngong]

I was reminded to start a new topic instead of commenting this: https://www.sparxsystems.com/forums/smf/index.php/topic,42731.msg253782.html#msg253782.

I am about to recommend to switch from EA13.0 (1306) to EA14.1 or EA15.
The current model - maintained by 10+ engineers - use stereotypes without providing a profile.

What do I have to expect if switching to EA15 regarding stereotypes (will the team kill me)?

A short report from your experience would be helpful.

Rolf

p.s. I would like to recommend to provide a profile. Usually that is not so much work. But how much work has to be done to exchange the existing stereotypes at each element by the profile-based ones in a 600MB model?

[Geert Bellekens]

I don't think there's too much difference, except for the fact that you can no longer just type a stereotype. You always have to select an existing one.

Updating existing stereotypes to stereotypes from a profile won't take too much time.
I've done this before with a small script.

Geert

[Eve]

I would absolutely 100% suggest migrating to EA 15 explicitly for the stereotype handling.

Some people will find the fact that you can't type in stereotypes inconvenient. They will get used to it. More importantly they will actually know what stereotype you are applying.

The properties window will now display fully qualified stereotype names and all stereotypes applied. Where the point above helps to avoid making mistakes, this helps you to identify mistakes that have already been made.

Stereotype properties (and unstructured tagged values) are the biggest UI change related to stereotypes. Tagged values from a profile are fully integrated into the properties window. If you're using a lot of unstructured tagged values your team may get upset. They lose the dedicated window, being relegated into a page within the properties window. It's a big win if you're using a profile, a small loss if you're not.

[ngong]

Thank you Eve and Geert for encouraging me convincing the team for EA15.

Geert, would you mind to provide your script to me - sure, without any warrenties?

Rolf

[Geert Bellekens]

It's somewhere in this script: https://github.com/GeertBellekens/Enterprise-Architect-VBScript-Library/blob/master/Projects/Project%20BRO/BRO%20Scripts/SetTraceabilityMain.vbs

It does a lot more then only updating stereotypes. It first creates a copy of the packages, then sets traceability to the original package, and then transforms the new package, renaming stereotypes etc..

Geert