Java software development with event B : a practical guide / Néstor Cataño Collazos.
| Author/creator | Cataño Collazos, Nestor, 1975- author. |
| Format | Electronic |
| Publication | [San Rafael, California] : Morgan & Claypool, [2020] |
| Copyright Date | ©2020 |
| Description | 1 online resource (x, 89 pages) : illustrations (some color). |
| Supplemental Content | EBSCOhost |
| Subjects |
| Series | Synthesis lectures on software engineering, 2328-3327 ; #5 Synthesis lectures on software engineering ; #5. ^A1167911 |
| Contents | 1. Introduction -- 2. An overview of EVENT B -- 2.1. Relations and functions -- 2.2. EVENT B mathematical notation -- 2.3. Software development with EVENT B -- 2.4. A methodology for early validation of software requirements -- 2.5. Correctness-by-construction -- 2.6. RODIN -- 2.7. JML -- 2.8. EVENTB2JAVA -- 2.9. A Chat application |
| Contents | 3. Software development of a chat system with EVENT B -- 3.1. MachineZero -- 3.2. MachineOne -- 3.3. MachineTwo -- 3.4. MachineZero in EVENT B -- 3.5. MachineOne in EVENT B -- 3.6. MachineTwo in EVENT B -- 3.7. The implementation of the chat system -- 3.8. Testing and code animation of the chat system -- 3.9. Fixing the software requirements -- 3.10. Lessons learned |
| Contents | 4. The Poporo social network -- 4.1. Poporo's general structure -- 4.2. Poporo's formalization in EVENT B -- 4.3. Invariant POs -- 4.4. Discharging POs in Rodin -- 4.5. POs for quantified expressions -- 4.6. Strengthening the specification -- 4.7. Further strengthening -- 4.8. Refinement proof obligations -- 5. Conclusion. |
| Abstract | 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. |
| Bibliography note | Includes bibliographical references (pages 83-84) and index. |
| Source of description | Title from PDF title page (viewed on January 28, 2020). |
| Issued in other form | Print version: 9781681736877 |
| Genre/form | Electronic books. |
| Genre/form | Electronic books. |
| ISBN | 9781681736884 (electronic bk.) |
| ISBN | 1681736888 (electronic bk.) |
| ISBN | (hardcover) |
| ISBN | (hardcover) |
| ISBN | (paperback) |
| ISBN | (paperback) |
| Standard identifier# | 10.2200/S00957ED1V01Y201910SWE005 |