Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 447130

Summary: [uml-pivot] Provide a validate/not-validate control capability for UML Instance validation
Product: [Modeling] OCL Reporter: Ed Willink <ed>
Component: CoreAssignee: OCL Inbox <mdt-ocl-inbox>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: P3    
Version: unspecified   
Target Milestone: RC2   
Hardware: PC   
OS: Windows NT   
Whiteboard:
Bug Depends on:    
Bug Blocks: 417062    

Description Ed Willink CLA 2014-10-14 11:16:06 EDT 
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 <<Validity>>::shouldBeValid could be published in the same profile.
Comment 1 Ed Willink CLA 2015-05-21 04:47:39 EDT 
Just one of the facilities of the OCLforUML profile appearing in Mars RC2.

*** This bug has been marked as a duplicate of bug 467686 ***