Only 30% originate in the code. Very expensive reactive approach.
Sounds good but isn't good. This is how you analyze hardware not software.
Only about 9% of all defects originate in a single shall statement. Very expensive. It's more efficient to run requirements analyzers.
If it takes forever to finish the FMEA then it can't affect design
Identifies 50-100x preventable failure modes than other methods
These CDEs typically occur 7+ times more often than defects in a single shall statement
These CDEs are hiding in plain sight. No need to dig through code to find them.
About the product and environment. Import from MBSE.
Relevant and likely edge cases identified from world's largest database of root causes
Requs.ai does the heavy lifting so you can do what you are good at - connecting the failure mode to a system hazard
Risk based ranking of root causes and recommended design controls and tests
The only tool with a built in comprehensive list of root causes that have caused most of the worlds software failures
While some tools use AI, ours is the only tool to use AI for the purpose of predicting the most likely root causes
Brainstorming the root causes and assessing likelihood are 67% of the effort. Requs.ai does both for you.
Generate a highly effective software FMEA in 2 weeks
Combined with Requs AI Predict, know the total number of defects, where the edge cases lie, and the effects of the failure modes.
Requs AI imports STMs, software component list, hardware component lists, and key interfaces from Cameo. Requs AI Software FMEA has an API and open architecture. So, you can integrate the Software FMEA with hardware FMEA tools.
Dedicated or floating licenses. Yearly subscriptions or perpetual plans. Cloud or Desktop solution.
Feature tiers allow you to purchase only the features you need.
IEEE 1633, AIAG & VDA FMEA Handbook, ISO 26262, Mil-Std-882E, SAE 1025, IEC 60812, DI-SESS-81495. Supports safety assessments as per Mil-Std-882E.
Requs.ai runs on air gapped computers