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.1 Introduction

12.1.1 Overview of Critical Systems

Let's start by explaining what we mean by "critical" systems. A simple definition: systems in which failure(s) may have significant and far-reaching consequences. This is, of course, a very broad view of things, so something more precise is needed. To put things into perspective, consider the following representative real-world examples (Figure 12.1). The first four systems can be categorized as "safety-critical"; the others are "mission-critical." The essential difference is self-evident:

Figure 12.1: Typical systems – failures and their consequences

Assume that your computer forms part of a critical system. What should (or can) you do to put operational quality into your product? There is no simple answer; it all depends on how systems must operate when faults occur. Very broadly, we can categorize system requirements as shown in Figure 12.2. First, we have...