Re: What about multiple definitions?
The question of "What is Real Time?" has been quite a problem for control and robotic systems. All too often, an OS is advertised as "Real Time" when the truth is far from it. While the definition may vary based on the system needed response times, I like to use the concept of Repeatability. If the OS can guarantee the repeating of code blocks in the same period / time frame then it "could be" considered "Real Time". I use this concept to address the various issues of speed to process, lag and response times, interrupt overhead, etc. A simple multi-tasking OS is not real time unless there is a fixed scheduler with enough processing capacity to service all the needed tasks without interference with the others. I am sure that there are better definitions and would welcome them for review.