You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our current transformations are inconsistent in how they name the UML model:
PCM→UML: Call the modcel "umlrootmodel"
Java→UML: Ask the user for the name
This is also inconsistent in so far as that a UML model roughly corresponds to a PCM Repository. For PCM repositories, we derive the name from the package name in the Java→PCM transformation. For a UML model, we don’t. On the other hand, giving the model the name of the first package does not make sense for the Java→UML transformation if it isn’t used together with the PCM transformation.
My proposal: Let’s not set any name on the UML model at all, since the name is unsettable. There are other possible solutions, of course, but I think we should settle for a consistent one.
The text was updated successfully, but these errors were encountered:
Our current transformations are inconsistent in how they name the UML model:
PCM→UML: Call the modcel
"umlrootmodel"
Java→UML: Ask the user for the name
This is also inconsistent in so far as that a UML model roughly corresponds to a PCM Repository. For PCM repositories, we derive the name from the package name in the Java→PCM transformation. For a UML model, we don’t. On the other hand, giving the model the name of the first package does not make sense for the Java→UML transformation if it isn’t used together with the PCM transformation.
My proposal: Let’s not set any name on the UML model at all, since the name is unsettable. There are other possible solutions, of course, but I think we should settle for a consistent one.
The text was updated successfully, but these errors were encountered: