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

12.7 Processor Problems

12.7.1 Overview

This section is primarily concerned with processor-related runtime problems. It deals with issues resulting from either CPU register or memory malfunctions. Such malfunctions may be induced in a number of ways: electrical noise, aberrant program behavior, excessive temperatures, hardware faults, and more. The techniques used to seek to answer three questions:

  1. Is it OK to use the processor system in the first place?
  2. Is it safe to continue using the processor system in its normal running mode?
  3. If problems are detected, can we recover from the situation?

Questions (2) and (3) are closely interlinked and will be dealt with together as appropriate.

It is important to understand that these tests are not foolproof. Therefore, they augment, not replace, hardware-based techniques (for example, watchdogs and memory management units). Their advantages, when they work, are that they can do the following:

  • Warn us of processor...