Analysis of failures in the tandem NonStop-UX operating system

Anshuman Thakur, Ravishankar K. Iyer, Luke Young, Inhwan Lee

Research output: Contribution to journalConference article

Abstract

This paper presents results from an investigation of failures in several releases of Tandem's NonStop-UX Operating System, which is based on UNIX System V. The analysis covers software failures from the field and failures reported by Tandem's test center. Fault classification is based on the status of the reported failures, the detection point of the errors in the operating system code, the panic message generated by the systems, the module that was found to be faulty, and the type of programming mistake. This classification reveals which modules in the operating system generate the most faults and the modules in which most errors are detected. We also present distributions of the failure and repair times including inter-arrival time of unique failures and time between duplicate failures. These distributions, unlike generic time distributions, such as time between failures, help characterize the software quality. Distribution of the repair times emphasizes the repair process and the factors influencing repair. Distribution of up-time of the systems before the panic reveals the factors triggering the panic.

Original languageEnglish (US)
Pages (from-to)40-49
Number of pages10
JournalProceedings of the International Symposium on Software Reliability Engineering, ISSRE
StatePublished - Dec 1 1995
EventProceedings of the 1995 6th International Symposium on Software Reliability Engineering - Toulouse, Fr
Duration: Oct 24 1995Oct 27 1995

Fingerprint

Repair
UNIX
Computer operating systems
Computer systems

ASJC Scopus subject areas

  • Software

Cite this

Analysis of failures in the tandem NonStop-UX operating system. / Thakur, Anshuman; Iyer, Ravishankar K.; Young, Luke; Lee, Inhwan.

In: Proceedings of the International Symposium on Software Reliability Engineering, ISSRE, 01.12.1995, p. 40-49.

Research output: Contribution to journalConference article

@article{fb2144a3194049c1bb978bb76674b6f9,
title = "Analysis of failures in the tandem NonStop-UX operating system",
abstract = "This paper presents results from an investigation of failures in several releases of Tandem's NonStop-UX Operating System, which is based on UNIX System V. The analysis covers software failures from the field and failures reported by Tandem's test center. Fault classification is based on the status of the reported failures, the detection point of the errors in the operating system code, the panic message generated by the systems, the module that was found to be faulty, and the type of programming mistake. This classification reveals which modules in the operating system generate the most faults and the modules in which most errors are detected. We also present distributions of the failure and repair times including inter-arrival time of unique failures and time between duplicate failures. These distributions, unlike generic time distributions, such as time between failures, help characterize the software quality. Distribution of the repair times emphasizes the repair process and the factors influencing repair. Distribution of up-time of the systems before the panic reveals the factors triggering the panic.",
author = "Anshuman Thakur and Iyer, {Ravishankar K.} and Luke Young and Inhwan Lee",
year = "1995",
month = "12",
day = "1",
language = "English (US)",
pages = "40--49",
journal = "Proceedings of the International Symposium on Software Reliability Engineering, ISSRE",
issn = "1071-9458",

}

TY - JOUR

T1 - Analysis of failures in the tandem NonStop-UX operating system

AU - Thakur, Anshuman

AU - Iyer, Ravishankar K.

AU - Young, Luke

AU - Lee, Inhwan

PY - 1995/12/1

Y1 - 1995/12/1

N2 - This paper presents results from an investigation of failures in several releases of Tandem's NonStop-UX Operating System, which is based on UNIX System V. The analysis covers software failures from the field and failures reported by Tandem's test center. Fault classification is based on the status of the reported failures, the detection point of the errors in the operating system code, the panic message generated by the systems, the module that was found to be faulty, and the type of programming mistake. This classification reveals which modules in the operating system generate the most faults and the modules in which most errors are detected. We also present distributions of the failure and repair times including inter-arrival time of unique failures and time between duplicate failures. These distributions, unlike generic time distributions, such as time between failures, help characterize the software quality. Distribution of the repair times emphasizes the repair process and the factors influencing repair. Distribution of up-time of the systems before the panic reveals the factors triggering the panic.

AB - This paper presents results from an investigation of failures in several releases of Tandem's NonStop-UX Operating System, which is based on UNIX System V. The analysis covers software failures from the field and failures reported by Tandem's test center. Fault classification is based on the status of the reported failures, the detection point of the errors in the operating system code, the panic message generated by the systems, the module that was found to be faulty, and the type of programming mistake. This classification reveals which modules in the operating system generate the most faults and the modules in which most errors are detected. We also present distributions of the failure and repair times including inter-arrival time of unique failures and time between duplicate failures. These distributions, unlike generic time distributions, such as time between failures, help characterize the software quality. Distribution of the repair times emphasizes the repair process and the factors influencing repair. Distribution of up-time of the systems before the panic reveals the factors triggering the panic.

UR - http://www.scopus.com/inward/record.url?scp=0029487429&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=0029487429&partnerID=8YFLogxK

M3 - Conference article

AN - SCOPUS:0029487429

SP - 40

EP - 49

JO - Proceedings of the International Symposium on Software Reliability Engineering, ISSRE

JF - Proceedings of the International Symposium on Software Reliability Engineering, ISSRE

SN - 1071-9458

ER -