Book Image

The Complete Edition - Software Engineering for Real-Time Systems

By : Jim Cooling
Book Image

The Complete Edition - Software Engineering for Real-Time Systems

By: Jim Cooling

Overview of this book

From air traffic control systems to network multimedia systems, real-time systems are everywhere. The correctness of the real-time system depends on the physical instant and the logical results of the computations. This book provides an elaborate introduction to software engineering for real-time systems, including a range of activities and methods required to produce a great real-time system. The book kicks off by describing real-time systems, their applications, and their impact on software design. You will learn the concepts of software and program design, as well as the different types of programming, software errors, and software life cycles, and how a multitasking structure benefits a system design. Moving ahead, you will learn why diagrams and diagramming plays a critical role in the software development process. You will practice documenting code-related work using Unified Modeling Language (UML), and analyze and test source code in both host and target systems to understand why performance is a key design-driver in applications. Next, you will develop a design strategy to overcome critical and fault-tolerant systems, and learn the importance of documentation in system design. By the end of this book, you will have sound knowledge and skills for developing real-time embedded systems.
Table of Contents (16 chapters)
Preface
15
Glossary of terms

5.5 Inter-task Communication

5.5.1 Introduction

The topic of inter-task communication was introduced in an informal way in Figure 5.18. As demonstrated, two tasks "communicate" by transferring data using a shared read/write data store. However, it turns out that this is just one of three communication techniques used in embedded systems (Figure 5.26):

Figure 5.26: Inter-task communication features

First, tasks may need to communicate in order to synchronize and/or coordinate their activities without exchanging data. Synchronization and coordination requirements generally occur where tasks are linked by events (or event sequences), not data. Such events include time-related factors such as time delays, elapsed time, and calendar time.

Second, tasks may exchange data but without needing to synchronize operations, as demonstrated in the tasking diagram of Figure 5.22.

Third, tasks may wish to exchange data but only at carefully synchronized...