Model Checking Contracts A case study Gordon Pace Cristian - - PowerPoint PPT Presentation

model checking contracts a case study
SMART_READER_LITE
LIVE PREVIEW

Model Checking Contracts A case study Gordon Pace Cristian - - PowerPoint PPT Presentation

Model Checking Contracts A case study Gordon Pace Cristian Prisacariu Gerardo Schneider gordon.pace@um.edu.mt cristi@ifi.uio.no gerardo@ifi.uio.no Department of Informatics, University of Oslo ATVA07 Tokyo, Japan October 22-25, 2007


slide-1
SLIDE 1

university-logo

Model Checking Contracts A case study

Gordon Pace Cristian Prisacariu Gerardo Schneider

gordon.pace@um.edu.mt cristi@ifi.uio.no gerardo@ifi.uio.no Department of Informatics, University of Oslo

ATVA’07 Tokyo, Japan October 22-25, 2007

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 1 / 24

slide-2
SLIDE 2

university-logo

Contracts

“A contract is a binding agreement between two or more persons that is enforceable by law.” [Webster on-line]

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 2 / 24

slide-3
SLIDE 3

university-logo

Contracts

“A contract is a binding agreement between two or more persons that is enforceable by law.” [Webster on-line]

This deed of Agreement is made between:

  • 1. [name], from now on referred to as Provider and
  • 2. the Client.

INTRODUCTION

  • 3. The Provider is obliged to provide the Internet Services as stipulated in this Agreement.
  • 4. DEFINITIONS

a) Internet traffic may be measured by both Client and Provider by means of Equipment and may take the two values high and normal. OPERATIVE PART

  • 1. The Client shall not supply false information to the Client Relations Department of the

Provider.

  • 2. Whenever the Internet Traffic is high then the Client must pay [price] immediately, or the

Client must notify the Provider by sending an e-mail specifying that he will pay later.

  • 3. If the Client delays the payment as stipulated in 2, after notification he must immediately

lower the Internet traffic to the normal level, and pay later twice (2 ∗ [price]).

  • 4. If the Client does not lower the Internet traffic immediately, then the Client will have to pay

3 ∗ [price].

  • 5. The Client shall, as soon as the Internet Service becomes operative, submit within seven (7)

days the Personal Data Form from his account on the Provider’s web page to the Client Relations Department of the Provider.

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 2 / 24

slide-4
SLIDE 4

university-logo

Contracts

We call the above a conventional contract An e-contract is a machine-readable contract Two scenarios:

1 Obtain an e-contract from a conventional contract

Context: legal (e.g. financial) contracts

2 Write the e-contract directly in a formal language

Context: web services, components, OO, etc

Definition

A contract is a document which engages several parties in a transaction and stipulates their (conditional) obligations, rights, and prohibitions, as well as penalties in case of contract violations. A better name: ‘deontic’ e-contracts

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 3 / 24

slide-5
SLIDE 5

university-logo

Contracts

We call the above a conventional contract An e-contract is a machine-readable contract Two scenarios:

1 Obtain an e-contract from a conventional contract

Context: legal (e.g. financial) contracts

2 Write the e-contract directly in a formal language

Context: web services, components, OO, etc

Definition

A contract is a document which engages several parties in a transaction and stipulates their (conditional) obligations, rights, and prohibitions, as well as penalties in case of contract violations. A better name: ‘deontic’ e-contracts

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 3 / 24

slide-6
SLIDE 6

university-logo

Aim and Motivation

Use deontic e-contracts to ‘rule’ services exchange

1 Give a formal language for specifying/writing contracts 2 Analyze contracts “internally”

Detect contradictions/inconsistencies statically Determine the obligations (permissions, prohibitions) of a signatory Detect superfluous contract clauses

3 Develop a theory of contracts

Contract composition Subcontracting Conformance between a contract and the governing policies Meta-contracts (policies)

4 Monitor contracts

Run-time system to ensure the contract is respected In case of contract violations, act accordingly

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 4 / 24

slide-7
SLIDE 7

university-logo

Aim and Motivation

Use deontic e-contracts to ‘rule’ services exchange

1 Give a formal language for specifying/writing contracts 2 Analyze contracts “internally”

Detect contradictions/inconsistencies statically Determine the obligations (permissions, prohibitions) of a signatory Detect superfluous contract clauses

3 Develop a theory of contracts

Contract composition Subcontracting Conformance between a contract and the governing policies Meta-contracts (policies)

4 Monitor contracts

Run-time system to ensure the contract is respected In case of contract violations, act accordingly

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 4 / 24

slide-8
SLIDE 8

university-logo

Aim and Motivation

Use deontic e-contracts to ‘rule’ services exchange

1 Give a formal language for specifying/writing contracts 2 Analyze contracts “internally”

Detect contradictions/inconsistencies statically Determine the obligations (permissions, prohibitions) of a signatory Detect superfluous contract clauses

3 Develop a theory of contracts

Contract composition Subcontracting Conformance between a contract and the governing policies Meta-contracts (policies)

4 Monitor contracts

Run-time system to ensure the contract is respected In case of contract violations, act accordingly

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 4 / 24

slide-9
SLIDE 9

university-logo

Aim and Motivation

Use deontic e-contracts to ‘rule’ services exchange

1 Give a formal language for specifying/writing contracts 2 Analyze contracts “internally”

Detect contradictions/inconsistencies statically Determine the obligations (permissions, prohibitions) of a signatory Detect superfluous contract clauses

3 Develop a theory of contracts

Contract composition Subcontracting Conformance between a contract and the governing policies Meta-contracts (policies)

4 Monitor contracts

Run-time system to ensure the contract is respected In case of contract violations, act accordingly

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 4 / 24

slide-10
SLIDE 10

university-logo

Aim and Motivation

Use deontic e-contracts to ‘rule’ services exchange

1 Give a formal language for specifying/writing contracts 2 Analyze contracts “internally”

Detect contradictions/inconsistencies statically Determine the obligations (permissions, prohibitions) of a signatory Detect superfluous contract clauses

3 Develop a theory of contracts

Contract composition Subcontracting Conformance between a contract and the governing policies Meta-contracts (policies)

4 Monitor contracts

Run-time system to ensure the contract is respected In case of contract violations, act accordingly

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 4 / 24

slide-11
SLIDE 11

university-logo

Outline

1

The Contract Language CL

2

Model Checking Contracts

3

Final Remarks

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 5 / 24

slide-12
SLIDE 12

university-logo

Outline

1

The Contract Language CL

2

Model Checking Contracts

3

Final Remarks

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 6 / 24

slide-13
SLIDE 13

university-logo

The Contract Specification Language CL

Contract := D ; C C := CO | CP | CF | C ∧ C | [α]C | αC | C U C | C | C CO := O(α) | CO ⊕ CO CP := P(α) | CP ⊕ CP CF := F(α) | CF ∨ [α]CF O(α), P(α), F(α) specify obligation, permission (rights), and prohibition (forbidden) over actions α are actions given in the definition part D

+ choice · concatenation (sequencing) & concurrency φ? test

∧, ∨, and ⊕ are conjunction, disjunction, and exclusive disjunction [α] and α are the action parameterized modalities of dynamic logic U , , and correspond to temporal logic operators

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 7 / 24

slide-14
SLIDE 14

university-logo

The Contract Specification Language CL

Contract := D ; C C := CO | CP | CF | C ∧ C | [α]C | αC | C U C | C | C CO := O(α) | CO ⊕ CO CP := P(α) | CP ⊕ CP CF := F(α) | CF ∨ [α]CF O(α), P(α), F(α) specify obligation, permission (rights), and prohibition (forbidden) over actions α are actions given in the definition part D

+ choice · concatenation (sequencing) & concurrency φ? test

∧, ∨, and ⊕ are conjunction, disjunction, and exclusive disjunction [α] and α are the action parameterized modalities of dynamic logic U , , and correspond to temporal logic operators

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 7 / 24

slide-15
SLIDE 15

university-logo

The Contract Specification Language CL

Contract := D ; C C := CO | CP | CF | C ∧ C | [α]C | αC | C U C | C | C CO := O(α) | CO ⊕ CO CP := P(α) | CP ⊕ CP CF := F(α) | CF ∨ [α]CF O(α), P(α), F(α) specify obligation, permission (rights), and prohibition (forbidden) over actions α are actions given in the definition part D

+ choice · concatenation (sequencing) & concurrency φ? test

∧, ∨, and ⊕ are conjunction, disjunction, and exclusive disjunction [α] and α are the action parameterized modalities of dynamic logic U , , and correspond to temporal logic operators

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 7 / 24

slide-16
SLIDE 16

university-logo

The Contract Specification Language CL

Contract := D ; C C := CO | CP | CF | C ∧ C | [α]C | αC | C U C | C | C CO := O(α) | CO ⊕ CO CP := P(α) | CP ⊕ CP CF := F(α) | CF ∨ [α]CF O(α), P(α), F(α) specify obligation, permission (rights), and prohibition (forbidden) over actions α are actions given in the definition part D

+ choice · concatenation (sequencing) & concurrency φ? test

∧, ∨, and ⊕ are conjunction, disjunction, and exclusive disjunction [α] and α are the action parameterized modalities of dynamic logic U , , and correspond to temporal logic operators

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 7 / 24

slide-17
SLIDE 17

university-logo

The Contract Specification Language CL

Contract := D ; C C := CO | CP | CF | C ∧ C | [α]C | αC | C U C | C | C CO := O(α) | CO ⊕ CO CP := P(α) | CP ⊕ CP CF := F(α) | CF ∨ [α]CF O(α), P(α), F(α) specify obligation, permission (rights), and prohibition (forbidden) over actions α are actions given in the definition part D

+ choice · concatenation (sequencing) & concurrency φ? test

∧, ∨, and ⊕ are conjunction, disjunction, and exclusive disjunction [α] and α are the action parameterized modalities of dynamic logic U , , and correspond to temporal logic operators

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 7 / 24

slide-18
SLIDE 18

university-logo

More on the Contract Language

CTD and CTP

Expressing contrary-to-duty (CTD) OC(α) = O(α) ∧ [α]C

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 8 / 24

slide-19
SLIDE 19

university-logo

More on the Contract Language

CTD and CTP

Expressing contrary-to-duty (CTD) OC(α) = O(α) ∧ [α]C Expressing contrary-to-prohibition (CTP) FC(α) = F(α) ∧ [α]C

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 8 / 24

slide-20
SLIDE 20

university-logo

CL Semantics

Cµ – A variant of the modal µ-calculus

Translation into a variant of µ-calculus (Cµ) The syntax of the Cµ logic ϕ := P | Z | Pc | ⊤ | ¬ϕ | ϕ ∧ ϕ | [γ]ϕ | µZ.ϕ(Z) Main differences with respect to the classical µ-calculus:

1 Pc is set of propositional constants Oa and Fa, one for each basic

action a

2 Multisets of basic actions: i.e. γ = {a, a, b} is a label Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 9 / 24

slide-21
SLIDE 21

university-logo

CL Semantics

Cµ – A variant of the modal µ-calculus

Translation into a variant of µ-calculus (Cµ) The syntax of the Cµ logic ϕ := P | Z | Pc | ⊤ | ¬ϕ | ϕ ∧ ϕ | [γ]ϕ | µZ.ϕ(Z) Main differences with respect to the classical µ-calculus:

1 Pc is set of propositional constants Oa and Fa, one for each basic

action a

2 Multisets of basic actions: i.e. γ = {a, a, b} is a label Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 9 / 24

slide-22
SLIDE 22

university-logo

CL Semantics

Obligation

Obligation f T (O(a&b)) = {a, b}(Oa ∧ Ob)

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 10 / 24

slide-23
SLIDE 23

university-logo

CL Semantics

Obligation

Obligation f T (O(a&b)) = {a, b}(Oa ∧ Ob)

{a, b} O(a&b) Ob Oa

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 10 / 24

slide-24
SLIDE 24

university-logo

Outline

1

The Contract Language CL

2

Model Checking Contracts

3

Final Remarks

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 11 / 24

slide-25
SLIDE 25

university-logo

Model Checking Contracts

1 Model the conventional contract (in English) as a CL expression 2 Translate the CL specification into Cµ 3 Obtain a Kripke-like model (LTS) from the Cµ formulas 4 Translate the LTS into the input language of NuSMV 5 Perform model checking using NuSMV

Check the model is ‘good’ Check some properties about the client and the provider

6 In case of a counter-example given by NuSMV, interpret it as a CL

clause and repeat the model checking process until the property is satisfied

7 In some cases rephrase the original contract Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 12 / 24

slide-26
SLIDE 26

university-logo

Model Checking Contracts

1 Model the conventional contract (in English) as a CL expression 2 Translate the CL specification into Cµ 3 Obtain a Kripke-like model (LTS) from the Cµ formulas 4 Translate the LTS into the input language of NuSMV 5 Perform model checking using NuSMV

Check the model is ‘good’ Check some properties about the client and the provider

6 In case of a counter-example given by NuSMV, interpret it as a CL

clause and repeat the model checking process until the property is satisfied

7 In some cases rephrase the original contract Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 12 / 24

slide-27
SLIDE 27

university-logo

Model Checking Contracts

1 Model the conventional contract (in English) as a CL expression 2 Translate the CL specification into Cµ 3 Obtain a Kripke-like model (LTS) from the Cµ formulas 4 Translate the LTS into the input language of NuSMV 5 Perform model checking using NuSMV

Check the model is ‘good’ Check some properties about the client and the provider

6 In case of a counter-example given by NuSMV, interpret it as a CL

clause and repeat the model checking process until the property is satisfied

7 In some cases rephrase the original contract Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 12 / 24

slide-28
SLIDE 28

university-logo

Model Checking Contracts

1 Model the conventional contract (in English) as a CL expression 2 Translate the CL specification into Cµ 3 Obtain a Kripke-like model (LTS) from the Cµ formulas 4 Translate the LTS into the input language of NuSMV 5 Perform model checking using NuSMV

Check the model is ‘good’ Check some properties about the client and the provider

6 In case of a counter-example given by NuSMV, interpret it as a CL

clause and repeat the model checking process until the property is satisfied

7 In some cases rephrase the original contract Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 12 / 24

slide-29
SLIDE 29

university-logo

Model Checking Contracts

1 Model the conventional contract (in English) as a CL expression 2 Translate the CL specification into Cµ 3 Obtain a Kripke-like model (LTS) from the Cµ formulas 4 Translate the LTS into the input language of NuSMV 5 Perform model checking using NuSMV

Check the model is ‘good’ Check some properties about the client and the provider

6 In case of a counter-example given by NuSMV, interpret it as a CL

clause and repeat the model checking process until the property is satisfied

7 In some cases rephrase the original contract Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 12 / 24

slide-30
SLIDE 30

university-logo

Model Checking Contracts

1 Model the conventional contract (in English) as a CL expression 2 Translate the CL specification into Cµ 3 Obtain a Kripke-like model (LTS) from the Cµ formulas 4 Translate the LTS into the input language of NuSMV 5 Perform model checking using NuSMV

Check the model is ‘good’ Check some properties about the client and the provider

6 In case of a counter-example given by NuSMV, interpret it as a CL

clause and repeat the model checking process until the property is satisfied

7 In some cases rephrase the original contract Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 12 / 24

slide-31
SLIDE 31

university-logo

Model Checking Contracts

1 Model the conventional contract (in English) as a CL expression 2 Translate the CL specification into Cµ 3 Obtain a Kripke-like model (LTS) from the Cµ formulas 4 Translate the LTS into the input language of NuSMV 5 Perform model checking using NuSMV

Check the model is ‘good’ Check some properties about the client and the provider

6 In case of a counter-example given by NuSMV, interpret it as a CL

clause and repeat the model checking process until the property is satisfied

7 In some cases rephrase the original contract Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 12 / 24

slide-32
SLIDE 32

university-logo

Case Study

A Contract Example

  • 1. The Client shall not:

a) supply false information to the Client Relations Department of the Provider.

  • 2. Whenever the Internet Traffic is high then the Client must pay [price]

immediately, or the Client must notify the Provider by sending an e-mail specifying that he will pay later.

  • 3. If the Client delays the payment as stipulated in 2, after notification he must

immediately lower the Internet traffic to the normal level, and pay later twice (2 ∗ [price]).

  • 4. If the Client does not lower the Internet traffic immediately, then the Client

will have to pay 3 ∗ [price].

  • 5. The Client shall, as soon as the Internet Service becomes operative, submit

within seven (7) days the Personal Data Form from his account on the Provider’s web page to the Client Relations Department of the Provider.

  • 6. Provider may, at its sole discretion, without notice or giving any reason or

incurring any liability for doing so: a) Suspend Internet Services immediately if Client is in breach of Clause 1;

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 13 / 24

slide-33
SLIDE 33

university-logo

Case Study

A Contract Example

  • 1. The Client shall not:

a) supply false information to the Client Relations Department of the Provider.

  • 2. Whenever the Internet Traffic is high then the Client must pay [price]

immediately, or the Client must notify the Provider by sending an e-mail specifying that he will pay later.

  • 3. If the Client delays the payment as stipulated in 2, after notification he must

immediately lower the Internet traffic to the normal level, and pay later twice (2 ∗ [price]).

  • 4. If the Client does not lower the Internet traffic immediately, then the Client

will have to pay 3 ∗ [price].

  • 5. The Client shall, as soon as the Internet Service becomes operative, submit

within seven (7) days the Personal Data Form from his account on the Provider’s web page to the Client Relations Department of the Provider.

  • 6. Provider may, at its sole discretion, without notice or giving any reason or

incurring any liability for doing so: a) Suspend Internet Services immediately if Client is in breach of Clause 1;

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 13 / 24

slide-34
SLIDE 34

university-logo

Case Study

Translating into CL syntax

  • 1. F(fi)
  • 2. Whenever the Internet Traffic is high then the Client must pay [price]

immediately, or the Client must notify the Provider by sending an e-mail specifying that he will pay later.

  • 3. If the Client delays the payment as stipulated in 2, after notification he must

immediately lower the Internet traffic to the normal level, and pay later twice (2 ∗ [price]).

  • 4. If the Client does not lower the Internet traffic immediately, then the Client

will have to pay 3 ∗ [price].

  • 5. The Client shall, as soon as the Internet Service becomes operative, submit

within seven (7) days the Personal Data Form from his account on the Provider’s web page to the Client Relations Department of the Provider.

  • 6. Provider may, at its sole discretion, without notice or giving any reason or

incurring any liability for doing so: a) Suspend Internet Services immediately if Client is in breach of Clause 1;

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 14 / 24

slide-35
SLIDE 35

university-logo

Case Study

Translating into CL syntax

  • 1. F(fi)
  • 2. Whenever the Internet Traffic is high then the Client must pay [price]

immediately, or the Client must notify the Provider by sending an e-mail specifying that he will pay later.

  • 3. If the Client delays the payment as stipulated in 2, after notification he must

immediately lower the Internet traffic to the normal level, and pay later twice (2 ∗ [price]).

  • 4. If the Client does not lower the Internet traffic immediately, then the Client

will have to pay 3 ∗ [price].

  • 5. The Client shall, as soon as the Internet Service becomes operative, submit

within seven (7) days the Personal Data Form from his account on the Provider’s web page to the Client Relations Department of the Provider.

  • 6. Provider may, at its sole discretion, without notice or giving any reason or

incurring any liability for doing so: a) Suspend Internet Services immediately if Client is in breach of Clause 1;

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 14 / 24

slide-36
SLIDE 36

university-logo

Case Study

Translating into CL syntax

  • 1. FP(s)(fi)
  • 2. Whenever the Internet Traffic is high then the Client must pay [price]

immediately, or the Client must notify the Provider by sending an e-mail specifying that he will pay later.

  • 3. If the Client delays the payment as stipulated in 2, after notification he must

immediately lower the Internet traffic to the normal level, and pay later twice (2 ∗ [price]).

  • 4. If the Client does not lower the Internet traffic immediately, then the Client

will have to pay 3 ∗ [price].

  • 5. The Client shall, as soon as the Internet Service becomes operative, submit

within seven (7) days the Personal Data Form from his account on the Provider’s web page to the Client Relations Department of the Provider.

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 14 / 24

slide-37
SLIDE 37

university-logo

Case Study

Translating into CL syntax

  • 1. FP(s)(fi)
  • 2. [h](φ ⇒ O(p + (d&n)))
  • 3. If the Client delays the payment as stipulated in 2, after notification he must

immediately lower the Internet traffic to the normal level, and pay later twice (2 ∗ [price]).

  • 4. If the Client does not lower the Internet traffic immediately, then the Client

will have to pay 3 ∗ [price].

  • 5. The Client shall, as soon as the Internet Service becomes operative, submit

within seven (7) days the Personal Data Form from his account on the Provider’s web page to the Client Relations Department of the Provider.

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 14 / 24

slide-38
SLIDE 38

university-logo

Case Study

Translating into CL syntax

  • 1. FP(s)(fi)
  • 2. [h](φ ⇒ O(p + (d&n)))
  • 3. ([d&n](O(l) ∧ [l]♦O(p&p)))
  • 4. If the Client does not lower the Internet traffic immediately, then the Client

will have to pay 3 ∗ [price].

  • 5. The Client shall, as soon as the Internet Service becomes operative, submit

within seven (7) days the Personal Data Form from his account on the Provider’s web page to the Client Relations Department of the Provider.

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 14 / 24

slide-39
SLIDE 39

university-logo

Case Study

Translating into CL syntax

  • 1. FP(s)(fi)
  • 2. [h](φ ⇒ O(p + (d&n)))
  • 3. ([d&n](O(l) ∧ [l]♦O(p&p)))
  • 4. ([d&n · l ]♦O(p&p&p))
  • 5. The Client shall, as soon as the Internet Service becomes operative, submit

within seven (7) days the Personal Data Form from his account on the Provider’s web page to the Client Relations Department of the Provider.

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 14 / 24

slide-40
SLIDE 40

university-logo

Case Study

Translating into CL syntax

  • 1. FP(s)(fi)
  • 2. [h](φ ⇒ O(p + (d&n)))
  • 3. ([d&n](O(l) ∧ [l]♦O(p&p)))
  • 4. ([d&n · l ]♦O(p&p&p))
  • 5. ([o]O(sfD))

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 14 / 24

slide-41
SLIDE 41

university-logo

Case Study

Handcrafting the model

φ = the Internet traffic is high fi = client supplies false information to Client Relations Department h = client increases Internet traffic to high level p = client pays [price] d = client delays payment n = client notifies by e-mail l = client lowers the Int. traffic sfD = client sends the Personal Data Form to Client Relations Department

  • = provider activates the Internet

Service (it becomes operative) s = provider suspends service

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 15 / 24

slide-42
SLIDE 42

university-logo

Case Study

Handcrafting the model

φ = the Internet traffic is high fi = client supplies false information to Client Relations Department h = client increases Internet traffic to high level p = client pays [price] d = client delays payment n = client notifies by e-mail l = client lowers the Int. traffic sfD = client sends the Personal Data Form to Client Relations Department

  • = provider activates the Internet

Service (it becomes operative) s = provider suspends service Fs ¬ Ffi Ol Op O sfD , Od On

,

Op

φ,

l

sfD

  • l

s fi {d,n} fi h p fi fi fi fi fi else else

s3 s4 s5 s7 s6 s8 s1 s2

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 15 / 24

slide-43
SLIDE 43

university-logo

Case Study

Checking the contract on the model

1. FP(s)(fi) 2. [h](φ ⇒ O(p + (d&n))) 3. ([d&n](O(l) ∧ [l]♦O(p&p))) 4. ([d&n · l ]♦O(p&p&p)) 5. ([o]O(sfD)) Fs ¬ Ffi Ol Op O sfD , Od On

,

Op

φ,

l

sfD

  • l

s fi {d,n} fi h p fi fi fi fi fi else else

s3 s4 s5 s7 s6 s8 s1 s2

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 16 / 24

slide-44
SLIDE 44

university-logo

Case Study

Checking the contract on the model

1. FP(s)(fi) 2. [h](φ ⇒ O(p + (d&n))) 3. ([d&n](O(l) ∧ [l]♦O(p&p))) 4. ([d&n · l ]♦O(p&p&p)) 5. ([o]O(sfD)) 1, 2, and 4: OK Fs ¬ Ffi Ol Op O sfD , Od On

,

Op

φ,

l

sfD

  • l

s fi {d,n} fi h p fi fi fi fi fi else else

s3 s4 s5 s7 s6 s8 s1 s2

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 16 / 24

slide-45
SLIDE 45

university-logo

Case Study

Checking the contract on the model

1. FP(s)(fi) 2. [h](φ ⇒ O(p + (d&n))) 3. ([d&n](O(l) ∧ [l]♦O(p&p))) 4. ([d&n · l ]♦O(p&p&p)) 5. ([o]O(sfD)) 1, 2, and 4: OK 3 and 5: FAIL! Fs ¬ Ffi Ol Op O sfD , Od On

,

Op

φ,

l

sfD

  • l

s fi {d,n} fi h p fi fi fi fi fi else else

s3 s4 s5 s7 s6 s8 s1 s2

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 16 / 24

slide-46
SLIDE 46

university-logo

Case Study

Checking the contract on the model (cont.)

Failure of 3. It fails since there is a dependency with clause 2 We need to combine clauses 2 and 3: it model checks!

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 17 / 24

slide-47
SLIDE 47

university-logo

Case Study

Checking the contract on the model (cont.)

Failure of 3. It fails since there is a dependency with clause 2 We need to combine clauses 2 and 3: it model checks! Failure on our formalization in CL!

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 17 / 24

slide-48
SLIDE 48

university-logo

Case Study

Checking the contract on the model (cont.)

Failure of 3. It fails since there is a dependency with clause 2 We need to combine clauses 2 and 3: it model checks! Failure on our formalization in CL! Failure of 5. (([o]O(sfD))) The system should become operative only once

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 17 / 24

slide-49
SLIDE 49

university-logo

Case Study

Checking the contract on the model (cont.)

Failure of 3. It fails since there is a dependency with clause 2 We need to combine clauses 2 and 3: it model checks! Failure on our formalization in CL! Failure of 5. (([o]O(sfD))) The system should become operative only once

1 We rewrite the original contract 2 This is formulated in CL, written in NuSMV, and it

model checks!

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 17 / 24

slide-50
SLIDE 50

university-logo

Case Study

Checking the contract on the model (cont.)

Failure of 3. It fails since there is a dependency with clause 2 We need to combine clauses 2 and 3: it model checks! Failure on our formalization in CL! Failure of 5. (([o]O(sfD))) The system should become operative only once

1 We rewrite the original contract 2 This is formulated in CL, written in NuSMV, and it

model checks! ’Failure’ on the original contract!

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 17 / 24

slide-51
SLIDE 51

university-logo

Case Study

Verifying a property about client obligations

“It is always the case that whenever the Internet traffic is high, if the clients pays immediately, then the client is not obliged to pay again immediately afterward”

Fs ¬ Ffi Ol Op O sfD , Od On

,

Op

φ,

l

sfD

  • l

s fi {d,n} fi h p fi fi fi fi fi else else

s3 s4 s5 s7 s6 s8 s1 s2

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 18 / 24

slide-52
SLIDE 52

university-logo

Case Study

Verifying a property about client obligations

“It is always the case that whenever the Internet traffic is high, if the clients pays immediately, then the client is not obliged to pay again immediately afterward” It fails!

Fs ¬ Ffi Ol Op O sfD , Od On

,

Op

φ,

l

sfD

  • l

s fi {d,n} fi h p fi fi fi fi fi else else

s3 s4 s5 s7 s6 s8 s1 s2

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 18 / 24

slide-53
SLIDE 53

university-logo

Case Study

Verifying a property about client obligations

“It is always the case that whenever the Internet traffic is high, if the clients pays immediately, then the client is not obliged to pay again immediately afterward” It fails! We get a counter-example –Problem: state s4

Fs ¬ Ffi Ol Op O sfD , l

Od On

,

Op

φ,

sfD

  • l

s fi {d,n} fi h p fi fi fi fi fi else else

s3 s4 s5 s7 s6 s8 s1 s2

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 18 / 24

slide-54
SLIDE 54

university-logo

Case Study

Verifying a property about client obligations

“It is always the case that whenever the Internet traffic is high, if the clients pays immediately, then the client is not obliged to pay again immediately afterward” It fails! We get a counter-example –Problem: state s4 We modify the original contract to capture the above more precisely

Fs ¬ Ffi Ol Op O sfD , l

Od On

,

sfD

  • l

s fi {d,n} fi h fi fi fi fi fi else else

s3 s4 s5 s7 s6 s8 s1 s2

φ

p

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 18 / 24

slide-55
SLIDE 55

university-logo

Case Study

Verifying a property about payment in case of increasing Internet traffic

“It is always the case that whenever Internet traffic is high, if the client delays payment and notifies, and afterward lowers the Internet traffic, then the client is forbidden to increase Internet traffic until he pays twice” Fs ¬ Ffi Ol Op O sfD , l − Od On

,

sfD

  • l

s fi {d,n} fi h fi fi fi fi fi else else

s3 s4 s5 s7 s6 s8 s1 s2

p

φ

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 19 / 24

slide-56
SLIDE 56

university-logo

Case Study

Verifying a property about payment in case of increasing Internet traffic

“It is always the case that whenever Internet traffic is high, if the client delays payment and notifies, and afterward lowers the Internet traffic, then the client is forbidden to increase Internet traffic until he pays twice”

It fails!

Fs ¬ Ffi Ol Op O sfD , l

Od On

,

sfD

  • l

s fi {d,n} fi h fi fi fi fi fi else else

s3 s4 s5 s7 s6 s8 s1 s2

p

φ

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 19 / 24

slide-57
SLIDE 57

university-logo

Case Study

Verifying a property about payment in case of increasing Internet traffic

“It is always the case that whenever Internet traffic is high, if the client delays payment and notifies, and afterward lowers the Internet traffic, then the client is forbidden to increase Internet traffic until he pays twice”

It fails! Counter-example: From s4 (φ holds), after d&n · l, it is possible to increase Internet traffic in state s7, so neither F(h) nor donep&p hold

Fs ¬ Ffi l

Od On

,

Op O sfD , Ol sfD

  • l

s fi {d,n} fi h fi fi fi fi fi else else

s3 s4 s5 s7 s6 s8 s1 s2

p

φ

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 19 / 24

slide-58
SLIDE 58

university-logo

Case Study

Verifying a property about payment in case of increasing Internet traffic

“It is always the case that whenever Internet traffic is high, if the client delays payment and notifies, and afterward lowers the Internet traffic, then the client is forbidden to increase Internet traffic until he pays twice”

It fails! Counter-example: From s4 (φ holds), after d&n · l, it is possible to increase Internet traffic in state s7, so neither F(h) nor donep&p hold Add to the original contract the clause above!

Fs ¬ Ffi Ol Op O sfD , l

Od On

,

sfD

  • l

s fi {d,n} fi h fi fi fi fi fi

s3 s4 s5 s7 s6 s8 s1 s2

p

φ

{p,p,p} {p,p}

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 19 / 24

slide-59
SLIDE 59

university-logo

Outline

1

The Contract Language CL

2

Model Checking Contracts

3

Final Remarks

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 20 / 24

slide-60
SLIDE 60

university-logo

Model Checking Contracts

Initial ideas on how to model check contracts Based on: A formal specification language for contracts with semantics based on a variant of µ-calculus

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 21 / 24

slide-61
SLIDE 61

university-logo

Model Checking Contracts

Initial ideas on how to model check contracts Based on: A formal specification language for contracts with semantics based on a variant of µ-calculus Use of model checking for reasoning about contracts:

1 We use model checking to increase our confidence in the correctness

  • f the model with respect to the original natural language contract

2 By finding errors in the model, we identify problems in the original

natural language contract or its interpretation in CL

3 We enable the signatories to safeguard their interests by ensuring

certain desirable properties hold (and certain undesirable ones do not)

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 21 / 24

slide-62
SLIDE 62

university-logo

Current and Further Work

Currently: Direct semantics: “Normative” automata Redesign CL Automate the model checking process

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 22 / 24

slide-63
SLIDE 63

university-logo

Current and Further Work

Currently: Direct semantics: “Normative” automata Redesign CL Automate the model checking process Further work: Develop a proof system Internal vs external operations Add time Case studies Explore how to extract a contract monitor (?!)

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 22 / 24

slide-64
SLIDE 64

university-logo

Thank you!

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 23 / 24

slide-65
SLIDE 65

university-logo

Links and Papers

  • C. Prisacariu and G. Schneider. A formal language for electronic
  • contracts. In FMOODS’07, vol. 4468 of LNCS, pages 174-189, June

2007 COSoDIS: “Contract-Oriented Software Development for Internet Services” –A Nordunet3 project (http://folk.uio.no/gerardo/nordunet3/index.shtml) FLACOS’07 – 1st Workshop on Formal Languages and Analysis of Contract-Oriented Software (http://www.ifi.uio.no/flacos07/)

Oslo, 9-10 October 2007

Gerardo Schneider (UiO) Model Checking Contracts ATVA’07 Tokyo, Japan 24 / 24