TUB-TCI An Architecture for Dynamic Deployment of Test Components

  • Markus Lepper
  • Baltasar Trancón y Widemann
  • Jacob Wieland
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 2644)


The test definition language TTCN-3 is currently under standardization by ETSI/ITU-T. Its intended field of application is testing and performance measurement of communication hard- and software. TTCN-3 does include mechanisms for specifying remote hardware access and for distributed execution of testing code components.

But for running compiled TTCN-3 code distributed onto distinct nodes of different vendors an architecture is needed which offers standardized means for dynamic, program controlled deployment, configuration and status inquiry of active and passive resources.

TUB-TCI is a proposal for such an architecture, characterized by (1) totally generic definition of component classes, (2) coexistence of standardized (XML based) and specialized (high-speed) communication channels, (3) a model-based, strictly formal definition given in Z and (4) a simple, minimized but powerful execution model.

Especially because of the integration of non-standard, high speed data channels TUB-TCI seems applicable for dynamical routing of real-time signals in general, beyond the field of test execution.


Dynamic Deployment Conformance Testing XML based configuration 


  1. 1.
    Mohammed Bennattou, Leo Cacciari, Régis Pasini, and Omar Rafiq. Principles and tools for testing open distributed systems. In IFIP TC 12th International Workshop on Testing Communicating Systems. Kluwer Academic Publishers, 1999.Google Scholar
  2. 2.
    Generic Compiler/Interpreter Interface. INTOOL CGI/NPL 038 (v.2.2), decenber 1996.Google Scholar
  3. 3.
    Markus Lepper. TUB-TCI — A Generic Architecture for Distributed Test Execution. Technical report, Berlin, September 2002.
  4. 4.
    TTCN-3 Control Interface (TCI). Technical report, ETSI ES 201 837-5, to appear 2003.Google Scholar
  5. 5.
    Maria Törö. Decision on tester configuration for multiparty testing. In IFIP TC5 12th International Workshop on Testing Communicating Sysytems. Kluwer Academic Publishers, 1999.Google Scholar
  6. 6.
    TRI — the TTCN-3 Runtime Interface. Technical report. ETSI TR 102 043 V.1.1.1, Sofia-Antipolis, April 2002.Google Scholar
  7. 7.
    Test synchronization Protocol 1 Plus (TSP1+) Specification. Technical report, ETSI TC-MTS, ETSI Standard ES 201 770, Sofia-Antipolis, Jan 1997.Google Scholar
  8. 8.
    Methods for Testing and Specification (MTS); Part 1: TTCN-3 Core Language. Technical report. ETSI ES 201 837-1 (V1.0.11), Sofia-Antipolis, May 2001.Google Scholar
  9. 9.
    Andreas Ulrich and Hartmut König. Architectures for testing distributed systems. In IFIP TC5 12th International Workshop on Testing Communicating Systems. Kluwer Academic Publishers, 1999Google Scholar

Copyright information

© IFIP 2003

Authors and Affiliations

  • Markus Lepper
    • 1
  • Baltasar Trancón y Widemann
    • 1
  • Jacob Wieland
    • 1
  1. 1.Institut f:ur Softwaretechnik und Theoretische Informatik, Sekr. FR 5-13Technische Universität Berlin, Fakultät IV, ÜBBBerlin

Personalised recommendations