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 ModelJernej Virag14. 6. 20101Jernej Virag

2. A Task14. 6. 2010Jernej Virag2basic execution unit

3. Task-oriented designDesigning embedded programs with tasks14. 6. 2010Jernej Virag3

4. Task-oriented design14. 6. 2010Jernej Virag4Paralleltasks have to be able to run in parallel

5. Task-oriented design14. 6. 2010Jernej Virag5Timingseparate time domains

6. Task-oriented design14. 6. 2010Jernej Virag6Prioritydifferent response time and importance

7. Task-oriented design14. 6. 2010Jernej Virag7Structuresingle task for single piece of functionality

8. Task-oriented design14. 6. 2010Jernej Virag8Couplingloose coupling

9. Task-oriented design14. 6. 2010Jernej Virag9Periodic executionperiodic functions warrant their own task

10. Inter-task communicationTasks talking to each other14. 6. 2010Jernej Virag10

11. Inter-task communication14. 6. 2010Jernej Virag11Shared variablesvariables accessable by all tasks

12. Inter-task communication14. 6. 2010Jernej Virag12Event buffers and queuesa more execution safe approach

13. Inter-task communication14. 6. 2010Jernej Virag13Synchronizationconcurrent access problems and solutions

14. The Task DiagramOutlook and elements14. 6. 2010Jernej Virag14

15. The Task Diagram14. 6. 2010Jernej Virag15

16. The Task Diagram14. 6. 2010Jernej Virag16data flowinformation flow

17. ?14. 6. 2010Jernej Virag17