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.5 Model-Driven Architecture

9.5.1 Fundamental Concepts

Model-Driven Architecture (MDA) is essentially a process for developing software where designs are based on model-driven engineering techniques. The basic concepts of MDA are outlined in Figure 9.47, showing the essential steps in the development process.

Figure 9.47: MDA concepts

We start work by designing a model (or set of models) of our software using diagramming techniques. Such models are general in nature (generic), ignoring any platform-specific (implementation) factors. The objective is to produce an abstract design solution that can then be used on a variety of platforms. Such platforms include servers, mainframes, desktops, and internet-based hardware units. Note that the primary driving factors in the design process are the system requirements and software specifications.

This general model – the Platform Independent Model (PIM) – is then transformed into a Platform...