LEADER 05567nam 2200709 a 450 001 9910821368103321 005 20240313144213.0 010 $a1-118-60286-2 010 $a1-118-60295-1 010 $a1-118-60284-6 010 $a1-299-18778-1 035 $a(CKB)2550000001005909 035 $a(EBL)1124674 035 $a(OCoLC)828298908 035 $a(SSID)ssj0000832009 035 $a(PQKBManifestationID)11521864 035 $a(PQKBTitleCode)TC0000832009 035 $a(PQKBWorkID)10882198 035 $a(PQKB)11028278 035 $a(OCoLC)828198486 035 $a(MiAaPQ)EBC1124674 035 $a(Au-PeEL)EBL1124674 035 $a(CaPaEBR)ebr10660561 035 $a(CaONFJC)MIL450028 035 $a(EXLCZ)992550000001005909 100 $a20111021d2012 uy 0 101 0 $aeng 135 $aur|n|---||||| 181 $ctxt 182 $cc 183 $acr 200 00$aStatic analysis of software$b[electronic resource] $ethe abstract interpretation /$fedited by Jean-Louis Boulanger 205 $a1st ed. 210 $aHoboken, N.J. $cWiley$d2012 215 $a1 online resource (347 p.) 225 1 $aISTE 300 $aDescription based upon print version of record. 311 $a1-84821-320-4 320 $aIncludes bibliographical references and index. 327 $aCover; Title Page; Copyright Page; Table of Contents; Introduction; Chapter 1. Formal Techniques for Verification and Validation; 1.1. Introduction; 1.2. Realization of a software application; 1.3. Characteristics of a software application; 1.4. Realization cycle; 1.4.1. Cycle in V and other realization cycles; 1.4.2. Quality control (the impact of ISO standard 9001); 1.4.3. Verification and validation; 1.5. Techniques, methods and practices; 1.5.1. Static verification; 1.5.2. Dynamic verification; 1.5.3. Validation; 1.6. New issues with verification and validation; 1.7. Conclusion 327 $a1.8. BibliographyChapter 2. Airbus: Formal Verification in Avionics; 2.1. Industrial context; 2.1.1. Avionic systems; 2.1.2. A few examples; 2.1.3. Regulatory framework; 2.1.4. Avionic functions; 2.1.5. Development of avionics levels; 2.2. Two methods for formal verification; 2.2.1. General principle of program proof; 2.2.2. Static analysis by abstract interpretation; 2.2.3. Program proof by calculation of the weakest precondition; 2.3. Four formal verification tools; 2.3.1. Caveat; 2.3.2. Proof of the absence of run-time errors: Astre?e; 2.3.3. Stability and numerical precision: Fluctuat 327 $a2.3.4. Calculation of the worst case execution time: aiT (AbsInt GmbH)2.4. Examples of industrial use; 2.4.1. Unitary proof (verification of low level requirements); 2.4.2. The calculation of worst case execution time; 2.4.3. Proof of the absence of run-time errors; 2.5. Bibliography; Chapter 3. Polyspace; 3.1. Overview; 3.2. Introduction to software quality and verification procedures; 3.3. Static analysis; 3.4. Dynamic tests; 3.5. Abstract interpretation; 3.6. Code verification; 3.7. Robustness verification or contextual verification; 3.7.1. Robustness verifications 327 $a3.7.2. Contextual verification3.8. Examples of PolyspaceŽ results; 3.8.1. Example of safe code; 3.8.2. Example: dereferencing of a pointer outside its bounds; 3.8.3. Example: inter-procedural calls; 3.9. Carrying out a code verification with Polyspace; 3.10. Use of PolyspaceŽ can improve the quality of embedded software; 3.10.1. Begin by establishing models and objectives for software quality; 3.10.2. Example of a software quality model with objectives; 3.10.3. Use of a subset of languages to satisfy coding rules; 3.10.4. Use of PolyspaceŽ to reach software quality objectives 327 $a3.11. Carrying out certification with PolyspaceŽ3.12. The creation of critical onboard software; 3.13. Concrete uses of PolyspaceŽ; 3.13.1. Automobile: Cummins Engines improves the reliability of its motor's controllers; 3.13.2. Aerospace: EADS guarantees the reliability of satellite launches; 3.13.3. Medical devices: a code analysis leads to a recall of the device; 3.13.4. Other examples of the use of PolyspaceŽ; 3.14. Conclusion; 3.15. Bibliography; Chapter 4. Software Robustness with Regards to Dysfunctional Values from Static Analysis; 4.1. Introduction; 4.2. Normative context 327 $a4.3. Elaboration of the proof of the robustness method 330 $aThe existing literature currently available to students and researchers is very general, covering only the formal techniques of static analysis. This book presents real examples of the formal techniques called ""abstract interpretation"" currently being used in various industrial fields: railway, aeronautics, space, automotive, etc. The purpose of this book is to present students and researchers, in a single book, with the wealth of experience of people who are intrinsically involved in the realization and evaluation of software-based safety critical systems. As the authors are people curr 410 0$aISTE 606 $aComputer software$xTesting 606 $aDebugging in computer science 606 $aComputer software$xQuality control 615 0$aComputer software$xTesting. 615 0$aDebugging in computer science. 615 0$aComputer software$xQuality control. 676 $a005.1/4 701 $aBoulanger$b Jean-Louis$0847395 801 0$bMiAaPQ 801 1$bMiAaPQ 801 2$bMiAaPQ 906 $aBOOK 912 $a9910821368103321 996 $aStatic analysis of software$93983000 997 $aUNINA