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.6 Functionally Structured Design and Functional Flow Modeling

4.6.1 Software Design and Structured Charts – Limitations

Visualize a situation where you have been appointed software manager of the anti-skid braking system project. You have never worked on this project or even have any previous knowledge of the design. So, on day one, you set out to get an in-depth knowledge of the system and its software. Assume that the project documentation held by the software team consists of:

  • A structure chart(s) as per Figure 4.41
  • Source code modules for the application, at varying stages of completion:

Figure 4.70: CRC cards for the system of Figure 4.60

The question is, how helpful is this material, especially the structure chart? Well, it would certainly give you a very clear guide as to how the software should be structured. Moreover, it would allow you to do a code walk-through to check the compliance of the code (the implementation) with...