This shows you the differences between two versions of the page.
sem_2 [2013/04/05 08:14] arnaud created |
sem_2 [2013/05/24 12:00] (current) arnaud |
||
---|---|---|---|
Line 7: | Line 7: | ||
* Issues: | * Issues: | ||
- | * How to properly determine that an operation is a <<create>> operation? | + | * <del>How to properly determine that an operation is a <<create>> operation?</del> |
- | * Currently, the solution is implementation specific (Eclipse UML2) | + | * <del>Currently, the solution is implementation specific (Eclipse UML2)</del> |
* How do we manage operation dispatching (i.e., a parent class has a constructor operation with a method. Should we execute it before performing default construction?) | * How do we manage operation dispatching (i.e., a parent class has a constructor operation with a method. Should we execute it before performing default construction?) | ||
* TODOs: | * TODOs: | ||
- | * When instantiating values for parts, the default construction strategy is systematically applied. | + | * <del>When instantiating values for parts, the default construction strategy is systematically applied.</del> |
- | * It should be used only if the type of the part has a <<create>> operation, and this operation has no method. If it is not the case, construction should follow conventions of the Alf to fUML mapping for an instance creation expression. | + | * <del>It should be used only if the type of the part has a <<create>> operation, and this operation has no method. If it is not the case, construction should follow conventions of the Alf to fUML mapping for an instance creation expression.</del> |
- | * Start classifier behavior of classes constructed for parts | + | * <del>Start classifier behavior of classes constructed for parts</del> |
- | * Account for default values when instantiating values for parts | + | * <del>Account for default values when instantiating values for parts</del> |