DOC PREVIEW
UI CS 448 - Introduction

This preview shows page 1 out of 4 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 4 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 4 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

1 Page: 1 © 2006 A.W. Krings CS448/548 Survivable Systems and Networks, Lecture 1 Introduction  Different definitions of what survivability is – From AIAA (American Institute of Aeronautics and Astronautics). » http://www.aiaa.org » survivability is defined for aircrafts as “the capability of an aircraft to avoid or withstand hostile environments, including both man-made and naturally occurring environments, such as lightning strikes, mid-air collisions, and crashes” – National Communication System Technology and Standards Division » Federal Standard 1037C, Telecommunications: Glossary of telecommunication terms, 1996 » survivability of telecommunication systems is “the property of a system, subsystem, equipment, process, or procedure that provides a defined degree of assurance that the named entity will continue to function during and after a natural or man-made disturbance; e.g., nuclear burst”. Page: 2 © 2006 A.W. Krings CS448/548 Survivable Systems and Networks, Lecture 1 Introduction  Different definitions of what survivability is – From [M.S. Deutsch and R.R. Willis 1988]. » survivability of software systems is “The degree to which essential functions are still available even though some part of the system is down”. – From Ellison et.al. (Tech Report CMU/SEI-97-TR-013) May 1999 » “We define survivability as the capability of a system to fulfill its mission, in a timely manner, in the presence of attacks, failures, or accidents. We use the term system in the broadest possible sense, including networks and large-scale systems of systems.”2 Page: 3 © 2006 A.W. Krings CS448/548 Survivable Systems and Networks, Sequence 2 Introduction  Different definitions of what survivability is – From June 2000 Neumann Report » ability of a computer-communication system-based application to satisfy and to continue to satisfy certain critical requirements (e.g., specific requirements for security, reliability, real-time responsiveness, and correctness) in the face of adverse conditions. » Survivability must be defined with respect to the set of adversities that are supposed to be withstood. » Types of adversities might be typically include hardware faults, software flaws, attacks on systems and networks perpetrated by malicious users, and electromagnetic interference Page: 4 © 2006 A.W. Krings CS448/548 Survivable Systems and Networks, Sequence 2 Introduction – In the T1A1.2 Working Group » Network survivability is: (i) the ability of a network to maintain or restore an acceptable level of performance during network failures by applying various restoration techniques, and (ii) the mitigation or prevention of service outages from network failures by applying preventative techniques.3 Page: 5 © 2006 A.W. Krings CS448/548 Survivable Systems and Networks, Sequence 2 Introduction – Liu & Trivedi capture the definition of T1A1 as » Suppose a measure of interest M has the value m0 just before a failure occurs. The survivability behavior can be depicted by the following attributes: ma is the value of M just after the failure occurs, mu is the maximum difference between the value of M and ma after the failure, mr is the restored value of M after some time tr, and tR is the time for the system to restore the value of m0. Page: 6 © 2006 A.W. Krings CS448/548 Survivable Systems and Networks, Sequence 2 Introduction – From Liu & Trivedi paper4 Page: 7 © 2008 A.W. Krings CS448/548 Survivable Systems and Networks, Sequence 2 Introduction – Knight & Sullivan 2000 in “On the Definition of Survivability” assumes that “a system is survivable if it complies with its survivability specifications” – Survivability Specifications: » a four-tuple, {E, R, P, M} where:  E = A statement of the assumed operating environment for the system.  R = A set of specifications each of which is a complete statement of a tolerable form of service that the system must provide.  P = A probability distribution across the set of specifications, R.  M = A finite-state machine denoted by the four-tuple {S, s0, V, T} with the following meanings: – S: A finite set of states each of which has a unique label which is one of the specifications defined in R. – s0: s0 in S is the initial or preferred state for the machine. – V: A finite set of customer values. – T: A state transition matrix. – We will discuss this later in more


View Full Document

UI CS 448 - Introduction

Download Introduction
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Introduction and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Introduction 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?