Extension Package: Behaviour Types Thomas Deiß Nokia Siemens Networks MTS#48

Summary CRs resolved Status CR412: Function Reference CR2012: runs on self Status Technical issues resolved, package written Missing C++ and XML language mapping for TCI Proposal for operational semantics of one operation exists Needs to be checked and applied to 3 other operations similarly Open Issue: package is written as change to main parts of the TTCN-3 standard Is this readable enough? Thomas Deiß / Advanced Typing / March 2009

Behaviour types type function MyFunc3 ( in integer p1 ) return charstring; function blanks (in integer p1) return charstring { // return a charstring of p1 blank chars } //function reference var MyFunc3 myVar1 := blanks; var MyFunc3 myVar2 := int2char; var MyFunc3 myVar3 := null; Thomas Deiß / Advanced Typing / March 2009

Behaviour Types Usage Test configurations State machine implementation Flexible default handling Load and robustness tests Behaviour types for Functions Altsteps Testcases Thomas Deiß / Advanced Typing / March 2009

Usage of behaviours Pass as actual parameters Compare Send to other components log Apply to arguments Also activate, start, execute Thomas Deiß / Advanced Typing / March 2009

Semantics Instead of considering function, altstep, test case names as literals, evaluate an expression that results in a behaviour Thomas Deiß / Advanced Typing / March 2009

TRI / TCI TRI: no effect TCI New abstract types for function, altstep, testcase Thomas Deiß / Advanced Typing / March 2009

Next steps Proposal: Add C++ and XML language mappings Finalize operational semantics Then proceed to approval Thomas Deiß / Advanced Typing / March 2009