# Formal methods

In computer science, specifically software engineering and hardware engineering, **formal methods** are a particular kind of mathematically based techniques for the specification, development and verification of software and hardware systems.^{[1]} The use of formal methods for software and hardware design is motivated by the expectation that, as in other engineering disciplines, performing appropriate mathematical analysis can contribute to the reliability and robustness of a design.^{[2]}

Formal methods are best described as the application of a fairly broad variety of theoretical computer science fundamentals, in particular logic calculi, formal languages, automata theory, discrete event dynamic system and program semantics, but also type systems and algebraic data types to problems in software and hardware specification and verification.^{[3]}

## Contents

## Taxonomy[edit]

Formal methods can be used at a number of levels:

**Level 0:** Formal specification may be undertaken and then a program developed from this informally. This has been dubbed *formal methods lite*, this may be the most cost-effective option in many cases.

**Level 1:** Formal development and formal verification may be used to produce a program in a more formal manner. For example, proofs of properties or refinement from the specification to a program may be undertaken, this may be most appropriate in high-integrity systems involving safety or security.

**Level 2:** Theorem provers may be used to undertake fully formal machine-checked proofs. This can be very expensive and is only practically worthwhile if the cost of mistakes is extremely high (e.g., in critical parts of microprocessor design).

Further information on this is expanded below.

As with programming language semantics, styles of formal methods may be roughly classified as follows:

- Denotational semantics, in which the meaning of a system is expressed in the mathematical theory of domains. Proponents of such methods rely on the well-understood nature of domains to give meaning to the system; critics point out that not every system may be intuitively or naturally viewed as a function.
- Operational semantics, in which the meaning of a system is expressed as a sequence of actions of a (presumably) simpler computational model. Proponents of such methods point to the simplicity of their models as a means to expressive clarity; critics counter that the problem of semantics has just been delayed (who defines the semantics of the simpler model?).
- Axiomatic semantics, in which the meaning of the system is expressed in terms of preconditions and postconditions which are true before and after the system performs a task, respectively. Proponents note the connection to classical logic; critics note that such semantics never really describe what a system
*does*(merely what is true before and afterwards).

### Lightweight formal methods[edit]

Some practitioners believe that the formal methods community has overemphasized full formalization of a specification or design,^{[4]}^{[5]} they contend that the expressiveness of the languages involved, as well as the complexity of the systems being modelled, make full formalization a difficult and expensive task. As an alternative, various *lightweight* formal methods, which emphasize partial specification and focused application, have been proposed. Examples of this lightweight approach to formal methods include the Alloy object modelling notation,^{[6]} Denney's synthesis of some aspects of the Z notation with use case driven development,^{[7]} and the CSK VDM Tools.^{[8]}

## Uses[edit]

Formal methods can be applied at various points through the development process.

### Specification[edit]

Formal methods may be used to give a description of the system to be developed, at whatever level(s) of detail desired, this formal description can be used to guide further development activities (see following sections); additionally, it can be used to verify that the requirements for the system being developed have been completely and accurately specified.

The need for formal specification systems has been noted for years; in the ALGOL 58 report,^{[9]} John Backus presented a formal notation for describing programming language syntax, later named Backus normal form then renamed Backus–Naur form (BNF).^{[10]} Backus also wrote that a formal description of the meaning of syntactically valid ALGOL programs wasn't completed in time for inclusion in the report. "Therefore the formal treatment of the semantics of legal programs will be included in a subsequent paper." It never appeared.

### Development[edit]

Once a formal specification has been produced, the specification may be used as a guide while the concrete system is developed during the design process (i.e., realized typically in software, but also potentially in hardware). For example:

- If the formal specification is in an operational semantics, the observed behavior of the concrete system can be compared with the behavior of the specification (which itself should be executable or simulateable). Additionally, the operational commands of the specification may be amenable to direct translation into executable code.
- If the formal specification is in an axiomatic semantics, the preconditions and postconditions of the specification may become assertions in the executable code.

### Verification[edit]

Once a formal specification has been developed, the specification may be used as the basis for proving properties of the specification (and hopefully by inference the developed system).

#### Human-directed proof[edit]

Sometimes, the motivation for proving the correctness of a system is not the obvious need for reassurance of the correctness of the system, but a desire to understand the system better. Consequently, some proofs of correctness are produced in the style of mathematical proof: handwritten (or typeset) using natural language, using a level of informality common to such proofs. A "good" proof is one which is readable and understandable by other human readers.

Critics of such approaches point out that the ambiguity inherent in natural language allows errors to be undetected in such proofs; often, subtle errors can be present in the low-level details typically overlooked by such proofs. Additionally, the work involved in producing such a good proof requires a high level of mathematical sophistication and expertise.

#### Automated proof[edit]

In contrast, there is increasing interest in producing proofs of correctness of such systems by automated means. Automated techniques fall into three general categories:

- Automated theorem proving, in which a system attempts to produce a formal proof from scratch, given a description of the system, a set of logical axioms, and a set of inference rules.
- Model checking, in which a system verifies certain properties by means of an exhaustive search of all possible states that a system could enter during its execution.
- Abstract interpretation, in which a system verifies an over-approximation of a behavioural property of the program, using a fixpoint computation over a (possibly complete) lattice representing it.

Some automated theorem provers require guidance as to which properties are "interesting" enough to pursue, while others work without human intervention. Model checkers can quickly get bogged down in checking millions of uninteresting states if not given a sufficiently abstract model.

Proponents of such systems argue that the results have greater mathematical certainty than human-produced proofs, since all the tedious details have been algorithmically verified, the training required to use such systems is also less than that required to produce good mathematical proofs by hand, making the techniques accessible to a wider variety of practitioners.

Critics note that some of those systems are like oracles: they make a pronouncement of truth, yet give no explanation of that truth. There is also the problem of "verifying the verifier"; if the program which aids in the verification is itself unproven, there may be reason to doubt the soundness of the produced results. Some modern model checking tools produce a "proof log" detailing each step in their proof, making it possible to perform, given suitable tools, independent verification.

The main feature of the abstract interpretation approach is that it provides a sound analysis, i.e. no false negatives are returned. Moreover, it is efficiently scalable, by tuning the abstract domain representing the property to be analyzed, and by applying widening operators^{[11]} to get fast convergence.

## Applications[edit]

Formal methods are applied in different areas of hardware and software, including routers, Ethernet switches, routing protocols, and security applications. There are several examples in which they have been used to verify the functionality of the hardware and software used in DCs^{[clarification needed]}. IBM used ACL2, a theorem prover, in AMD x86 processor development process^{[citation needed]}. Intel uses such methods to verify its hardware and firmware (permanent software programmed into a read-only memory)^{[citation needed]}. Dansk Datamatik Center used formal methods in the 1980s to develop a compiler system for the Ada programming language that went on to become a long-lived commercial product.^{[12]}^{[13]}

There are several other projects of NASA in which formal methods are applied, such as Next Generation Air Transportation System^{[citation needed]}, Unmanned Aircraft System integration in National Airspace System,^{[14]} and Airborne Coordinated Conflict Resolution and Detection (ACCoRD).^{[15]} B-Method with AtelierB,^{[16]} is used to develop safety automatisms for the various subways installed throughout the world by Alstom and Siemens, and also for Common Criteria certification and the development of system models by ATMEL and STMicroelectronics.

Formal verification has been frequently used in hardware by most of the well-known hardware vendors, such as IBM, Intel, and AMD. There are many areas of hardware, where Intel have used FMs to verify the working of the products, such as parameterized verification of cache coherent protocol,^{[17]} Intel Core i7 processor execution engine validation ^{[18]} (using theorem proving, BDDs, and symbolic evaluation), optimization for Intel IA-64 architecture using HOL light theorem prover,^{[19]} and verification of high performance dual-port gigabit Ethernet controller with a support for PCI express protocol and Intel advance management technology using Cadence.^{[20]} Similarly, IBM has used formal methods in the verification of power gates,^{[21]} registers,^{[22]} and functional verification of the IBM Power7 microprocessor.^{[23]}

## In software development[edit]

In software development, formal methods are mathematical approaches to solving software (and hardware) problems at the requirements, specification, and design levels. Formal methods are most likely to be applied to safety-critical or security-critical software and systems, such as avionics software. Software safety assurance standards, such as DO-178B, DO-178C, and Common Criteria demand formal methods at the highest levels of categorization.

For sequential software, examples of formal methods include the B-Method, the specification languages used in automated theorem proving, RAISE, and the Z notation.

In functional programming, property-based testing has allowed the mathematical specification and testing (if not exhaustive testing) of the expected behaviour of individual functions.

The Object Constraint Language (and specializations such as Java Modeling Language) has allowed object-oriented systems to be formally specified, if not necessarily formally verified.

For concurrent software and systems, Petri nets, process algebra, and finite state machines (which are based on automata theory - see also virtual finite state machine or event driven finite state machine) allow executable software specification and can be used to build up and validate application behavior.

Another approach to formal methods in software development is to write a specification in some form of logic—usually a variation of first-order logic (FOL)—and then to directly execute the logic as though it were a program, the OWL language, based on Description Logic (DL), is an example. There is also work on mapping some version of English (or another natural language) automatically to and from logic, and executing the logic directly. Examples are Attempto Controlled English, and Internet Business Logic, which do not seek to control the vocabulary or syntax. A feature of systems that support bidirectional English-logic mapping and direct execution of the logic is that they can be made to explain their results, in English, at the business or scientific level.^{[citation needed]}

## Formal methods and notations[edit]

This section
is in a list format that may be better presented using prose. (August 2009) |

There are a variety of formal methods and notations available.

### Specification languages[edit]

- Abstract State Machines (ASMs)
- A Computational Logic for Applicative Common Lisp (ACL2)
- ANSI/ISO C Specification Language (ACSL)
- Alloy
- Autonomic System Specification Language (ASSL)
- B-Method
- CADP
- Common Algebraic Specification Language (CASL)
- Java Modeling Language (JML)
- Knowledge Based Software Assistant (KBSA)
- Process calculi
- Actor model
- Esterel
- Lustre
- mCRL2
- Perfect Developer
- Petri nets
- Predicative programming
- RAISE
- Rebeca Modeling Language
- SPARK Ada
- Spec sharp (Spec#)
- Specification and Description Language
- TLA+
- USL
- VDM
- VDM-SL
- VDM++

- Z notation

### Model checkers[edit]

- SPIN
- PAT is a powerful free model checker, simulator and refinement checker for concurrent systems and CSP extensions (e.g. shared variables, arrays, fairness).
- MALPAS Software Static Analysis Toolset is an industrial strength model checker used for formal proof of safety-critical systems
- UPPAAL
- ESBMC

## See also[edit]

- Abstract interpretation
- Automated theorem proving
- Design by contract
- Formal methods people
- Formal specification
- Formal verification
- Formal system
- Model checking
- Software engineering
- Specification language

## References[edit]

**^**R. W. Butler (2001-08-06). "What is Formal Methods?". Retrieved 2006-11-16.**^**C. Michael Holloway. "Why Engineers Should Consider Formal Methods" (PDF). 16th Digital Avionics Systems Conference (27–30 October 1997). Archived from the original (PDF) on 16 November 2006. Retrieved 2006-11-16.**^**Monin, pp.3-4**^**Daniel Jackson and Jeannette Wing, "Lightweight Formal Methods",*IEEE Computer*, April 1996**^**Vinu George and Rayford Vaughn, "Application of Lightweight Formal Methods in Requirement Engineering" Archived 2006-03-01 at the Wayback Machine.,*Crosstalk: The Journal of Defense Software Engineering*, January 2003**^**Daniel Jackson, "Alloy: A Lightweight Object Modelling Notation",*ACM Transactions on Software Engineering and Methodology (TOSEM)*, Volume 11, Issue 2 (April 2002), pp. 256-290**^**Richard Denney,*Succeeding with Use Cases: Working Smart to Deliver Quality*, Addison-Wesley Professional Publishing, 2005, ISBN 0-321-31643-6.**^**Sten Agerholm and Peter G. Larsen, "A Lightweight Approach to Formal Methods" Archived 2006-03-09 at the Wayback Machine., In*Proceedings of the International Workshop on Current Trends in Applied Formal Methods*, Boppard, Germany, Springer-Verlag, October 1998**^**Backus, J.W. (1959). "The Syntax and Semantics of the Proposed International Algebraic Language of Zürich ACM-GAMM Conference".*Proceedings of the International Conference on Information Processing*. UNESCO.**^**Knuth, Donald E. (1964), Backus Normal Form vs Backus Naur Form.*Communications of the ACM*, 7(12):735–736.**^**A.Cortesi and M.Zanioli, Widening and Narrowing Operators for Abstract Interpretation. Computer Languages, Systems and Structures. Volume 37(1), pp. 24–42, Elsevier, ISSN 1477-8424 (2011).**^**Bjørner, Dines; Gram, Christian; Oest, Ole N.; Rystrøm, Leif (2011). "Dansk Datamatik Center". In Impagliazzo, John; Lundin, Per; Wangler, Benkt.*History of Nordic Computing 3: IFIP Advances in Information and Communication Technology*. Springer. pp. 350–359.**^**Bjørner, Dines; Havelund, Klaus. "40 Years of Formal Methods: Some Obstacles and Some Possibilities?".*FM 2014: Formal Methods: 19th International Symposium, Singapore, May 12–16, 2014. Proceedings*. Springer. pp. 42–61.**^**Gheorghe, A. V., & Ancel, E. (2008, November). Unmanned aerial systems integration to National Airspace System; in Infrastructure Systems and Services: Building Networks for a Brighter Future (INFRA), 2008 First International Conference on (pp. 1-5). IEEE.**^**Airborne Coordinated Conflict Resolution and Detection, http://shemesh.larc.nasa.gov/people/cam/ACCoRD/**^**website : http://www.atelierb.eu/en/**^**C. T. Chou, P. K. Mannava, S. Park, “A simple method for parameterized verification of cache coherence protocols”, Formal Methods in Computer-Aided Design, pp. 382–398, 2004.**^**Formal Verification in Intel® Core™ i7 Processor Execution Engine Validation, http://cps-vo.org/node/1371, accessed at Sep. 13, 2013.**^**J. Grundy, “Verified optimizations for the Intel IA-64 architecture”, In Theorem Proving in Higher Order Logics, Springer Berlin Heidelberg, 2004, pp. 215–232.**^**E. Seligman, I. Yarom, “Best known methods for using Cadence Conformal LEC”, at Intel.**^**C. Eisner, A. Nahir, K. Yorav, “Functional verification of power gated designs by compositional reasoning”, Computer Aided Verification Springer Berlin Heidelberg, pp. 433–445.**^**P. C. Attie, H. Chockler, “Automatic verification of fault-tolerant register emulations”, Electronic Notes in Theoretical Computer Science, vol. 149, no. 1, pp. 49–60.**^**K. D. Schubert, W. Roesner, J. M. Ludden, J. Jackson, J. Buchert, V. Paruthi, B. Brock, “Functional verification of the IBM POWER7 microprocessor and POWER7 multiprocessor systems”, IBM Journal of Research and Development, vol. 55, no 3.

This article is based on material taken from the *Free On-line Dictionary of Computing* prior to 1 November 2008 and incorporated under the "relicensing" terms of the GFDL, version 1.3 or later.

## Further reading[edit]

- Jean François Monin and Michael G. Hinchey,
*Understanding formal methods*, Springer, 2003, ISBN 1-85233-247-6. - Jonathan P. Bowen and Michael G. Hinchey,
*Formal Methods*; in Allen B. Tucker, Jr. (ed.),*Computer Science Handbook*, 2nd edition, Section XI,*Software Engineering*, Chapter 106, pages 106-1 – 106-25, Chapman & Hall / CRC Press, Association for Computing Machinery, 2004. - Michael G. Hinchey, Jonathan P. Bowen, and Emil Vassev,
*Formal Methods*; in Philip A. Laplante (ed.),*Encyclopedia of Software Engineering*, Taylor & Francis, 2010, pages 308–320.

- Hubert Garavel (editor) and Susanne Graf.
*Formal Methods for Safe and Secure Computer Systems*. Bundesamt für Sicherheit in der Informationstechnik, BSI study 875, Bonn, Germany, 362 pages, December 2013.

## External links[edit]

- Formal Methods Europe (FME)
- Formal method keyword on Microsoft Academic Search
- Foldoc:formal methods
- Evidence on Formal Methods uses and impact on Industry Supported by the DEPLOY project (EU FP7)