1 / 14

STATEMATE

STATEMATE. A Working Environment for the Development of Complex Reactive Systems. Overview. Reactive System Why is STATEMATE so Great? Visual formalism & Graphical orientation Unique debugging abilities. Reactive System. Reactions to discrete events Focus on control driven aspect

kara
Download Presentation

STATEMATE

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. STATEMATE A Working Environment for the Development of Complex Reactive Systems

  2. Overview • Reactive System • Why is STATEMATE so Great? • Visual formalism & Graphical orientation • Unique debugging abilities

  3. Reactive System • Reactions to discrete events • Focus on control driven aspect • Real time • Involve complex sequences, actions, conditions, and info flow under time constraint • Multiple levels of detail

  4. Visual formalism & Graphical orientation:System Under Development • Structure (architecture) -module hierarchy -flow of data chunks and control signals • Conceptual Model • Functionality -activity hierarchy -data flow • Behavior -control activities -when, how, why Structure Conceptual Model Functionality Behavior

  5. Modeling Languages • Structure: module-charts • Functionality: activity-charts • Behavior: state-charts -Based on common set of graphical conventions -Graphics editors that check syntax -Formal semantics embedded in each

  6. Module-charts C E3 E1 A C1 Sub-modules Modules C2 B E4 E2 Environment module Shared Data Storage module

  7. Activity-charts C Flow of control item Control activity E1 S1 D External activity S2 A E3 K E2 B H Sub-activity Flow of data item activity

  8. State-charts A B C D H t E n J s u o G m v I F p r w q y x K L

  9. Unique Debugging Abilities • Dynamic Stepping • Programmed Executions -Simulation Control Language (SCL) • Debugging Partial System • Source-Level Debugging

  10. Dynamic Stepping • User emulates environment • View all consequences of one dynamic step • STATEMATE highlights all resulting active states and actions

  11. Programmed Executions • User writes programs to handle details • Set up breakpoints • Trace database during execution • View progress as a discrete animation of system behavior

  12. Debugging Partial System • User emulates environment and system events external to focus part • Dynamic tests • Run-time exhaustive, brute-force, sets of executions • For very critical, well isolated, and SUFFICIENTLY SMALL parts of model • Ex: reachability, nondeterminism, deadlock, usage of transitions

  13. Source-Level Debugging • Prototype code: • Generated higher level code (Ada, C) • Replace parts of the model & Interacts with remaining model • Test closer to final environment • Link code with “soft” panels • Trace parts of code back to model • Incremental substitution of model with code

  14. Conclusions • Visual Formalism & Graphical Orientation • Clarity in complexity detailed systems • Unique Debugging Abilities • Deep and comprehensive testing and debugging

More Related