| --- | --- |
| Bugzilla Link | 447130 |
| Status | RESOLVED DUPLICATE of bug 467686 |
| Importance | P3 normal |
| Reported | Oct 14, 2014 11:16 EDT |
| Modified | May 21, 2015 04:47 EDT |
| Blocks | 417062 |
| Reporter | Ed Willink |
Description
Using UML Instances to test UML constraints can be useful, but not all UML Instance diagrams represent valid states, so validating always could be really irritating.
Suggest a diagram level profile that can be applied to define a control. Perhaps all finer grain apploication on individual instances/classes.
If OCL has to provide a small profile to define Integer/Real precisions then another stereotype for <>::shouldBeValid could be published in the same profile.
| --- | --- | | Bugzilla Link | 447130 | | Status | RESOLVED DUPLICATE of bug 467686 | | Importance | P3 normal | | Reported | Oct 14, 2014 11:16 EDT | | Modified | May 21, 2015 04:47 EDT | | Blocks | 417062 | | Reporter | Ed Willink |
Description
Using UML Instances to test UML constraints can be useful, but not all UML Instance diagrams represent valid states, so validating always could be really irritating.
Suggest a diagram level profile that can be applied to define a control. Perhaps all finer grain apploication on individual instances/classes.
If OCL has to provide a small profile to define Integer/Real precisions then another stereotype for <>::shouldBeValid could be published in the same profile.