Suggestions for TDL Graphical
Symbols
Package
packagename
Comment
text
Annotation Type, Annotation
action actionname
body
action
body
actionref actionname
text
actionname
Question: where to define actions?
[ key ]
text
Configuration elements
• Gate instance
or
name:type
name:type
name:type
name:type
SUT/TESTER
name:type
gate1:GT1
comp1:CT1
SUT
• Component instance
with gates
gate2:GT2
• Example
TestConfiguration
• Problem: type definitions must be given
somewhere
• Proposed: divide the canvas into definitions
and test configuration parts
Gate type, Gate instance
• Gate type
or
typename
interaction messagelist
or
name:type
name:type
• I know, not the best
• Gate instance
Component type – new MM
type
typename
timerlist
name:type
name:type
name:type
typename
timerlist
name:type
name:type
typename
timers timerlist
name:type
• Component type with
gate and timer
definitions
ComponentInstanceRole
SUT|TESTER
• Component instance
role
Component instance – new MM
name : type
name
name
name : type
SUT|TESTER
name
name
• Component instance
Connection
[ name ]
Configuration - new MM
Test Configuration
ExampleConfig
comp1:CT1
SUT
gate1
gate1
SIPconnection
gate2
gate2
CONTROLconnection
comp2:CT1
TESTER
• [ ] : optional name
Test Description
•
Test Description
name (params)
Test Objective [ name ]
Description:
Reference:
Configuration: name
•
Optionally: not only the configuration
reference, but the configuration specification
itself
The headers of the component/gate lifelines
shall be indicated in the behaviour
CompoundBehaviour of the TestDescription
– The component headers are not part of
the “general” CombinedBehaviours,
therefore it is adviseable to (re)introduce
a special behaviour block in the metamodel instead of a simple
CompoundBehaviour
– Question: Shall we introduce the notion
of lifeline into the meta-model?
Behaviour of TestDescription
Comp1
Comp1
G1
G2
• Left: all gates of
the component
(thick lifeline)
• Right: gates
individually
(thin lifelines,
gate symbols
on top)
Single Combined Behaviour
type
[ [ guard ] ]
type
[ [ guard ] ]
exceptional
type
Single Combined Behaviour Compound, Optional
compound
[ [ guard ] ]
optional
[ [ guard ] ]
compound
[ [ guard ] ]
optional
[ [ guard ] ]
Single Combined Behaviour - loops
boundedLoop
unboundedLoop
Iteration: value
unboundedLoop
[ [ guard ] ]
[ [ guard ] ]
boundedLoop
Iteration: value
Multiple Combined Behaviour
type
type
•
•
[ [ guard ] ]
[ [ guard ] ]
[ [ guard ] ]
[ [ guard ] ]
exceptional
type
type: alt, compound,
parallel, etc.
Right side version
preferable (blocks
are not separate
objects, they are
integrated into
CombinedBehaviour
Multiple Combined Behaviour - alt
alt
alt
[ [ guard ] ]
[ [ guard ] ]
[ [ guard ] ]
[ [ guard ] ]
Multiple Combined Behaviour Conditional
conditional
conditional
[ guard ]
[ guard ]
[ [ guard ] ]
[ [ guard ] ]
Multiple Combined Behaviour Parallel
parallel
parallel
Atomic Behaviour
break
stop
Can be mixed up
with timer stop
pass | fail | inconc
pass | fail | inconc
Atomic Behaviour - Actions
action actionname
body
action
body
actionref actionname
actionname
Question: where to define actions?
Test Description Reference
ref calledTD
( params )
ref calledTD ( params )
calledTD ( params )
Exceptional Behaviour
type
type
Exceptional Behaviour – Default,
Interrupt
default
default
interrupt
optional
interrupt
Periodic Behaviour
periodic
period: time
periodic
period: time
Interactions
• Point-to-point
• Point-to-multipoint
(broadcast)
– Ordering of
receiving???
Timer Operations – Start, Stop,
Timeout
timername (start value)
timername (start value)
timername
timername
timername
timername
timername
timername
Time Operations
• Wait
or
5s
5s
time
• Quiescence
or
5s
5s
time