2. visualSTATE 4 Workshop

3. Seminar Content, Day 1 Introduction Different analysis methods State/Transition principles,  Mealy notation  Moore notation  The visualSTATE S/E notation  Use of concurrency visualSTATE demonstration  Navigator  Designer, S/E notation Exercise 1: Design of an S/E system The UML notation for state/event machines  Use of hierarchy  Use of variables  Use of signals visualSTATE demonstration  Designer, UML notation Exercise 2: Design of a small UML system

4. Seminar Content, Day 2 Test facilities using visualSTATE visualSTATE demonstration  Validator  Verificator Exercise 3: The visualSTATE test environment  Verifying a system  Validating a system  Use of log and sequence files  Use of dynamic and static analysis How the final application works with visualSTATE  Input to Event mapping  Action to Output mapping  API Library, runtime functions  A final application program Demonstration: A run-time example  The Application program structure  Compile and link of a visualSTATE application Real time environment  ROM-demands  Compiler demands  Use of real time kernel or operating system Command-line visualSTATE Making prototypes with visualSTATE Maintenance of the application, documentation, C-code generation Other visualSTATE applications Summary

5. visualSTATE Verificator Integration Exhaustive computation 7 different checks Use of elements Reachable transitions Conflicting transitions Activation of elements State dead end Local dead end System dead end Forward / Backward mode Backward = no dead-end check

6. Manual validation Simulation Sending events Monitoring Current States Active events Guards Triggered actions Timers Variables Signals

7. Using Breakpoints Thorough examination Predefined “disasters” Pre- & post-deduct Debugging purpose

8. Log & Animation Record test sequences Static analysis, use of Events Actions Signals Internal & External-variables Dynamic analysis Test coverage analysis Non-activated elements Most frequently used

9. RealLink Send events to target Monitor what’s going on in target Animate log files

10. Fundamentals visualSTATE is based on state machines Control logic is separated from device drivers

11. A visualSTATE application

12. State/Event Deduction

13. State/Event input Inquiry