Advantages and disadvantages with Static- and Dynamic Scheduling
<p>I'm opening this questions since I can't find <strong>easy to understand</strong> summarized information about this topic. There isn't even a good youtube-video that explains this.</p>

<p>I'm currently studying realtime programming and statical- and dynamical scheduling is a part of it. I just can't seem to get my head around it.</p>

<p>If there is someone who can explain the advantages and disadvantages with statical- and dynamical scheduling in a educational way, that would really be helpful.</p>

<p>What I've got so far is the following:</p>

<ol>
<li><p>Statical scheduling:
Is a off-line approach where a schedule is generated manually. It can be modified during run-time, but isn't suggested because it then can cause the threads to miss it's deadlines. It's easy to implement and to analyze. Because it's easy to analyze it's easy to see if the system is going to make all of its deadlines.</p></li>
<li><p>Dynamical scheduling:
Is a on-line approach where the schedule is generated automatically. It can be modified during run-time by the system and it should't cause (in most cases) the threads to miss its deadlines. If the system changes it's easy to generate a new schedule since it's automatically generated. There isn't a guarantee that the system meets all its deadlines.</p></li>
</ol>

<p>Anyone that can explain these two a bit better than me? Or perhaps add more information about these two. Perhaps illustrate it with a image so it'll be easier to wrap my head around it.</p>