When a label type is transformed into an object type (nominalisation), CaseTalk automatically places a totality constraint covering every role the label type used to play.

This transformation is a refactoring step performed on an existing model. At that moment the modeler is reconsidering how the concept is used, and which rules apply to it is part of that reconsideration. Placing a constraint automatically states a business rule the modeler has not expressed, and it has to be located and removed again whenever it is not intended.

In the FCO-IM method the constraint is correct when the transformation happens as part of modelling from examples. As a refactoring action on an existing model, however, the modeler should decide which constraints apply.

We would like the transformation to create only the structure - the new object type, its expression and the uniqueness constraint that identifies it - and to leave the placement of totality constraints to the modeler.