The Object Constraint Language 2.0 (OCL) is an addition to the UML 2.0 specification that provides you with a way to express constraints and logic on your models. For example, you can use OCL to convey that a person’s age must always be greater than 0 or that a branch office must always have one secretary for every 10 employees.
OCL isn’t new to UML 2.0; it was first introduced in UML 1.4. However, as of UML 2.0, it was formalized using the Meta-Object Facility and UML 2.0. From a user’s perspective the language has been updated and refined but the fundamentals remain the same. This appendix introduces the basic concepts of OCL. For more detailed information, consult the OCL specification available from the Object Management Group’s web site (http://www.omg.org/).
The Object Constraint Language is just that: a language. It obeys a syntax and has keywords. However, unlike other languages, it can’t be used to express program logic or flow control. By design, OCL is a query-only
language; it can’t modify the model (or executing system) in any way. It can be used to express preconditions, postconditions, invariants (things that must always be
true), guard conditions, and results of method calls.
OCL can be used virtually anywhere in UML and is typically associated with a classifier using a note. When an OCL expression is evaluated, it is considered to be instantaneous, meaning the associated classifier can’t change state during ...