Abstracting formal specifications to generate software tests via model checking
Read Online

Abstracting formal specifications to generate software tests via model checking

  • 396 Want to read
  • ·
  • 90 Currently reading

Published by U.S. Dept. of Commerce, Technology Administration, National Institute of Standards and Technology in Gaithersburg, MD .
Written in English


  • Computer software -- Testing,
  • Computer software -- Specifications

Book details:

Edition Notes

StatementPaul E. Ammann, Paul E. Black.
SeriesNISTIR -- 6405.
ContributionsBlack, Paul E., National Institute of Standards and Technology (U.S.)
The Physical Object
Pagination25 p.
Number of Pages25
ID Numbers
Open LibraryOL17598399M

Download Abstracting formal specifications to generate software tests via model checking


Get this from a library! Abstracting formal specifications to generate software tests via model checking. [Paul E Ammann; Paul E Black; National Institute of Standards and Technology (U.S.)]. Abstract. Software Model-Checking and Testing are some of the most used techniques to analyze software systems and identify hidden faults. While software model-checking allows for an exhaustive and automatic analysis of the system expressed through a model, software testing is based on a clever selection of “relevant” test cases, which may be manually or automatically run over the prideinpill.com by: Test Generation Using Model Checking and Specification Mutation Article in IT Professional 16(2) · March with 15 Reads How we measure 'reads'. Mutation analysis on model checking specifications is a recent development. This approach mutates a specification, then applies a model checker to compare the mutants with the original specification to automatically generate tests or evaluate coverage. The properties of specification mutation operators have not been explored in prideinpill.com by:

Paul E. Ammann, Paul E. Black, William Majurski, Using Model Checking to Generate Tests from Specifications, Proceedings of the Second IEEE International Conference on Formal Engineering Methods, p, December , Cited by: CiteSeerX - Document Details (Isaac Councill, Lee Giles, Pradeep Teregowda): Recently, many formal methods, such as the SCR (Software Cost Reduction) requirements method, have been proposed for improving the quality of software specifications. Although improved specifications are valuable, the ultimate objective of software development is to produce software that satisfies its requirements. Formal Methods in Software Engineering Why formalize? specifications of requirements (so we can document them precisely) Specifications of program design (so we can verify correctness) Key technologies: Consistency checking, Model checking Formal Conceptual Modelling For capturing real-world knowledge in RE. Using model checking to generate tests from specifications. In Proceedings of the 2nd IEEE International Conference on Formal Engineering Methods (ICFEM, Brisbane, Australia). Author: M HieronsRobert, BogdanovKirill, P BowenJonathan, CleavelandRance, DerrickJohn, DickJeremy, Gheorghe.

Background. Semi-Formal Methods are formalisms and languages that are not considered fully “formal”.It defers the task of completing the semantics to a later stage, which is then done either by human interpretation or by interpretation through software like code or test case generators. to model checking software specifications is to apply mathematically sound abstraction methods. Such methods extract a reduced model from the specification, thus making model checking feasible. Currently, users of model checkers routinely analyze reduced models but often generate the models in ad hoc ways. As a result, the reduced. Abstracting the Geniuses Away from Failure Testing. By Peter Alvaro, Severine Tymon (academics in particular) looked to formal methods such as model checking 16,20,29,39,40,53,54 to assist "mere mortal" programmers in writing distributed code that upholds its guarantees despite pervasive uncertainty in distributed executions. It is not. 1 Software Test Specification 1. Introduction – This section provides an overview of the entire test document. – This document describes both the test plan and the test procedure. Goals and objectives • Overall goals and objectives of the test process are described. Statement of scope – A description of the scope of software testing is developed.