According to W. Edwards Deming, American companies require nothing less than a transformation of management style and of governmental relations with industry. In Out of the Crisis, originally published in 1982, Deming offers a theory of management based on his famous 14 Points for Management. Management's failure to plan for the future, he claims, brings about loss of market, which brings about loss of jobs. Management must be judged not only by the quarterly dividend, but by innovative plans to stay in business, protect investment, ensure future dividends, and provide more jobs through improved product and service. In simple, direct language, he explains the principles of management transformation and how to apply them.

Out of the Crisis

Objective measurement of test quality is one of the key issues in software testing. It has been a major research focus for the last two decades. Many test criteria have been proposed and studied for this purpose. Various kinds of rationales have been presented in support of one criterion or another. We survey the research work in this area. The notion of adequacy criteria is examined together with its role in software dynamic testing. A review of criteria classification is followed by a summary of the methods for comparison and assessment of criteria.

/pdf/software-unit-test-coverage-and-adequacy-43qk91tobg.pdf

Software unit test coverage and adequacy

Extensively class tested, this text takes an innovative approach to explaining the process of software testing: it defines testing as the process of applying a few well-defined, general-purpose test criteria to a structure or model of the software. The structure of the text directly reflects the pedagogical approach and incorporates the latest innovations in testing, including techniques to test modern types of software such as OO, web applications, and embedded software.

/pdf/introduction-to-software-testing-454uueymyx.pdf

Introduction to Software Testing

Introduction to Software Testing: List of Figures

Quick Check is a tool which aids the Haskell programmer in formulating and testing properties of programs. Properties are described as Haskell functions, and can be automatically tested on random input, but it is also possible to define custom test data generators. We present a number of case studies, in which the tool was successfully used, and also point out some pitfalls to avoid. Random testing is especially suitable for functional programs because properties can be stated at a fine grain. When a function is built from separately tested components, then random testing suffices to obtain good coverage of the definition under test.

/pdf/quickcheck-a-lightweight-tool-for-random-testing-of-haskell-2n9cx98wn4.pdf

QuickCheck: a lightweight tool for random testing of Haskell programs

Plant protection software may be realistically tested using inputs from a plant model before its initial use, or when it is not feasible to take the plant into certain fault conditions. The process of testing to estimate a software reliability is illustrated, including simulation of the software input space and statistical inference from test results to a reliability estimate. In addition to a conventional statistics approach to this problem, a new statistical model is presented which has been developed within a program of Nuclear Electric research into software reliability testing.

Reliability estimation from appropriate testing of plant protection software

We address the difficult problem of estimating the reliability of multiple-version software. The central issue is the degree of statistical dependence between failures of diverse versions. Previously published models of failure dependence described what behavior could be expected "on average" from a pair of "independently generated" versions. We focus instead on predictions using specific information about a given pair of versions. The concept of "variation of difficulty" between situations to which software may be subject is central to the previous models cited, and it turns out to be central for our question as well. We provide new understanding of various alternative imprecise estimates of system reliability and some results of practical use, especially with diverse systems assembled from pre-existing (e.g., "off-the-shelf") subsystems. System designers, users, and regulators need useful bounds on the probability of system failure. We discuss how to use reliability data about the individual diverse versions to obtain upper bounds and other useful information for decision making. These bounds are greatly affected by how the versions' probabilities of failure vary between subdomains of the demand space or between operating regimes-it is even possible in some cases to demonstrate, before operation, upper bounds that are very close to the true probability of failure of the system-and by the level of detail with which these variations are documented in the data.

Estimating bounds on the reliability of diverse systems

The LNICST series publishes ICST's conferences, symposia and workshops. It reports stateof-the-art results in areas related to the scope of the Institute. LNICST reports state-of-theart results in areas related to the scope of the Institute.  The type of material published includes • Proceedings (published in time for the respective event) • Other edited monographs (such as project reports or invited volumes) LNICST topics span the following areas: • General Computer Science • E-Economy • E-Medicine • Knowledge Management • Multimedia • Operations, Management and Policy • Social Informatics • Systems

Lecture Notes of the Institute for Computer Sciences, Social Informatics and Telecommunications Engineering

SCADA and industrial control systems have been traditionally isolated in physically protected environments. However, developments such as standardisation of data exchange protocols and increased use of IP, emerging wireless sensor networks and machine-to-machine communication mean that in the near future related threat vectors will require consideration too outside the scope of traditional SCADA security and incident response. In the light of the significance of SCADA for the resilience of critical infrastructures and the related targeted incidents against them (e.g. the development of stuxnet), cyber security and digital forensics emerge as priority areas. In this paper we focus on the latter, exploring the current capability of SCADA operators to analyse security incidents and develop situational awareness based on a robust digital evidence perspective. We look at the logging capabilities of a typical SCADA architecture and the analytical techniques and investigative tools that may help develop forensic readiness to the level of the current threat environment requirements. We also provide recommendations for data capture and retention.

/pdf/incident-analysis-digital-forensics-in-scada-and-industrial-3dzx6zv7ba.pdf

John H R May

Papers

Software unit test coverage and adequacy

Reliability estimation from appropriate testing of plant protection software

Estimating bounds on the reliability of diverse systems

Lecture Notes of the Institute for Computer Sciences, Social Informatics and Telecommunications Engineering

Incident Analysis & Digital Forensics in SCADA and Industrial Control Systems