Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » Papyrus » Sysml14 Trace stereotype not extending Trace stereotype from standard profile?
Sysml14 Trace stereotype not extending Trace stereotype from standard profile? [message #1746634] Wed, 02 November 2016 10:52 Go to next message
Andreas Pleuss is currently offline Andreas PleussFriend
Messages: 18
Registered: June 2015
Junior Member
Hi,

in SysML14 version 0.7 the stereotype "Trace" extends the "Trace" stereotype from the UML standard profile as defined in the SysML specification.
But since version 0.8 this stereotype extension seems to be missing (though base_Abstraction is defined as a redefined property).
Is there a reason for this?

Many thanks,
Andreas
Re: Sysml14 Trace stereotype not extending Trace stereotype from standard profile? [message #1746640 is a reply to message #1746634] Wed, 02 November 2016 12:12 Go to previous messageGo to next message
Klaas Gadeyne is currently offline Klaas GadeyneFriend
Messages: 165
Registered: July 2009
Senior Member
Andreas Pleuss wrote on Wed, 02 November 2016 06:52
Hi,

in SysML14 version 0.7 the stereotype "Trace" extends the "Trace" stereotype from the UML standard profile as defined in the SysML specification.
But since version 0.8 this stereotype extension seems to be missing (though base_Abstraction is defined as a redefined property).
Is there a reason for this?


Hi Andreas,

AFAICT, at least in version 0.10 the Trace stereotype is present? Could you elaborate a little bit on how you come to the conclusion that is missing?

BR,

Klaas

Re: Sysml14 Trace stereotype not extending Trace stereotype from standard profile? [message #1746659 is a reply to message #1746640] Wed, 02 November 2016 14:39 Go to previous messageGo to next message
Andreas Pleuss is currently offline Andreas PleussFriend
Messages: 18
Registered: June 2015
Junior Member
Hi Klaas,

Thanks for your quick reply.

What I mean is, not the Trace stereotype itself is missing but its generalization relationship to the Trace stereotype from the UML standard profile.
In sysml14 v0.7 the Trace stereotype generalizes both, DirectedRelationshipPropertyPath and Trace from standard profile (as specified in the SysML specification). Since v0.8 it generalizes DirectedRelationshipPropertyPath only.

This makes a (little) difference when working with the Ecore implementation of the sysml profile as org.eclipse.papyrus.sysml14.requirements.Trace no longer extends org.eclipse.uml2.uml.profile.standard.Trace. For instance, its feature base_Abstraction is now defined in org.eclipse.papyrus.sysml14.requirements.RequirementsPackage instead of in org.eclipse.uml2.uml.profile.standard.StandardPackage.

The same holds for the stereotype "Refine".

So I was wondering if this is by intention and why? Or maybe I'm overlooking something?

Best regards,
Andreas
Re: Sysml14 Trace stereotype not extending Trace stereotype from standard profile? [message #1746693 is a reply to message #1746634] Thu, 03 November 2016 10:36 Go to previous messageGo to next message
Benoit Maggi is currently offline Benoit MaggiFriend
Messages: 129
Registered: March 2013
Location: Bordeaux, France
Senior Member
Hi Andreas,

Indeed, but there is no "intention" behind that.
(I didn't know that the generalization was present in SysML 1.4 v0.7)

The main reason is that v0.7 was built using the WorkInProgress xmi file from the OMG and v0.8 was built using the official release.
The generalization wasn't present in the Official XMi (whereas still present in the pdf norm)

The problem is reported here:
Eclipse: https://bugs.eclipse.org/bugs/show_bug.cgi?id=497650
OMG: http://issues.omg.org/issues/SYSMLR-281

Does it block one of your real use case?

Regards,
Benoît
Re: Sysml14 Trace stereotype not extending Trace stereotype from standard profile? [message #1746697 is a reply to message #1746693] Thu, 03 November 2016 11:03 Go to previous message
Andreas Pleuss is currently offline Andreas PleussFriend
Messages: 18
Registered: June 2015
Junior Member
Hi Benoît,

Thanks for clarification. No, it doesn't block anything, we just have to be aware of it.

Best regards,
Andreas
Previous Topic:Papyrus error (org.eclipse.emf.ecore.xmi.IllegalValueException: Value '0.0' is not legal.)
Next Topic:Setting values for stereotype properties typed by profile defined classes
Goto Forum:
  


Current Time: Sat Jul 11 15:21:18 GMT 2020

Powered by FUDForum. Page generated in 0.02189 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top