As a guest user you are not logged in or recognized by your IP address. You have
access to the Front Matter, Abstracts, Author Index, Subject Index and the full
text of Open Access publications.
Now that we can formally verify software models, why do we still need Protection from programming errors? For a similar reason, why do we still need protection from hardware errors? The key reason is that formal models are abstractions and programmers are humans with an illogical brain using illogical and error-prone dynamic programming languages. In addition, software runs on a shared resource, called a processor, and that processor exists in the real physical world, in which external influences like cosmic rays can change its state.
Hence, protection has to be seen in the context of increasing the trustworthiness (as defined by the Assured Reliability Resiliance Level criterion) of the system. The key is to do it in such a way that we do not jeopardise the properties we expect from a system in absence of the errors mentioned above. This was the rationale for developing VirtuosoNext, offering fine-grain and space partitioning with some help from the hardware. Slides used in the presentation can be downloaded from [1].
This website uses cookies
We use cookies to provide you with the best possible experience. They also allow us to analyze user behavior in order to constantly improve the website for you. Info about the privacy policy of IOS Press.
This website uses cookies
We use cookies to provide you with the best possible experience. They also allow us to analyze user behavior in order to constantly improve the website for you. Info about the privacy policy of IOS Press.