Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
The Complete Edition - Software Engineering for Real-Time Systems

You're reading from   The Complete Edition - Software Engineering for Real-Time Systems A software engineering perspective toward designing real-time systems

Arrow left icon
Product type Paperback
Published in Dec 2019
Publisher
ISBN-13 9781839216589
Length 824 pages
Edition 1st Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
Jim Cooling Jim Cooling
Author Profile Icon Jim Cooling
Jim Cooling
Arrow right icon
View More author details
Toc

Table of Contents (16) Chapters Close

Preface
1. Real-Time Systems – Setting the Scene 2. The Search for Dependable Software FREE CHAPTER 3. First Steps – Requirements Analysis and Specification 4. Software and Program Design Concepts 5. Multitasking Systems – an Introduction 6. Diagramming – an Introduction 7. Practical Diagramming Methods 8. Designing and Constructing Software – Code-Related Issues 9. Software Analysis and Design – Methods and Methodologies 10. Analyzing and Testing Source Code 11. Development Tools 12. Mission-Critical and Safety-Critical Systems 13. Performance Engineering 14. Documentation Glossary of terms

4.2 The Elements of Modular Design

4.2.1 Introduction

At this stage, the overall concepts of structured design should be clear (if they aren't, go back and reread earlier sections). We can now put them in the context of specific software design methodologies. But before doing so, the more important elements and building blocks of the design process need to be explained. Some of these we've already met within the framework of general design procedures. Now their functions as software design elements are examined.

4.2.2 Modules and Modularization

It can be seen that a basic feature of "good" design is the partitioning of systems into smaller chunks. The primary reason is to reduce the total problem into one of the manageable proportions (the "head full of information" limit). In software terms, this process is called "modularization, "the elements resulting from this being "modules." It is a basic requirement that modules should...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image