Java Software Development with Event B (Record no. 85182)
[ view plain ]
| 000 -LEADER | |
|---|---|
| fixed length control field | 03878nam a22005415i 4500 |
| 001 - CONTROL NUMBER | |
| control field | 978-3-031-02550-1 |
| 005 - DATE AND TIME OF LATEST TRANSACTION | |
| control field | 20240730163959.0 |
| 008 - FIXED-LENGTH DATA ELEMENTS--GENERAL INFORMATION | |
| fixed length control field | 220601s2020 sz | s |||| 0|eng d |
| 020 ## - INTERNATIONAL STANDARD BOOK NUMBER | |
| ISBN | 9783031025501 |
| -- | 978-3-031-02550-1 |
| 082 04 - CLASSIFICATION NUMBER | |
| Call Number | 620 |
| 100 1# - AUTHOR NAME | |
| Author | Collazos, Néstor Cataño. |
| 245 10 - TITLE STATEMENT | |
| Title | Java Software Development with Event B |
| Sub Title | A Practical Guide / |
| 250 ## - EDITION STATEMENT | |
| Edition statement | 1st ed. 2020. |
| 300 ## - PHYSICAL DESCRIPTION | |
| Number of Pages | X, 89 p. |
| 490 1# - SERIES STATEMENT | |
| Series statement | Synthesis Lectures on Software Engineering, |
| 505 0# - FORMATTED CONTENTS NOTE | |
| Remark 2 | Introduction -- An Overview of Event B -- Software Development of a Chat System with Event B -- The Poporo Social Network -- Conclusion -- Bibliography -- Author's Biography. |
| 520 ## - SUMMARY, ETC. | |
| Summary, etc | 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. |
| 856 40 - ELECTRONIC LOCATION AND ACCESS | |
| Uniform Resource Identifier | https://doi.org/10.1007/978-3-031-02550-1 |
| 942 ## - ADDED ENTRY ELEMENTS (KOHA) | |
| Koha item type | eBooks |
| 264 #1 - | |
| -- | Cham : |
| -- | Springer International Publishing : |
| -- | Imprint: Springer, |
| -- | 2020. |
| 336 ## - | |
| -- | text |
| -- | txt |
| -- | rdacontent |
| 337 ## - | |
| -- | computer |
| -- | c |
| -- | rdamedia |
| 338 ## - | |
| -- | online resource |
| -- | cr |
| -- | rdacarrier |
| 347 ## - | |
| -- | text file |
| -- | |
| -- | rda |
| 650 #0 - SUBJECT ADDED ENTRY--SUBJECT 1 | |
| -- | Engineering. |
| 650 #0 - SUBJECT ADDED ENTRY--SUBJECT 1 | |
| -- | Mathematics. |
| 650 #0 - SUBJECT ADDED ENTRY--SUBJECT 1 | |
| -- | Computer science. |
| 650 #0 - SUBJECT ADDED ENTRY--SUBJECT 1 | |
| -- | Software engineering. |
| 650 14 - SUBJECT ADDED ENTRY--SUBJECT 1 | |
| -- | Technology and Engineering. |
| 650 24 - SUBJECT ADDED ENTRY--SUBJECT 1 | |
| -- | Mathematics. |
| 650 24 - SUBJECT ADDED ENTRY--SUBJECT 1 | |
| -- | Computer Science. |
| 650 24 - SUBJECT ADDED ENTRY--SUBJECT 1 | |
| -- | Software Engineering. |
| 830 #0 - SERIES ADDED ENTRY--UNIFORM TITLE | |
| -- | 2328-3327 |
| 912 ## - | |
| -- | ZDB-2-SXSC |
No items available.