Schedule a Software Walkthrough
Early edge case prediction

AI enabled software identifies hidden edge cases before the code is written

Using the Common Defect Enumeration (CDE)

Requs AI Edge Case common defect enumeration software
CDE
Employs common defect enumeration published on the DOW Warfighter Acquisition University (which we authored)
Test strategy recommendations
Generates potential test strategies for each edge case
Design loop
Import from MBSE and affect design
01 — Authority

Our founder is the global leader in software failures

World's largest database of software failures analyzed by root cause

CDE Taxonomy inventor

From it, we created the Common Defect Enumeration, the primary taxonomy currently adopted and cited across DOW technical frameworks.

Standards Body

IEEE 1633 Leadership

Chair of the 2026 IEEE 1633 working group — the governing standard for software reliability engineering.

SAE 1025 FMEA

Section 7

Section 7 of SAE 1025 FMEA is based on our 6D CDE Software FMEA approach.

02 — Requs AI Edge Case

Other tools "shift to the left". Requs AI Edge Case "starts to the left"

See how in our whitepaper, Identifying Hidden Edge Cases Early.

Capability
Other Edge Case Software
Our solution
Compliant with industry standards
Don't support section 7 or the IEEE 1633 clauses
Software FMEA can be tailored for SAE 1025 FMEA section 7, IEEE 1633, AIAG & VDA, IEC 60812.
Software centric failure modes
Built on a few overused oversimplified failure modes
Focuses in the things that have historically go wrong.
Integrated systems viewpoint
They focus largely on the code.
Software doesn't fail in a vacuum so it shouldn't be modeled with that assumption. We use the 6 Dimensional viewpoint.
Customizable to your application type and industry
Not supported
Requs AI Blueprint is an industry specific customization of Requs AI Edge Case.
edge case common defect enumeration defect snowball diagram

Stop the defect snowball before the first line of code is written — Requs AI Edge Case identifies edge cases at requirements and design, before they compound into the defects that show up in code.

03 — Requs AI Software avoids the popular but ineffective approaches

CSCI/hardware centric, "shall" statement, and detailed viewpoints aren't recommended in the IEEE 1633 2026

§1"Shall" statement focus

Individual shall statements are analyzed in isolation

Focus

A small minority of failures originate in a single shall statement.

Better approach

Analyze the requirements as a collective whole.

§2Detailed

Lines of code or code functions are analyzed

Focus

Exhaustively expensive. Only about one third of the failures can be found with this viewpoint.

Better approach

Analyze the design models, interfaces and specifications before the code is written.

"Start to the left"

Start with the online demo or a demonstration.