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 Conceptual Model FunctionalityBehavior Structure

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 E1 Shared Data E2 E4 E3 C C1 C2 B A Environment module Storage module Sub-modules Modules

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

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

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