# Computation tree logic

This article includes a list of references, but its sources remain unclear because it has insufficient inline citations. (October 2015) (Learn how and when to remove this template message) |

**Computation tree logic (CTL)** is a branching-time logic, meaning that its model of time is a tree-like structure in which the future is not determined; there are different paths in the future, any one of which might be an actual path that is realized. It is used in formal verification of software or hardware artifacts, typically by software applications known as model checkers which determine if a given artifact possesses safety or liveness properties. For example, CTL can specify that when some initial condition is satisfied (e.g., all program variables are positive or no cars on a highway straddle two lanes), then all possible executions of a program avoid some undesirable condition (e.g., dividing a number by zero or two cars colliding on a highway). In this example, the safety property could be verified by a model checker that explores all possible transitions out of program states satisfying the initial condition and ensures that all such executions satisfy the property. Computation tree logic is in a class of temporal logics that includes linear temporal logic (LTL). Although there are properties expressible only in CTL and properties expressible only in LTL, all properties expressible in either logic can also be expressed in CTL*.

CTL was first proposed by Edmund M. Clarke and E. Allen Emerson in 1981, who used it to synthesize so-called *synchronisation skeletons*, *i.e* abstractions of concurrent programs.

## Contents

## Syntax of CTLEdit

The language of well formed formulas for CTL is generated by the following grammar:

where ranges over a set of atomic formulas. It is not necessary to use all connectives – for example, comprises a complete set of connectives, and the others can be defined using them.

- means 'along All paths'
*(Inevitably)* - means 'along at least (there Exists) one path'
*(possibly)*

For example, the following is a well-formed CTL formula:

- )

The following is not a well-formed CTL formula:

The problem with this string is that can occur only when paired with an or an . It uses atomic propositions as its building blocks to make statements about the states of a system. CTL then combines these propositions into formulas using logical operators and temporal logics.

## OperatorsEdit

### Logical operatorsEdit

The logical operators are the usual ones: ¬,∨,∧,⇒ and ⇐. Along with these operators CTL formulas can also make use of the boolean constants true and false.

### Temporal operatorsEdit

The temporal operators are the following:

- Quantifiers over paths
**A***φ*–**A**ll:*φ*has to hold on all paths starting from the current state.**E***φ*–**E**xists: there exists at least one path starting from the current state where*φ*holds.

- Path-specific quantifiers
**X***φ*– Ne**x**t:*φ*has to hold at the next state (this operator is sometimes noted**N**instead of**X**).**G***φ*–**G**lobally:*φ*has to hold on the entire subsequent path.**F***φ*–**F**inally:*φ*eventually has to hold (somewhere on the subsequent path).*φ***U***ψ*–**U**ntil:*φ*has to hold*at least*until at some position*ψ*holds. This implies that*ψ*will be verified in the future.*φ***W***ψ*–**W**eak until:*φ*has to hold until*ψ*holds. The difference with**U**is that there is no guarantee that*ψ*will ever be verified. The**W**operator is sometimes called "unless".

In CTL*, the temporal operators can be freely mixed. In CTL, the operator must always be grouped in two: one path operator followed by a state operator. See the examples below. CTL* is strictly more expressive than CTL.

### Minimal set of operatorsEdit

In CTL there is a minimal set of operators. All CTL formulas can be transformed to use only those operators. This is useful in model checking. One minimal set of operators is: {true, ∨, ¬, **EG**, **EU**, **EX**}.

Some of the transformation used for temporal operator are:

**EF***φ*==**E**[true**U**(*φ*)] ( because**F***φ*== [true**U**(*φ*)] )**AX***φ*== ¬**EX**(¬*φ*)**AG***φ*== ¬**EF**(¬*φ*) == ¬**E**[true**U**(¬*φ*)]**AF***φ*==**A**[true**U***φ*] == ¬**EG**(¬*φ*)**A**[*φ***U***ψ*] == ¬(**E**[(¬*ψ*)**U**¬(*φ*∨*ψ*)] ∨**EG**(¬*ψ*) )

## Semantics of CTLEdit

### DefinitionEdit

CTL formulae are interpreted over Transition Systems. A transition system is a triple , where is a set of states, is a transition relation, assumed to be serial, i.e. every state has at least one successor, and is a labelling function, assigning propositional letters to states. Let be such a transition model

Then the relation of semantic entailment is defined recursively on :

### Characterisation of CTLEdit

Rules 10–15 above refer to computation paths in models and are what ultimately characterise the "Computation Tree"; they are assertions about the nature of the infinitely deep computation tree rooted at the given state .

### Semantic equivalencesEdit

The formulae and are said to be semantically equivalent if any state in any model which satisfies one also satisfies the other. This is denoted

It can be seen that A and E are duals, being universal and existential computation path quantifiers respectively: .

Furthermore, so are G and F.

Hence an instance of De Morgan's Laws can be formulated in CTL:

It can be shown using such identities that a subset of the CTL temporal connectives is adequate if it contains , at least one of and at least one of and the boolean connectives.

The important equivalences below are called the expansion laws; they allow to unfold the verification of a CTL connective towards its successors in time.

## ExamplesEdit

Let "P" mean "I like chocolate" and Q mean "It's warm outside."

**AG**.P

- "I will like chocolate from now on, no matter what happens."

**EF**.P

- "It's possible I may like chocolate some day, at least for one day."

**AF**.**EG**.P

- "It's always possible (AF) that I will suddenly start liking chocolate for the rest of time." (Note: not just the rest of my life, since my life is finite, while
**G**is infinite).

**EG**.**AF**.P

- "This is a critical time in my life. Depending on what happens next (E), it's possible that for the rest of time (G), there will always be some time in the future (AF) when I will like chocolate. However, if the wrong thing happens next, then all bets are off and there's no guarantee about whether I'll ever like chocolate."

The two following examples show the difference between CTL and CTL*, as they allow for the until operator to not be qualified with any path operator (**A** or **E**):

**AG**(P**U**Q)

- "From now until it's warm outside, I will like chocolate every single day. Once it's warm outside, all bets are off as to whether I'll like chocolate anymore. Oh, and it's guaranteed to be warm outside eventually, even if only for a single day."

**EF**((**EX**.P)**U**(**AG**.Q))

- "It's possible that: there will eventually come a time when it will be warm forever (AG.Q) and that before that time there will always be
*some*way to get me to like chocolate the next day (EX.P)."

## Relations with other logicsEdit

Computation tree logic (CTL) is a subset of CTL* as well as of the modal µ calculus. CTL is also a fragment of Alur, Henzinger and Kupferman's Alternating-time Temporal Logic (ATL).

Computation tree logic (CTL) and Linear temporal logic (LTL) are both a subset of CTL*. CTL and LTL are not equivalent and they have a common subset, which is a proper subset of both CTL and LTL.

**FG**.P exists in LTL but not in CTL.**AG**(P ((**EX**.Q) (**EX**¬Q))) and**AG.EF**.P exist in CTL but not in LTL.

## See alsoEdit

## ReferencesEdit

- E.M. Clarke; E.A. Emerson (1981). "Design and synthesis of synchronisation skeletons using branching time temporal logic".
*Logic of Programs, Proceedings of Workshop, Lecture Notes in Computer Science, Vol. 131*. Springer, Berlin: 52–71. - Michael Huth; Mark Ryan (2004).
*Logic in Computer Science (Second Edition)*. Cambridge University Press. p. 207. ISBN 978-0-521-54310-1. - Emerson, E. A.; Halpern, J. Y. (1985). "Decision procedures and expressiveness in the temporal logic of branching time".
*Journal of Computer and System Sciences*.**30**(1): 1–24. doi:10.1016/0022-0000(85)90001-7. - Clarke, E. M.; Emerson, E. A. & Sistla, A. P. (1986). "Automatic verification of finite-state concurrent systems using temporal logic specifications".
*ACM Transactions on Programming Languages and Systems*.**8**(2): 244–263. doi:10.1145/5397.5399. - Emerson, E. A. (1990). "Temporal and modal logic". In Jan van Leeuwen.
*Handbook of Theoretical Computer Science, vol. B*. MIT Press. pp. 955–1072. ISBN 978-0-262-22039-2.