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

7.5 Diagrams and the Design Process

We have covered a great deal of ground in this chapter concerning the syntax and semantics of diagrams. Now, though, is the time to step back and take a look at the larger picture: the use of these diagrams within the software design process. Here, our process model is based on implementing a large system consisting of a network, node, processor, and task-level designs. The diagrams listed have been defined in general or generic terms only; detailed syntax and semantics are not specified. Now, in practice, we're likely to implement a design using either standard structured (functional or data flow methods) or OO techniques. So, how well do these support the diagramming needs outlined in Figure 6.20? The answer to this is given in Figures 7.67 to 7.70:

Figure 7.67: Diagrams and network-level design

Figure 7.68: Diagrams and node-level design

Figure 7.69: Diagrams and processor...