Sujet : Re: "RESET"
De : jl (at) *nospam* glen--canyon.com (john larkin)
Groupes : sci.electronics.designDate : 06. Jun 2025, 14:40:44
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <dsr54kpih0lffgg5gsmcj6rg0g319ghqvi@4ax.com>
References : 1 2 3 4 5
User-Agent : ForteAgent/8.00.32.1272
On Fri, 06 Jun 2025 13:45:02 +0200,
albert@spenarnc.xs4all.nl wrote:
In article <101p8sd$phe5$1@dont-email.me>,
David Brown <david.brown@hesbynett.no> wrote:
<SNIP>
I recall something of the opposite - a long time ago, we had to add a
variety of "safety" features to a product to fulfil a customer's safety
/ reliability checklist, without regard to how realistic the failure
scenarios were and without spending time and money on analysis. The
result was, IMHO, lower reliability because it was more likely for the
extra monitoring and checking hardware and software to fail than for the
original functional stuff to fail. Many of these extra checks were in
themselves impossible to test.
>
I worked on the Dutch railway systems safety and control software.
Once they added external control checking.
I've seen the code. In places there was an 8 level indentation
caused by if's switches and loops.
>
There was also a ban on automatic testing. I got on a row, because
I used a 3 line batch file (.BAT) to save on repetitive typing.
>
Groetjes Albert
The advantage of a state machine is that it forces people to know the
state of the system.