Info
- Utilizzare la checkbox di selezione a fianco di ciascun documento per attivare le funzionalità di stampa, invio email, download nei formati disponibili del (i) record.
Static analysis of software [[electronic resource] ] : the abstract interpretation / / edited by Jean-Louis Boulanger
| Static analysis of software [[electronic resource] ] : the abstract interpretation / / edited by Jean-Louis Boulanger |
| Pubbl/distr/stampa | Hoboken, N.J., : Wiley, 2012 |
| Descrizione fisica | 1 online resource (347 p.) |
| Disciplina | 005.1/4 |
| Altri autori (Persone) | BoulangerJean-Louis |
| Collana | ISTE |
| Soggetto topico |
Computer software - Testing
Debugging in computer science Computer software - Quality control |
| Soggetto genere / forma | Electronic books. |
| ISBN |
1-118-60286-2
1-118-60295-1 1-118-60284-6 1-299-18778-1 |
| Formato | Materiale a stampa  |
| Livello bibliografico | Monografia |
| Lingua di pubblicazione | eng |
| Nota di contenuto |
Cover; 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
1.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: Astrée; 2.3.3. Stability and numerical precision: Fluctuat 2.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 3.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 3.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 4.3. Elaboration of the proof of the robustness method |
| Record Nr. | UNINA-9910138863203321 |
| Hoboken, N.J., : Wiley, 2012 | ||
| Materiale a stampa | ||
| Lo trovi qui: Univ. Federico II | ||
| ||
Static analysis of software [[electronic resource] ] : the abstract interpretation / / edited by Jean-Louis Boulanger
| Static analysis of software [[electronic resource] ] : the abstract interpretation / / edited by Jean-Louis Boulanger |
| Edizione | [1st ed.] |
| Pubbl/distr/stampa | Hoboken, N.J., : Wiley, 2012 |
| Descrizione fisica | 1 online resource (347 p.) |
| Disciplina | 005.1/4 |
| Altri autori (Persone) | BoulangerJean-Louis |
| Collana | ISTE |
| Soggetto topico |
Computer software - Testing
Debugging in computer science Computer software - Quality control |
| ISBN |
1-118-60286-2
1-118-60295-1 1-118-60284-6 1-299-18778-1 |
| Formato | Materiale a stampa |
| Livello bibliografico | Monografia |
| Lingua di pubblicazione | eng |
| Nota di contenuto |
Cover; 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
1.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: Astrée; 2.3.3. Stability and numerical precision: Fluctuat 2.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 3.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 3.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 4.3. Elaboration of the proof of the robustness method |
| Record Nr. | UNINA-9910821368103321 |
| Hoboken, N.J., : Wiley, 2012 | ||
| Materiale a stampa | ||
| Lo trovi qui: Univ. Federico II | ||
| ||
Tru64 UNIX troubleshooting [electronic resource] : diagnosing and correcting system problems / Martin Moore, Steven Hancock
| Tru64 UNIX troubleshooting [electronic resource] : diagnosing and correcting system problems / Martin Moore, Steven Hancock |
| Autore | Moore, Martin L. |
| Pubbl/distr/stampa | Amsterdam ; Boston : Digital Press ; 2003 |
| Descrizione fisica | xiii, 337 p. ; 24 cm. |
| Disciplina | 005.4/32 |
| Altri autori (Persone) | Hancock, Steven M. |
| Soggetto topico |
Operating systems (Computers)
Software maintenance Debugging in computer science |
| Soggetto genere / forma | Electronic books. |
| ISBN |
9781555582746
1555582745 |
| Formato | Risorse elettroniche  |
| Livello bibliografico | Monografia |
| Lingua di pubblicazione | eng |
| Nota di contenuto | Introduction; Principles and Techniques; Tools and Resources; User Account Problems; System Problems; System Performance; Network Problems; Storage; File System Problems; Configuration Issues; System Administration Issues; Display Problems; Appendix A: Online Resources; Appendix B: Bibliography. |
| Record Nr. | UNISALENTO-991003245929707536 |
Moore, Martin L.
|
||
| Amsterdam ; Boston : Digital Press ; 2003 | ||
| Risorse elettroniche | ||
| Lo trovi qui: Univ. del Salento | ||
| ||
Understanding coding through debugging / / Patricia Harris
| Understanding coding through debugging / / Patricia Harris |
| Autore | Harris Patricia |
| Pubbl/distr/stampa | New York : , : PowerKids Press, , 2017 |
| Descrizione fisica | 1 online resource (24 pages) : color illustrations |
| Disciplina | 005.14 |
| Collana | Spotlight on kids can code |
| Soggetto topico |
Debugging in computer science
Computer programming |
| ISBN | 1-4994-2910-X |
| Formato | Materiale a stampa |
| Livello bibliografico | Monografia |
| Lingua di pubblicazione | eng |
| Nota di contenuto | Eeeek, a bug! -- Hopper's bug -- Building and inspecting -- Debugging detectives -- Debugging tools -- Let's start debugging -- Real-world coding. |
| Record Nr. | UNINA-9910150301103321 |
|
Harris Patricia
|
||
| New York : , : PowerKids Press, , 2017 | ||
| Materiale a stampa | ||
| Lo trovi qui: Univ. Federico II | ||
| ||
Windows 10 troubleshooting : learn to troubleshoot and repair windows 10 problems like the pros do / / Mike Halsey
| Windows 10 troubleshooting : learn to troubleshoot and repair windows 10 problems like the pros do / / Mike Halsey |
| Autore | Halsey Mike |
| Edizione | [Second edition.] |
| Pubbl/distr/stampa | [Place of publication not identified] : , : Apress, , [2022] |
| Descrizione fisica | 1 online resource (807 pages) |
| Disciplina | 005.14 |
| Soggetto topico | Debugging in computer science |
| ISBN | 1-4842-7471-7 |
| Formato | Materiale a stampa |
| Livello bibliografico | Monografia |
| Lingua di pubblicazione | eng |
| Record Nr. | UNINA-9910522963603321 |
|
Halsey Mike
|
||
| [Place of publication not identified] : , : Apress, , [2022] | ||
| Materiale a stampa | ||
| Lo trovi qui: Univ. Federico II | ||
| ||
