Java software development with event B : a practical guide / by Néstor Cataño Collazos.

By:

Collazos, Néstor Cataño [author]

Material type:

Computer fileLanguage: English Publication details: San Rafael, California : Morgan & Claypool, 2020Description: 1 online resource (101, pages) : color illustrationsContent type:

text

Media type:

computer

Carrier type:

online resource

ISBN:

9781681736884 (e-book)

Subject(s):

LOC classification:

QA76.73 C68 2020

Online resources:

Contents:

1. Introduction -- 2. An overview of EVENT B -- 3. Software development of a chat system with EVENT B -- 4. The poporo social network -- 5. Conclusion

Summary: he 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.

List(s) this item appears in: Online E-Books 2022

Average rating: 0.0 (0 votes)

Holdings
Item type	Current library	Collection	Call number	Materials specified	Status	Notes	Date due	Barcode
Online E-Books	Ladislao N. Diwa Memorial Library	Non-fiction	OEBP QA76.73 C68 2020 (Browse shelf(Opens below))		Available	OEBP000167		OEBP000167
Compact Discs	Ladislao N. Diwa Memorial Library Multimedia Section	Non-fiction	EB QA76.73 C68 2020 (Browse shelf(Opens below))		Not for loan	CD0000920		CD0000920

https://portal.igpublish.com/iglibrary/obj/MCPB0006515?searchid=1628736271587peeVkDlFtBs38tHHpNhrj

Include bibliographical references and index

1. Introduction -- 2. An overview of EVENT B -- 3. Software development of a chat system with EVENT B -- 4. The poporo social network -- 5. Conclusion

he 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.

Fund 164 CE-Logic, Inc. Purchased March 2, 2021 OEBP000167 P. Roderno PHP 13,828.00
2021-03-110 7813 to 7820

Click on an image to view it in the image viewer