Bug 487728 - Creating InstanceSpecifications of Associations yields unexpected results
Summary: Creating InstanceSpecifications of Associations yields unexpected results
Status: NEW
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: 1.1.3   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-12 06:46 EST by Yves BERNARD CLA
Modified: 2019-09-09 03:29 EDT (History)
2 users (show)

See Also:

Attachments
Sample model (22.29 KB, image/png)
2016-02-12 06:46 EST, Yves BERNARD CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Yves BERNARD CLA 2016-02-12 06:46:22 EST 
Created attachment 259726 [details]
Sample model

In the screenshot attached we can see a simple model with two classes: Class1 and Class2 with an association A1 between them. One end of this association has a [1..*] multiplicity.

Below, I defined one instance of Class1 (is1) and  two instances of Class2 (is2), then I created two links as A1 instances.

The Model Explorer on the left side shows the result:
a) 2 slots are created on the is1 instance for the class2 Property
b) 2 instances of A1 are created

Point (a) clearly violates the UML::InstanceSpecification::structural_feature constraint (see UML 2.5, §9.9.9.6): it cannot have more than one slot for a given feature (but this slot can have more than one value). It's less obvious for point (b) but I believe that only one instance of the association should be created as well.
Comment 1 Vincent Lorenzo CLA 2018-12-20 11:03:09 EST 
Validation rules must be added to UML. 
We plan to open a bug to UML2 project for 4.3.0 releases
Comment 2 Vincent Lorenzo CLA 2019-03-07 09:00:11 EST 
postponed
Comment 3 Nicolas FAUVERGUE CLA 2019-09-09 03:29:12 EDT 
Postponed again.