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

7.1 Introduction

At this point, it wouldn't be surprising if you are wondering the following:

  • Why the topic has been left until now (when we've already used diagrams extensively)?
  • If you are faced with learning the details of yet another set of diagrams?

Dealing with the first point: diagrams were introduced – in a very informal way – only as and when needed (in other words, used in a relevant context). The reasons for doing this are threefold. First, it demonstrated the power of diagramming techniques. Second, it implicitly made a good case for using diagrams as a design tool (they aren't just a set of pretty pictures). Third, it (hopefully) made the task of learning the syntax and semantics of a wide range of diagrams a fairly painless process. Now, though, we can deal with diagramming in a more formal manner. And, to answer the second question: yes, we will meet some new diagrams along the way. But we won't need to redo the material...