High-Integrity System Specification and Design

Michael G. Hinchey

ISBN 10: 3540762264 / ISBN 13: 9783540762263

Editore: Springer London, Springer Berlin Heidelberg Apr 1999, 1999

Riguardo questo articolo

This item is printed on demand - Print on Demand Titel. Neuware -Errata, detected in Taylor's Logarithms. London: 4to, 1792. [sic] 14.18.3 6 Kk Co-sine of 3398 3298 - Nautical Almanac (1832) In the list of ERRATA detected in Taylor's Logarithms, for cos. 4° 18'3', read cos. 14° 18'2'. - Nautical Almanac (1833) ERRATUM ofthe ERRATUM ofthe ERRATA of TAYLOR'S Logarithms. For cos. 4° 18'3', read cos. 14° 18' 3'. - Nautical Almanac (1836) In the 1820s, an Englishman named Charles Babbage designed and partly built a calculating machine originally intended for use in deriving and printing logarithmic and other tables used in the shipping industry. At that time, such tables were often inaccurate, copied carelessly, and had been instrumental in causing a number of maritime disasters. Babbage's machine, called a 'Difference Engine' because it performed its cal culations using the principle of partial differences, was intended to substantially reduce the number of errors made by humans calculating the tables. Babbage had also designed (but never built) a forerunner of the modern printer, which would also reduce the number of errors admitted during the transcription of the results. Nowadays, a system implemented to perform the function of Babbage's engine would be classed as safety-critical. That is, the failure of the system to produce correct results could result in the loss of human life, mass destruction of property (in the form of ships and cargo) as well as financial losses and loss of competitive advantage for the shipping firm.Springer Verlag GmbH, Tiergartenstr. 17, 69121 Heidelberg 724 pp. Englisch. Codice articolo 9783540762263

Dati bibliografici

Titolo: High-Integrity System Specification and ...

Casa editrice: Springer London, Springer Berlin Heidelberg Apr 1999

Data di pubblicazione: 1999

Legatura: Taschenbuch

Condizione: Neu

Descrizione articolo

Riassunto:

Errata, detected in Taylor's Logarithms. London: 4to, 1792. [sic] 14.18.3 6 Kk Co-sine of 3398 3298 - Nautical Almanac (1832) In the list of ERRATA detected in Taylor's Logarithms, for cos. 4° 18'3", read cos. 14° 18'2". - Nautical Almanac (1833) ERRATUM ofthe ERRATUM ofthe ERRATA of TAYLOR'S Logarithms. For cos. 4° 18'3", read cos. 14° 18' 3". - Nautical Almanac (1836) In the 1820s, an Englishman named Charles Babbage designed and partly built a calculating machine originally intended for use in deriving and printing logarithmic and other tables used in the shipping industry. At that time, such tables were often inaccurate, copied carelessly, and had been instrumental in causing a number of maritime disasters. Babbage's machine, called a 'Difference Engine' because it performed its cal­ culations using the principle of partial differences, was intended to substantially reduce the number of errors made by humans calculating the tables. Babbage had also designed (but never built) a forerunner of the modern printer, which would also reduce the number of errors admitted during the transcription of the results. Nowadays, a system implemented to perform the function of Babbage's engine would be classed as safety-critical. That is, the failure of the system to produce correct results could result in the loss of human life, mass destruction of property (in the form of ships and cargo) as well as financial losses and loss of competitive advantage for the shipping firm.

Contenuti:

1. Specification and Design.- 1.1 An Analogy.- 1.2 The Development Life-Cycle.- 1.3 The Transformational Approach.- 1.4 Silver Bullets.- No Silver Bullet: Essence and Accidents of Software Engineering.- Biting the Silver Bullet: Toward a Brighter Future for System Development.- 2. Structured Methods.- 2.1 Structured Notations.- 2.2 The Jackson Approach.- Methodology: The Experts Speak.- An Overview of JSD.- 3. Formal Methods.- 3.1 What are Formal Methods?.- 3.2 Formal Specification Languages.- 3.3 Deductive Apparatus.- 3.4 Myths of Formal Methods.- 3.5 Which Formal Method?.- Seven Myths of Formal Methods.- Seven More Myths of Formal Methods.- A Specifier’s Introduction to Formal Methods.- An Overview of Some Formal Methods for Program Design.- Ten Commandments of Formal Methods.- 4. Object-Orientation.- 4.1 The Object Paradigm.- 4.2 Modularization.- 4.3 Information Hiding.- 4.4 Classes.- 4.5 Genericity and Polymorphism.- 4.6 Object-Oriented Design.- Object-Oriented Development.- Object-Oriented and Conventional Analysis and Design Methodologies:Comparison and Critique.- 5. Concurrent and Distributed Systems.- 5.1 Concurrent Systems.- 5.2 Distributed Systems.- 5.3 Models of Computation.- 5.4 Naming Considerations.- 5.5 Inter-Process Communication.- 5.6 Consistency Issues.- 5.7 Heterogeneity and Transparency.- 5.8 Security and Protection.- 5.9 Language Support.- 5.10 Distributed Operating Systems.- Communicating Sequential Processes.- A Simple Approach to Specifying Concurrent Systems.- 6. Real-Time and Safety-Critical Systems.- 6.1 Real-Time Systems.- 6.2 Safety-Critical Systems.- 6.3 Formal Methods for Safety-Critical Systems.- 6.4 Standards.- 6.5 Legislation.- 6.6 Education and Professional Issues.- 6.7 Technology Transfer.- Formal Methods for the Specification and Design of Real-Time Safety-Critical Systems.- Experience with Formal Methods in Critical Systems.- Regulatory Case Studies.- Medical Devices: The Therac-25 Story.- Safety-Critical Systems, Formal Methods and Standards.- 7. Integrating Methods.- 7.1 Motivation.- 7.2 Integrating Structured and Formal Methods.- 7.3 An Appraisal of Approaches.- Integrated Structured Analysis and Formal Specification Techniques.- 8. Implementation.- 8.1 Refinement.- 8.2 Rapid Prototyping and Simulation.- 8.3 Executable Specifications.- 8.4 Animating Formal Specifications.- Specifications are not (Necessarily) Executable.- Specifications are (Preferably) Executable.- 9. CASE.- 9.1 What is CASE?.- 9.2 CASE Workbenches.- 9.3 Beyond CASE.- 9.4 The Future of CASE.- CASE: Reliability Engineering for Information Systems.- On Visual Formalisms.- Author Biographies.