dacs: Software failure data
In okamumu/Rsrat: A Software Reliability Assessment Tool with NHPP-Based Models
dacs R Documentation
Software failure data
Description
Software failure data (time data, grouped data) collected by John Musa and Yoshihiro Tohma
Details
The follwoing data are software failure data in real application, which was
collected by John Musa. The name without g (e.g. sys1, sys2) indicates
the interval time of failures in CPU time, and the last negative value
means the time in which there is no failure from the last failure. The name with
the suffix g (e.g. sys1g, sys2g) means the grouped fauilure data, i.e., the sequence
of the number of failures per woring day.
- sys1, sys1g
136 failures have occured during system test and operations in the program with 21,700 instructions.
- sys2, sys2g
54 failures have occured during system test and operations in the program with 27,700 instructions.
- sys3, sys3g
38 failures have occured during system test and operations in the program with 23,400 instructions.
- sys4, sys4g
53 failures have occured during system test and operations in the program with 33,500 instructions.
- sys5, sys5g
831 failures have occured during system test in the program with 2,445,000 instructions.
- sys6, sys6g
73 failures have occured during subsystem test in the program with 5,700 instructions.
- sys14c, sys14cg
36 failures have occured during operations in the program with hundreds of thousands instructions.
- sys17, sys17g
38 failures have occured during system test in the program with 61,900 instructions.
- sys27, sys27g
41 failures have occured during system test in the program with 126,100 instructions.
- sys40, sys40g
101 failures have occured during system test in the program with 180,000 instructions.
- ss1a, ss1ag
112 failures have occured during operations in the program with hundreds of thousands instructions.
- ss1b, ss1bg
375 failures have occured during operations in the program with hundreds of thousands instructions.
- ss1c, ss1cg
277 failures have occured during operations in the program with hundreds of thousands instructions.
- ss2, ss2g
192 failures have occured during operations in the program with hundreds of thousands instructions.
- ss3, ss3g
278 failures have occured during operations in the program with hundreds of thousands instructions.
- ss4, ss4g
196 failures have occured during operations in the program with hundreds of thousands instructions.
The data tohma is the faliure data collected by Yoshihiro Tohma. This is the grouped failure data consisting of
the number of failures per a test.
okamumu/Rsrat documentation built on Feb. 10, 2024, 11:07 p.m.
R Package Documentation
Browse R Packages
We want your feedback!
Note that we can't provide technical support on individual packages. You should contact the package authors for that.
| dacs | R Documentation |
Software failure data
Description
Software failure data (time data, grouped data) collected by John Musa and Yoshihiro Tohma
Details
The follwoing data are software failure data in real application, which was
collected by John Musa. The name without g (e.g. sys1, sys2) indicates
the interval time of failures in CPU time, and the last negative value
means the time in which there is no failure from the last failure. The name with
the suffix g (e.g. sys1g, sys2g) means the grouped fauilure data, i.e., the sequence
of the number of failures per woring day.
- sys1, sys1g
136 failures have occured during system test and operations in the program with 21,700 instructions.
- sys2, sys2g
54 failures have occured during system test and operations in the program with 27,700 instructions.
- sys3, sys3g
38 failures have occured during system test and operations in the program with 23,400 instructions.
- sys4, sys4g
53 failures have occured during system test and operations in the program with 33,500 instructions.
- sys5, sys5g
831 failures have occured during system test in the program with 2,445,000 instructions.
- sys6, sys6g
73 failures have occured during subsystem test in the program with 5,700 instructions.
- sys14c, sys14cg
36 failures have occured during operations in the program with hundreds of thousands instructions.
- sys17, sys17g
38 failures have occured during system test in the program with 61,900 instructions.
- sys27, sys27g
41 failures have occured during system test in the program with 126,100 instructions.
- sys40, sys40g
101 failures have occured during system test in the program with 180,000 instructions.
- ss1a, ss1ag
112 failures have occured during operations in the program with hundreds of thousands instructions.
- ss1b, ss1bg
375 failures have occured during operations in the program with hundreds of thousands instructions.
- ss1c, ss1cg
277 failures have occured during operations in the program with hundreds of thousands instructions.
- ss2, ss2g
192 failures have occured during operations in the program with hundreds of thousands instructions.
- ss3, ss3g
278 failures have occured during operations in the program with hundreds of thousands instructions.
- ss4, ss4g
196 failures have occured during operations in the program with hundreds of thousands instructions.
The data tohma is the faliure data collected by Yoshihiro Tohma. This is the grouped failure data consisting of
the number of failures per a test.
R Package Documentation
Browse R Packages
We want your feedback!
Note that we can't provide technical support on individual packages. You should contact the package authors for that.
Embedding an R snippet on your website
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.