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.6 Review

At this point you should:

  • Appreciate that diagrams are an important part of the software design process
  • Understand why, in practice, a range of diagrams is required
  • Know what basic modeling features (for example, system dynamics, messaging, and structure) need to be supported by diagrams
  • Know when, why, and how to apply the various modeling techniques outlined in this chapter
  • Be able to select the diagram set that best meets your own needs
  • Recognize the distinction between design processes and diagramming (modeling) techniques
  • Have knowledge of the diagrams used when designing using both functionally structured and OO methods
  • Realize that these, in many cases, are not sufficient; extensions or additions may be needed
  • Realize that there isn't a uniquely right diagramming method