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

12.4 Application Software Aspects

12.4.1 Basic Design and Programming Issues (or Doing It Right in the First Place)

The advice given here is mainly intended to stop you from getting into trouble in the first place, that is, fault prevention:

  • Use rigorous design techniques.
  • Use well-ordered program structures.
  • Develop and use good programming standards. Produce readable code.
  • Where possible, use programming languages designed for critical applications. For safety-critical work, first consider Spark Ada.
  • If this isn't possible, use languages or language subsets that provide high levels of integrity (for example, Ada, MISRA C, and JSF C++).
  • If even this isn't possible, use appropriate development tools (for example, Lint for C) to check for code quality (but if this is your chosen route for safety-critical projects, great care is needed).
  • Do not, in normal code, use unconditional transfers of program control (these may be implemented explicitly...