jont- wrote:M1ke H wrote:/awaits comment from jont-/
![Wink ;)](./images/smilies/icon_e_wink.gif)
It's not the touchscreens that are failing per-se, but the memory chip filling up and causing other things to stop working.
This book:
https://www.waterstones.com/book/humble ... 0141989143Covers several examples like that, where the system's designers had one implementation in mind, but it didn't align with actual use. [There's a parallel in the 'safety' world: work as imagined Vs work as done]
This quote from a paper (google a few words to read it) covers on example:
On February 25, 1991, a Patriot missile defence system operating in Dhahran, Saudi Arabia, failed to engage an incoming Scud missile. The missile struck U.S. Army barracks killing 28 soldiers and injuring 98. The reason for the failure of the Patriot was a fixed-point round-off error in the range-gate algorithm of the Patriot radar unit’s tracking system. This paper reconstructs the events and explains, how the patriot system works. Then it illustrates in detail how the round-off error developed and how it amplified to a critical inaccuracy. This occurred because missile was designed to be a mobile defence system, switched on and off (so resetting the memory) often. But here it wasn't. It was switched on, then left. The rounding errors kept accumulating. And with supersonic missiles, you can't afford to be far out.
Your 'standard' is how you drive alone, not how you drive during a test.