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

3.5 Communication Aspects – the Role of Prototyping

3.5.1 Prototyping – an Introduction

In engineering, a prototype is a pre-production version of a manufactured product such as a component, sub-assembly, or system. The purpose of building a prototype is to prove design and manufacturing aspects as early as possible before resources are committed to full-scale production. A number of questions are evaluated during prototyping, including:

  • Is the product actually feasible? In other words, are problems present that are fundamentally impossible to overcome?
  • Are there unforeseen high-risk technical and cost aspects?
  • Are the design and build correct? That is, has the correct product been built (validation), and has the product been built correctly (verification)?
  • Can it be built in a manufacturing environment (as opposed to the hand-crafting methods of the prototyping phase)?
  • Can it be built for the right price?

Once this phase is completed...