Introduction to Model Checking

Total Page:16

File Type:pdf, Size:1020Kb

Introduction to Model Checking Introduction to Model Checking Cyrille Artho and Elena Troubitsyna KTH Royal Institute of Technology, Stockholm, Sweden School of Electrical Engineering and Computer Science Theoretical Computer Science [email protected] Cyrille Artho, KTH/EECS, 2019-03-26 Goal: Compute all possible system behaviors • Question: All possible outcomes of a program execution. No matter what the inputs/parameters are. • Answer: Enumerate all possibilities! → Model Checking. • Alternative: Reason about all outcomes (theorem proving). Cyrille Artho, KTH/EECS, 2019-03-26 1 Model Checking = state space search Trajectory P ? Counter−example S 0 Initial states • Traditionally applied to specifications, protocols, algorithms. • Certain types of software (embedded) can be mapped to such model checkers. Cyrille Artho, KTH/EECS, 2019-03-26 2 State space search P S U S 0 1 S 0 Cyrille Artho, KTH/EECS, 2019-03-26 3 State space search — 2 P S U S 0 1 ... U S 2 S 0 Cyrille Artho, KTH/EECS, 2019-03-26 4 State space search — 3 P S U S 0 1 ... U S ... U S 2 3 S 0 Cyrille Artho, KTH/EECS, 2019-03-26 5 Problem: State space explosion! A B • Process state space exponential in the size of the state. • Cross-product of processes. Cyrille Artho, KTH/EECS, 2019-03-26 6 Remedies Partial-order reduction System abstraction A B A B Cyrille Artho, KTH/EECS, 2019-03-26 7 Outline 1. The structure of common models: Kripke structures. 2. How to write (temporal) properties: (a) Linear Temporal Logic (LTL). (b) Computation Tree Logic (CTL). 3. How to use the NuSMV model checker, part 1. Cyrille Artho, KTH/EECS, 2019-03-26 8 How to define models: Kripke structures Trajectory P ? label ... Counter−example S 0 Initial states State transition system M = (S,S0,R,L). Each transition affects AP : atomic properties. S: set of states R : S × S: transition relation AP S0: set of initial states L: set of (action) labels: S → 2 2AP: power set: each atomic property is true or false at given state. Cyrille Artho, KTH/EECS, 2019-03-26 9 Example (by Ashutosh Gupta) S = {s1,s2,s3} s1 s2 S0 ={ } {p,q} {q} R = {(s1,s2),(s2,s1), } L = {(s1,{p,q}), s 3 } {p} Fill in the gaps Give some example paths that this system can generate! Cyrille Artho, KTH/EECS, 2019-03-26 10 Example (by Ashutosh Gupta) S = {s1,s2,s3} S0 ={s1} R = {(s1,s2),(s2,s1), s1 s2 (s2,s3),(s3,s3)} {p,q} {q} L = {(s1,{p,q}), (s2,{q}),(s3,{p})} s 3 Example paths: {p} hs1,s2,s3,s3i hs1,s2,s1,s2,s3i hs1,s2i (overline = inf. path) Cyrille Artho, KTH/EECS, 2019-03-26 11 Words generated by transition systems • Example: {p,q},{q},{p,q},{q},{p},... • Words can be infinitely long. • We need to reason about words (sequence of atomic properties). Cyrille Artho, KTH/EECS, 2019-03-26 12 How model is designed • We typically think of a „state” as certain (state) variables having certain values. • State transitions have preconditions and actions (more in next lecture). • Model checker translates this into (simpler but larger) Kripke structure. • Efficient algorithms to check reachability (more on that soon). • We could just label „bad” states but that’s not convenient. How to describe properties? Cyrille Artho, KTH/EECS, 2019-03-26 13 How to describe events and properties Cyrille Artho, KTH/EECS, 2019-03-26 14 Linear Temporal Logic (LTL) 1. Propositions: p, ¬p, p ∧ q, p ∨ q (also for subformulas) 2. Temporal operators X next U until F finally ♦ G globally Other operators exists but they are not used quite as frequently, and can be derived from the ones above. Cyrille Artho, KTH/EECS, 2019-03-26 15 Semantics: defined on paths 1. Propositions: p, ¬p, p ∧ q, p ∨ q (also for subformulas) Formula p is true if p holds in first state: w |= p if p ∈ w(0) Negation: w |= ¬p if w 6|= p; conjunct: w |= p ∧ q if w |= p and w |= q 2. Temporal operators X p next p w |= Xp if w1 |= p p U q until ∃ j ≥ 0,w j |= q ∧∀i,0 ≤ i < j,wi |= p F p finally ♦p true U p, equivalent to ∃ j ≥ 0,w j |= p G p globally p ¬F¬p, equivalent to ∀ j ≥ 0,w j |= p 3. Temporal operators can be nested. Furthermore, instead of just atomic propositions for p and q, we can also use other temporal formulas as subexpressions. Cyrille Artho, KTH/EECS, 2019-03-26 16 Examples finally globally F p G p next until X p p U q Cyrille Artho, KTH/EECS, 2019-03-26 17 Until true? true? !p, q !p, !q !p, q p U q p U q true? true? p, !q p, !q p, !q p, q p, q p U q p U q Cyrille Artho, KTH/EECS, 2019-03-26 18 Nesting true? FG p true? FG p How about infinite traces? Cyrille Artho, KTH/EECS, 2019-03-26 19 Computation Tree Logic 1. Propositions 2. Path quantifiers + temporal operators F AF p: For all paths, p is eventually true. A G AG p: For all paths, p is always true. AX p: For all paths, p is true in the next state. E X A[p U q]: For all paths, p holds until q holds. E: There exists a path. U 3. Temporal operators always follow path quantifier Cyrille Artho, KTH/EECS, 2019-03-26 20 Semantics: Defined on transition systems 1. Propositions: same as above 2. Temporal operators for model M(S,→,L) AX p ((M,s) |= AXp) ⇔ (∀hs → s1i((M,s1) |= p)) AG p ((M,s) |= AGp) ⇔ (∀hs1 → s2 → ...i(s = s1)∀i((M,si) |= p)) AF p ((M,s) |= AFp) ⇔ (∀hs1 → s2 → ...i(s = s1)∃i((M,si) |= p)) A [p U q] ((M,s) |= A[p U q]) ⇔∀(hs1 → s2 → ...i(s = s1)∃ j (((M,s j) |= q) ∧ (∀(i < j)(M,si) |= p))) E... defined analogously with existential path quantifier. 3. Temporal operators canNOT be directly nested. However, instead of just atomic propositions for p and q, we can also use other temporal formulas as subexpressions. Cyrille Artho, KTH/EECS, 2019-03-26 21 Computation Tree Logic (CTL): finally, globally finally globally for all paths AF p AG p there exists a path EF p EG p Cyrille Artho, KTH/EECS, 2019-03-26 22 Computation Tree Logic (CTL): next, until next until for all paths AX p A[ p U q ] there exists a path EX p E[ p U q ] Cyrille Artho, KTH/EECS, 2019-03-26 23 LTL 6= CTL 1. FG(p) 2. EX(p) • Which logic can express the formulas above? • What is the semantics of each formula? • Where does the counterpart fail to express it? CTL*: Combines LTL and CTL. Cyrille Artho, KTH/EECS, 2019-03-26 24 Safety vs. Liveness Safety: Something bad will never happen. Ensures absence of defects and hazards. Liveness: Something good eventually happens. Ensures progress. Which temporal logic operators are suitable for which type of property? Cyrille Artho, KTH/EECS, 2019-03-26 25 Summary Temporal logics Linear temporal logic (LTL): Computational tree logic (CTL): • No branching. • Branching. • Defined on paths. • Defined on transition systems. Model checking Enumerate all reachable states. • Check if „bad” state reachable. • Active research, many optimizations (such as BDDs). Cyrille Artho, KTH/EECS, 2019-03-26 26 SMV and NuSMV • Symbolic Model Verifier (SMV): First practical symbolic model checker by Ken McMillan/CMU. • Re-implementation NuSMV (open source) at IRST Trento, Italy. • NuSMV is still being maintained and developed. • Current version is 2.6.0 (used in this course). Cyrille Artho, KTH/EECS, 2019-03-26 27 NuSMV • Re-implementation NuSMV (open source) at IRST Trento, Italy. • NuSMV is still being maintained and developed. • Current version is 2.6.0 (used in this course). Cyrille Artho, KTH/EECS, 2019-03-26 28 Example: Vending machine ready choice made choice canceled expect item dispensed payment payment made dispense item Cyrille Artho, KTH/EECS, 2019-03-26 29 Details not modeled • How choice is made (how many choices) and canceled. → Button, timeout, both? • How payment is handled/accepted; price of goods. • Item dispenser mechanism, time taken to dispense item. Cyrille Artho, KTH/EECS, 2019-03-26 30 Example: Vending machine—2 ready choice made choice canceled expect item dispensed payment payment made dispense item • Three states: ready, expect payment, dispense item. • Two user inputs (non-deterministic): 1. Choice (of item); can be cancelled. 2. Payment (requires choice to be made first). Cyrille Artho, KTH/EECS, 2019-03-26 31 Vending machine in NuSMV MODULE main VAR choice, payment: boolean; state: { ready, expect payment, dispense item }; ASSIGN init (state) := ready; next (state) := case state = ready & choice: expect payment; state = expect payment & payment: dispense item; state = expect payment & !choice: ready; state = dispense item: ready; esac; Cyrille Artho, KTH/EECS, 2019-03-26 32 NuSMV syntax • Module, variables, assignments. • case (follows order of declaration); can have multiple outcomes. Cyrille Artho, KTH/EECS, 2019-03-26 33 Error message file vending.smv: line 3: at token ",": syntax error file vending.smv: line 3: Parser error NuSMV terminated by a signal • Cannot declare more than one variable per line! • Try again... Cyrille Artho, KTH/EECS, 2019-03-26 34 Another error message file vending.smv: line 14: case conditions are not exhaustive • Recall the case block: state = ready & choice: expect payment; state = expect payment & payment: dispense item; state = expect payment & !choice: ready; state = dispense item: ready; • State should remain the same by default: specify! Cyrille Artho, KTH/EECS, 2019-03-26 35 Complete case block ASSIGN init (state) := ready; next (state) := case state = ready & choice: expect payment; state = expect payment & payment: dispense item; state = expect payment & !choice: ready; state = dispense item: ready; TRUE: state; esac; • Transitions from ready and expect payment depend on user choice.
Recommended publications
  • Reasoning in the Temporal Logic of Actions Basic Research in Computer Science
    BRICS BRICS DS-96-1 U. Engberg: Reasoning in the Temporal Logic of Actions Basic Research in Computer Science Reasoning in the Temporal Logic of Actions The design and implementation of an interactive computer system Urban Engberg BRICS Dissertation Series DS-96-1 ISSN 1396-7002 August 1996 Copyright c 1996, BRICS, Department of Computer Science University of Aarhus. All rights reserved. Reproduction of all or part of this work is permitted for educational or research use on condition that this copyright notice is included in any copy. See back inner page for a list of recent publications in the BRICS Dissertation Series. Copies may be obtained by contacting: BRICS Department of Computer Science University of Aarhus Ny Munkegade, building 540 DK - 8000 Aarhus C Denmark Telephone: +45 8942 3360 Telefax: +45 8942 3255 Internet: [email protected] BRICS publications are in general accessible through WWW and anonymous FTP: http://www.brics.dk/ ftp ftp.brics.dk (cd pub/BRICS) Reasoning in the Temporal Logic of Actions The design and implementation of an interactive computer system Urban Engberg Ph.D. Dissertation Department of Computer Science University of Aarhus Denmark Reasoning in the Temporal Logic of Actions The design and implementation of an interactive computer system A Dissertation Presented to the Faculty of Science of the University of Aarhus in Partial Fulfillment of the Requirements for the Ph.D. Degree by Urban Engberg September 1995 Abstract Reasoning about algorithms stands out as an essential challenge of computer science. Much work has been put into the development of formal methods, within recent years focusing especially on concurrent algorithms.
    [Show full text]
  • Alternation-Free Modal Mu-Calculus for Data Trees (Extended Abstract)
    Alternation-free modal mu-calculus for data trees (Extended abstract) Marcin Jurdzi´nski and Ranko Lazi´c∗ Department of Computer Science, University of Warwick, UK Abstract The recent survey by Segoufin [30] summarises the sub- stantial progress made on reasoning about data words and An alternation-free modal µ-calculus over data trees is data trees. A data word is a word over a finite alphabet, introduced and studied. A data tree is an unranked or- with an equivalence relation on word positions. Implicitly, dered tree whose every node is labelled by a letter from every word position is labelled by an element (“datum”) a finite alphabet and an element (“datum”) from an infi- from an infinite set (“data domain”), but since the infinite nite set. For expressing data-sensitive properties, the calcu- set is equipped only with the equality predicate, it suffices lus is equipped with freeze quantification. A freeze quanti- to know which word positions are labelled by equal data, fier stores in a register the datum labelling the current tree and that is what the equivalence relation represents. Simi- node, which can then be accessed for equality comparisons larly, a data tree is a tree (countable, unranked and ordered) deeper in the formula. whose every node is labelled by a letter from a finite alpha- The main results in the paper are that, for the fragment bet, with an equivalence relation on the set of its nodes. with forward modal operators and one register, satisfiabi- First-order logic for data words was considered in [5], lity over finite data trees is decidable but not primitive re- where variables range over word positions ({0,...,l− 1} cursive, and that for the subfragment consisting of safety or N), there is a unary predicate for each letter from the formulae, satisfiability over countable data trees is decid- finite alphabet, and there is a binary predicate x ∼ y for able but not elementary.
    [Show full text]
  • Lecture 7: Computation Tree Logics
    Lecture 7: Computation Tree Logics Model of Computation Computation Tree Logics The Logic CTL Path Formulas and State Formulas CTL and LTL Expressive Power of Logics 1 Model of Computation a b State Transition Graph or Kripke Model b c c a b b c c a b c c Infinite Computation Tree (Unwind State Graph to obtain Infinite Tree) 2 Model of Computation (Cont.) Formally, a Kripke structure is a triple , where is the set of states, is the transition relation, and gives the set of atomic propositions true in each state. We assume that is total (i.e., for all states there exists a state such that ). A path in M is an infinite sequence of states, such that for , . We write to denote the suffix of starting at . Unless otherwise stated, all of our results apply only to finite Kripke structures. 3 Computation Tree Logics Temporal logics may differ according to how they handle branching in the underlying computation tree. In a linear temporal logic, operators are provided for describing events along a single computation path. In a branching-time logic the temporal operators quantify over the paths that are possible from a given state. 4 The Logic CTL The computation tree logic CTL combines both branching-time and linear-time operators. In this logic a path quantifier can prefix an assertion composed of arbitrary combinations of the usual linear-time operators. 1. Path quantifier: A—“for every path” E—“there exists a path” 2. Linear-time operators: X — holds next time. F — holds sometime in the future G — holds globally in the future U — holds until holds 5 Path Formulas and State Formulas The syntax of state formulas is given by the following rules: If , then is a state formula.
    [Show full text]
  • Computation Tree Logic Is Equivalent to Failure Trace Testing
    COMPUTATION TREE LOGIC IS EQUIVALENT TO FAILURE TRACE TESTING by A. F. M. NOKIB UDDIN A thesis submitted to the Department of Computer Science in conformity with the requirements for the degree of Master of Science Bishop’s University Sherbrooke, Quebec, Canada July 2015 Copyright c A. F. M. Nokib Uddin, 2015 Abstract The two major systems of formal verification are model checking and algebraic techniques such as model-based testing. Model checking is based on some form of temporal logic such as linear temporal logic (LTL) or computation tree logic (CTL). CTL in particular is capable of expressing most interesting properties of processes such as liveness and safety. Alge- braic techniques are based on some operational semantics of processes (such as traces and failures) and its associated preorders. The most fine-grained practical preorder is based on failure traces. The particular algebraic technique for formal verification based on failure traces is failure trace testing. It was shown earlier [8] that CTL and failure trace testing are equivalent; that is, for any failure trace test there exists a CTL formula equivalent to it, and the other way around. Both conversions are constructive and algorithmic. The proof of the conversion from fail- ure trace tests to CTL formulae and implicitly the associated algorithm is however incor- rect [6]. We now provide a correct proof for the existence of a conversion from failure trace tests to CTL formulae. We also offer intuitive support for our proof by providing worked ex- amples related to the examples used earlier [9] to support the conversion the other way around, thus going full circle not only with the conversion but also with our examples.
    [Show full text]
  • Model Checking with Mbeddr
    Model Checking for State Machines with mbeddr and NuSMV 1 Abstract State machines are a powerful tool for modelling software. Particularly in the field of embedded software development where parts of a system can be abstracted as state machine. Temporal logic languages can be used to formulate desired behaviour of a state machine. NuSMV allows to automatically proof whether a state machine complies with properties given as temporal logic formulas. mbedder is an integrated development environment for the C programming language. It enhances C with a special syntax for state machines. Furthermore, it can automatically translate the code into the input language for NuSMV. Thus, it is possible to make use of state-of-the-art mathematical proofing technologies without the need of error prone and time consuming manual translation. This paper gives an introduction to the subject of model checking state machines and how it can be done with mbeddr. It starts with an explanation of temporal logic languages. Afterwards, some features of mbeddr regarding state machines and their verification are discussed, followed by a short description of how NuSMV works. Author: Christoph Rosenberger Supervising Tutor: Peter Sommerlad Lecture: Seminar Program Analysis and Transformation Term: Spring 2013 School: HSR, Hochschule für Technik Rapperswil Model Checking with mbeddr 2 Introduction Model checking In the words of Cavada et al.: „The main purpose of a model checker is to verify that a model satisfies a set of desired properties specified by the user.” [1] mbeddr As Ratiu et al. state in their paper “Language Engineering as an Enabler for Incrementally Defined Formal Analyses” [2], the semantic gap between general purpose programming languages and input languages for formal verification tools is too big.
    [Show full text]
  • Finite-State Abstractions for Probabilistic Computation Tree Logic
    Imperial College London Department of Computing Finite-State Abstractions for Probabilistic Computation Tree Logic Daniel Wagner 2011 Supervised by Dr. Michael Huth Submitted in part fulfilment of the requirements for the degree of Doctor of Philosophy in Computing of Imperial College London and the Diploma of Imperial College London Declaration I herewith certify that all material in this dissertation which is not my own work has been duly acknowledged. Selected results from this dissertation have been disseminated in scientific publications as detailed in Chapter 1.10. Daniel Wagner 2 Abstract Probabilistic Computation Tree Logic (PCTL) is the established temporal logic for probabilistic verification of discrete-time Markov chains. Probabilis- tic model checking is a technique that verifies or refutes whether a property specified in this logic holds in a Markov chain. But Markov chains are of- ten infinite or too large for this technique to apply. A standard solution to this problem is to convert the Markov chain to an abstract model and to model check that abstract model. The problem this thesis therefore stud- ies is whether or when such finite abstractions of Markov chains for model checking PCTL exist. This thesis makes the following contributions. We identify a sizeable frag- ment of PCTL for which 3-valued Markov chains can serve as finite abstrac- tions; this fragment is maximal for those abstractions and subsumes many practically relevant specifications including, e.g., reachability. We also de- velop game-theoretic foundations for the semantics of PCTL over Markov chains by capturing the standard PCTL semantics via a two-player games.
    [Show full text]
  • Model Checking
    1 MODEL CHECKING Arie Gurfinkel 2 Overview • Kripke structures as models of computation • CTL, LTL and property patterns • CTL model-checking and counterexample generation • State of the Art Model-Checkers 3 SW/HW Correct? Correctness Artifact properties Model Translation Extraction Abstraction Finite Temporal Model logic Model Yes/No + Checker Counter-example 4 Models: Kripke Structures s 0 req req, s1 Conventional state machines busy • K = (V, S, s0, I , R) • V is a (finite) set of atomic s2 s3 propositions busy • S is a (finite) set of states • s0 S is a start state • I: S 2V is a labelling function that maps each state to the set of propositional variables that hold in it • That is, I(S) is a set of interpretations specifying which propositions are true in each state • R S S is a transition relation 5 Propositional Variables Fixed set of atomic propositions, e.g, {p, q, r} Atomic descriptions of a system “Printer is busy” “There are currently no requested jobs for the printer” “Conveyer belt is stopped” Do not involve time! 6 Modal Logic Extends propositional logic with modalities to qualify propositions • “it is raining” – rain • “it will rain tomorrow” – ☐rain • it is raining in all possible futures • “it might rain tomorrow” – ⃟rain • it is raining in some possible futures Modal logic formulas are interpreted over a collection of possible worlds connected by an accessibility relation Temporal logic is a modal logic that adds temporal modalities: next, always, eventually, and until 7 Computation Tree Logic (CTL) CTL: Branching-time
    [Show full text]
  • Lecture Notes on Computations & Computation Tree Logic
    15-414: Bug Catching: Automated Program Verification Lecture Notes on Computations & Computation Tree Logic Matt Fredrikson Andre´ Platzer Carnegie Mellon University Lecture 16 1 Introduction Linear temporal logic is a very important logic for model checking [Eme90, CGP99, BKL08] but has the downside that its verification algorithms are rather complex. To get a good sense of how model checking works, we, thus, consider the closely related but different(!) Computation Tree Logic (CTL) instead. Both LTL and CTL are common in model checking even if they have different advantages and downsides. The main point about LTL is that its semantics fixes a trace and then talks about temporal properties along that particular trace. CTL instead switches to a new trace every time a temporal operator is used. CTL has the advantage of having a pretty simple model checking algorithm. 2 Kripke Structures Definition 1 (Kripke structure). A Kripke frame (W; y) consists of a set W with a transi- tion relation y ⊆ W ×W where s y t indicates that there is a direct transition from s to t in the Kripke frame (W; y). The elements s 2 W are also called states. A Kripke struc- ture K = (W; y; v) is a Kripke frame (W; y) with a mapping v : W ! Σ ! ftrue; falseg assigning truth-values to all the propositional atoms in all states. The program semantics [[α]] which was defined as a relation of initial and final states in Lecture 3 is an example of a Kripke structure. Definition 2 (Computation structure). A Kripke structure K = (W; y; v) is called a computation structure if W is a finite set of states and every element s 2 W has at least one direct successor t 2 W with s y t.
    [Show full text]
  • Modal Mu-Calculi
    Modal Mu-Calculi Julian Bradfield and Colin Stirling Contents 1 Introduction 2 2 Contextual background 2 2.1 Modal logics in program verification 2 2.2 Precursors to modal mu-calculus 4 2.3 The small model property 5 3 Syntax and semantics of modal mu-calculus 5 3.1 Fixpoints as recursion 6 3.2 Approximating fixpoints and µ as ‘finitely’ 6 3.3 Syntax of Lµ 7 3.4 Semantics of Lµ 8 3.5 Examples 9 3.6 Fixpoint regeneration and the ‘fundamental semantic theorem’ 10 3.7 Modal equation systems 12 4 Expressive power 12 4.1 CTL and friends as fragments of Lµ 13 4.2 Bisimulation and tree model property 13 4.3 Lµ and automata 14 4.4 Lµ and games 15 5 Decidability of satisfiability 16 5.1 The aconjunctive fragment 17 5.2 Towards automata 17 5.3 Alternating parity automata 18 5.4 Automaton normal form 20 6 Complete axiomatization 21 7 Alternation 21 8 Bisimulation invariance 23 8.1 Lµ and MSOL 23 8.2 Multi-dimensional Lµ and Ptime 24 8.3 Bisimulation quantifiers and interpolation 25 9 Generalized mu-calculi 25 9.1 Lµ with past 25 9.2 Least fixpoint logic 26 9.3 Finite variable fixpoint logics 26 9.4 Guarded fragments 27 9.5 Inflationary mu-calculus 27 References 28 Preprint submitted to 15 November 2005 1 Introduction Modal mu-calculus is a logic used extensively in certain areas of computer science, but also of considerable intrinsic mathematical and logical interest. Its defining feature is the addition of inductive definitions to modal logic; thereby it achieves a great increase in expressive power, and an equally great increase in difficulty of understanding.
    [Show full text]
  • Model Checking Is Refinement— Computational Temporal Logic Is Equivalent to Failure Trace Testing
    Model Checking is Refinement— Computational Temporal Logic is Equivalent to Failure Trace Testing by Zhiyu ZHANG A thesis submitted to the Department of Computer Science in conformity with the requirements for the degree of Master of Science Bishop’s Unversity Sherbrooke, Quebec, Canada December 2008 Copyright @ Zhiyu ZHANG, 2008 Abstract The two major systems of formal verification are model checking and algebraic model-based testing. Model checking is based on some form of temporal logic such as linear temporal logic (LTL) or computational temporal logic (CTL). The most powerful and realistic logic being used is CTL, which is capable of expressing most interesting properties of processes such as liveness and safety. Model-based testing is based on some operational semantics of processes (such as traces, failures, or both) and their associated preoders. The most fine-grained preorder beside bisimulation (of theoretical importance only) is the one based on failure traces. We show that these two most powerful variants are equivalent. That is to say, we show that for any failure trace test, there exists a CTL formula equivalent to it (meaning that a system passes the test if and only if the system satisfies the formula and the other way around). When we specify the system, we can use temporal logic formulas such as CTL formulas to express the properties of it. We can also use algebraic method such as labelled transition system or finite state automaton to describe the system’s desired behaviour. If parts of a larger system are specified by these two means at the same time, combining the result of doing model checking and the result of applying model-based testing won’t be ideal, satisfactory and even correct.
    [Show full text]
  • A Probabilistic Temporal Logic with Frequency Operators and Its Model Checking
    A Probabilistic Temporal Logic with Frequency Operators and Its Model Checking Takashi Tomita Shigeki Hagihara Naoki Yonezaki Dept. of Computer Science, Graduate School of Information Science and Engineering, Tokyo Institute of Technology {tomita, hagihara, yonezaki}@fmx.cs.titech.ac.jp Probabilistic Computation Tree Logic (PCTL) and Continuous Stochastic Logic (CSL) are often used to describe specifications of probabilistic properties for discrete time and continuous time, respec- tively. In PCTL and CSL, the possibility of executions satisfying some temporal properties can be quantitatively represented by the probabilistic extension of the path quantifiers in their basic Com- putation Tree Logic (CTL), however, path formulae of them are expressed via the same operators in CTL. For this reason, both of them cannot represent formulae with quantitative temporal proper- ties, such as those of the form “some properties hold to more than 80% of time points (in a certain bounded interval) on the path.” In this paper, we introduce a new temporal operator which expressed the notion of frequency of events, and define probabilistic frequency temporal logic (PFTL) based on CTL∗. As a result, we can easily represent the temporal properties of behavior in probabilistic systems. However, it is difficult to develop a model checker for the full PFTL, due to rich expres- siveness. Accordingly, we develop a model-checking algorithm for the CTL-like fragment of PFTL against finite-state Markov chains, and an approximate model-checking algorithm for the bounded Linear Temporal Logic (LTL) -like fragment of PFTL against countable-state Markov chains. 1 Introduction To analyze probabilistic systems, probabilistic model checking is often used.
    [Show full text]
  • Temporal Representation and Reasoning
    Temporal Representation and Reasoning Michael Fisher∗ Department of Computer Science, University of Liverpool, UK In: F. van Harmelen, B. Porter and V. Lifschitz (eds) Handbook of Knowledge Representation,† c Elsevier 2007 This book is about representing knowledge in all its various forms. Yet, whatever phenomenon we aim to represent, be it natural, computational, or abstract, it is unlikely to be static. The natural world is always decaying or evolving. Thus, computational processes, by their nature, are dynamic, and most abstract notions, if they are to be useful, are likely to incorporate change. Consequently, the notion of representations changing through time is vital. And so, we need a clear way of representing both our temporal basis, and the way in which entities change over time. This is exactly what this chapter is about. We aim to provide the reader with an overview of many of the ways temporal phenomena can be modelled, described, reasoned about, and applied. In this, we will often overlap with other chapters in this collection. Some of these topics we will refer to very little, as they will be covered directly by other chapters, for example temporal action logic [84], situation calculus [185], event calculus [209], spatio-temporal reasoning [74], temporal constraint satisfaction [291], temporal planning [84, 271], and qualitative temporal reasoning [102]. Other topics will be described in this chapter, but overlap with descriptions in other chapters, in particular: • automated reasoning, in Section 3.2 and in [290]; • description logics, in Section 4.6 and in [154]; and • natural language, in Section 4.1 and in [250].
    [Show full text]