Offline scheduling

Complex algorithms fit complex problems
Many tasks, long WCET, serious processing power, ...

But most real-world situations are much simpler
Critical tasks feature a small WCET but are jitter-sensitive
The number of critical tasks is limited
Their period is usually "compatible" one another
e.g.: 5ms, 10ms, 50ms
Jitter should be limited, ideally zero

This is best solved by manual placement of release times
Which still requires a sort of scheduler, to manage context switches