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.3 Sharing Resources in Multitasking Systems

5.3.1 Problems with Sharing Resources

Up to this point, our example systems have consisted of separate, independent tasks; these perform their functions without any interaction with other tasks. In reality, this situation is rarely met in practical systems; tasks almost always influence each other in some way or means. Let's look at the most common reason for this: task intercommunication, as shown in Figure 5.18:

Figure 5.18: Sharing resources in a multitasking system – example 1

Assume that the design requirement of this pressure control system calls for the control and alarming tasks to exchange and share information. To support such operations, we now include a data store, one that can be written to and read from. Stores like this are frequently formed as records (structs) and/or data arrays, being located in RAM.

Sharing resources in a multitasking system is not, in itself, a problem. What...