At Mission Ready Software, we’ve spent nearly four decades analyzing the root causes of hundreds of thousands of software failures—more than any other organization in the world. Through this unparalleled research, we’ve identified that most failures stem from only a few hundred unique, recurring software defects.
These account for <30% and are exhaustive to find without an automated tool
Most defects don't originate in a single shall statement.
Our class focuses on the Top 100 Most Common and Easily Detectable Issues that arise early in development—often before a single line of code is written.
It all began with the creation of the “Common Defect Enumeration” (CDE), —a structured, publicly available catalog of software defects that have historically affected mission- and safety-critical systems.
For example, if your software doesn't have machine learning then it can't encounter machine learning failure modes.
The edge cases are hiding in plain site. You will learn how to review the relevant common defect enumerations while looking at your system and software models such as the state diagrams, interfaces, critical sensors. Don't focus on individual "shall" statements but instead focus on what's missing from the collection of shall statements.
Each of the CDEs can be tested in simulation or fault injection testing. This class shows you how.
The specifications and design can be improved by adding or modifying a few controls and mitigations for the common defect, ensuring greater resilience and preventing future defects.
Learn how to see defects and edge cases before the software is even coded. Learn how to test for those defects.
Discover how to identify overlooked defects and edge cases that may be hiding in plain sight within your system architecture and MBSE design flows.
Learn how to spot the underlying root causes of safety hazards
Discover how to identify common defects that compromise availability and uptime.