TTCN-3 Bibliography

WIKINDX Resources

U. Grude, F. W. Schröer, and P. Enskonatus, "TTCN-3 for .NET," ETSI TTCN-3 User Conference 2006: Berlin (Germany), May 31-June 2, 2006. 
Added by: Deleted user (09 Jul 2008 11:22:44 Europe/Berlin)   Last edited by: Deleted user (13 Aug 2008 14:25:12 Europe/Berlin)
Resource type: Conference Paper
BibTeX citation key: Grudea
View all bibliographic details
Categories: General
Creators: Enskonatus, Grude, Schröer
Publisher: Fraunhofer FOKUS, ETSI (Berlin (Germany))
Collection: ETSI TTCN-3 User Conference 2006
Views: 7/2385
Views index: %
Popularity index: 31.75%
We present a compiler and an environment that brings TTCN-3 to the ECMA/ISO Common Language Infrastructure as implemented by Microsoft .NET and Novell Mono.

After giving a short overview on .NET we discuss the architecture of the compiler and the tools that were used to generate it from a high level specification. The compiler has been tested extensively using a toolkit especially designed for compiler validation. The compiler supports the full TTCN-3 language as defined by edition 2 of the ETSI standard. Support for edition 3 is in preparation.

Adapters and Codecs can be written by the user in any .NET language using a .NET binding of the TRI and TCI APIs. The system not only supports the implementation of test systems but is also intended for modelling reactive systems. In an early project phase the user can run tests against a model written in TTCN-3. In a later phase the model can be replaced by the actual System Under Test without the need to adapt the test specification. Models may also be written in other notations such as Modellica.

A TTCN-3 application may run on a single processor or distributed on several nodes. We discuss the component connection model that underlies this approach.
Added by: Deleted user  Last edited by: Deleted user
wikindx 5.2.1 ©2017 | Total resources: 348 | Username: -- | Bibliography: WIKINDX Master Bibliography | Style: Institute of Electrical and Electronics Engineers (IEEE) | Database queries: 49 | DB execution: 0.04443 secs | Script execution: 0.05897 secs