1 / 8

Summary of Behaviour Types and CR Resolutions for Nokia Siemens Networks MTS

This document summarizes the change requests (CRs) resolved in Behaviour Types for Nokia Siemens Networks. Key updates include the successful resolution of technical issues and the development of the package, with particular attention to CR412 (Function Reference) and CR2012 (self-execution). Currently, the C++ and XML language mappings for TCI are missing and require attention alongside proposals for operational semantics applicable to several operations. The text describes various functions, testing configurations, and the next steps for adding language mappings and finalizing semantics.

hideaki-oota
Télécharger la présentation

Summary of Behaviour Types and CR Resolutions for Nokia Siemens Networks MTS

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. Extension Package: Behaviour Types Thomas Deiß Nokia Siemens Networks MTS#48

  2. Summary • CRs resolved • 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

  3. 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 referencevar MyFunc3 myVar1 := blanks; • var MyFunc3 myVar2 := int2char; • var MyFunc3 myVar3 := null; Thomas Deiß / Advanced Typing / March 2009

  4. 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

  5. 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

  6. 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

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

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

More Related