5 ms·
There is no root cause. https://www.kitchensoap.com/2012/02/10/each-necessary-but-only-jointly-sufficient/ https://www.kitchensoap.com/2012/02/10/each-necessar
by devdas 7y ago
There is no root cause.
https://www.kitchensoap.com/2012/02/10/each-necessary-but-only-jointly-sufficient/ https://www.kitchensoap.com/2012/02/10/each-necessary-but-on...
https://blog.acolyer.org/2016/02/10/how-complex-systems-fail/ https://blog.acolyer.org/2016/02/10/how-complex-systems-fail...
http://web.mit.edu/2.75/resources/random/How%20Complex%20Systems%20Fail.pdf http://web.mit.edu/2.75/resources/random/How%20Complex%20Sys...
- astine 7y agoThe OP is talking about bugs not complex system failures. These are not the same thing. It might take multiple bugs to cause a complex system to fail, because complex systems often have enormous amounts of complexity built in, but a single bug is often a fairly unidimensional thing. You can identify the root cause of a bug.
- inflatableDodo 7y agoAnother way to look at that is that a root cause can be a set.
- hnick 7y agoI've had more than one case at work where it would come down to bad requirements. Both systems worked exactly as specified and were bug free (for the issue in scope). They just had a different understanding of reality by design. Root cause here is some mixture of poor understanding of the problem domain by various staff.
- JohnFen 7y ago> Both systems worked exactly as specified and were bug free If the system is working as designed, then there really is no bug. A bug is a malfunction, after all. I've always called broken systems that are working as designed BAD: Broken As Designed.
- hnick 7y agoI'd agree. The defect (not sure you can call it a bug?) was in the design/spec not the system.