Static Analysis of Software: The Abstract Interpretation

Static Analysis of Software: The Abstract Interpretation

Language: English

Pages: 331

ISBN: 1848213204

Format: PDF / Kindle (mobi) / ePub

The 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 currently working within the industry, the usual problems of confidentiality, which can occur with other books, is not an issue and so makes it possible to supply new useful information (photos, architectural plans, real examples).

An Introduction to Functional Programming Through Lambda Calculus (Dover Books on Mathematics)

A Discipline of Multiprogramming: Programming Theory for Distributed Applications (Monographs in Computer Science)

Randomized Algorithms

Apprendre Java Et C++ en Parallèle

Concise Guide to Databases: A Practical Introduction (Undergraduate Topics in Computer Science)



















for example) recommend the implementation of formal methods but they do not mention the notion of abstract interpretation (or derived methods). 1.8. Bibliography [ABR 96] ABRIAL J.R., The B Book – Assigning Programs to Meanings, Cambridge University Press, Cambridge, 1996. [AFN 90] NF F 71-013, Installation fixes et matériel roulant ferroviaires, informatique, sûreté de fonctionnement des logiciels – méthodes appropriées aux analyses de sécurité des logiciels, AFNOR, December 1990. [ANS 83] ANSI,

Verification of the completeness of requirements and detection of unintended functions . . . . . . . . . . . . . . . . 6.5. LLR verification by model-checking . . . . . . . . . . . . . . . . 6.6. Contribution to the verification of robustness properties with Frama-C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.6.1. Introduction to Frama-C . . . . . . . . . . . . . . . . . . . . 6.6.2. Presentation of the case study. . . . . . . . . . . . . . . . . . 6.6.3. Analysis process of

plug integrated into the Eclipse and Visual Studio development environments. Polyspace® analyses are often carried out on a dedicated server and users can follow the status of ongoing analyses from the work station. Polyspace® uses the multicore characteristics of machines to accelerate verifications. Figure 3.6. The project view of Polyspace® 3.7. Robustness verification or contextual verification Polyspace® users can carry out so-called robustness or contextual verifications. Robustness

models. In the SQO model described in Table 3.2, all the potential execution errors to correct or to justify increase as the SQO objectives become more rigorous. The Polyspace Metrics dashboard, based on a Web interface, provides specific views enabling us to follow quality objectives according to different thresholds defined by the SQO model. Software quality objectives (SQO) Criteria A quality plan is in place There is a detailed design Code complexity metrics have been defined and verified

combining all of these methods. It is necessary to remark that a large proportion of this information is produced as intermediate results because they are useful for the verification of the absence of run-time errors. This information is, however, not accessible in general. This is true for Polyspace®, as well as numerous other static analysis tools that “know” a lot of things about the source code they are symbolically executing but do not show this information to the user. To our knowledge, no

Download sample