The document discusses task-oriented design for embedded programs. It describes tasks as basic execution units that can run in parallel with separate time domains and different priorities. Tasks should have loose coupling and a single task is recommended for each piece of functionality, especially periodic functions. Methods for inter-task communication include shared variables, event buffers and queues, and synchronization techniques for concurrent access. The task diagram can depict information flow between tasks.

1. The Task Model Jernej Virag 14. 6. 2010 1 Jernej Virag

2. A Task 14. 6. 2010 Jernej Virag 2 basic execution unit

3. Task-oriented design Designing embedded programs with tasks 14. 6. 2010 Jernej Virag 3

4. Task-oriented design 14. 6. 2010 Jernej Virag 4 Parallel tasks have to be able to run in parallel

5. Task-oriented design 14. 6. 2010 Jernej Virag 5 Timing separate time domains

6. Task-oriented design 14. 6. 2010 Jernej Virag 6 Priority different response time and importance

7. Task-oriented design 14. 6. 2010 Jernej Virag 7 Structure single task for single piece of functionality

8. Task-oriented design 14. 6. 2010 Jernej Virag 8 Coupling loose coupling

9. Task-oriented design 14. 6. 2010 Jernej Virag 9 Periodic execution periodic functions warrant their own task

10. Inter-task communication Tasks talking to each other 14. 6. 2010 Jernej Virag 10

11. Inter-task communication 14. 6. 2010 Jernej Virag 11 Shared variables variables accessable by all tasks

12. Inter-task communication 14. 6. 2010 Jernej Virag 12 Event buffers and queues a more execution safe approach

13. Inter-task communication 14. 6. 2010 Jernej Virag 13 Synchronization concurrent access problems and solutions

14. The Task Diagram Outlook and elements 14. 6. 2010 Jernej Virag 14

15. The Task Diagram 14. 6. 2010 Jernej Virag 15

16. The Task Diagram 14. 6. 2010 Jernej Virag 16 data flow information flow

17. ? 14. 6. 2010 Jernej Virag 17