![]() |
VOOZH | about |
In computer science, real-time systems are an intrinsic component of applications with high demands on time, for input processing. According to their response to time constraints, there are two categories as follows Hard Real-Time Systems and Soft Real-Time Systems.
Note: Even though both systems have deadlines to be met it is the consequences of failure to meet those deadlines that set the two apart.
Note: In a medical device that monitors a patient's vital signs, Free RTOS can ensure that the data is collected, processed and displayed in a timely and accurate manner, even under heavy system load, without sacrificing the responsiveness and stability of the system.
Example:
1. Air Traffic Control
2. Medical System
A Soft Real-Time System is a variant of real-time system where timely processing is desirable but late processing do not cause the system to fail or can cause dramatic loss of life and property. However, failing to meet the time expectation, lead to a decline of service delivery or limited quality output.
Example:
1. Multimedia Transmission and Reception
2. Computer Games
3. Communication system like voice over IP
| Hard Real Time System | Soft Real Time System |
|---|---|
| In hard real time system, the size of data file is small or medium. | In soft real time system, the size of data file is large. |
| In this system response time is in millisecond. | In this system response time are higher. |
| Peak load performance should be predictable. | In soft real time system, peak load can be tolerated. |
| In this system safety is critical. | In this system safety is not critical. |
| A hard real time system is very restrictive. | A Soft real time system is less restrictive. |
| In case of an error in a hard real time system, the computation is rolled back. | In case of an soft real time system, computation is rolled back to previously established a checkpoint. |
| Satellite launch, Railway signaling system etc. | DVD player, telephone switches, electronic games etc. |
| Guarantees response within a specific deadline. | Does not guarantee response within a specific deadline. |
| Catastrophic or severe consequences (e.g., loss of life or property damage). | Minor consequences (e.g., degraded performance or reduced quality). |
| Focused on processing critical tasks with high priority. | Focused on processing tasks with lower priority. |
| Highly predictable, with well-defined and deterministic behavior. | Less predictable, with behavior that may vary depending on system load or conditions. |