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

2.1 What Do We Want in Our Software?

In an ideal world, what do we look for in our software? There are many answers to this question, but, more than anything else, one stands out: the production of totally fault-free software. We look for that because, we reason, given such software, our systems should work exactly as planned. But will they? Unfortunately, not necessarily so, as will be shown later. When designing software, a total system view must be taken. There are too many opportunities to get designs and implementations wrong; it isn't just confined to the code-writing stage.

In this chapter, we'll first look at the root problems of such errors. Then, we'll define the qualities of software that attempt to eliminate these. You must be realistic about them, however. Given the current state of design tools, it is impossible to guarantee the delivery of fault-free systems (on a personal note, I believe that totally fault-free systems are a myth).

Therefore, if...