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

9.8 Review

You should now:

  • Understand the underlying concepts involved in translating specifications into practical designs
  • Be able to distinguish clearly between concepts, diagramming, and processes when applied to software systems
  • Understand the fundamentals of functionally structured, OO, MDA, MDB, and Agile techniques
  • Have a general understanding of the diagrams used in these methods
  • Appreciate that while design methods are frequently different, their methodologies may be very similar
  • Realize that proper tools are needed to support diagram-based modeling techniques

The closing message here is that there is only one real way to understand what's involved in the software design process: get out and do it. Taking just one project to completion using just one software tool provides significant insight and understanding, which can never be obtained from trawling through countless chapters like this.