Real-Time Systems: Definitions, Features & Applications

1. What is a Real-Time System (RTS)?

A Real-Time System (RTS) is a computer system where correctness depends not only on the logical result but also on the timeliness of the result. If the system fails to respond within a specified time, it is considered a failure.

Key Idea: Timeliness Over Accuracy

• In general-purpose systems (e.g., web browsers, word processors), correctness is about logical output.
• In RTS, correctness = logical result + timing constraints. Example: A pacemaker must deliver an electric pulse at the exact right time to regulate a patient’s heartbeat. If it delays, the patient’s life is at risk.

Why Timing Matters?

Real Picture:

---

2. Classification of Real-Time Systems

RTS are categorized based on their response-time requirements:

Worked Example: Hard vs. Soft RTS in Nepal

• Hard RTS: NTC’s traffic signal control system must switch lights in <1 second to prevent accidents. A delay could cause collisions.
• Soft RTS: eSewa’s payment processing should complete within 2 seconds, but a slight delay (e.g., 3 seconds) is tolerable.

---

3. Key Characteristics of Real-Time Systems

RTS must satisfy four critical properties to ensure reliability:

A. Determinism

• The system must produce consistent, predictable responses under the same conditions.
• Why? A hard RTS (e.g., Ncell’s network switch) must prioritize emergency calls over data downloads to meet deadlines.

B. Predictability

• The system’s behavior must be guaranteed within specified time bounds.
• Example: A Pathao driver’s route optimizer must predict traffic delays to estimate arrival times accurately.

C. Timeliness

• Tasks must complete within deadlines (e.g., Daraz’s order fulfillment must ship within 24–48 hours, or customers lose trust).

D. Resource Constraints

• RTS often operate on limited resources (CPU, memory, bandwidth).
• Example: A bank’s ATM system must handle multiple transactions simultaneously without crashing.

Comparison Table: RTS vs. General-Purpose Systems

---

4. Applications of Real-Time Systems

RTS are everywhere—from life-saving devices to everyday services. Here’s how Nepal and global companies use them:

In the Real World

1. eSewa (Nepal)

   • Idea Used: Soft RTS for transaction processing.
   • How? When you pay an electricity bill via eSewa, the system must:
     • Deduct money from your account within 1–2 seconds.
     • Update the NTC database instantly.
     • Send a confirmation SMS without delay.
   • Failure Impact: If the system lags, users may face billing errors or service disruptions.

2. NTC’s Traffic Management System

   • Idea Used: Hard RTS for signal control.
   • How? Traffic lights at Kathmandu’s busy intersections (e.g., Thapathali) use sensors to:
     • Detect vehicles in real time.
     • Adjust signal timings within milliseconds to prevent gridlock.
   • Failure Impact: A delay of even 0.5 seconds could cause accidents.

3. Google Maps (Global)

   • Idea Used: Firm RTS for navigation updates.
   • How? When you drive, Google Maps:
     • Recalculates routes every few seconds based on traffic.
     • Updates ETA in real time using GPS and server data.
   • Failure Impact: A 1-second delay in route updates might lead to wrong turns, but it’s not catastrophic.

4. NEPSE (Nepal Stock Exchange)

   • Idea Used: Soft RTS for stock trading.
   • How? When you buy/sell shares:
     • The system must execute trades within milliseconds.
     • Update your portfolio instantly.
   • Failure Impact: A delay of >100ms could mean missing a profitable trade.

Real Picture:

---

5. Challenges in Real-Time Systems

Despite their importance, RTS face unique challenges:

A. Timing Constraints

• Problem: Ensuring tasks meet deadlines under varying loads.
• Example: During Dashain, when Khalti processes millions of transactions, the system must handle spikes without delays.

B. Resource Competition

• Problem: Multiple tasks competing for CPU/memory.
• Example: A hospital’s patient monitoring system must prioritize critical alerts (e.g., a patient’s heart rate dropping) over routine checks.

C. Fault Tolerance

• Problem: RTS must recover from failures without missing deadlines.
• Example: If a bank’s ATM network crashes, backup servers must take over instantly to avoid customer frustration.

D. Complexity in Design

• Problem: Balancing predictability and flexibility is difficult.
• Example: Pathao’s ride-hailing app must:
  • Match drivers to riders in <5 seconds.
  • Adjust fares based on demand dynamically.

Mermaid Diagram: RTS Challenges

---

6. Real-Time Systems vs. General-Purpose Systems

Worked Example: Comparing a Pacemaker (RTS) and a Smartphone (General-Purpose)

• Pacemaker (Hard RTS):
  • Must deliver a pulse every 1 second (deterministic).
  • If it misses a beat, the patient’s life is at risk.
• Smartphone (General-Purpose):
  • Can take minutes to update an app.
  • A delay is annoying but not dangerous.

---

7. Exam Tip: How to Score Full Marks

1. Define RTS Clearly

   • Always start with: "A Real-Time System is a computer system where the correctness of the system depends on both the logical result and the time at which the result is produced."
   • Marks Tip: Examiners love precise definitions.

2. Classify with Examples

   • For hard/soft/firm RTS, always give one Nepalese and one global example.
   • Example:
     • Hard: NTC traffic signals (Nepal), aircraft autopilot (global).
     • Soft: eSewa payments (Nepal), online banking (global).

3. Compare RTS vs. General Systems

   • Use a table (as above) to highlight differences in scheduling, error handling, and applications.

4. Discuss Challenges with Real Scenarios

   • Link challenges to Nepali companies (e.g., Khalti during festivals, NTC during load-shedding).
   • Example: "During Dashain, Khalti’s system faces resource competition as millions of users make transactions simultaneously. The RTS must prioritize critical payments (e.g., utility bills) over non-urgent ones (e.g., shopping)."

5. Use Diagrams

   • Draw timeline figures for scheduling examples.
   • Example:

     TIMELINE: Task Deadlines in RTS
     |--------|--------|--------|--------|
     Task A  | Task B  | Task C  | Task D
     Deadline: 1s    2s    3s    4s
     

   • Marks Tip: Label axes and tasks clearly.

---

Final Note: Real-Time Systems are everywhere—from saving lives in hospitals to improving your commute in Kathmandu. Mastering this unit means understanding why timing matters and how systems like eSewa, NTC, and Google Maps rely on RTS to function smoothly. For exams, focus on definitions, classifications, and real-world applications—they carry the most marks!