Schedule a Software Walkthrough Free Trial
Requs AI Predict — Help Index

Help & reference for software reliability prediction

Requs AI Predict turns a software size and development-practice survey into a full reliability growth picture — defect density, defect counts, failure rate, MTTF, availability and reliability — using a machine-learning model trained on historical projects.

7 Formulas
From size through to reliability, each stage feeding the next
9 Steps
The quickstart path from LRU to a reliability growth summary
IEEE 1633
Aligned methodology, referenced throughout this help set
01 — Tabs

Every tab in Requs AI Predict

The application is organized around a project file. Open or create one, then work through these tabs in order.

Reference

EULA

The end user license agreement.

Setup

Installation

Install and activate a floating server license or a dedicated computer license.

File

Project tab

Create, open, edit, delete, import or export a prediction project.

Input

Survey tab

Assess the software reliability. Visible only when a project is open.

Output

Dashboard

See the results. Visible once a project is open and the required inputs are confirmed.

Optional

Software FMEA tab

The software FMEA module — visible only when purchased and a project is open.

Optional

Estimation

Reliability growth module — trends actual test data against Exponential and Logarithmic models to forecast MTBF.

02 — Prediction Formulas

The 7 software reliability prediction formulas

Each stage below feeds the next — size scales the defect count, the defect profile drives the failure rate, and failure rate resolves into availability and reliability.

§1Size

Predict size

Covers

Estimating software size using detailed source-lines-of-code estimates, or via people-hours, normalized to one base language.

Feeds
  • Normalized effective KSLOC
  • Upper / lower size bounds
Read the size prediction guide
§2Density

Predict defect density

Covers

Completing the development-practice survey so the machine learning model can predict defect density from your assessment.

Feeds
  • Predicted defects per KSLOC
  • Sensitivity analysis inputs
Read the survey guide
§3Counts

Predict defect counts

Covers

Total predicted defects = normalized effective size × predicted defect density.

Feeds
  • Total predicted defect count
  • Upper / lower defect bounds
Read the defect count guide
§4Profile

Predict defect profile

Covers

Predicting when defects will be detected for the first time, across the Rayleigh growth curve.

Feeds
  • Monthly discovery profile
  • Failure rate calculation
Read the defect profile guide
§5MTTF

Predict failure rate / MTTF

Covers

Deriving failure rate, MTTF, critical failure rate and MTTCF from the defect profile, duty cycle and installed sites.

Feeds
  • MTTF / MTTCF
  • Availability calculation
Read the failure rate guide
§6Availability

Predict availability

Covers

Predicting availability from MTTCF and restore time (MTSWR) — the measure that matters for continually-operating systems.

Feeds
  • Monthly availability growth
  • Reliability calculation
Read the availability guide
§7Reliability

Predict reliability

Covers

Predicting the probability of failure or success over a specific mission time.

Feeds
  • Reliability growth summary
  • Export to the Dashboard
Read the reliability guide
03 — Quickstart Guide

Nine steps from LRU to release decision

Work through these in order the first time you set up a project.

01Scope

Identify the software LRUs

Identify the software LRUs (Line Replaceable Units) in your system. See IEEE 1633 for more guidance.

02Project

Create a project per LRU

Press “New” on the Project tab for each LRU. Different LRUs can have different duty cycles, development organizations or languages — don’t model them as one project.

03Inputs

Confirm the required inputs

Go to Survey → Required Inputs. Every input must be edited or confirmed — size estimates have no default and must be entered. Ask software engineering if you don’t know an answer.

04Survey

Answer every category

Visit each remaining Survey tab. Answering some questions in every category beats answering all questions in just one. Leave a response as “U” if it’s unknown.

05Refresh

Run the Dashboard

Press “Refresh all inputs” on the Dashboard tab. The frames show the average of each estimate over the life of this software version, up to the next feature release.

06Review

Read the growth profiles

View the remaining-fault and remaining-critical-fault profiles, plus failure rate, MTTF, MTTCF, reliability and availability. Save any graph with the disk icon.

07Summary

Pull the growth summary

Press “Reliability Growth Summary” for every metric in tabular form, and export it if you need it elsewhere.

08Export

Export the project

Back on the Project tab, press Export to export all inputs and the average predictions shown on the Dashboard.

09Iterate

Revisit as things change

Revisit your inputs whenever size estimates, required inputs or development practices change, or you learn more. More accurate answers make for a more accurate prediction.

Advanced — optional Create a new project and import the responses exported in Step 8. Flag any development practices that could be adopted this release, set them to affirmative, and review the change in the Dashboard — the reduction in defect density is linearly related to the reduction in failure rate.
04 — Support & Training

Support, training, and release notes

Helpful tips, FAQ, videos, and the latest release notes for Requs AI Predict.

Reference

Support

Support email blasts, templates, FAQ and videos.

Reference

Release notes

What’s new in the latest version of Requs AI Predict.

Training

In-person & virtual training

September 24–26, Historic Savannah, GA. 1.5 days of software reliability predictions training, and 1.5 days of SFMEA training. Attend in person or virtually.

Find the formula, tab, or step you're working with.

Jump straight into the prediction pipeline, or start from the quickstart guide.