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.4 Practical Approaches to Analysis and Specification

3.4.1 General Aspects

What is the fundamental purpose of the analysis and specification – the requirements – phase? It is to define what a proposed system is to do, not how it is supposed to do it; "how" is the function of the design process. However, in practice, there isn't always a sharp boundary between requirements and design. And the problem is compounded because some design methods make little distinction between the two. We can see why these overlap by considering the make-up of the requirements stage (Figure 3.15). The first part of this process is concerned with analyzing and recording the system requirements. Note this well. Many traditional (that is DP) descriptions discuss the analysis of systems, but you can only analyze a system if one already exists.

In the initial run-through, design factors shouldn't affect the outcome of the analysis work. Using the information acquired...