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.7 Exercises

  1. Select an appropriate set of diagrams for use in the following situations:

    (a) Development of a service or library module (component)

    (b) Design of the software for a small controller where operations are mainly interrupt-driven

    (c) Development of a larger multi-tasking software system (single processor structure)

    (d) Development of a pipelined multiprocessor system

  2. Choose diagram(s) for use in modeling the following aspects of systems and software:

    (a) Concurrent (multi-tasking) structures

    (b) Logical software sub-systems

    (c) The interaction of software and its environment

    (d) Overall system structure and related physical devices

  3. You can use a meta-CASE tool to produce diagrams of your own choosing. What are the advantages and disadvantages of going down this route?
  4. Compare and contrast the features of the following diagrams:

    (a) Use case and event/response lists

    (b) SDL process diagrams, UML activity diagrams, and structure charts

    (c) Sequence and communication...