Software reliability-engineered testing

Author

Musa, John D.

Author_Institution

Software Reliability Eng., AT&T Bell Labs., Murray Hill, NJ, USA

Volume

29

Issue

11

fYear

1996

fDate

11/1/1996 12:00:00 AM

Firstpage

61

Lastpage

68

Abstract

Software testing often results in delays to market and high cost without assuring product reliability. Software reliability engineered testing (SRET), an AT&T best practice, carefully engineers testing to overcome these weaknesses. The article describes SRET in the context of an actual project at AT&T, which is called Fone Follower. The author selected this example because of its simplicity; it in no way implies that SRET is limited to telecommunications systems. SRET is based on the AT&T Best Current Practice of Software Reliability Engineering, approved in May 1991. Qualification as an AT&T best current practice requires use on typically eight to 10 projects with documented large benefit/cost ratios, as well as a probing review by two boards of high level managers. Some 70 project managers also reviewed this particular practice. Standards for approval as a best current practice are high; only five of 30 proposed best current practices were approved in 1991

Keywords

program testing; software reliability; telecommunication; telecommunication computing; AT&T Best Current Practice; AT&T best practice; Fone Follower; SRET; benefit/cost ratios; high level managers; product reliability; project managers; software reliability engineered testing; telecommunications systems; Application software; Automatic testing; Certification; Hardware; Life testing; Reliability engineering; Software systems; Software testing; System testing; Systems engineering and theory;

fLanguage

English

Journal_Title

Computer

Publisher

ieee

ISSN

0018-9162

Type

jour

DOI

10.1109/2.544239

Filename

544239