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

14. Documentation

Documentation. Paperwork. Records. Words that induce instant apathy in any design team. Such things appeal to bureaucrats, not creative designers. Maybe this is a slightly harsh judgment – apologies to dedicated bureaucrats – but it is true. Unfortunately, documentation is a key feature of all professional design and development activities. It can be regarded as the lifeblood of the design body. Once it stops flowing properly, functions quickly deteriorate, eventually ending in rigor mortis. We just can't do without it. For some people, paperwork is an end in itself – but for the software engineer, it is an essential component of the design process.

The approach adopted here is essentially a pragmatic one. It explains:

  • Why documentation is necessary
  • How documentation fits into and supports the various phases of the software life cycle
  • The content, structure, and use of specific software documents
  • The concepts...