An Intuitive TTCN-3 Data Presentation Format

1
An Intuitive TTCN-3 Data Presentation Format

• Roland Gecse and Sarolta Dibuz
• Ericsson Hungary, 1037 Budapest Laborc u. 1.
• Roland.Gecse, Sarolta.Dibuz_at_eth.ericsson.se

2
Motivation

• Find an intuitive graphical representation format
  for abstract data (excluding OO)
• Abstract data a set of simple types with given
  value domain and rules for constructing complex
  types (e.g. ASN.1, TTCN-3)
• Intuitive Keep it super simple (e.g. introduce
  a minimal set of symbols)

3
Goals

• Facilitate test suite data part development
• Help testers getting the overview of type
  definitions hierarchy
• Provide a graphical tool for test data
  development (e.g. contants, templates), which are
  significant parts of Test Suites
• Translate between different formal data
  description methods (e.g. TTCN, TTCN-3 and ASN.1)

4
Conceptual architecture

• Basic NotationGraphical representation of
  common language concepts
• ProfilesLanguage-specific features
• XMLPotential common data exchange format
  between different implementations

TTCN-3 Profile
ASN.1 Profile
Basic Notation
5
Data Presentation Format

• Basic Notation TTCN-3 profile
• Supports data part Type definitions, constant
  declarations, signature declarations, template
  declarations, port type definitions, component
  type definitions, module parameter declarations
• Dynamic parts out of scope functions, altsteps,
  testcases, control
• 7 disjunct parts (25)
• Separated containers for all supported TTCN-3
  constructions
• Resolves context sensitivity of graphical
  representations(e.g. specific value template
  value template looks equal to a constant, but
  these are in different parts!)

6
Simple Type and Value Representation
Simple-type-spec
Field-identifier
with-attributes
value

• Simple-type-spec simple-type-id
  base-simple-type-id
  subtype-spec
• 4 forms of simple-type-spec simple type
  reference, simple type alias, subtype definition
  and inline subtype definition
• 3 context specific attributes Field-identifier,
  value, with-attributes

7
Simple type reference
A
field_a

• TTCN-3 equivalenttype ltrecordgt R
  A field_a,

8
Simple Type Alias
C charstring

• TTCN-3 equivalent
• type charstring C

9
Simple Type Subtype definition
I integer(1..10)

• TTCN-3 equivalenttype integer I (1..10)

10
Simple Type Inline subtype definition
charstring(abc)
field_abc

• TTCN-3 equivalenttype ltrecordgt R
  charstring field_abc (abc),

11
Field identifier attribute
integer
INT_field
428

• Different meaning in different contexts
• Simple value notation (together with the value
  attribute)identifier of that valueltconstgt
  integer INT_field 428

12
Value attribute

• Simple type
• Literal, e.g. true, 4, 10110B, Hello!
• Value reference

Value attribute
13
With-attributes
BER_INT integer
encode BER1997
with

• Location of TTCN-3 with statements attributes
  w/o braces
• type integer BER_INT with encode BER1997

14
Building Structured Types from Simple Types
alternatives

• Model
• ordering, choice
• Consider an imaginary plane
• Vertical axis ordering
• Horizontal axis alternatives
• repetition
• quantor
• grouping of elements
• structured type header attributes

Field-id
quantor
Structured-type-id
with-attributes
value
A
B
C
ordering
15
Structured Type and Value Representation

• Structured type reference has the same graphical
  representation than simple type reference
• Context specific attributes Field-identifier,
  value, with-attributes and quantor

16
Element type list

• Determines structured type content
• Graphical representation depends on the format of
  constructed type

• Record type rectangles of neighbouring elements
  have joint edges along vertical axis

• Set type rectangles of neighbouring elements are
  encircled and have disjoint edges

• Union type rectangles of alternative elements
  have joint edges along the horizontal axis

17
Optional elements

• marked with dotted border

Elements B and C are optional
18
Field identifier attribute (2)
Field identifier in structured type element

• Structured type definition Field identifier is
  used to refer to a structured type element (e.g.
  a field of a record type)type record R
  charstring host, integer port

19
Value attribute

• Structured type header
• Empty all values MUST be provided in elements
  value attribute
• Structured value reference get the value of each
  element by ref.
• Both Reference AND some elements values
  presentelements values modify the referred
  value

20
The quantor

• Used to express set-of and record-of
  constructions
• Includes length restriction subtype
• type set length(1..9) of A SetOfType
• type record of B RecordOfType

quantor
21
TTCN-3 specific constructions

• These are unknown to the Basic Notation but
  belong to the TTCN-3 Profile (DPF)
• Signature declaration
• Port type definition
• Component type definition
• Template declaration
• Module parameter declaration

22
Signature
Exception
Return type
Parameter list
Parameter type
Parameter name
In, out, inout
23
Port type
Port type identifier
message, procedure, mixed
direction
Message/ signature type or all
24
Component type
Component identifier
Port decl.
Initial value
Component variable
Component timer
25
Template
parameter m
Literal
Formal parameters
Omit value
26
Implementation

• Graphical front-end for data part development
• Display partscontents in separate windows
• Create and edit language entities incl. drag
  drop features
• Support overview of hierarchy (expand, collapse)
• Resolve references on click
• Create constants and templates from types and
  fill-in values
• Syntactical/semantical check of module
• Import/export module (w/o touching irrelevant
  parts)

27
Example SIP RequestLine (view by reference)
28
Example Embedded view
Expand type SipUrl
Expand GenericParam_List
29
Conclusion

• Basic Notation complete
• TTCN-3 profile ready (waiting for feedback)
• Prototype implementation working
• Positive feedback from testers
• Productification, case study
• ASN.1 profile design started

30
Thank you for your attention!