Define constraints for the component diagram

Cooperate-Project / CooperateModelingEnvironment

Modeling environment for UML modeling by diversity teams (sighted and visual impaired people).

Eclipse Public License 1.0

6 stars 3 forks source link

Define constraints for the component diagram #224

Open joehen opened 6 years ago

joehen commented 6 years ago

Define constraints for the allowed elements in a cooperate component diagram. I.e. find illegal graphical diagram that need to be constrained...

seiferma commented 6 years ago

We should provide a natural language based list of constraints that have to hold based on the implemented transformation. @joehen Could you provide this list?

joehen commented 6 years ago

My initial ones: In textual diagram: a port is only allowed to be present in connector once (special case for attributes that have a port, thus the same port can be present for different attributes)

two ports connected with a connector shall have compatible types (might even work elsewise)

In Papyrus: The classifier of a Port or a Component must reside in the same diagram A connector shall have a name (at least by now)

joehen commented 6 years ago

In cgs components are not allowed to be abstract (not (yet?) supported by cts)