An Example Pattern from the Book
Design patterns, the elegant and time-tested solutions to recurring software design problems, serve as the foundation for this enlightening journey. Rather than inundating you with abstract theories and convoluted code snippets, this book takes a refreshing approach. It leverages design patterns as the means to explain complex concepts, making them not only comprehensible but also actionable.
The format of the patterns in this book is simple and understandable, even for a layperson. It also makes it easy to read the book quite fast, by just following the format to focus on the most important parts.
First, the pattern name serves as the title. Pattern names are always written in small caps to make them stand out. The pattern name is followed by either no stars or one or two stars. This star rating gives an idea of how well the authors think this pattern captures timeless beauty and knowledge to solve a recurring problem in the domain.
An ellipsis, three dots, begins the description of the context of the problem. It can provide hints about which other patterns might have been used in the design before arriving at this problem. Then, in bold typeface, the problem is described in a few sentences. The pattern then presents the forces inherent in this problem, as every problem solution needs to balance conflicting demands.
Next, in bold typeface and preceded by the formulaic "Therefore:", the solution is provided. At this point, the reader can also see an icon for the pattern, depicting an abstract presentation of the solution. The solution is discussed in detail, and the consequences of its application are explained. Finally, real-world examples are presented.
Read an example pattern from the book: Separate Real-time
Graph of the Pattern Language
Each pattern when applied has its own positive and negative consequences. Some of these consequences and new arising problems can be alleviated by applying more advanced patterns. The sequence in which the patterns can be applied after each other forms a network or graph. A Graph is a powerful way to navigate between the patterns. The graph is available here
Table of Contents of the Book
- Foreword
- Acknowledgements
- Table of Contents
- Setting the Landscape
- Why to Read This Book?
- How to Use This Book
- Comparison with Previous Works
- Domain of Distributed Control Systems
- Characteristics of Distributed Control Systems
- Long Life Cycle
- Distribution
- Functional Safety
- Safety-related Aspects in Distributed Control Systems
- Real-time Behavior
- Fault Tolerance
- Common Approaches and Challenges
- Agile Development in the Control System Domain
- Testing and Simulation
- Product Lines
- Documentation
- Technologies
- Data-Centric Middleware: Data Distribution Service (DD)S for Real-Time Systems
- Common Pitfalls
- Tackling the Challenges
- New Trends in the Domain
- Orchestrating Multiple Machines
- Service as Business
- Autonomous and Intelligent Machines
- Openness for 3rd Party Software
- Energy Consumption and Eco-Efficiency
- Information Security
- Software Architecture and Quality
- What Is Quality?
- Quality Attributes
- Measuring Quality
- External Quality and Internal Quality
- About Patterns
- Patterns – What Are They?
- From Patterns to Pattern Language
- The Story of the Patterns in This Book
- The Pattern Format Used in This Book
- Pattern Language for Distributed Control Systems
- Control System **
- Watchdog **
- Self-tests *
- Forced Input Value
- Error Counter *
- Patterns for Distribution
- Isolated Functionalities **
- Distributed Safety *
- Heartbeat **
- Global Time *
- Messaging Patterns
- One to Many **
- High Level Protocol **
- Messaging Interface *
- Protocol Version Handshake
- Message Queue **
- Categorized Messages **
- Message Channel Multiplexing *
- Message Gateway **
- Vector Clock for Messages *
- Unique Confirmation
- Event Handling Patterns
- Notifications *
- Notification Levels **
- Notification Logging *
- Early Warning **
- Patterns for Control System Modes
- Operating Modes **
- Safe State **
- Limp Home *
- Sensor Bypass *
- Devil May Care *
- Interchangeable Algorithm *
- Patterns for Data Management
- Variable Manager **
- Variable Guard *
- Variable Value Translator
- Data Status
- Counters *
- Snapshot *
- Patterns to Handle Scarce Resources
- Concurrent Execution **
- Static Scheduling **
- Separate Real-time **
- Partial Results
- Static Resource Allocation **
- Locker Key *
- Half Tasks *
- Early work *
- Patterns Decoupling Software and Hardware
- Hardware Abstraction Layer * *
- Operating System Abstraction *
- Virtual Runtime Environment * * a.k.a VIRTUAL MACHINE
- Redundancy Patterns
- 1+1 Redundancy **
- Voting *
- Patterns for System Start-up
- Bootstrapper **
- System Start-up **
- Start-up Negotiation
- Software Update Patterns
- Updateable Software * *
- Centralized Updater *
- Bumpless Updater
- Human-Machine Interface Patterns
- Human-Machine Interface * *
- Artificial Feedback * *
- Two-step Confirmation *
- Upright is OK *
- Task-based UI *
- Role-based UI * *
- Alternative Operating Station *
- Multiple Operating Stations *
- Appliance-Provided UI *
- Beacon *
- HMI Notifications
- Operator Profile * *
- Common Look-and-Feel *
- High Level Services Patterns
- Diagnostics *
- Blackbox
- Third-party Sandbox *
- Remote Access *
- Dynamic Message Channel Selector *
- Fleet Management Patterns
- Fleet Management *
- M2M Communication
- Opportunistic Delegation
- System Adapter *
- Patterns for System Configuration
- Parameters * *
- Configuration Parameter Versions
- Component-based Configuration *
- Control System Options *
- Applying Patterns
- Concluding Remarks
- Appendix
- Quality Attribute Table
- Patlets
- Glossary
- References
ISBN and Other Details
- ISBN-10 9781118694152
- ISBN-13 978-1118694152
- 1st Edition
- Publisher Wiley
- Published June 9, 2014
Cite: Eloranta, Veli-Pekka; Koskinen, Johannes; Leppänen, Marko; Reijonen, Ville (2014). Designing distributed control systems: a pattern language approach. ISBN: 978-1-118-69415-2 Wiley series in software design patterns. John Wiley and Sons.