visualSTATE 4 Workshop

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

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

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

Manual validation

• Simulation

• Sending events

• Monitoring

• Current States

• Active events

• Guards

• Triggered actions

• Timers

• Variables

• Signals

AA AB

AD AC

E1() /

E2() /

E3() /

E4() /

E3() /

Using Breakpoints

• Thorough examination

• Predefined “disasters”

• Pre- & post-deduct

• Debugging purpose

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

RealLink

• Send events to target• Monitor what’s going

on in target• Animate log files

Fundamentals

• visualSTATE is based on state machines

• Control logic is separated from device drivers

visua lSTATEenigne

Device Driverconvert inputs

to events

R eal L ife

x=port(0); port(1) = 1 ;

R ea l L ife

Device Driverconvert actions

to outputs

A visualSTATE application

app lica tion app lica tionv isua lS T A T EA P I

s ta techart

s ta techart da ta

ac tioneven t

State/Event Deduction

Statechart data

Action

The State/EventDeduction finds all

Actions and updatesvariables and the internal

state vector.

Functions:SEM_DeductSEM_GetOutputSEM_NextS tate

Event

Contradictionstatus

State/Event input Inquiry

Statechart data

The State/Event input(s)Inquiry finds all eventsw hich can be used toperform a State/Event

Deduction that w ill giveactions and/or new states

Functions:SEM_InquirySEM_GetInput

Event