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

4.2 The Elements of Modular Design

4.2.1 Introduction

At this stage, the overall concepts of structured design should be clear (if they aren't, go back and reread earlier sections). We can now put them in the context of specific software design methodologies. But before doing so, the more important elements and building blocks of the design process need to be explained. Some of these we've already met within the framework of general design procedures. Now their functions as software design elements are examined.

4.2.2 Modules and Modularization

It can be seen that a basic feature of "good" design is the partitioning of systems into smaller chunks. The primary reason is to reduce the total problem into one of the manageable proportions (the "head full of information" limit). In software terms, this process is called "modularization, "the elements resulting from this being "modules." It is a basic requirement that modules should...