What is software reliability prediction?
Software reliability prediction estimates how many defects a release will contain, when they will be found, and how they affect availability — before the code is written. Requs applies IEEE 1633 prediction models to your requirements, process data and development practices to produce defect counts, a defect discovery profile and RAM figures early enough to change the outcome.
How is Software FMEA different from hardware FMEA?
Software FMEA analyses failure modes caused by requirements, logic, data, timing, states and interfaces — not physical wear-out. Requs uses the Common Defect Enumeration (CDE) and the 6D CDE process aligned with IEEE 1633 and SAE J1025, so software failure modes are enumerated systematically instead of brainstormed.
Which standards does Requs support?
IEEE 1633 (Recommended Practice for Software Reliability) and SAE J1025 (software FMEA), plus reliability program expectations in safety and mission standards — including software fault tree analysis, software allocation in the system reliability model, and software failures in FRACAS.
Who wrote the IEEE 1633 software reliability standard?
Ann Marie Neufelder, founder of Mission Ready Software, is the Chairperson of the IEEE 1633 working group and co-wrote IEEE Std 1633, the Recommended Practice for Software Reliability. Her credentials are grounded in the world's largest data set of software failure and failure rate documentation — over one million documents — which was used to derive and validate the prediction models in the standard.
Can software defects really be predicted before coding starts?
Yes. Defect density and failure modes correlate strongly with measurable program characteristics: requirements quality, staffing, process maturity, complexity and test strategy. Requs scores those inputs against decades of industry failure data to predict defect counts, edge cases and reliability growth before the first line of code.
What are edge cases, and why do they cause field failures?
Edge cases are the inputs, states, timings and sequences at the boundary of what a system was designed to handle. Most escaped field failures trace back to edge cases never enumerated in requirements or tests. Requs identifies the most common edge cases by function type so they can be designed for and verified.
Who uses Requs?
Reliability engineers, systems engineers, software leads, quality managers and program managers across aerospace, defense, medical devices, automotive, energy and industrial manufacturing — wherever software failure carries safety, mission or warranty cost.