69
1 The Object Constraint Language: Expressing Constraints in the UML (Most slides created by Robert B. France, Professor Department of Computer Science, Colorado State University. Other material from: (Source: http://www.cse.dmu.ac.uk/~aoc/teaching-notes/Contents/CSCI3007/CSCI3 007OCLtutorial.pdf )

The Object Constraint Language: Expressing Constraints in the UML

  • Upload
    varuna

  • View
    54

  • Download
    0

Embed Size (px)

DESCRIPTION

The Object Constraint Language: Expressing Constraints in the UML. (Most slides created by Robert B. France, Professor - PowerPoint PPT Presentation

Citation preview

Page 1: The Object Constraint Language:  Expressing Constraints in the UML

1

The Object Constraint Language: Expressing Constraints in the UML

(Most slides created by Robert B. France, ProfessorDepartment of Computer Science, Colorado State University. Other material from: (Source: http://www.cse.dmu.ac.uk/~aoc/teaching-notes/Contents/CSCI3007/CSCI3007OCLtutorial.pdf )

Page 2: The Object Constraint Language:  Expressing Constraints in the UML

Declarative vs Imperative Programming With imperative programming, you say both what is to be done – and how it is to be

done:

2

List<int> collection = new List<int> { 1, 2, 3, 4, 5 }; List<int> results = new List<int>(); foreach(var num in collection) { if (num % 2 != 0) results.Add(num); }

1. Create a result collection 2. Step through each number in the collection 3. Check the number, if it's odd, add it to the results

With declarative programming, you say what is to be done – but not how it is to be done:

var results = collection.Where( num => num % 2 != 0);

From this link

Page 3: The Object Constraint Language:  Expressing Constraints in the UML

3

What is OCL? The Object Constraint Language (OCL) is a

declarative language for describing rules that apply to UML models

OCL expressions are always associated with a UML model OCL expressions can be associated with any model element

in UML OCL can be used

to describe constraints A constraint is a restriction on one or more values of a model or

system. A constraint is an expression that evaluates to true or false

as a query language Queries are expressions that evaluate to a value (true, false and

other values) Can be used to define new attributes and operations

Page 4: The Object Constraint Language:  Expressing Constraints in the UML

4

Constraints vs. Queries

Examples of constraints: The duration of a flight is the same as the difference between the arrival

and departure times The maximum number of passengers on a flight must be less than

1,001 The origin of a flight must be different than its destination

Examples of queries: Return all the departing flights from a given airport Return all the flights departing from a given airport with a departure time

after 4p.m. Derive the arrival time by adding the duration of the flight to the

departure time.

AirportFlight

*

*

departTime: Time/arrivalTime: Timeduration : IntervalmaxNrPassengers: Integer

origin

desti-nation

name: String

arrivingFlights

departingFlights

1

1

Page 5: The Object Constraint Language:  Expressing Constraints in the UML

5

Why OCL?

Required age of car owners? Requirement that a person may own at most one red car

- because UML is not enough!

Page 6: The Object Constraint Language:  Expressing Constraints in the UML

6

Specifying Constraints

Page 7: The Object Constraint Language:  Expressing Constraints in the UML

7

Different kinds of constraints Class invariant

a constraint that must always be met by all instances of the class

Precondition of an operation a constraint that must always be true BEFORE the

execution of the operation Postcondition of an operation

a constraint that must always be true AFTER the execution of the operation

Page 8: The Object Constraint Language:  Expressing Constraints in the UML

8

Specifying Constraints: Invariants

Page 9: The Object Constraint Language:  Expressing Constraints in the UML

9

Note: self can be omitted

context Flightinv capacity: maxNrPassengers <= 1000

Example: Expressing Invariants Flight capacity constraint: The maximum number of passengers

that can be on a flight must be less than or equal to 1,000.

context Flightinv capacity: self.maxNrPassengers <= 1000

AirportFlight

*

*

departTime: Time/arrivalTime: Timeduration : IntervalmaxNrPassengers: Integer

origin

desti-nation

name: String

arrivingFlights

departingFlights

1

1

Page 10: The Object Constraint Language:  Expressing Constraints in the UML

10

Constraint context and self

Every OCL expression is bound to a specific context. The context is often the element that the

constraint restricts The context may be denoted within the

expression using the keyword ‘self’. ‘self’ is implicit in all OCL expressions Similar to ‘this’ in C++

Page 11: The Object Constraint Language:  Expressing Constraints in the UML

11

Notation Constraints may be denoted within the

UML model or in a separate document. the expression:

context Flight inv durationLimit: self.duration < 4

is identical to:context Flight inv: duration < 4

Flight

duration: Integerinv: duration < 4

is identical to:

Page 12: The Object Constraint Language:  Expressing Constraints in the UML

12

Example modelAirport

Flight

Passenger

Airline

*

**

*

minAge: Integerage: IntegerneedsAssistance: Boolean

departTime: Time/arrivalTime: Timeduration : IntervalmaxNrPassengers: Integer

origin

desti-nation

name: String

name: String

{ordered}

arrivingFlights

departingFlights

CEO

0..1

flights

passengers

book(f : Flight)

0..1

airline

airline

Time

difference(t:Time):Intervalbefore(t: Time): Booleanplus(d : Interval) : Time

$midnight: Timemonth : Stringday : Integeryear : Integerhour : Integerminute : Integer

Interval

equals(i:Interval):Boolean$Interval(d,h,m : Integer) : Interval

nrOfDays : IntegernrOfHours : IntegernrOfMinutes : Integer

11

1

1

Page 13: The Object Constraint Language:  Expressing Constraints in the UML

13

Airport

Flight

Passenger

Airline

*

**

*

minAge: Integerage: IntegerneedsAssistance: Boolean

departTime: Time/arrivalTime: Timeduration : IntervalmaxNrPassengers: Integer

origin

desti-nation

name: String

name: String

{ordered}

arrivingFlights

departingFlights

CEO

0..1

flights

passengers

book(f : Flight)

0..1

airline

airline

Time

difference(t:Time):Intervalbefore(t: Time): Booleanplus(d : Interval) : Time

$midnight: Timemonth : Stringday : Integeryear : Integerhour : Integerminute : Integer

Interval

equals(i:Interval):Boolean$Interval(d,h,m : Integer) : Interval

nrOfDays : IntegernrOfHours : IntegernrOfMinutes : Integer

11

1

1

• Constraint: The difference between the depart and arrival time for a flight must be the same as its duration.

context Flightinv duration:

self.departTime.difference(self.arrivalTime).equals(self.duration)

Page 14: The Object Constraint Language:  Expressing Constraints in the UML

14

Elements of an OCL expression In an OCL expression these elements may

be used: basic types: String, Boolean, Integer, Real. classifiers from the UML model and their features

attributes, and class attributes associations from the UML model

Page 15: The Object Constraint Language:  Expressing Constraints in the UML

15

OCL types

Page 16: The Object Constraint Language:  Expressing Constraints in the UML

16

Precedence Rules

Page 17: The Object Constraint Language:  Expressing Constraints in the UML

17

Some OCL Reserved Words AND ATTR ELSE ENDIF IF IMPLIES INV LET NOT OR POST PRE THEN XOR

Page 18: The Object Constraint Language:  Expressing Constraints in the UML

18

OCL Comments

Comments in OCL are written following two successive dashes “--” -- this is a comment

Page 19: The Object Constraint Language:  Expressing Constraints in the UML

19

Airport

Flight

Passenger

Airline

*

**

*

minAge: Integerage: IntegerneedsAssistance: Boolean

departTime: Time/arrivalTime: Timeduration : IntervalmaxNrPassengers: Integer

origin

desti-nation

name: String

name: String

{ordered}

arrivingFlights

departingFlights

CEO

0..1

flights

passengers

book(f : Flight)

0..1

airline

airline

Time

difference(t:Time):Intervalbefore(t: Time): Booleanplus(d : Interval) : Time

$midnight: Timemonth : Stringday : Integeryear : Integerhour : Integerminute : Integer

Interval

equals(i:Interval):Boolean$Interval(d,h,m : Integer) : Interval

nrOfDays : IntegernrOfHours : IntegernrOfMinutes : Integer

11

1

1

• context Airline inv: name.toLower = ‘usair’• context Passenger inv: age >= ((9.6 - 3.5)* 3.1).floor implies mature = true• NB: A B = ~A v B

Example: OCL basic types

Page 20: The Object Constraint Language:  Expressing Constraints in the UML

20

Associations and navigations

Every association in the model is a navigation path.

The context of the expression is the starting point.

Role names are used to identify the navigated association.

Page 21: The Object Constraint Language:  Expressing Constraints in the UML

21

Example: navigations

The name of the airline for a flight is Delta

context Flight inv: airline.name = ‘Delta’

Airport

Flight

*

*

departTime: Time/arrivalTime: Timeduration : IntervalmaxNrPassengers: Integer

origin

desti-nation

name: String

arrivingFlights

departingFlights

Airline

name: String

airline1 The origin of a flight must be different than its destination

context Flightinv: origin <> destination

Page 22: The Object Constraint Language:  Expressing Constraints in the UML

22

Example: Invariant involving Enumerated Type

• The type of a flight must be the same as the type of the airplane.

{context Flightinv ftype = Ftype::cargo implies Airplane.atype = Ftype::cargoinv ftype = Ftype::passenger implies Airplane.atype = Ftype:: passenger}

1*Flight Airplaneftype : Ftype atype : Ftypeflights

<<enumeration>>Ftype

cargopassenger

Page 23: The Object Constraint Language:  Expressing Constraints in the UML

23

Association classes Persons working with IBM have the job type “trainer”

otherwise their job type is “programmer”.context Person inv:if employer.name = ‘IBM’ then

Job.type = JobType::trainerelse Job.type = JobType::programmerendif

Person Company

Job

* 1employee employer

type : JobType

name : String

JobTypetrainerprogrammer

Page 24: The Object Constraint Language:  Expressing Constraints in the UML

24

Specifying Constraints: Operation Specifications

Page 25: The Object Constraint Language:  Expressing Constraints in the UML

25

Syntax for specifying operationscontext NameOfClass::operationName():returnTypepre : -- some expressionbody : -- some expressionpost : some expression

Page 26: The Object Constraint Language:  Expressing Constraints in the UML

26

Pre- and PostCondition Example

A class named Account has an attribute balance and an operation overdraft() that returns true if the balance is less than 0 and false otherwise.

context Account::overdraft():Booleanpre : -- nonepost : result = (balance < 0)

Page 27: The Object Constraint Language:  Expressing Constraints in the UML

27

More complex operation specifications

The operation birthdayOccurs() adds 1 to the customer age.

context Customer::birthdayOccurs()pre : -- nonepost : age = age@pre + 1

What does this describe?

context Account::safeWithdraw(amt:Integer)pre : balance > amtpost : balance = balance@pre - amt

Page 28: The Object Constraint Language:  Expressing Constraints in the UML

28

Specifying Queries

Page 29: The Object Constraint Language:  Expressing Constraints in the UML

29

Example modelAirport

Flight

Passenger

Airline

*

**

*

$minAge: Integerage: IntegerneedsAssistance: Boolean

departTime: Time/arrivalTime: Timeduration : IntervalmaxNrPassengers: Integer

origin

desti-nation

name: String

name: String

{ordered}

arrivingFlights

departingFlights

CEO

0..1

flights

passengers

book(f : Flight)

0..1

airline

airline

Time

difference(t:Time):Intervalbefore(t: Time): Booleanplus(d : Interval) : Time

$midnight: Timemonth : Stringday : Integeryear : Integerhour : Integerminute : Integer

Interval

equals(i:Interval):Boolean$Interval(d,h,m : Integer) : Interval

nrOfDays : IntegernrOfHours : IntegernrOfMinutes : Integer

11

1

1

Page 30: The Object Constraint Language:  Expressing Constraints in the UML

30

Derived Attribute & Initial Value Example

Defining derived attributescontext Flight::arrivalTime:Timederive:departTime.plus(duration)

Defining initial attribute valuecontext Flight::maxNrPassengers:Integerinit: 100

Defining initial association end valuecontext Flight::passengers:Set(Passenger)init: Set{}

Page 31: The Object Constraint Language:  Expressing Constraints in the UML

31

Query operation examplesReturn all the departing flights from a given airportcontext Airport::departures():Set(Flight)body: result=departingFlights

Return all the airports served by an airlinecontext Airline::served():Set(Airport)body: result=flights.destination->asSet()

Airline

name: StringAirport

Flight

*

* *

departTime: Time/arrivalTime: Timeduration : IntervalmaxNrPassengers: Integer

origin

desti-nation

name: String

arrivingFlights

departingFlights

flights

airline1

1

1

1

Page 32: The Object Constraint Language:  Expressing Constraints in the UML

32

More Advanced OCL Expressions

Page 33: The Object Constraint Language:  Expressing Constraints in the UML

33

Significance of collections in OCL Most navigations return collections rather

than single elements

10..*Flight Airplane

type : enum of cargo, passenger

type : enum of cargo, passenger

flights

Page 34: The Object Constraint Language:  Expressing Constraints in the UML

34

Subtypes of Collection

1. Set: each element occurs only once (Non-ordered, unique)

2. OrderedSet: a set with ordered elements.

3. Bag: elements may be present more than once(non-ordered, non-unique)

4. Sequence: a bag with ordered elements (ordered, non-unique)

Page 35: The Object Constraint Language:  Expressing Constraints in the UML

35

Subtypes of CollectionAirline

name: StringAirport

Flight

*

* *

departTime: Time/arrivalTime: Timeduration : IntervalmaxNrPassengers: Integer

origin

desti-nation

name: String

arrivingFlights

departingFlights

flights

airline1

1

1

1

Passenger*

$minAge: Integerage: IntegerneedsAssistance: Boolean

{ordered}passengers

book(f : Flight)

Set: arrivingFlights - from the context Airport Non-ordered, unique

Bag: arrivingFlights.duration - from the context Airport Non-ordered, non-unique

Sequence: passengers - from the context Flight Ordered, non-unique

Page 36: The Object Constraint Language:  Expressing Constraints in the UML

36

Collection operations

OCL has a great number of predefined operations on the collection types.

Syntax: collection->operation

Use of the “->” (arrow) operator instead of the“.” (dot) operator

Page 37: The Object Constraint Language:  Expressing Constraints in the UML

37

The collect operation

Syntax:collection->collect(elem : T | expr)collection->collect(elem | expr)collection->collect(expr)

The collect operation results in the collection of the values resulting from evaluating expr for all elements in the collection

Shorthand often trips people up. Be Careful!

Page 38: The Object Constraint Language:  Expressing Constraints in the UML

38

Example: collect operation

context Airport inv:self.arrivingFlights -> collect(airLine) ->notEmpty

airp1

airp2

f1

f2

f3

f4

f5

airline1

airline2

airline3

departing flights arriving flights

All arriving flights must be associated with an airline

Page 39: The Object Constraint Language:  Expressing Constraints in the UML

39

The select operation

Syntax:collection->select(elem : T | expression)collection->select(elem | expression)collection->select(expression)

The select operation results in the subset of all elements for which expression is true

Page 40: The Object Constraint Language:  Expressing Constraints in the UML

40

Example: select operation

context Airport inv:self.departingFlights->select(duration<4)->notEmpty

departing flights

arriving flights

airp1

airp2

airline1

airline2

airline3

f5duration = 2

f1duration = 2

f4duration = 5

f2duration = 5

f3duration = 3

There must be at least one departing flight whose duration is less than 4

Page 41: The Object Constraint Language:  Expressing Constraints in the UML

41

The forAll operation

Syntax: collection->forAll(elem : T | expr) collection->forAll(elem | expr) collection->forAll(expr)

The forAll operation results in true if expr is true for all elements of the collection

Page 42: The Object Constraint Language:  Expressing Constraints in the UML

42

Example: forAll operationcontext Airport inv:self.departingFlights->forAll(departTime.hour>6)

departing flights arriving flights

airp1

airp2

airline1

airline2

airline3

f5depart = 8

f1depart = 7

f4depart = 9

f2depart = 5

f3depart = 8

All departing flights must leave after 6

Page 43: The Object Constraint Language:  Expressing Constraints in the UML

43

The exists operation

Syntax:collection->exists(elem : T | expr)collection->exists(elem | expr)collection->exists(expr)

The exists operation results in true if there is at least one element in the collection for which the expression expr is true.

Page 44: The Object Constraint Language:  Expressing Constraints in the UML

44

Example: exists operationcontext Airport inv:self.departingFlights->exists(departTime.hour<6)

departing flights arriving flights

airp1

airp2

airline1

airline2

airline3

f5depart = 8

f1depart = 7

f4depart = 9

f2depart = 5

f3depart = 8

Page 45: The Object Constraint Language:  Expressing Constraints in the UML

45

Other collection operations

isEmpty: true if collection has no elements notEmpty: true if collection has at least one element size: number of elements in collection count(elem): number of occurences of elem in

collection includes(elem): true if elem is in collection excludes(elem): true if elem is not in collection includesAll(coll): true if all elements of coll are in

collection

Page 46: The Object Constraint Language:  Expressing Constraints in the UML

46

Examples

A vehicle owner must be at least 18 years old.:context Vehicle inv: self.owner. age >= 18

Page 47: The Object Constraint Language:  Expressing Constraints in the UML

47

A car owner must be at least 18 years old.:context Car inv: self.owner. age >= 18

Examples

Page 48: The Object Constraint Language:  Expressing Constraints in the UML

48

Nobody has more than 3 vehicles:context Person inv: self.fleet->size <= 3

Examples

Page 49: The Object Constraint Language:  Expressing Constraints in the UML

49

All vehicles of a person are black:context Person inv: fleet->forAll(v | v.colour = #black)

Examples

Page 50: The Object Constraint Language:  Expressing Constraints in the UML

50

Nobody has more than 3 red vehicles:context Person inv: fleet->select(v | v.colour = #red)->size <= 3

Examples

Page 51: The Object Constraint Language:  Expressing Constraints in the UML

51

context Personinv: age<18 implies self.fleet->forAll(v | not v.oclIsKindOf(Car))

A person younger than 18 owns no cars..

Examples

Page 52: The Object Constraint Language:  Expressing Constraints in the UML

52

There is a red car in somebody’s fleet:context Person inv: fleet->select(v | v.colour = #red)->notEmpty

context Car inv: Car.allInstances()->exists(c | c.colour=#red)

Examples

Page 53: The Object Constraint Language:  Expressing Constraints in the UML

53

Examples: pre-post conditions

If setAge(. . . ) is called with a non-negative argument then the argument becomes the new value of the attribute age.

context Person::setAge(newAge:int) pre: newAge >= 0 post: age = newAge

Page 54: The Object Constraint Language:  Expressing Constraints in the UML

54

Examples: pre-post conditions

Calling birthday() increments the age of a person by 1.

context Person::birthday() post: age = age@pre + 1

Page 55: The Object Constraint Language:  Expressing Constraints in the UML

55

Examples: pre-post conditions

Calling getName() delivers the value of the attribute name.

context Person::getName() post: result = name

Page 56: The Object Constraint Language:  Expressing Constraints in the UML

56

Local variables The let construct defines variables local to

one constraint:Let var : Type = <expression1> in <expression2>

Example:context Airport inv:Let supportedAirlines : Set (Airline) =

self.arrivingFlights -> collect(airLine) in (supportedAirlines ->notEmpty) and (supportedAirlines ->size < 500)

Page 57: The Object Constraint Language:  Expressing Constraints in the UML

57

Iterate

The iterate operation for collections is the most generic and complex building block.

collection->iterate(elem : Type; answer : Type = <value> |

<expression-with-elem-and-answer>)

Page 58: The Object Constraint Language:  Expressing Constraints in the UML

58

Iterate example

Example iterate:context Airline inv:flights->select(maxNrPassengers > 150)->notEmpty

Is identical to:context Airline inv:flights->iterate (f : Flight;

answer : Set(Flight) = Set{ } |if f.maxNrPassengers > 150 then

answer->including(f)else

answer endif )->notEmpty

Page 59: The Object Constraint Language:  Expressing Constraints in the UML

59

Inheritance of constraints

Guiding principle Liskov’s Substitution Principle (LSP): “Whenever an instance of a class is expected,

one can always substitute an instance of any of its subclasses.”

Page 60: The Object Constraint Language:  Expressing Constraints in the UML

60

Inheritance of constraints Consequences of LSP for invariants:

An invariant is always inherited by each subclass. Subclasses may strengthen the invariant.

Consequences of LSP for preconditions and postconditions: A precondition may be weakened (contravariance)

A method in a subclass can weaken the precondition of a method in the superclass. That means the subclass method can accept a wider range of values. So data that is valid in the subclass may be invalid in the superclass.

A postcondition may be strengthened (covariance) A subclass’s method can strengthen the postcondition (but it cannot

weaken it): a subclass‘s method can return a subset of the values returned by the method it overrides.

Page 61: The Object Constraint Language:  Expressing Constraints in the UML

Weakening Preconditions abstract class Payment { /** * @pre amt >= 0 */ public void setPaymentAmount(int amt) {…} }

61

class CreditCardPayment extends Payment { /** * @pre true */ public void setPaymentAmount(int amt) {…} }

class CashPayment extends Payment { … }

Page 62: The Object Constraint Language:  Expressing Constraints in the UML

Why does it not make sense to strengthen the precondition?• Suppose we set the precondition on the setPaymentAmount ofCreditCardPayment to be: @pre amt >= 25

• Client should be able to do:Payment p;// substitute CashPayment for Paymentp = new CashPayment();p.setPaymentAmount( 5 );// substitute CreditCardPayment for Paymentp = new CreditCardPayment();p.setPaymentAmount( 5 ); // oops!

62Example from: http://www.ugrad.cs.ubc.ca/~cs211/notes/L07-InheritanceGoodBad-4up.pdf

Page 63: The Object Constraint Language:  Expressing Constraints in the UML

Why does it not make sense to weaken the postcondition? • Suppose the client writes code based on the postcondition of the

superclass. • That client code could break if we substitute a superclass object

with an instance of one of its subclasses if the subclass' method has a weaker postcondition. • client writes code assuming that a method returns a value that is positive • subclass overrides method to return *any* value (so postcondition is weakened) • client code is going to break if a negative value is returned.

63

Page 64: The Object Constraint Language:  Expressing Constraints in the UML

64

Exercise: The Stack Data Structure push(Element elm) – add elm to top of stack pop() – removes and returns element on top of stack isEmpty() – returns true if stack has no elements top() – returns element on top of stack previous(Element elm) – returns the element inserted on the

stack immediately before elm. isFull() – returns true if stack has maximum number of elements

Assuming top, previous and isFull are already specified, specify pre and post conditions for the other operations.

Stack

push(Element elm)pop():ElementisEmpty():Booleantop(): Elementprevious(Element elm):ElementisFull():Boolean

Page 65: The Object Constraint Language:  Expressing Constraints in the UML

65

Summary and OCL Tips

OCL invariants allow you to model more precisely remain implementation independent

OCL pre- and postconditions allow you to specify contracts (design by contract) specify interfaces of components more precisely

OCL usage tips keep constraints simple always combine natural language with OCL use a tool to check your OCL

Page 66: The Object Constraint Language:  Expressing Constraints in the UML

Further Resources for OCL

The Object Constraint Language ISBN 0-201-37940-6

Page 67: The Object Constraint Language:  Expressing Constraints in the UML

67

ConclusionFinally!

!

Page 68: The Object Constraint Language:  Expressing Constraints in the UML

Questions: operational invariants - ANSWERS

Context Stack::isEmpty() Pre: none Post: result = (^top() = null)

Page 69: The Object Constraint Language:  Expressing Constraints in the UML

Questions: operational invariants - ANSWERS

Context Stack::push(Element elm) pre: ^isFull() = false post: ^top() = elm

Context Stack::pop() Pre: ^isEmpty() = false and elm = ^top() Post: result = elm and ^top() = previous(elm@pre)