Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [] Plan for SysML 1.5


And remember that SysML 2.x is 'on the way' or perhaps given the lack of consensus amongst the submitters, multiple SysML 2.x's are on the way with no doubt awkward incompatibilities with 1.x.

Even if SysML 1.4 can obsolete SysML 1.1, and SysML 1.5 can obsolete SysML 1.4, it seems unlikely that SysML 2.x will instantly obsolete 1.x so surely the project must have an architecture that supports multiple SysMLs?

The Eclipse UML2 project's inspiration was UML 2.0 from which version migration has been 'comparatively easy'. Model transformation was not available.

In contrast, model transformation is now available, so surely each incompatible SysML could have an independent Ecore-generated model with model transformations to forward/?backward migrate between them. If these model transformations are not already available from OMG, then raise an issue and offer prototypes.


        Ed Willink

On 10/01/2018 16:52, wrote:
Benoît et al.,

I will take the point of view of a SysML industrial Papyrus SysML product user:

  • Are there any known Papyrus SysML industrial users?
    • If so, the next two questions need to be answered and considered as part of this decision.

  • What is the impact of this change for an industrial SysML 1.1 user?
  • What is the impact of this change for an industrial SysML 1.4 user?

From a product governance point of view, the impact of these changes need to be evaluated, both from a user and a development team points of view, and remediation approaches defined and published. If remediation require user actions, these must be published as release notes at the same time as the software release.

Regards / Cordialement,

Charles Rivet
Senior Product Manager / Directeur principal de produits - Zeligsoft
Chairman, Papyrus IC Product Management Committee / Président du comité de gestion de produits du Consortium industriel de Papyrus

On 2018-01-10, at 09:26 , LORENZO Vincent <vincent.lorenzo@xxxxxx> wrote:

Hello Benoît, 
                I’m quite surprised you decided to change the plugin namespace from oep.sysml14 to oep.sysml (which is currently 1.1) for SysML 1.5.
In one hand, this kind of decision implies to force the user to upgrade its profile and forbid to have some model in 1.4 and some others in 1.5.
In other hand, 1.5 is just a new version of 1.4 so it could make sense to force a such upgrade.
De : [] De la part de MAGGI Benoit
Envoyé : mardi 9 janvier 2018 10:54
À : Papyrus Project list <>
Objet : [PROVENANCE INTERNET] [] Plan for SysML 1.5
I checked the SysML 1.5 profile from OMG to plan the next release.
So far:
-          Differences between SysML 1.4 and 1.5:
o   Requirement is split in Abstract Requirement and Requirement
o   Requirement:master change its signature (return a list)
o   All ids have changed L
-          Expected change in Papyrus
o   Rebranding string from SysML 1.4 to SysML 1.5
o   Change namespace from org.eclipse.papyrus.sysml14 to org.eclipse.papayrus.sysml
o   Bump to version 4.0.0 (first major available for org.eclipse.papyrus.sysml)
§  SysML 1.5 (oep.sysml 4.0.0) on Oxygen
§  SysML 1.5 (oep.sysml 5.0.0) on Photon
§  I will try to keep this mapping for the next versions SysML 1.X (oep.sysml X.0.0)
ð  As soon as I got something working, I will push an experimental branch (committers\bmaggi\sysml15)
For the moment, the migration from SysML 1.4 to 1.5 should be quite simple
-          Replace all org.eclipse.papyrus.sysml14 by org.eclipse.papyrus.sysml
Open questions:
-          Switch to the UML generator?
-          How to implement the model migration?
Any remarks/suggestion? 
_______________________________________________ mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

_______________________________________________ mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit


Back to the top