Algebraic semantics (computer science)

From HandWiki

In computer science, algebraic semantics is a form of axiomatic semantics based on algebraic laws for describing and reasoning about program specifications in a formal manner.[1][2][3][4]

Syntax

The syntax of an algebraic specification is formulated in two steps: (1) defining a formal signature of data types and operation symbols, and (2) interpreting the signature through sets and functions.

Definition of a signature

The signature of an algebraic specification defines its formal syntax. The word "signature" is used like the concept of "key signature" in musical notation.

A signature consists of a set [math]\displaystyle{ S }[/math] of data types, known as sorts, together with a family [math]\displaystyle{ \Sigma }[/math] of sets, each set containing operation symbols (or simply symbols) that relate the sorts. We use [math]\displaystyle{ \Sigma_{s_1 s_2 ... s_n,~s} }[/math] to denote the set of operation symbols relating the sorts [math]\displaystyle{ s_1,~s_2,~...,~s_n \in S }[/math] to the sort [math]\displaystyle{ s \in S }[/math].

For example, for the signature of integer stacks, we define two sorts, namely, [math]\displaystyle{ int }[/math] and [math]\displaystyle{ stack }[/math], and the following family of operation symbols:

[math]\displaystyle{ \begin{align} \Sigma_{\Lambda,~stack} & = \{ {\rm new} \} \\ \Sigma_{int~stack,~stack} & = \{ {\rm push} \} \\ \Sigma_{stack,~stack} & = \{ {\rm pop} \} \\ \Sigma_{stack,~int} & = \{ {\rm depth}, {\rm top} \} \\ \end{align} }[/math]

where [math]\displaystyle{ \Lambda }[/math] denotes the empty string.

Set-theoretic interpretation of signature

An algebra [math]\displaystyle{ A }[/math] interprets the sorts and operation symbols as sets and functions. Each sort [math]\displaystyle{ s }[/math] is interpreted as a set [math]\displaystyle{ A_s }[/math], which is called the carrier of [math]\displaystyle{ A }[/math] of sort [math]\displaystyle{ s }[/math], and each symbol [math]\displaystyle{ \sigma }[/math] in [math]\displaystyle{ \Sigma_{s_1 s_2 ... s_n,~s} }[/math] is mapped to a function [math]\displaystyle{ \sigma_A : A_{s_1} \times A_{s_2} \times~... \times~A_{s_n} }[/math], which is called an operation of [math]\displaystyle{ A }[/math].

With respect to the signature of integer stacks, we interpret the sort [math]\displaystyle{ int }[/math] as the set [math]\displaystyle{ \Z }[/math] of integers, and interpret the sort [math]\displaystyle{ stack }[/math] as the set [math]\displaystyle{ Stack }[/math] of integer stacks. We further interpret the family of operation symbols as the following functions:

[math]\displaystyle{ \begin{align} {\rm new} & : ~ \to Stack \\ {\rm push} & : ~ \Z \times Stack \to Stack \\ {\rm pop} & : ~ Stack \to Stack \\ {\rm depth} & : ~ Stack \to \Z \\ {\rm top} & : ~ Stack \to \Z \\ \end{align} }[/math]

Semantics

Semantics refers to the meaning or behavior. An algebraic specification provides both the meaning and behavior of the object in question.

Equational axioms

The semantics of an algebraic specifications is defined by axioms in the form of conditional equations.[1]

With respect to the signature of integer stacks, we have the following axioms:

For any [math]\displaystyle{ z \in \Z }[/math] and [math]\displaystyle{ s \in Stack }[/math],
[math]\displaystyle{ \begin{align} & A1: ~~ {\rm pop} ({\rm push} (z, s)) = s \\ & A2: ~~ {\rm depth} ({\rm push} (z, s)) = {\rm depth} (s) + 1 \\ & A3: ~~ {\rm top} ({\rm push} (z, s)) = z \\ & A4: ~~ {\rm pop} ({\rm new}) = {\rm new} \\ & A5: ~~ {\rm depth} ({\rm new}) = 0 \\ & A6: ~~ {\rm top} (s) = -404 ~ {\rm if ~ depth} (s) = 0 \\ \end{align} }[/math]
where "[math]\displaystyle{ -404 }[/math]" indicates "not found".

Mathematical semantics

The mathematical semantics (also known as denotational semantics)[5] of a specification refers to its mathematical meaning.

The mathematical semantics of an algebraic specification is the class of all algebras that satisfy the specification. In particular, the classic approach by Goguen et al.[1][2] takes the initial algebra (unique up to isomorphism) as the "most representative" model of the algebraic specification.

Operational semantics

The operational semantics[6] of a specification means how to interpret it as a sequence of computational steps.

We define a ground term as an algebraic expression without variables. The operational semantics of an algebraic specification refers to how ground terms can be transformed using the given equational axioms as left-to-right rewrite rules, until such terms reach their normal forms, where no more rewriting is possible.

Consider the axioms for integer stacks. Let "[math]\displaystyle{ \Rrightarrow }[/math]" denote "rewrites to".

[math]\displaystyle{ \begin{align} & {\rm top} ({\rm pop} ({\rm pop} ({\rm push} (1,~{\rm push} (2,~{\rm push} (3,~{\rm pop} ({\rm new}))))))) & \\ \Rrightarrow ~ & {\rm top} ({\rm pop} ({\rm pop} ({\rm push} (1,~{\rm push} (2,~{\rm push} (3,~{\rm new})))))) & ({\rm by~Axiom~} A4) \\ \Rrightarrow ~ & {\rm top} ({\rm pop} ({\rm push} (2,~{\rm push} (3,~{\rm new})))) & ({\rm by~Axiom~} A1) \\ \Rrightarrow ~ & {\rm top} ({\rm push} (3,~{\rm new})) & ({\rm by~Axiom~} A1) \\ \Rrightarrow ~ & 3 & ({\rm by~Axiom~} A3) \\ \end{align} }[/math]

Canonical property

An algebraic specification is said to be confluent (also known as Church-Rosser) if the rewriting of any ground term leads to the same normal form. It is said to be terminating if the rewriting of any ground term will lead to a normal form after a finite number of steps. The algebraic specification is said to be canonical (also known as convergent) if it is both confluent and terminating. In other words, it is canonical if the rewriting of any ground term leads to a unique normal form after a finite number of steps.

Given any canonical algebraic specification, the mathematical semantics agrees with the operational semantics.[7]

As a result, canonical algebraic specifications have been widely applied to address program correctness issues. For example, numerous researchers have applied such specifications to the testing of observational equivalence of objects in object-oriented programming. See Chen and Tse[8] as a secondary source that provides a historical review of prominent research from 1981 to 2013.

See also

References

  1. 1.0 1.1 1.2 J.A. Goguen; J.W. Thatcher; E.G. Wagner; J.B. Wright (1977). "Initial algebra semantics and continuous algebras". Journal of the ACM 24 (1): 68–95. doi:10.1145/321992.321997. 
  2. 2.0 2.1 J.A. Goguen; J.W. Thatcher; E.G. Wagner (1978). "An initial algebra approach to the specification, correctness and implementation of abstract data types". in R.T. Yeh. Current Trends in Programming Methodology, Vol. IV: Data Structuring. Prentice Hall. pp. 80–149. 
  3. J.A. Goguen; C. Kirchner; H. Kirchner; A. Megrelis; J. Meseguer (1988). "An introduction to OBJ3". Proceedings of the First Workshop on Conditional Term Rewriting Systems. Lecture Notes in Computer Science. 308. Springer. pp. 258–263. doi:10.1007/3-540-19242-5_22. ISBN 978-3-540-19242-8. https://link.springer.com/chapter/10.1007/3-540-19242-5_22. 
  4. J.A. Goguen; G. Malcolm (1996). Algebraic Semantics of Imperative Programs. MIT Press. ISBN 9780262071727. https://mitpress.mit.edu/books/algebraic-semantics-imperative-programs. 
  5. David A. Schmidt (1986). Denotational Semantics: A Methodology for Language Development. William C. Brown Publishers. ISBN 9780205104505. 
  6. Gordon D. Plotkin (1981). A structural approach to operational semantics. Computer Science Department, Aarhus University. 
  7. S. Lucas; J. Meseguer (2014). "Strong and Weak Operational Termination of Order-Sorted Rewrite Theories". in S. Escobar. Rewriting Logic and Its Applications. Lecture Notes in Computer Science. 8663. Cham: Springer. pp. 178–194. doi:10.1007/978-3-319-12904-4_10. ISBN 978-3-319-12903-7. https://link.springer.com/book/10.1007/978-3-319-12904-4. 
  8. H.Y. Chen; T.H. Tse (2013). "Equality to equals and unequals: A revisit of the equivalence and nonequivalence criteria in class-level testing of object-oriented software". IEEE Transactions on Software Engineering 39 (11): 1549–1563. doi:10.1109/TSE.2013.33. https://doi.org/10.1109/TSE.2013.33.