Keith W. Miller

Learn More
Software veriication encompasses a wide range of techniques and activities that are geared towards demonstrating that software is reliable. Veriication techniques such as testing provide a way to assess the likelihood that software will fail during use. This paper introduces a diierent type of ver-iication that shows how likely it is that an incorrect(More)
AbstructIn this paper we introduce formulae for estimating the probability of failure when testing reveals no errors. These formulae incorporate random testing results, information about the input distribution, and prior assumptions about the probability of failure of the software. The formulae are not restricted to equally-likely input distributions, and(More)
Sensitivity analysis, which estimates the probability that a program location can hide a failure-causing fault, is addressed. The concept of sensitivity is discussed, and a fault/failure model that accounts for fault location is presented. Sensitivity analysis requires that every location be analyzed for three properties: the probability of execution(More)
This paper presents a fault injection methodology that predicts how software will behave when com ponents of the software fail hardware components external to the software fail human factor errors occur and bad input is provided to the software and the software is executing in unlikely operational modes Because of the enterprise critical nature of many of(More)
T he Board of Governors of the IEEE Computer Society established a steering committee in May 1993 for evaluating, planning, and coordinating actions related to establishing software engineering as a profession. In that same year the ACM Council endorsed the establishment of a Commission on Software Engineering. By January 1994, both societies formed a joint(More)
between these two versions. The original eight Principles were reordered to reflect the order in which software professionals should consider their ethical obligations—version 3.0’s first Principle was the Product while version 5.2’s first Principle is the Public. A shortened version of the Code was added to the front of the full version of the Code to(More)