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

11.3 Software Debugging – What and Why?

11.3.1 Debugging – Fundamental Concepts

One point must be clearly understood. Software debugging is concerned with error detection in the software, not in the hardware. We assume that the hardware is fault-free. Hardware faults introduced by the software are here regarded as software errors. So, they are included in the listing of software bugs.

A simplistic view of program execution ("journey into the unknown") is depicted in Figure 11.8. The complete program consists of the instructions and data needed to get from A to B. Along the way, many actions are carried out. Data is collected, deposited, and modified, output devices are activated, and input devices are interrogated. When B is reached and all actions are correctly performed, we can be pretty sure that the program is correct.

Now, how do we test this program? The simplest way is to install it on the target system and run it. In fact, unless special test...