These aren't much better than just trending the failures in a spreadsheet
By the time you have this data, the project can already be late due to resource misallocation
we learn about state-of-the-art predictive models built from decades of benchmarking defects
Just answer some questions about your software and how it's developed
Predict defects in advance of testing and be better prepared.
Predict defect density and risk level. Identify a risky project while there is still time to change course. Identify resources needed to avoid technical debt.
These are the first 2 modules needed for predicting failure rates, MTBF, availability, and reliability.
First, the risk of the software program is assessed by predicting a normalized measure of defects – defect density
Then the defect density is multiplied by an effective size that’s derived from the story points/people effort predicted for the version
Then the defect arrival times are forecasted based on the expected number of installed sites.
The more questions you answer (accurately) the better the confidence in the prediction