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

10.5 Integration Testing

10.5.1 Fundamentals

The basic ideas of software integration and integration testing were spelled out earlier in Section 10.1. Let's return to this issue, to look at the general aspects of the testing of integrated units. The ideas are generally applicable to all the levels and units of the software shown in Figure 10.4. In practice, a variety of units are likely to be used, including software machines, modules, objects, components, and tasks. The one item that stands out as being different is an object within an inheritance structure; this is dealt with separately in the section on OO testing. Clearly, test details will depend on the precise nature of the individual software units.

Three integration techniques in general use are the following:

  • Big-bang approach. All integration and testing is executed in a single phase.
  • Top-down incremental route.
  • Bottom-up incremental path.

The big-bang method has been pretty well discredited...