Using Papyrus Neon with SysML 1.4, I have created a bdd. Linking blocks with PartAssociation, I get an error message on each association edge when validating the model:
Description: 188.8.131.52 Block  In the UML metamodel on which SysML is built, any instance of the Property metaclass that is typed by a block (a Class with the «block» stereotype applied) and which is owned by an Association may not have a name and may not be defined as a navigable owned end of the association. (While the Property has a «name» property as defined by its NamedElement
Element: <Property> domain : Domain
Type: EMF Problem
I have several questions:
Removing the Name of the second Member End (which is non-navigable and owned by the association), and the validation passes. Is this the right thing to do? If yes, why is this not the standard setting when creating such an association? If no, what should I do? Is this a bug?
The symbol shown for this association path (as well as for the reference association path) has a bullet at the arrow end. It disappears when I set the first Member End's Navigability to false (resulting in Owner changing to Association) and reappears when setting Owner back to Classifier. What does this bullet mean?
For info: I tested also with two installations I used previously (briefly for testing): Papyrus Oxygen has the same problem. PolarSys IDE 0.8 validates just fine these associations.
Hope someone can enlighten me on these issues.
Benoit Maggi Messages: 108 Registered: March 2013 Location: Bordeaux, France
In short the tooling was done way before the validation, then the validation comes and we discover that a lot of element were created non conform to the norm.
So we are currently in the process to modify these elements to avoid validation error on newly created elements.
That said, you can disable "annoying" validation: Window>Preferences>Model Validation > Constraints (uncheck block.propertynoname)