TTCN-3 Bibliography
TTCN-3 Bibliography |
|
 |
 |
 |
|
Rezzano, R. 2008, June 3–6, TTCN3 tools operatibility between Java y C++ platforms. Unpublished paper presented at ETSI TTCN-3 User Conference 2008, Madrid (Spain). Added by: Deleted user (22/08/2008, 10:49) |
| Resource type: Conference Paper BibTeX citation key: Rezzano View all bibliographic details  |
Categories: General Creators: Rezzano Publisher: MTP, ETSI (Madrid (Spain)) Collection: ETSI TTCN-3 User Conference 2008 |
Views: 41/4101
|
| Abstract |
|
The TTCN-3 language addresses the definition of Abstract Test Suites (ATS) and does not address directly the definition of platform specific low level details. The TTCN-3 ATS is combined with platform specific routines in order to produce Executable Test Suites (ETS). By doing this, TTCN-3 language keeps abstraction and removes from the language itself handling of platform specific details, making the language abstract and platform independent. Ultimately, executables have to be built and run against an implementation. Doing so requires to extend certain operations using Platform Languages. TTCN-3 standardizes two platform language mappings and interfaces: C/C++ and Java Languages. As a consequence of this, the industry has developed disjoint efforts to create tools based on these platforms. The result is that two families of compilers and tools one for C/C++ and other for Java. For this reason different communities are unable to reuse easily the libraries or tools developed by the other. The standard itself does not impose that tools must be either Java or C based, this de-facto situation is not required by the standard itself. This work aims to the experimental extension of a TTCN-3 compiler capable of integrating Libraries and Tools from both platforms natively, making the tools that test developers need available , despite of it is platform availability, in a more transparently and easy way. This new interpretation of the standard will allow the reuse of tools and libraries between different platforms and suppliers and promote the effort and partnering to its construction in different and new fields. It will allow the users of the tool to use the best services and solutions provided by each platform instead of having to choose beforehand the platform of a project as a whole. With this objective in mind, we decided to investigate options for platform interoperability and select JNI alternative. It results to be the more useful for our goals and a validated interoperability solution. The necessary specification for mapping libraries and when this should cross platform shall be external, will be provided by the same files that contain other interface specifications. The result of this work will be a prototype to permit proofing that we can have a TTCN-3 compiler and its corresponding tools where the developers transparently could use libraries and components from the more convenient platform, without any changes in the language programming itself. They will not take care about which is the API's base platform language else how it help to design and implement the Test Cases in the specific field. Added by: Deleted user Last edited by: Deleted user |