This paper gives the main definitions relating to dependability, a generic concept including a special case of such attributes as reliability, availability, safety, integrity, maintainability, etc. Security brings in concerns for confidentiality, in addition to availability and integrity. Basic definitions are given first. They are then commented upon, and supplemented by additional definitions, which address the threats to dependability and security (faults, errors, failures), their attributes, and the means for their achievement (fault prevention, fault tolerance, fault removal, fault forecasting). The aim is to explicate a set of general concepts, of relevance across a wide range of situations and, therefore, helping communication and cooperation among a number of scientific and technical communities, including ones that are concentrating on particular types of system, of system failures, or of causes of system failures.

/pdf/basic-concepts-and-taxonomy-of-dependable-and-secure-4u8aflogtd.pdf

Basic concepts and taxonomy of dependable and secure computing

Basic Concepts and Taxonomy of Dependable and Secure Computing

Distributed operating systems have many aspects in common with centralized ones, but they also differ in certain ways This paper is intended as an introduction to distributed operating systems, and especially to current university research about them After a discussion of what constitutes a distributed operating system and how it is distinguished from a computer network, various key design issues are discussed Then several examples of current research projects are examined in some detail, namely, the Cambridge Distributed Computing System, Amoeba, V, and Eden

https://cds.cern.ch/record/400319/files/p101.pdf

Distributed Operating Systems

Evolution of the N-version software approach to the tolerance of design faults is reviewed. Principal requirements for the implementation of N-version software are summarized and the DEDIX distributed supervisor and testbed for the execution of N-version software is described. Goals of current research are presented and some potential benefits of the N-version approach are identified.

The N-Version Approach to Fault-Tolerant Software

This is one of the only books to provide a complete and coherent review of the theory of genetic programming (GP). In doing so, it provides a coherent consolidation of recent work on the theoretical foundations of GP. A concise introduction to GP and genetic algorithms (GA) is followed by a discussion of fitness landscapes and other theoretical approaches to natural and artificial evolution. Having surveyed early approaches to GP theory it presents new exact schema analysis, showing that it applies to GP as well as to the simpler GAs. New results on the potentially infinite number of possible programs are followed by two chapters applying these new techniques.

Foundations of Genetic Programming

ion versus procedural specifications. More experience is needed in wxriting and using true abstract specifications as xvell as \"rapid prototypes.\" What are the consequences of introducing bias in a \"rapid prototype,\" and are the more difficult abstract specifications wxorth the extra effort? This experiment showed that, at the current lexel of dexelopment, a familiar procedural specification, PDL, was easier to use and understand than the more difficult, unfamiliar, abstract specification of OBJ. Our studv of both formal and informal specification languag-es has showxn that none of the languages available is sufficiently automated. Formal specification languaaes, while showing promise for the future, thus far have been Xerv difficult to use and understand and are sex erely limited in poxxer. SPEC. FAU LT

Fault Tolerance by Design Diversity: Concepts and Experiments

Can we trust the new AAS to deliver highly dependable air traffic control services until the year 2000? Yes, systematic application of fault tolerance offers a solid promise of success. T he Advanced Automation System, or AAS, will provide automation T services to both en-route and terminal air traffic controllers throughout the United States. Although controllers are able to maintain separation between aircraft during periods of interruption of the automatic services, the transition to backup modes of operation is potentially hazardous. The increased controller workload resulting from interruption of the services provided to controllers limits the traffic handling capability of the Air Traffic Control System, which can result in major delays during periods of heavy traffic. As the level of automation services provided to controllers increases, interruption of computer services to the controllers will become even more critical. Accordingly, extremely high reliability and availability of the services provided by the AAS will be required on a continuous basis, 24 hours a day, seven days a week.

Avizienis

Papers

Fault Tolerance by Design Diversity: Concepts and Experiments

On the Achievement of a Highly Dependable and Fault-Tolerant Air Traffic Control System