Legacy Issue Number: 7972
I been using rational rose and bold for delphi in some projects. This have worked very well for me.
When adding constraints to my models i have some times whished that there whas a way to do this
on different levels. Eg. error-constraints (if persisted the object would be a dirty data) ,
warning-constraints these can be broken but there is high probability that the object is ill formed from the
system user perspective (example a new customer whith no billing adress) and finally a hint-contraint that
when broken indicates that the object containes strange data (example a new customer object with the
same phone number as a existing customer)
My own solution to this have been to add contraints of the first type to the model. This have enabeld me
to create generic code dealing with if the user should be allowed to save a object or not.
The other types of constraints have been added as coments as a way to make the model as complete as
possibel. The implementation of checking and dealing with these constraints later in the project have ben
solved in a mutch less generic and cumbersom way.
I thin´k that if the standard included a way to specify different levels of ocl statements in the model this would
benefit the model driven way to make software
Reported: OCL 2.0b2 — Fri, 10 Dec 2004 05:00 GMT
Updated: Thu, 8 Oct 2015 14:12 GMT
OCL25 — OCL Constraints in many levels
- Key: OCL25-105
- OMG Task Force: OCL 2.5 RTF