Protecting against cosmic bitflips for example, relevant if you write software that ends up on airplanes/space crafts. Also if you just want resilient software that work even though hardware is starting to fail. See https://en.wikipedia.org/wiki/Soft_error
Comments
Protecting against cosmic bitflips for example, relevant if you write software that ends up on airplanes/space crafts. Also if you just want resilient software that work even though hardware is starting to fail. See https://en.wikipedia.org/wiki/Soft_error
Yes but what is the FMECA case where software is a better domain to address this than hardware?
I think the point is to implement in software for redundancy, not as an alternative to doing it in hardware. You'll do both essentially.