Hello,

I assume that you use the "validate the model" facility.
First, you can make your own check on what is available through this check.
Write the constraint in a Topcased OCL rule file and apply the check through
the OCL Check (popup menu) after having selected an OCL rule file.
You can find a documentation on the use of the ocl checker at
http://gforge.enseeiht.fr/docman/view.php/30/3474/TPC_OCL_Tutorial_v1.0.pdf
(The editor will allow you to check that the written constraint conforms to
the metamodel you use, too, using the completion facility. In your case, the
constraint seems to be correct.)

As regard to your question :
Does this mean that not all OCL rules defined in UML's standard are checked,
or am I missing something ? ... It is Eclipse relevant :
http://www.eclipse.org/newsportal/thread.php?group=eclipse.modeling.mdt.uml2
(This is the same function as the "validate" option when you see your model
as a tree.)

Regards
Christophe
  -----Message d'origine-----
  De : [email protected]
[mailto:[email protected]]de la part de
[email protected]
  Envoyé : vendredi 4 septembre 2009 17:55
  À : [email protected]
  Objet : [Topcased-users] [OCL Checker] Checking type-related constraints
onan UML model


  Dear Topcased Members,


  I would like to do some type checking on a UML model using OCL.

  For some reason, although Topcased's OCL checker does seem to work
perfectly and reports all kinds of errors within my model, it never reports
type-related errors (... at least the one I tried to make).

  I added an AddStructuralFeatureValueAction in an activity diagram with an
input typed as an A, and a structural feature typed as a B. Considering that
A and B don't have any kind of relation between them, I was hoping to have a
warning from the OCL checker pointing out that my model doesn't comply with
the constraint #1 on WriteStructuralFeatureValueActions (UML Superstructure,
p.292) ... but I didn't.

  I also connected the output of a ReadStructuralFeatureAction, typed as an
A, to the input of an AddStructuralFeatureValueAction, typed as a B. This
time, I was hoping to have a warning because my model doesn't comply with
the constraint #2 on ObjectFlows (UML Superstructure, p.387) ... I still
didn't.

  Does this mean that not all OCL rules defined in UML's standard are
checked, or am I missing something ? Is there a way to make the OCL checker
check these type-related constraints ?


  Regards,
  Martin


        Martin NEIDERT
        Agence 104 - STIE
        Sopra group.
        1 Avenue André Marie Ampère
        BP 10134 - 31772 Colomiers Cedex
        Phone : +33 (0)5 34 56 73 18
        Mob : +33 (0)6 82 57 37 25
        [email protected] - www.sopragroup.com
        This message may contain confidential and proprietary material for
the sole use of the intended recipient. Any review or distribution by others
is strictly prohibited. If you are not the intended recipient, please
contact the sender and delete all copies.

        P Before printing, think about the environment.

_______________________________________________
Topcased-users mailing list
[email protected]
http://lists.gforge.enseeiht.fr/mailman/listinfo/topcased-users

Reply via email to