Using Cause-and-Effect Diagrams in Research and Development
How to use fishbone (Ishikawa) diagrams in engineering investigations without mistaking ideas for causes: a precise effect statement, testable hypotheses, discriminating tests, corrective action and follow-up, with a worked example of a microcontroller that halts when a motor starts.
What the cost-escalation rule does and does not show, and how requirements review, FMEA and targeted verification reduce late defect discovery, with a worked embedded-firmware example that estimates the cost of the same defect at four discovery points.