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.3. Design Implementation Using Functionally Structured Techniques

9.3.1 Overview of the Design Process

Figure 9.18 provides an overview of the activities performed when implementing a design using functionally structured methods.

Figure 9.18: Overview of the functionally structured design process

This should be self-explanatory. The rationale underlying this approach is as follows:

  • The designer, when developing the ideal software model, must consider only how best to satisfy the software system requirements, not how it's going to be implemented. Underpinning this work is the need to clearly identify the major functions performed by the software and how they can be described as a set of software modules. This model must be exercised to ensure that it is correct both functionally and temporally. After all, if the ideal model doesn't work, there's no point in proceeding further with the design; you will have to tear it up and start...