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

3.3 Making Mistakes – Sources and Causes

3.3.1 A General Comment

Why and how do we make mistakes? Figure 3.11 attempts, in a light-hearted way, to highlight some of the issues involved:

Figure 3.11: Making mistakes

It may be simplistic, but it does get to the heart of the matter because it shows that three major factors are at work here:

  • How we convert what we think into what we say
  • How we express ourselves
  • How we convert what we see (receive) into thought

How do these apply to the requirements stage of a project? Let's first look at the customer-supplier relationship in more detail, as modeled in Figure 3.12:

Figure 3.12: Simplistic view of the customer-supplier relationship

This model also applies to the system's designer and software designer relationship. So rules derived to enhance customer-supplier interactions can also be applied later in the software development cycle.

The first...