1 / 15

Real-Time System Development

Real-Time System Development. Issues and Methods. (As part of CSA404). Some opening wise-cracks!. “The computer is controlling something that interacts with with reality on a timely basis. … … An unresponsive real-time system may be worse than no system at all.”

charleen-nigel
Télécharger la présentation

Real-Time System Development

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Real-Time System Development Issues and Methods (As part of CSA404)

  2. Some opening wise-cracks! “The computer is controlling something that interacts with with reality on a timely basis. … … An unresponsive real-time system may be worse than no system at all.” [R. Glass - 1983] “In today’s society, an incorrectly responsive real-time system is something that should be put to death before it itself has time to do so to others.” [E. Cachia - 1998] 

  3. A General Definition Systems whose correct functioning depends on the timeliness of its response(s)forcing its timing to be defined under some form of constraint This definition is very broad and clearly lends itself to further definition

  4. R-T Distinguishing Features (1) • Form part of a larger system (embedded systems) • Often interact with non-human external entities (direct control systems) • Pre-defined timing constraints typically in the range of ms to minutes (time critical systems)

  5. R-T Distinguishing Features (2) • Automatic (R-T) system control excluding any human intervention (automated control systems) • The current state of a R-T systems depends not only on any external stimuli it receives but also on its present state (reactive systems)

  6. Application Areas of R-T Systems • Industrial • Commercial • Military Typical features Complexity Multiple control streams Strict timing constraints

  7. WHAT?! R-T Categorisation Soft (missed timing deadlines are fault causing but not catastrophic) Hard (missed timing deadlines cause catastrophic system failure) Furthermore ... • Soft or hard R-T systems can be • Slow • Fast • Therefore, 4 classes of R-T systems can be defined

  8. 4 R-T System Classes

  9. Some R-T Class Examples(1) • Hard-fast (computation times  10ms) • Vehicle airbag systems • Safety cut-off control systems • Aircraft control systems • Hard-slow (computation times  10s) • Missile engagement systems • Conventional process control • Critical environment monitoring systems

  10. Some R-T Class Examples(2) • Soft-fast (times may vary up to minutes) • Specific characteristics include • Humans are a system component • Contain a substantial MMI • Weapon fire-control systems • System status monitor systems • Soft-slow (times usually vary up to minutes) • Trend monitoring systems • Analysis-for-feedback systems • Auto-adaptation systems

  11. Modelling R-T Systems • Understand which aspects of R-T systems require particular attention • Adapt or create adequate representation tools for modelling the required R-T system aspects • Understand how specific R-T modelling techniques can be integrated into generic software development procedures

  12. R-T System Aspects to Model • Model control functions • Model control data • Model timing constraints • Model system reactions • Model fault handling/recovery • (Sub) System redundancy

  13. Modelling Control Functions • Control modelling is dynamic by nature • Modelling techniques to describe dynamic system behaviour exist • Control modelling can be tackled separately but should always be considered as part of the whole system model • One particular control modelling technique might not model all the required control aspects of a system

  14. Some Tools for Modelling Dynamic System Behaviour • Finite State Machines in the form of Mealy State Transition Diagrams • Modified DFDs (e.g. Hatley-Pirbhai extensions a.k.a. Control Flow Diagrams - CFDs ) • Mathematical logic

  15. Aspects to look out for when specifying R-T systems • Task execution time CPU time required for task completion • Task period/Task rate Time interval between task starts. The number of task starts in a fixed period of time is the rate • Task deadline Time by which a task must reach completion • Jitter Time interval in which a task may begin and terminate before its deadline • Transport lag Time interval between actual real-world event and the system’s response (signal to actuator)

More Related