Tipo de artículo
Condición
Encuadernación
Más atributos
Ubicación del vendedor
Valoración de los vendedores
Publicado por Springer, 2007
ISBN 10: 3540737693ISBN 13: 9783540737698
Librería: Basi6 International, Irving, TX, Estados Unidos de America
Libro
Condición: Brand New. New. US edition. Expediting shipping for all USA and Europe orders excluding PO Box. Excellent Customer Service.
Publicado por Springer, 2007
ISBN 10: 3540737693ISBN 13: 9783540737698
Librería: booksXpress, Bayonne, NJ, Estados Unidos de America
Libro Impresión bajo demanda
Soft Cover. Condición: new. This item is printed on demand.
Publicado por Springer, 2007
ISBN 10: 3540737693ISBN 13: 9783540737698
Librería: Lucky's Textbooks, Dallas, TX, Estados Unidos de America
Libro
Condición: New.
Publicado por Springer, 2007
ISBN 10: 3540737693ISBN 13: 9783540737698
Librería: Ria Christie Collections, Uxbridge, Reino Unido
Libro Impresión bajo demanda
Condición: New. PRINT ON DEMAND Book; New; Fast Shipping from the UK. No. book.
Publicado por Springer-Verlag New York Inc, 2007
ISBN 10: 3540737693ISBN 13: 9783540737698
Librería: Revaluation Books, Exeter, Reino Unido
Libro
Paperback. Condición: Brand New. 1st edition. 216 pages. 9.25x6.00x0.50 inches. In Stock.
Publicado por Springer Berlin Heidelberg, 2007
ISBN 10: 3540737693ISBN 13: 9783540737698
Librería: AHA-BUCH GmbH, Einbeck, Alemania
Libro
Taschenbuch. Condición: Neu. Druck auf Anfrage Neuware - Printed after ordering - To prove the correctness of a program is to demonstrate, through impeccable mathematical techniques, that it has no bugs. To test a program is to run it with the expectation of discovering bugs. These two paths to software reliability seem to diverge from the very start: if you have proved your program correct, it is fruitless to comb it for bugs; and if you are testing it, that surely must be a sign that you have given up on any hope to prove its correctness. Accordingly, proofs and tests have, since the onset of software engineering research, been pursued by distinct communities using different kinds of techniques and tools. Dijkstra's famous pronouncement that tests can only show the presence of errors - in retrospect, perhaps one of the best advertisements one can imagine for testing, as if 'only' finding bugs were not already a momentous achievement! - didn't help make testing popular with provers, or proofs attractive to testers. And yet the development of both approaches leads to the discovery of common issues and to the realization that each may need the other. The emergence of model checking was one of the first signs that apparent contradiction may yield to complementarity; in the past few years an increasing number of research efforts have encountered the need for combining proofs and tests, dropping earlier dogmatic views of incompatibility and taking instead the best of what each of these software engineering domains has to offer.