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

13.7 Review

Having completed this chapter, you should now:

  • Understand the various types of timing requirements of real-time (especially embedded) systems
  • Appreciate that neglecting to take performance into account during design can lead to disastrous results
  • Know the difference between reactive and proactive design processes
  • Understand what software performance engineering (SPE) is
  • Recognize its importance
  • Realize why and when you should use the techniques of SPE
  • Know what is meant by performance modeling and simulation
  • Know what is meant by performance requirements, performance targets, and performance achievable
  • Understand the underlying concepts of top-down, bottom-up, and middle-out performance modeling
  • See how these approaches can be used in isolation or in concert
  • Be able to do simple time-budgeting for software design
  • Be able to make a case for the use of performance modeling tools in the design of complex systems