1. International Telecommunication Union ITU-T Study Group 17, Geneva, 5-14 October 2005 An Introduction to version 3 Dr. Michael Ebner University Göttingen, Germany ebner@cs.uni-goettingen.de

2. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 2 12 October 2005 About the speaker o Is researcher in the telematics group of Prof. Dr. D. Hogrefe at the Institute for Informatics, University of Göttingen, Germany o Is active in the research area of test automation, model-based testing, and protocol modeling o Working with TTCN-3 since 2000 Influenced data types and synchronous communication of TTCN-3

3. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 3 12 October 2005 An Introduction to Institute for Informatics, University of Göttingen George-August-Universität Göttingen Department of Mathematics Institute for Informatics Gauß, Weber, Hilbert, … Center for Informatics Other 12 departments Founded in 1737 by King George II (England), who also founded Princeton U (1746) and Columbia U (1754) 01/2003~ Telematics Group Prof. Hogrefe Distributed Systems Group, Prof. Switzer Theory Group Prof. Waack Softw. Eng. Group Prof. Grabowski Database Group Prof. May 2000~ Practical Informatics Group Prof. Neumair (GWDG) Service Eng. Group Prof. Margaria 44 Nobel Prize-winner live(d) and work(ed) here

4. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 4 12 October 2005 Table of contents 1. Overall view of TTCN-3 2. TTCN-3 en detail a.Types and values b.Behavior specification 3. Implementation of TTCN-3 4. Presentation formats 5. Final remarks

5. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 5 12 October 2005 Why using a standardised test language?1(3) Developer Heterogeneity increases Testing throughout the process Integrator Systems Integrator

6. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 6 12 October 2005 Why using a standardised test language?2(3) Testing tight to Services TTCN-3 Testing tight to Development e.g. JUnit Developer Integrator Systems Integrator

7. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 7 12 October 2005 Why using a standardised test language?3(3) o Standardised test language improves communication among developers with the customer improves transparency one test language for all departments No proprietary test languages reduces costs costs of training usage of commercial test equipments (tools, test suites, etc.)

8. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 8 12 October 2005 What is TTCN-3 ? o The standardised (black-box) test specification and test implementation language. o Developed by the European Telecommunications Standards Institute (ETSI) from 1999 to 2001. based on the experiences from previous TTCN versions. o Applicable for all kinds of black-box testing for reactive and distributed systems, e.g. Telecom systems (ISDN, ATM); Mobile (telecom) systems (GSM, UMTS); Internet (has been applied to IPv6); CORBA based systems.

9. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 9 12 October 2005 TTCN stands for …??? o Tree and Tabular Combined Notation For TTCN-1 and TTCN-2 o Testing and Test Control Notation Since TTCN-3

10. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 10 12 October 2005 The TTCN-3 series of standards 1(3) TTCN-3 User Graphical Format Tabular Format ASN.1 Types & Values Other Types & Values n Other Types & Values 2 TTCN-3 Core Notation Presentation Format n Other Types & Values 3

11. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 11 12 October 2005 The TTCN-3 series of standards 2(3) TTCN-3 User Graphical Format Tabular Format ASN.1 Types & Values Other Types & Values n Other Types & Values 2 TTCN-3 Core Notation Presentation Format n Other Types & Values 3 mscmi_synch1_conc1 mtcISAP1MSAP2 UML Testing Profile IDLXMLC/C++ : testcase myTestcase () runs on MTCType system TSIType {mydefault := activate (OtherwiseFail); verdict.set(pass); : connect(PTC_ISAP1:CP_ISAP1,mtc:CP_ISAP1); : map(PTC_ISAP1:ISAP1, system:TSI_ISAP1); : PTC_ISAP1.start(func_PTC_ISAP1()); PTC_MSAP2.start(func_PTC_MSAP2()); Synchronization(); all component.done; log(Correct Termination); } :

12. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 12 12 October 2005 The TTCN-3 series of standards 3(3) o European Standard (ES) in 6 parts ES 201 873-1: TTCN-3 Core Language ES 201 873-2: TTCN-3 Tabular Presentation Format (TFT) ES 201 873-3: TTCN-3 Graphical Presentation Format (GFT) ES 201 873-4: TTCN-3 Operational Semantics ES 201 873-5: TTCN-3 Runtime Interface (TRI) ES 201 873-6: TTCN-3 Control Interface (TCI) ES 201 873-7: Using ASN.1 with TTCN-3 ES 201 873-8: Using IDL with TTCN-3 ES 201 873-9: Using XML with TTCN-3 ES 201 873-10: Using C/C++ with TTCN-3 (planned) Z.140 Z.141 Z.142 Z.143 Z.144 Z.145 Z.146 ITU-T Recommendation (SG17 / WP3 / Q14) New edition 3.1.1 of TTCN-3 since June 2005

13. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 13 12 October 2005 Concepts o Black-Box Testing with TTCN-3 o Test Configuration o Test Components o Communication Ports o Test Verdicts o Ingredients of TTCN-3 o Structure of TTCN-3 specs o Re-use of existing Code

14. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 14 12 October 2005 Black-box testing with TTCN-3 TTCN-3 Test Case Port.send(Stimulus) Port.receive(Response) System Under Test Port Assignment of a Test Verdict

15. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 15 12 October 2005 TTCN-3 Test Case Test configuration1(2) create MTC start create TCs TC start SUT

16. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 16 12 October 2005 Test configuration2(2) SUT Real Test System Interface Test System Abstract Test System Interface TC2 TC1 IN OUT OUT IN Connected Ports INOUT Mapped Ports INOUT Real Test System Interface

17. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 17 12 October 2005 Test components o There are three kinds of components Abstract Test System Interface defined as component MTC (Main Test Component) PTC (Parallel Test Component) Test System Real test system connected to the SUT Abstract Test System Interface MTC PTC n PTC 1 PTC 2

18. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 18 12 October 2005 Communication ports 1(2) o Test components communicate via ports o A test port is modeled as an infinite FIFO queue o Ports have direction (in, out, inout) o There are three types of port message-based, procedure-based or mixed TC 1 TC 2 P1.send (Msg)P2.receive (Msg) P2 (in)P1 (out)

19. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 19 12 October 2005 Communication ports 2(2) call getcall reply or raise exception Caller Callee getreply or catch exception blocking Language

20. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 20 12 October 2005 PIF Test verdicts o Test verdicts: none < pass < inconc < fail < error o Each test component has its own local verdict, which can be set (setverdict) and read (getverdict). o A test case returns a global verdict MTCPTC 1 PTC N Verdict returned by the test case when it terminates I setverdict(inconc)setverdict(fail) FP setverdict(pass)

21. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 21 12 October 2005 Ingredients of TTCN-3 o Built-in and user-defined generic data types (e.g., to define messages, service primitives, information elements, PDUs). o Actual test data transmitted/received during testing. o Definition of the components and communication ports that are used to build various testing configurations. o Specification of the dynamic test system behavior. Test Behavior Test Configuration TTCN-3 Test Data Data Types

22. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 22 12 October 2005 Structure of TTCN-3 specs – TTCN-3 Modules o Modules are the building blocks of all TTCN-3 test specifications. o A test suite is a module. o A module has a definitions part and an (optional) control part. o Modules can be parameterized. o Modules can import definitions from other modules. Module Module Control Module Definitions

23. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 23 12 October 2005 Structure of TTCN-3 specs – Module definitions part o Definitions are global to the entire module. o Data Type definitions are based on TTCN-3 predefined and structured types. o Templates define the test data. o Ports and Components are used in Test Configurations. o Functions, Altsteps and Test Cases define behavior. Test Cases Altsteps Functions Test Components Communication Ports Signature Templates Data Templates Signatures Constants Data Types

24. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 24 12 October 2005 Structure of TTCN-3 specs – Module control part1(2) Module Module Control Module Definitions o Module control is the dynamic part of a TTCN-3 specification where the test cases are executed. o Local declarations, such as variables and timers may be made in the control part. o Basic programming statements may be used to select and control the execution of the test cases.

25. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 25 12 October 2005 Structure of TTCN-3 specs – Module control part2(2) module … { … control{ var integer count; if(execute(SIP_UA_REC_V_001()) == pass) { // Execute test case 10 times count := 0; while( count <= 10) { execute(SIP_UA_REC_V_002()); count := count + 1; } // end while } // end if } // end control } // end module

26. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 26 12 October 2005 Reuse of existing code – The import mechanism1(2) o Main Module contains the control part, which specifies test suite execution. o Modules may reuse definitions from other (library) modules. o Implicit import of definitions via chains of imports is not allowed, i.e., an explicit import has to be added. Reason: A module shall know all modules which it depends on. Main Module Library Module 1 import Library Module 2 import Library Module 3 import implicit import of a definition required explicit import

27. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 27 12 October 2005 Reuse of existing code – The import mechanism2(2) o Import allows to import single definitions definitions of a certain kind, and groups of definitions from other modules. o Definitions may be imported recursively. o If several definitions are addressed, certain definitions can be excluded by using an except directive. import form ModuleOne { modulepar ModPar2; type RecordType_T2 } import from ModuleTwo recursive { testcase T_case } import from ModuleThree all except { template all } import form ModuleOne { modulepar ModPar2; type RecordType_T2 } import from ModuleTwo recursive { testcase T_case } import from ModuleThree all except { template all }

28. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 28 12 October 2005 Use of non – TTCN-3 code – Language mapping o Importing non TTCN-3 definitions requires a language mapping onto TTCN-3. o The language mapping defines the meaning of non TTCN-3 definitions in TTCN-3 modules. o The language mapping may provide TTCN-3 additional features for imported definitions (e.g., operations for ASN.1 data types). TTCN-3 Module import ASN.1 Spec. XML Spec. : XYZ Spec. : TTCN-3 ASN.1 : XML XYZ : language mapping

29. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 29 12 October 2005 Table of contents 1. Overall view of TTCN-3 2. TTCN-3 en detail a.Types and values b.Behavior specification 3. Implementation of TTCN-3 4. Presentation formats 5. Final remarks

30. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 30 12 October 2005 Language Data types and test data – Constants, types, templates 1(2) o TTCN-3 data types: integer, char, universal char, float, boolean, objid enumerated bitstring, hexstring, octetstring, charstring, universal charstring, record, record of, set, set of, union anytype verdicttype address o Useful types IEEE754float, long, byte, … Iso8859string, utf16string, … Test Cases Altsteps Functions Test Components Communication Ports Signature Templates Data Templates Signatures Constants Data Types

31. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 31 12 October 2005 Language Data types and test data – Constants, types, templates 2(2) const integer int_Const := 7; // Normal constant external const boolean bool_Const; // External constant type record Request { // Structured type definition RequestLine requestLine, ReqMessageHeader reqMessageHeader optional, charstring crlf, charstring messageBody optional } template Request Invite := { // template for the Request type requestLine := Request_Line("INVITE"), reqMessageHeader := Req_Mes_Header("INVITE"), crlf := ?, messageBody := omit }

32. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 32 12 October 2005 Language Encoding of Messages – Attributes1(2) o Attributes can be assigned to all kinds of definitions, groups and modules. o Kinds of attributes Encoding information encode – attribute variant – attribute Values are standardized for ASN.1 encoding Presentation information display – attribute Values are standardized for the graphical and tabular presentation format. User-defined extension - attribute Attributes Language Element

33. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 33 12 October 2005 Encoding of Messages – Attributes2(2) group MyPDUs { type record MyPDU1 { … } group MySpecialPDUs { type record MyPDU3 { … } with {extension "MyVerySpecialRule"} type record MyPDU4 { … } } with {extension "MySpecialRule"} } with { display "PDU"; extension "MyRule" } Language

34. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 34 12 October 2005 Table of contents 1. Overall view of TTCN-3 2. TTCN-3 en detail a.Types and values b.Behavior specification 3. Implementation of TTCN-3 4. Presentation formats 5. Final remarks

35. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 35 12 October 2005 Language Specifying test behavior – Alternative behavior 1(2) o … has to be specified whenever test component is ready to take a response from the SUT or a timeout. o … is typically defined by several alternatives, which are evaluated according to their appearance may be guarded can be part of an altstep, which may be called explicitly or activated as default. o … forks the test behavior (the typical tree), but in TTCN-3 alternatives can be joined again after the end of an alternative behavior. o All other cases can be handled in an else branch.

36. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 36 12 October 2005 Language Specifying test behavior – Alternative behavior 2(2) alt { [] L1.receive(MyMessage1) { : // do something } [x>1] L2.receive(MyMessage2) {} [x<=1] L2.receive(MyMessage3) {} [] MyAltstep;// call of a altstep [else] stop// else branch }

37. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 37 12 October 2005 o Shorthand for all alternative permutations All messages must be received, but in any order interleave { [] PCO1.receive(MyMessageOne) {} [] PCO1.receive(MyMessageTwo) {} [] PCO1.receive(MyMessageThree) {} } Specifying test behavior – Interleaved behaviorLanguage

38. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 38 12 October 2005 Table of contents 1. Overall view of TTCN-3 2. TTCN-3 en detail a.Types and values b.Behavior specification 3. Implementation of TTCN-3 4. Presentation formats 5. Final remarks

39. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 39 12 October 2005 Overview – The TTCN-3 test system o TE – TTCN-3 Executable o SA – System Adapter o PA – Platform Adapter o CD – Coder/Decoder o TM – Test Management o CH – Component Handling o SUT – System Under Test ETSI ES 201 873-1: TTCN-3 Core Language ETSI ES 201 873-5: TTCN-3 Runtime Interface (TRI) ETSI ES 201 873-6: TTCN-3 Control Interfaces (TCI)

40. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 40 12 October 2005 Overview – Implementing TTCN-3 Abstract Test Suite compile TE TTCN-3 Executable TTCN-3 Runtime System + SUT Executable Test Suite build

41. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 41 12 October 2005 Table of contents 1. Overall view of TTCN-3 2. TTCN-3 en detail a.Types and values b.Behavior specification 3. Implementation of TTCN-3 4. Presentation formats 5. Final remarks

42. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 42 12 October 2005 TTCN-3 presentation formats – Overall view TTCN-3 User Graphical Format Tabular Format ASN.1 Types & Values Other Types & Values n Other Types & Values 2 TTCN-3 Core Notation Presentation Format n Other Types & Values 3 UML Testing Profile IDL XML C/C++

43. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 43 12 October 2005 The graphical presentation format of TTCN-3 testcase MyTestCase (in boolean internetService,inout integer nrPass) runs on MtcType system TestSystemtype MtcType mtc mPCOtype P1 mCPtype CP map(self:P1, System:mPCO) if (internetservice) var default def := activate (MyDefault()) newInternetPTC() var reportType report Page 1(2)

44. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 44 12 October 2005 sd invalidPIN storeCardData(current) «sut» atm hwe display(Enter PIN) isPinCorrect(invalidPIN) isPinCorrect : false current {readOnly} Integer invalidPIN; { current.isPinCorrect(invalidPIN) == false } isPinCorrect(invalidPIN) display(Invalid PIN) display(Enter PIN again) isPinCorrect : false t1(2.0) t1 {0.. 3} «validationAction» pass U2TP – A test case Data partition Setting arbitrated verdict Stimulus Observation Setting a timer Stopping a timer Duration constraint Function return value

45. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 45 12 October 2005 Table of contents 1. Overall view of TTCN-3 2. TTCN-3 en detail a.Types and values b.Behavior specification 3. Implementation of TTCN-3 4. Presentation formats 5. Final remarks

46. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 46 12 October 2005 Managing TTCN-3 projects – Potential usage 1(2) o Applicability for different test phases Host/target tests System integration and system test User acceptance test o Features required for a test automation solution Test design (low-level, high-level, graphical) Scheduling of test runs Centralized/distributed test runs Log/trace analysis Test case management Support of standards Legend for the table on next slide … feature must be supported in this test phase ( )… feature should be supported fully colored field… feature supported by TTCN-3 hatched colored field… feature partly supported by TTCN-3

47. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 47 12 October 2005 Managing TTCN-3 projects – Potential usage 2(2) Requirement Host Test Target Test System Integr. System Test User Accept. Low-level test design (programming level) ( ) High-level test design (textual) Graphical test design and test result analysis Scheduling of test runs / test resource management ( ) Centralized test execution ( ) Distributed test execution Log / trace file analysis Test case management (including version control) Support of ASN.1 and standardized test suites ( )

48. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 48 12 October 2005 TTCN-3 extensions Work items in standardization o Language extensions mechanisms Packages and profiles o Extended communication mechanisms Broadcast / multicast (edition 3.0.0) Synchronization / coordination (edition 3.0.0) o Real-time extensions Absolute time support Time-constrained operations o Better performance testing support Implicit test configuration Implicit communication Performance measurement

49. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 49 12 October 2005 Current TTCN-3 tool providers o Tool providers Danet DaVinci Communication Open TTCN Telelogic Testing Technologies Strategic Test Solutions o Internal tools used by Nokia Ericsson Motorola o Existing test devices with TTCN-3 support (for telecommunication applications) Alcatel A1100 Navtel InterWatch Nethawk Tektronix G20

50. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 50 12 October 2005 Conclusions o TTCN-3 finds its way into practice o Lots of interest from industry and academia o Mature TTCN-3 standard o Stimulates further research & development New application domains, e.g. automotive Real-time and performance testing Test patterns o Still possibilities to shape the future TTCN-3

51. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 51 12 October 2005 Acknowledgement o Slides are based on a TTCN-3 Tutorial from Grabowski and Ulrich o Prof. Dr. Jens Grabowski Institute for Informatics, University of Göttingen Is in the TTCN-3 business since the beginning o Dr. Andreas Ulrich Is a Principal Engineer at Siemens Corporate Technology Division in München, Germany Member of the ETSI TTCN-3 maintenance group

52. International Telecommunication Union ITU-T Study Group 17, Geneva, 5-14 October 2005 An Introduction toversion 3 Dr. Michael Ebner University Göttingen, Germany ebner@cs.uni-goettingen.de

53. International Telecommunication Union ITU-T Study Group 17, Geneva, 5-14 October 2005 Literature on TTCN-3 Standard documents Overview articles Graphical presentation format TTCN-3 control and runtime interface IDL to TTCN-3 mapping TTCN-3 real-time extensions UML Testing Profile

54. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 54 12 October 2005 Literature on TTCN-31(6) o Standard documents: (can be found on the TTCN-3 homepage: http://www.ttcn3.org/ or http://www.etsi.org/ptcc/ptccttcn3.htm) ES 201 873-1: TTCN-3 Core Language ES 201 873-2: TTCN-3 Tabular Presentation Format (TFT) ES 201 873-3: TTCN-3 Graphical Presentation Format (GFT) ES 201 873-4: TTCN-3 Operational Semantics ES 201 873-5: TTCN-3 Runtime Interface (TRI) ES 201 873-6: TTCN-3 Control Interface (TCI) ES 201 873-7: Using ASN.1 with TTCN-3 ES 201 873-8: Using IDL with TTCN-3 ES 201 873-9: Using XML with TTCN-3 ES 201 873-10: Using C/C++ with TTCN-3 (planned) o Example test suites: See: http://www.etsi.org/ptcc/ptccttcn3.htm E.g., http://www.etsi.org/ptcc/ptccsip_osp.htm

55. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 55 12 October 2005 Literature on TTCN-32(6) o Overview articles Jens Grabowski, Dieter Hogrefe, György Réthy, Ina Schieferdecker, Anthony Wiles, Colin Willcock. An introduction into the testing and test control notation (TTCN-3). Computer Networks, Volume 42, Issue 3, Elsevier, Amsterdam, Juni 2003, 375-403. Jens Grabowski, Anthony Wiles, Colin Willcock, Dieter Hogrefe. On the Design of the new Testing Language TTCN-3. '13th IFIP International Workshop on Testing Communicating Systems' (Testcom 2000), Ottawa, 29.8.2000-1.9.2000, Kluwer Academic Publishers, August 2000. o Graphical presentation format P. Baker, E. Rudolph, I. Schieferdecker. Graphical Test Specification - The Graphical Format of TTCN-3. Proc. of the 10th SDL Forum 2001, Copenhagen, June 2001. E. Rudolph, I. Schieferdecker, J. Grabowski: HyperMSC - a Graphical Representation of TTCN. Proc. of the 2nd Workshop of the SDL Forum, Society on SDL and MSC, Grenoble, June 2000.

56. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 56 12 October 2005 Literature on TTCN-33(6) o TTCN-3 control and runtime interface S. Schulz, T. Vassiliou-Gioles. Implementation of TTCN-3 Test Systems using the TRI. Testing Internet Technologies and Services - The IFIP 14th International Conference on Testing of Communicating Systems March, 19th - 22nd, 2002, Berlin, Kluwer Academic Publishers, March 2002. I. Schieferdecker, T. Vassiliou-Gioles. Realizing distributed TTCN-3 test systems with TCI. IFIP 15th Intern. Conf. on Testing Communicating Systems - TestCom 2003, Cannes, France, May 2003. o IDL to TTCN-3 mapping M. Ebner, A. Yin, M. Li. A Definition and Utilisation of OMG IDL to TTCN-3 Mappings. TestCom 2002: Testing Internet Technologies and Services - The IFIP 14th International Conference on Testing of Communicating Systems March, 19th - 22nd, 2002, Berlin, Kluwer Academic Publishers, March 2002. o XML to TTCN-3 mapping I. Schieferdecker, B. Stepien. Automated Testing of XML/SOAP based Web Services. Proceedings of the 13. Fachkonferenz der Gesellschaft für Informatik (GI) Fachgruppe "Kommunikation in verteilten Systemen" (KiVS), Leipzig (Germnay), Febr. 26th-28th, 2003.

57. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 57 12 October 2005 Literature on TTCN-34(6) o TTCN-3 real-time extensions Zhen Ru Dai, Jens Grabowski, Helmut Neukirchen. Timed TTCN- 3 - A Real-Time Extension for TTCN-3. TestCom 2002: Testing Internet Technologies and Services -- The IFIP 14th International Conference on Testing of Communicating Systems March, 19th - 22nd, 2002, Berlin, Kluwer Academic Publishers, March 2002. Zhen Ru Dai, Jens Grabowski, Helmut Neukirchen. TimedTTCN-3 Based Graphical Real-Time Test Specification. Testing of Communicating Systems (Editors: D. Hogrefe, A. Wiles). Proceedings of the 15th IFIP International Conference on Testing of Communicating Systems, Sophia Antipolis, France, May 2003. LNCS 2644, Springer, May 2003. Helmut Neukirchen, Zhen Ru Dai, Jens Grabowski. Communication Patterns for Expressing Real-Time Requirements Using MSC and their Application to Testing. Testing of Communicating Systems. Proceedings of the 16th IFIP International Conference on Testing of Communicating Systems, Oxford, UK, March 2004. LNCS 2978, Springer, March 2004.

58. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 58 12 October 2005 Literature on TTCN-35(6) o UML Testing Profile Online Resources: http://www.fokus.gmd.de/u2tp/ U2TP consortium. UML 2.0 Testing Profile Specification. OMG Adopted Specification ptc/03-08-03. (for download see: http://www.fokus.gmd.de/u2tp/) Zhen Ru Dai, Jens Grabowski, Helmut Neukirchen, Holger Pals. From Design to Test with UML - Applied to a Roaming Algorithm for Bluetooth Devices. Testing of Communicating Systems. Proceedings of the 16th IFIP International Conference on Testing of Communicating Systems (TestCom2004), Oxford, United Kingdom, March 2004. LNCS 2978, Springer, March 2004. Ina Schieferdecker, Zhen Ru Dai, Jens Grabowski, Axel Rennoch. The UML 2.0 Testing Profile and its Relation to TTCN-3. Testing of Communicating Systems (Editors: D. Hogrefe, A. Wiles). Proceedings of the 15th IFIP International Conference on Testing of Communicating Systems (TestCom2003), Sophia Antipolis, France, May 2003. LNCS 2644, Springer, May 2003, pp. 79-94.

59. ITU-T ITU-T Study Group 17, Geneva, 5-14 October 2005 59 12 October 2005 Literature on TTCN-36(6) o UML Testing Profile (cont.) Paul Baker, Zhen Ru Dai, Jens Grabowski, Øystein Haugen, Serge Lucio, Eric Samuelsson, Ina Schieferdecker, Clay Williams. The UML Testing Profile. Proceedings of the 'Conference on Quality Engineering in Software Technology 2004' (CONQUEST 2004) in Nuremberg (Germany), September 22-24, 2004. o Further resources More can be found in the proceedings of the TestCom conferences and on the homepages of the TTCN-3 team members (e.g., I. Schieferdecker and J. Grabowski) and the TTCN-3 tool providers.