150 likes | 159 Views
Explore the principles of real-time systems, fault tolerance, and design paradigms with examples like railway operations and telecommunications. Learn about event-triggered and time-triggered systems for critical applications.
E N D
Real-time systems • Real-time (RT) Systems • RT transaction Controlled Object Computer System Operator Sensors / Actuators CS351 - Software Engineering (AY2004)
Example Computer System Railway Operator Alpha Engines / Points Ada CS351 - Software Engineering (AY2004)
System design • Finite processing capacity. • Critical Real-time transactions. • Assumptions • Load? • Faults? • Coverage? CS351 - Software Engineering (AY2004)
Load hypothesis • Peak load? • How rare are events? • Do events cascade? CS351 - Software Engineering (AY2004)
Fault hypothesis • Types of faults? • Frequency of faults? • Peak load & maximum fault rate? • Assumption coverage? CS351 - Software Engineering (AY2004)
Hard and soft High Availability Telephone Soft High Integrity Banking RT systems Fail Safe Signalling Hard Fail Operational Flight control CS351 - Software Engineering (AY2004)
Design paradigms • Guaranteed response (GR). • Best-effort. • Most RT systems are best-effort. • Safety critical systems must be GR. CS351 - Software Engineering (AY2004)
Example real-timesystems • Factory automation • open loop, • closed loop. • Telephone switching. • Car control. CS351 - Software Engineering (AY2004)
Fault-tolerance • Fault-tolerant (FT) systems. • Mask or repair errors to avoid faults. • Redundancy • physical, • time, • information. CS351 - Software Engineering (AY2004)
Redundancy • Passive redundancy • fail-silent, • fail-stop. • Active redundancy • voting/concensus, • replica determinism. CS351 - Software Engineering (AY2004)
Event triggered real-time systems • Event oriented execution. • Event showers • random, • sporadic. • Scheduling is dynamic and hard. • Extensible. CS351 - Software Engineering (AY2004)
Time triggered real-time systems • Process events at fixed times. • Overload not handled. • Piority events may be delayed. • Scheduling can be statically determined. • It is hard to extend. CS351 - Software Engineering (AY2004)
TT Example Operator ethernet Event Monitor Command Filter Alpha 9600 bps 2400 bps Trains CS351 - Software Engineering (AY2004)