Abstract State Machines: Verification Problems and Complexity

Total Page:16

File Type:pdf, Size:1020Kb

Abstract State Machines: Verification Problems and Complexity Abstract State Machines: Verification Problems and Complexity Dissertation Marc Spielmann Rheinisch-Westf¨alische Technische Hochschule Aachen June 2000 Abstract Abstract state machines (ASMs) provide the formal foundation for a success- ful methodology for specification and verification of complex dynamic systems. In addition, ASMs induce a computation model on structures, which|in some sense|is more powerful and universal than the standard computation models in theoretical computer science. An investigation of ASMs is therefore interesting from both the point of view of applied computer science and the point of view of theoretical computer science. In the present thesis, practically relevant as well as theoretically motivated questions concerning ASMs are investigated. Subject of the first part of the thesis is the automatic verifiability of ASM specifications. In the second part, the ASM computation model itself and choiceless complexity classes, which have recently been defined by means of ASMs, are discussed. Acknowledgements I would like to thank my advisor, Erich Gr¨adel,for many stimulating discussions, helpful suggestions, and providing direction for my research. Without his advice and support this thesis would not have been possible. A special debt of gratitude I owe to Eric Rosen for numerous conversations on related and unrelated topics and for his countless but futile attempts to improve my English. I am grateful to Jan Van den Bussche for volunteering to review the thesis and for becoming a member of my dissertation committee. Thanks are also due to Andreas Blass and Yuri Gurevich for valuable comments and suggestions concerning the `choiceless' part of this thesis. Contents Introduction 1 Preliminaries 7 Logic . 7 Abstract State Machines . 9 I Automatic Verification 15 1 Verification of Abstract State Machines 17 1.1 The Verification Problem for ASMs . 18 1.2 Sequential Nullary ASMs . 25 1.3 Verifiability Results . 30 2 Verification of Relational Transducers for Electronic Commerce 41 2.1 ASM Relational Transducers . 44 2.2 Verification Problems . 49 2.3 Natural Restrictions . 53 2.4 Verifiability Results . 56 2.5 Proof of Containment . 61 3 Logical Foundation 75 3.1 A Witness-Bounded Fragment of Transitive-Closure Logic . 76 3.2 Existential Transitive-Closure Logic . 83 3.3 Existential Least Fixed-Point Logic . 88 3.4 In the Presence of Function Symbols . 91 4 Discussion 95 II Choiceless Complexity 97 5 Logarithmic-Space Reducibility via Abstract State Machines 99 5.1 Hereditarily Finite Sets as a Domain for Computation . 103 5.2 A Restricted Model . 107 5.3 Bounded-Memory ASMs . 113 5.4 Choiceless Logarithmic Space . 124 6 Logical Descriptions of Choiceless Computations 131 6.1 A Logic for Choiceless Logarithmic Space . 132 6.2 A Logic for Choiceless Polynomial Time . 138 7 Discussion 147 Bibliography 149 Index 154 Introduction Abstract state machines (ASMs, formerly called evolving algebras) [Gur91, Gur95, Gur97b, Gur99] provide the formal foundation for a successful methodology for specification and verification of complex dynamic systems. The design of com- plex hardware or software systems is typically organized as a series of refinement steps: starting with a high-level description of the system under consideration, one stepwise refines intermediate description stages until a low-level description is obtained. Ideally, the last description stage is close to an actual implementa- tion. The ASM method now proposes to describe each stage of the refinement process in terms of ASMs. The advantage of ASMs is that they are close to logic, which makes the overall design easily amenable to well-understood mathe- matical techniques. Essentially the mathematical foundation of ASMs supports the formal verification of dynamic systems designed by means of ASMs. For a comprehensive introduction to the ASM method the reader is referred to [B¨or99]. Although ASMs can be seen merely as a specification formalism, strictly speaking, ASMs constitute a computation model on structures. The program of an ASM is|like the program of a Turing machine|a description of how to modify the current configuration of a machine in order to obtain a possible succes- sor configuration. The main difference between an ASM and a Turing machine is that the configurations of an ASM are mathematical structures rather than strings. (We view the work tapes of a Turing machine as strings. Notice that strings are particularly simple, one-dimensional structures. Consequently, ev- ery Turing machine can be viewed a particularly simple ASM.) ASMs perform computations on structures in the sense that they obtain a structure as input, modify this structure step by step, and output the resulting structure when reach- ing a halting state. (Aside from this basic model, there exist more general types of ASM, e.g., real-time ASMs and distributed ASMs [BGR95, Gur95, GR00].) The fact that ASMs work on structures rather than strings has important con- sequences: the ASM computation model is, in some sense, more powerful and universal than the standard computation models in theoretical computer science [Gur91, Gur95, Gur99]. In this thesis, we study ASMs from a practical as well as a theoretical perspec- tive. In the first part, we regard the ASM language as a specification formalism that has been proved useful in practice, and investigate the automatic verifiability 1 2 Introduction of dynamic systems formalized in terms of ASMs. In the second part, we con- sider the ASM computation model itself and discuss choiceless complexity classes defined by means of ASMs. Part I: Automatic Verification The success of the ASM method is witnessed by numerous publications using ASMs for rigorous mathematical correctness proofs of large-scale applications [BH98]. Interestingly, most of the contributions that can be found in the literature focus on manual verification, while the number of contributions where all or part of the verification process is automated is rather small (for exceptions again consult [BH98]). In a nutshell, computer-aided verification of ASMs, i.e., the (semi-) automatic verification of dynamic systems formalized in terms of ASMs, has not yet been well developed. In the first part of the thesis, we investigate the automatic verifiability of ASMs. More precisely, we view the problem of verifying ASMs as a decision problem of the following kind and investigate the decidability of (a yet to be made precise version of) this problem: Given an ASM M and a correctness property ', decide whether M satisfies ' on all inputs. Since ASMs are computationally complete|they can calculate all computable functions|this problem is, in its full generality, undecidable. (It is an easy ex- ercise to define a reduction of the halting problem for Turing machines to the verification problem for ASMs.) Therefore, we examine the decidability of the verification problem with respect to classes of restricted ASMs. That is, we at- tempt to identify conditions on ASMs such that the verification problem becomes decidable for ASMs satisfying these conditions. Once decidability with respect to a class of restricted ASMs is established, all ASMs in this class are automatically verifiable in the sense that there exists a procedure which decides whether a given ASM satisfies a given correctness property on all inputs. Outline of Part I. The first part consists of three chapters, each of which can be read independently. In Chapter 1, we formally define the verification problem for ASMs, present a class of restricted ASMs that can be verified automatically, and show that for straightforward extensions of this class the verification problem becomes undecidable. In Chapter 2, we focus our attention on the automatic verifiability of ASMs specially tailored for electronic commerce applications. All positive verifiability results in the first two chapters are based on reductions to logical decision problems, which are proved decidable in Chapter 3. We conclude our investigation of the automatic verifiability of ASMs with a discussion at the end of Part I. Introduction 3 Part II: Choiceless Complexity The standard computation model in complexity theory is the Turing machine. Of course, there is no problem with this computation model as long as we consider computational problems whose input instances are strings. However, many com- putational problems arising in computer science and logic have input instances that are naturally viewed as structures rather than strings. For example, consider the problem of evaluating a database query Q, i.e., a mapping from databases to answer relations: given a database , i.e., a finite collection of relations on some finite domain, compute the answerD relation of Q on . The input instances of this problem are databases, which are structures. AtD first glance there is no problem with Turing machines for one can always encode structures as strings and in this way make structures amenable to Turing machines. Unfortunately, this approach has a subtle but important disadvantage: all known string repre- sentations of structures generally incorporate superfluous data into the encodings of structures, where by superfluous data we mean data that was originally not contained in the structures (such as a linear order on the universe of a structure). The problem now is that this superfluous data can be retrieved and `misused' by a Turing machine. Here is an example. Fix some standard encoding of databases and consider the class of polynomial- time bounded Turing machines computing mappings from (string representations of) databases to (string representations of) answer relations. In general, this class contains a Turing machine which, on input of a database , computes an answer relation that depends on the string representation of ,D and not necessarily on alone. More to the point, one can find a Turing machineD that computes on twoD different string representations of one and the same database two different, in particular, non-isomorphic, answer relations. The mapping computed by this Turing machine is not considered to be a database query for one is usually not interested in queries whose answer relations depend on the internal representation of databases.
Recommended publications
  • CASM: Implementing an Abstract State Machine Based Programming Language ∗
    CASM: Implementing an Abstract State Machine based Programming Language ∗ Roland Lezuo, Gergo¨ Barany, Andreas Krall Institute of Computer Languages (E185) Vienna University of Technology Argentinierstraße 8 1040 Vienna, Austria frlezuo,gergo,[email protected] Abstract: In this paper we present CASM, a general purpose programming language based on abstract state machines (ASMs). We describe the implementation of an inter- preter and a compiler for the language. The demand for efficient execution forced us to modify the definition of ASM and we discuss the impact of those changes. A novel feature for ASM based languages is symbolic execution, which we briefly describe. CASM is used for instruction set simulator generation and for semantic description in a compiler verification project. We report on the experience of using the language in those two projects. Finally we position ASM based programming languages as an elegant combination of imperative and functional programming paradigms which may liberate us from the von Neumann style as demanded by John Backus. 1 Introduction Most of the well known programming languages have a sequential execution semantics. Statements are executed in the order they appear in the source code of the program (im- perative programming). The effects of a statement – changes to the program’s state – are evaluated before the next statement is considered. Examples of such programming lan- guages are assembly languages, C, Java, Python and many more. Actually there are so many languages based on the imperative paradigm that it may even feel ”natural”. However, there seems to be a demand for alternative programming systems. John Backus even asked whether programming can be liberated from the von Neumann style [Bac78].
    [Show full text]
  • A Survey Paper on Abstract State Machines and How It Compares to Z and Vdm
    European Journal of Computer Science and Information Technology Vol.2,No.4,pp.1-7, December 2014 Published by European Centre for Research Training and Development UK (www.eajournals.org) A SURVEY PAPER ON ABSTRACT STATE MACHINES AND HOW IT COMPARES TO Z AND VDM 1Dominic Damoah, 2Edward Ansong, 3Henry Quarshie, 4Dominic Otieku-Asare Damoah 5 Steve Thorman, 6Roy Villafame 1234Department of Computer Science Valley View University Box AF 595 Adenta Accra, Ghana 56 Department of Computer Science and Engineering Andrews University Berrien Springs, Michigan, United States ABSTRACT: This codeless method of programming using ASMs is not only capable of producing transparent software but reliable, proven and checked, all the way through its specification as ground model to its implementation. In other words evolving algebra method supports all the software life-cycle phases from initial specifications or requirement gathering to executable code. Above all, this method is platform independent and the ease with which computer scientist can build simple and clean system models out of evolving algebra pushes further the potential it needs to influence future industrial formal methods techniques. This formal specifications and designs demonstrate the consistency between the specifications and the code for all possible data inputs at various levels of abstractions. KEYWORDS: Formal Methods, Evolving Algebra, Specification, Verification INTRODUCTION Abstract State Machines (ASM) is a typical formal methods technique which leans heavily on Evolving Algebras with a wide variety of applications in both Hardware and Software Engineering practices. It is a reliable, less expensive and very fast method of system design process for industrial applications. This is a mature engineering discipline for developing, designing and analyzing complex computer systems.
    [Show full text]
  • An Object-Oriented Approach for Hierarchical State Machines
    AN OBJECT-ORIENTED APPROACH FOR HIERARCHICAL STATE MACHINES WILLIAM MALLOUK 1 2 ESTEBAN CLUA 1 Wet Productions LLC [email protected] 2Departamento de Informática – PUC-Rio / VisionLab [email protected] __________________________________________________________________________________________ Abstract Finite State Machines have been widely used as a tool for developing video games, especially as pertains to solving problems related to AI, input handling, and game progression. In this paper, we introduce a practical technique that can highly improve the productivity of development of Finite State Machines in video games. This technique consists of adapting concepts of OOP for use with Hierarchical Finite State Machines in an entirely visual system. An open source implementation of the technique that can be used as middleware in most games is also provided. Keywords: Artificial Intelligence, Hierarchical State Machines __________________________________________________________________________________________ 1 Introduction 2 Hierarchical Finite State Machines In FSM (Finite State Machines) is a technique that Games appears in many different forms and is used in We recall from [1] and [4] the idea of Finite major game titles such as Quake, Fifa Soccer, State Machines and Hierarchical State and Warcraft. In fact, FSM is the most popular Machines as used in games. An HFSM is a FSM approach for AI algorithms used in games [4]. In this paper, we demonstrate how Hierarchical in which states can be decomposed into other Finite State Machines can be combined with FSMs [4], as depicted in Figure 1. Object-Oriented Programming techniques to KeyP : ress For obtain productivity and HFSM reuse. We also ward provide an open-source implementation of the Transition technique as middleware that can be used in condition nearly any game.
    [Show full text]
  • A Toolset for Supporting UML Static and Dynamic Model Checking
    A Toolset for Supporting UML Static and Dynamic Model Checking Wuwei Shen£ Dept of Computer Science, Western Michigan University [email protected] Kevin Compton James Huggins Dept. of EECS, The University of Michigan Computer Science Program, Kettering University [email protected] [email protected] Abstract rules are provided using the Object Constraint Language. Finally the Semantics are described primarily in natural language. The Unified Modeling Language has become widely accepted Based on the metamodel of UML, we apply Abstract State Ma- as a standard in software development. Several tools have been chines in giving the semantics for the above three views in this produced to support UML model validation. However, most of project. We give the ASM semantics for class diagrams, Object them support either static or dynamic model checking; and no Constraint Language and the semantics parts for UML in our tools. tools support to check both static and dynamic aspects of a UML Therefore, a user can have syntax checking for a UML model by model . But a UML model should include the static and dynamic comparing it with the UML metamodel. aspects of a software system. Furthermore, these UML tools trans- The architecture of the UML is based on the four-layer meta- late a UML model into a validation language such as PROMELA. model structure, which consists of the following layers: user ob- But they have some shortcomings: there is no proof of correctness jects, model, meta-model and meta-metamodel. According to the (with respect to the UML semantics) for these tools. In order to UML document [16], a UML model defines a language to describe overcome these shortcomings, we present a toolset which can val- an information domain; however, user objects are an instance of a idate both static and dynamic aspects of a model; and this toolset model, which defines a specific information domain.
    [Show full text]
  • The Abstract Machine a Pattern for Designing Abstract Machines
    The Abstract Machine A Pattern for Designing Abstract Machines Julio García-Martín Miguel Sutil-Martín Universidad Politécnica de Madrid1. Abstract Because of the increasing gap between modern high-level programming languages and existing hardware, it has often become necessary to introduce intermediate languages and to build abstract machines on top of the primitive hardware. This paper describes the ABSTRACT- MACHINE, a structural pattern that captures the essential features addressing the definition of abstract machines. The pattern describes both the static and dynamic features of abstract machines as separate components, as well as it considers the instruction set and the semantics for these instructions as other first-order components of the pattern. Intent Define a common template for the design of Abstract Machines. The pattern captures the essential features underlying abstract machines (i.e., data area, program, instruction set, etc...), encapsulating them in separated loose-coupled components into a structural pattern. Furthermore, the proposal provides the collaboration structures how components of an abstract machine interact. Also known as Virtual Machine, Abstract State Machine. Motivation Nowadays, one of the buzziest of the buzzwords in computer science is Java. Though to be an object- oriented language for the development of distributed and GUI applications, Java is almost every day adding new quite useful programming features and facilities. As a fact, in the success of Java has been particular significant of Java the use of the virtual machine's technology2. As well known, the Java Virtual Machine (JVM) is an abstract software-based machine that can operate over different microprocessor machines (i.e., hardware independent).
    [Show full text]
  • Introducing Asml: a Tutorial for the Abstract State Machine Language
    Introducing AsmL: A Tutorial for the Abstract State Machine Language December 19, 2001 Revised May 23, 2002 Abstract This paper is an introduction to specifying robust software components using AsmL, the Abstract State Machine Language. Foundations of Software Engineering -- Microsoft Research (c) Microsoft Corporation. All rights reserved. 1 Introduction.............................................................................................. 1 1.1 Audience 1 1.2 Organization of the document 1 1.3 Notation 1 2 Models ...................................................................................................... 2 2.1 Abstract state 2 2.2 Distinct operational steps 3 2.3 The evolution of state variables 3 3 Programs .................................................................................................. 7 3.1 Hello, world 7 3.2 Reading a file 8 4 Steps ...................................................................................................... 11 4.1 Stopping conditions 11 4.1.1 Stopping for fixed points 11 4.1.2 Stopping for conditions 12 4.2 Sequences of steps 12 4.3 Iteration over collections 13 4.4 Guidelines for using steps 14 5 Updates .................................................................................................. 15 5.1 The update statement 15 5.2 When updates occur 16 5.3 Consistency of updates 17 5.4 Total and partial updates 18 6 Methods ................................................................................................. 20 6.1 Functions and update procedures 21 6.2
    [Show full text]
  • Generating Finite State Machines from Abstract State Machines
    Generating Finite State Machines from Abstract State Machines Wolfgang Grieskamp Yuri Gurevich Wolfram Schulte Margus Veanes Microsoft Research Microsoft Research Microsoft Research Microsoft Research Redmond, WA Redmond, WA Redmond, WA Redmond, WA [email protected] [email protected] [email protected] [email protected] We start with an abstract state machine which models some ABSTRACT implementation under test (IUT) and which is written in AsmL; this model will be referred to as the ASM or the ASM spec. The We give an algorithm that derives a finite state machine (FSM) ASM may have too many, often infinitely many, states. To this from a given abstract state machine (ASM) specification. This end, we group ASM states into finitely many hyperstates. This allows us to integrate ASM specs with the existing tools for test gives rise to a finite directed graph or finite state machine whose case generation from FSMs. ASM specs are executable but have nodes are the generated hyperstates. Then state transitions of the typically too many, often infinitely many states. We group ASM ASM are used to generate links between hyperstates. Let us note states into finitely many hyperstates which are the nodes of the that it is not necessary to first produce an FSM and then use the FSM. The links of the FSM are induced by the ASM state FSM for test generation. The graph-generating procedure itself transitions. can be used to produce a test suite as a byproduct. The FSM-generating algorithm is a particular kind of graph Keywords reachability algorithm. It starts from the initial state and builds up finite state machine, FSM, abstract state machine, ASM, test case a labeled state transition graph by invoking actions that are parts generation, executable specification of the ASM.
    [Show full text]
  • Model Checking Abstract State Machines
    Model Checking Abstract State Machines vorgelegt von Diplom-Informatikerin Kirsten Winter aus Uelzen Von der Fakult¨at IV - Elektrotechnik und Informatik der Technischen Universit¨at Berlin zur Erlangung des akademischen Grades Doktor der Ingenieurwissenschaften – Dr.-Ing. – genehmigte Dissertation Promotionsausschuß: Vorsitzender: Prof. Dr.-Ing. G. Hommel Berichter: Prof. Dr.-Ing. S. J¨ahnichen Berichter: Prof. Dr. W. Reisig Tag der wissenschaftlichen Aussprache: 17. Juli 2001 Berlin, 2001 D 83 Acknowledgements First of all, I would like to thank my supervisor Stefan J¨ahnichen who employed me as a PhD student at GMD FIRST. His open and personal approach towards his group strongly influenced my development from a student to a researcher. I was given much scope in choosing my own direction for my PhD topic. Moreover, the opportunity of working on other research projects encouraged me to consider many areas of related work. My experience at GMD FIRST has provided me with a broad background in the field of formal methods that will be useful in the future, I am sure. Next, I would like to thank Wolfgang Reisig for spontaneously agreeing to be my second supervisor. His discussions, often very critical, on drafts of this work helped improve it alot. I very much appreciated the time he took with me to go through his comments. Something one must learn when doing a PhD is to defend their results. I guess, a big part of this I learned on the other side of the road, at the Humboldt University. Also, Egon B¨orger’s support has had a great impact on this thesis.
    [Show full text]
  • Sequential Abstract State Machines Capture Sequential Algorithms
    Sequential Abstract State Machines Capture Sequential Algorithms Yuri Gurevich Microsoft Research One Microsoft Way Redmond, WA 98052, USA We examine sequential algorithms and formulate a Sequential Time Postulate, an Abstract State Postulate, and a Bounded Exploration Postulate. Analysis of the postulates leads us to the notion of sequential abstract state machine and to the theorem in the title. First we treat sequential algorithms that are deterministic and noninteractive. Then we consider sequential algorithms that may be nondeterministic and that may interact with their environments. Categories and Subject Descriptors: F.1.1 [Theory of Computation]: Models of Computation; I.6.5 [Computing Methodologies]: Model Development—Modeling methodologies General Terms: Computation Models, Simulation, High-Level Design Additional Key Words and Phrases: Turing’s thesis, sequential algorithm, abstract state machine, sequential ASM thesis 1. INTRODUCTION In 1982, I moved from mathematics to computer science. Teaching a programming language, I noticed that it was interpreted differently by different compilers. I wondered — as many did before me — what is exactly the semantics of the pro- gramming language? What is the semantics of a given program? In this connection, I studied the wisdom of the time, in particular denotational semantics and algebraic specifications. Certain aspects of those two rigorous approaches appealed to this logician and former algebraist; I felt though that neither approach was realistic. It occurred to me that, in some sense, Turing solved the problem of the semantics of programs. While the “official” Turing thesis is that every computable function is Turing computable, Turing’s informal argument in favor of his thesis justifies a stronger thesis: every algorithm can be simulated by a Turing machine.
    [Show full text]
  • Code Generation from an Abstract State Machine Into Contracted C
    Code Generation from an Abstract State Machine into Contracted C# Supervisor: Joseph R. Kiniry Thesis by: Asger Jensen Date of birth: 10-11-82 Email: [email protected] Thesis start: 01-12-11 Thesis end: 01-06-12 Abstract In computer science designing systems, whether it is hardware or software, using an abstract state machine diagram to model the system is a common approach. When using the diagram as a blueprint for programming, it is possible to lose the equality between the diagram and the actual code, not to mention the time that was spent creating the code. Having a tool which generates skeleton code from a state machine is not a new idea. In 2003 Engelbert Hubbers and Martijn Oostdijk created the AutoJML tool, which derives Java Modeling Language specifications from UML state diagrams. The same kind of tool does not exist in the .NET environment. Visual Studio 2010 does offer the possibilities of creating state machine diagrams, but it is not possible to generate code from the diagram. This thesis is about creating such a tool, based on Hubbers and Oostdijk work, where the user can create their abstract state machine diagram and generate contracted skeleton C# code from it. To accomplice this, a Domain Specific Language has been created, with an added feature to generate code. The user can create their state machine by adding states and transitions, specify what states should be initial-, normal- and final state, fill out the transition properties and initiate the validation and generation of the code. Code Contracts is used in the generated code to keep the constraints of the abstract state machine diagram.
    [Show full text]
  • Simulator for Real-Time Abstract State Machines
    Simulator for Real-Time Abstract State Machines P. Vasilyev1,2⋆ 1 Laboratory of Algorithmics, Complexity and Logic, Department of Informatics, University Paris-12, France 2 Computer Science Department, University of Saint Petersburg, Russia Abstract. We describe a concept and design of a simulator of Real-Time Ab- stract State Machines. Time can be continuous or discrete. Time constraints are defined by linear inequalities. Two semantics are considered: with and without non-deterministic bounded delays between actions. Simulation tasks can be gen- erated according to descriptions in a special language. The simulator will be used for on-the-fly verification of formulas in an expressible timed predicate logic. Several features facilitating the simulation are described: external functions defi- nition, delays settings, constraints specification, and others. 1 Introduction Usually the process of software development consists of several main steps: analysis, design, specification, implementation, and testing. The steps can be iterated several times and accompanied by this or that validation. We are interested in the validation by simulation of program specifications with respect to the given requirements. We con- sider real-time reactive systems with continuous or discrete time. Time constraints are expressed by linear inequalities and programs are specified as Abstract State Machines (ASM) [1]. The requirements are expressed in a First Order Timed Logic (FOTL) [2, 3]. The specification languages we consider are very powerful. Even rather simple, “basic” ASMs [4] are sufficient to represent any algorithmic state machine with exact isomor- phic modeling of runs. This formalism bridges human understanding, programming and logic. The ASM method has a number of successful practical applications, e.g., SDL semantics, UPnP protocol specification, semantics of VHDL, C, C++, Java, Prolog (see [5, 6]).
    [Show full text]
  • The Abstract State Machines Method for Modular Design and Analysis of Programming Languages
    The Abstract State Machines Method for Modular Design and Analysis of Programming Languages Egon B¨orger Universit`adi Pisa, Dipartimento di Informatica, I-56125 Pisa, Italy [email protected] Abstract. We survey the use of Abstract State Machines in the area of programming languages, namely to define behavioral properties of programs at source, intermediate and machine levels in a way that is amenable to mathematical and experimental analysis by practitioners, like correctness and completeness of compilers, etc. We illustrate how theorems about such properties can be integrated into a modular de- velopment of programming languages and programs, using as example a Java/JVM compilation correctness theorem about defining, interpreting, compiling, and executing Java/JVM code. We show how programming features (read: programming constructs) modularize not only the source programs, but also the program property statements and their proofs.1 1 Introduction The history of what became The Abstract State Machines Method for Modular Design and Analysis of Programming Languages starts with simple small ex- amples of Abstract State Machines (ASMs) from where I learnt the concept2| which at the time came with various tentative definitions and under various names: `dynamic structures', `dynamic algebras', `evolving algebras'. The exam- ples specified the semantics of Turing and stack machines [101, Sect. 4, 6] and of some tiny Pascal programs [100, Sect. 10, 11]. The idea to use `dynamic struc- tures' for an operational definition of the semantics of imperative programming constructs was pursued further in Morris' PhD thesis [131]. Although this model covers only the core language features of Modula-2, it nevertheless is of large size, complicated, hard to understand and not scalable, the technical reason being that it is flat and unstructured.
    [Show full text]