Taschenbuch. Condizione: Neu. This item is printed on demand - it takes 3-4 days longer - Neuware -The cost of fixing software design flaws after the completion of a software product is so high that it is vital to come up with ways to detect software design flaws in the early stages of software development, for instance, during the software requirements, the analysis activity, or during software design, before coding starts. It is not uncommon that software requirements are ambiguous or contradict each other. Ambiguity is exacerbated by the fact that software requirements are typically written in a natural language, which is not tied to any formal semantics. A palliative to the ambiguity of software requirements is to restrict their syntax to boilerplates, textual templates with placeholders. However, as informal requirements do not enjoy any particular semantics, no essential properties about them (or about the system they attempt to describe) can be proven easily. Formal methods are an alternative to address this problem. They offer a range of mathematical techniques and mathematical tools to validate software requirements in the early stages of software development.This book is a living proof of the use of formal methods to develop software. The particular formalisms that we use are EVENT B and refinement calculus. In short: (i) software requirements as written as User Stories; (ii) they are ported to formal specifications; (iii) they are refined as desired; (iv) they are implemented in the form of a prototype; and finally (v) they are tested for inconsistencies. If some unit-test fails, then informal as well as formal specifications of the software system are revisited and evolved.This book presents a case study of software development of a chat system with EVENT B and a case study of formal proof of properties of a social network. 100 pp. Englisch. Codice articolo 9783031014222

Contatta il venditore

Compra nuovo

EUR 29,95

Convertire valuta

Spese di spedizione: EUR 23,00

Da: Germania a: U.S.A.

Destinazione, tempi e costi

Quantit�: 2 disponibili

Aggiungi al carrello

Immagini fornite dal venditore

Java Software Development With Event B : A Practical Guide

Collazos, Nestor Catano

Editore: Springer, 2020

ISBN 10: 3031014227 ISBN 13: 9783031014222

Nuovo Brossura

Da: GreatBookPricesUK, Castle Donington, DERBY, Regno Unito

Valutazione del venditore 5 su 5 stelle

Condizione: New. Codice articolo 44571251-n

Contatta il venditore

Compra nuovo

EUR 37,37

Convertire valuta

Spese di spedizione: EUR 17,88

Da: Regno Unito a: U.S.A.

Destinazione, tempi e costi

Quantit�: 5 disponibili

Aggiungi al carrello

Immagini fornite dal venditore

Java Software Development With Event B : A Practical Guide

Collazos, Nestor Catano

Editore: Springer, 2020

ISBN 10: 3031014227 ISBN 13: 9783031014222

Antico o usato Brossura

Da: GreatBookPricesUK, Castle Donington, DERBY, Regno Unito

Valutazione del venditore 5 su 5 stelle

Condizione: As New. Unread book in perfect condition. Codice articolo 44571251

Contatta il venditore

Compra usato

EUR 41,21

Convertire valuta

Spese di spedizione: EUR 17,88

Da: Regno Unito a: U.S.A.

Destinazione, tempi e costi

Quantit�: 5 disponibili

Aggiungi al carrello

Immagini fornite dal venditore

Java Software Development with Event B : A Practical Guide

N�stor Cata�o Collazos

Editore: Springer International Publishing, 2020

ISBN 10: 3031014227 ISBN 13: 9783031014222

Nuovo Taschenbuch

Da: AHA-BUCH GmbH, Einbeck, Germania

Valutazione del venditore 5 su 5 stelle

Taschenbuch. Condizione: Neu. Druck auf Anfrage Neuware - Printed after ordering - The cost of fixing software design flaws after the completion of a software product is so high that it is vital to come up with ways to detect software design flaws in the early stages of software development, for instance, during the software requirements, the analysis activity, or during software design, before coding starts. It is not uncommon that software requirements are ambiguous or contradict each other. Ambiguity is exacerbated by the fact that software requirements are typically written in a natural language, which is not tied to any formal semantics. A palliative to the ambiguity of software requirements is to restrict their syntax to boilerplates, textual templates with placeholders. However, as informal requirements do not enjoy any particular semantics, no essential properties about them (or about the system they attempt to describe) can be proven easily. Formal methods are an alternative to address this problem. They offer a range of mathematical techniques and mathematical tools to validate software requirements in the early stages of software development.This book is a living proof of the use of formal methods to develop software. The particular formalisms that we use are EVENT B and refinement calculus. In short: (i) software requirements as written as User Stories; (ii) they are ported to formal specifications; (iii) they are refined as desired; (iv) they are implemented in the form of a prototype; and finally (v) they are tested for inconsistencies. If some unit-test fails, then informal as well as formal specifications of the software system are revisited and evolved.This book presents a case study of software development of a chat system with EVENT B and a case study of formal proof of properties of a social network. Codice articolo 9783031014222

Contatta il venditore

Compra nuovo

EUR 29,95

Convertire valuta

Spese di spedizione: EUR 32,99

Da: Germania a: U.S.A.

Destinazione, tempi e costi

Quantit�: 1 disponibili

Aggiungi al carrello

Vedi altre 1 copie di questo libro

Vedi tutti i risultati per questo libro

Articoli correlati a Java Software Development with Event B: A Practical...

Java Software Development with Event B: A Practical Guide - Brossura

Compra usato

Compra nuovo

I migliori risultati di ricerca su AbeBooks

Compra nuovo

Compra nuovo

Compra nuovo

Compra usato

Compra nuovo

Compra nuovo

Compra nuovo

Compra nuovo

Compra usato

Compra nuovo

Vedi altre 1 copie di questo libro