Skip to main content

Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » Papyrus » SysML 1.2 supported by Papyrus?
SysML 1.2 supported by Papyrus? [message #773885] Mon, 02 January 2012 20:10 Go to next message
Bryce Nordgren is currently offline Bryce NordgrenFriend
Messages: 3
Registered: January 2012
Junior Member
I'm just starting with SysML and I'm using Topcased 5.1/Papyrus to start fiddling. I'm finding myself stuck at the very beginning (with units/quantities). As I read the 1.2 spec, the correct way (meaning normative: sections thru to deal with units is to use the QuantityKind, Unit, and ValueType stereotypes, where Unit has an optional quantityKind property and ValueType has optional quantityKind and unit properties.

I seem to be unable to locate the QuantityKind stereotype, which sort of brings the whole house of cards tumbling down. I'm also wondering how one would assign values to "stereotype properties".

I was attempting to implement the informative units models in annex C.4 and/or C.5.

In addition, the "primitive types" library does not appear to define "Real", "Integer", etc. with the ValueType stereotype, as shown in Figure 8.7. However, there is a better than fair chance that I just don't know how to look for stereotypes on objects in an imported package.

The sum of this leaves me with the impression that SysML 1.2 may not be supported. Is that true or do I just need to be educated? Smile

Re: SysML 1.2 supported by Papyrus? [message #774175 is a reply to message #773885] Tue, 03 January 2012 12:20 Go to previous message
Raphael Faudou is currently offline Raphael FaudouFriend
Messages: 105
Registered: July 2009
Senior Member
Hi Bryce,

you are right, currently Papyrus only supports SysML 1.1. There are efforts to switch to SysML 1.2 but I can not give you detailed planning for now.
Concerning SysML stereotypes attributes, you can set values through the property view, SysML tab. for other user-defined stereotypes, use the "profile" tab.
To disaply the stereotypes attributes, you must use the "appearance" tab of the property view.
You will information and practical examples in this TOPCASED tutorial about UML/sysML features:

Kind regards
Previous Topic:Disposing editor Parts on Close
Next Topic:Programmatically configure visible palette for diagram
Goto Forum:

Current Time: Mon Apr 19 19:57:33 GMT 2021

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

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

Back to the top