Hi
I’m confuse by the implementation of RequirementLink. As illustrated in the following figure, in Capella with two way of creating RequirementLink with to different way to store RequirementLink in “.capella” file.
What is the meaning of relating a requirement to a Part instead of relating it to the corresponding AbstractType of the Part? Why not, while using the Palette of Diagram, also relate the RequirementLink to the data object available from Part using #getAbstracType() method?
Doing this way would have provided the same implementation as for object without Part (e,g. Function) and simplify the way of query a Capella model to get Requirements and their incoming or outgoing relations.
Kind Regards,
Valery