Also, hard real-time systems often don't have to be particularly fast. They are just not allowed to ever be late.
Re:C++14: Transducers
by AnimalMuppet on Wednesday December 16, 2015 @05:25PM
(#10747836)
This. "The right answer, too late, is wrong."
And it doesn't matter if you got the right answer 100 times faster than needed 99 times if you are late once.
Physical property damage isn't a requirement of the definition of 'hard real time', it's just that common examples are often given that way.
If deadlines are missed in multimedia applications the product isn't meeting its stated and implied requirements.
The consequences may be different, but a television that drops perceptible video frames is just as 'defective' (from an engineering point of view) as an industrial control system which drops motor control signals.
In hard real-time systems, there's generally the idea that if scheduling fails, things will break and/or property (or, worse, people) will be damaged.
Think of things like industrial high-torque motor control and avionics.