![]() |
![]() |
![]() |
![]() |
![]() |
TTCN Access and the TTCN Analyzer
All the components and definitions mentioned in Basic Compiling Theory, together build up the basics for compiling theory. As mentioned, TTCN Access is a C++ application programmers interface towards a test suite written in TTCN. It reveals the content of the test suite in a high level abstraction and allows various users to access the content in a read-only manner.
This section will once again mention these components, but this time put them in the context of the TTCN Suite and the functionality that it provides, thereby explaining the relationship between the TTCN Suite and TTCN Access.
Lexical Analysis
The lexical analysis in the TTCN Suite is done in two phases, depending on the format of the abstract test suite.
- If the source code is in MP format, a basic lexical analysis is done at the import stage, verifying that the imported test suite is written in correct MP format. A full lexical analysis is done when using the Analyzer. The complete lexical analysis is the first phase in the analysis.
- For more information see Importing a TTCN-MP Document.
- If the source code is written directly into the TTCN Suite via one of the editors, a lexical analysis is done by using the Analyzer as mentioned above.
- For more information see Analyzing TTCN Documents (on UNIX) and Analyzing TTCN Documents (in Windows).
Syntax Analysis
The syntax analysis is done when executing the Analyzer and it is done in the second phase. This second phase also contains a semantic analysis of the test suite, all in order to verify that the test suite complies with the standardized notations for TTCN and ASN.1.
Parse Tree
The last phase of the analysis is to generate a parse tree. This can only be done if the lexical and syntax analysis have been successfully completed.
Symbol Table Management
During execution of an TTCN Access application the symbol table is accessible at any time.
http://www.ibm.com/rational |
![]() |
![]() |
![]() |
![]() |