The Users Guide should have more entries within it: 'sort', for example. And the definitions, like the old DEC manuals, some warnings and contrasts. By way of definition, enumerated types can be set up in the same way that constraints can be, just different formats.
e.g., Bowlspeed: enum= 120, 270,300
or e.g.,
active: bool, sensorGroupID: enum
And now a
Constraint: {BowlSpeed = 120,370,300}
What is the difference? If I generate code from this design, I should know the effect. Is one (constraint) just a comment and the other (enum) imposes a control? That difference should be explained or warned about in the Users' Guide. (If there is no difference, shame on Sparx.) :-/
See
Constraint:P. 75, UML Std
Enumerated Type P. 69, UML Std
