1 / 31

Suggestions for TDL Graphical Symbols

This package provides suggestions for defining actions and test configurations in TDL using graphical symbols. It includes suggestions for gate, component, and timer definitions, as well as interaction messages and behavior descriptions.

milesr
Download Presentation

Suggestions for TDL Graphical Symbols

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Suggestions for TDL Graphical Symbols

  2. Package packagename

  3. Comment text

  4. Annotation Type, Annotation actionactionname action text body body actionrefactionname actionname Question: where to define actions? [ key ] text

  5. Configuration elements • Gate instance • Component instance with gates • Example or name:type name:type name:type name:type SUT/TESTER name:type gate1:GT1 comp1:CT1 SUT gate2:GT2

  6. TestConfiguration • Problem: type definitions must be given somewhere • Proposed: divide the canvas into definitions and test configuration parts

  7. Gate type, Gate instance • Gate type • I know, not the best • Gate instance or typenameinteraction messagelist or name:type name:type

  8. Component type – new MM name:type type • Component type with gate and timer definitions typename name:type timerlist name:type name:type typename typename name:type name:type timerlist timers timerlist

  9. ComponentInstanceRole • Component instance role SUT|TESTER

  10. Component instance – new MM • Component instance name name name : type name : type SUT|TESTER name name

  11. Connection [ name ]

  12. Configuration - new MM Test Configuration ExampleConfig • [ ] : optional name gate1 SIPconnection comp1:CT1 SUT gate2 CONTROLconnection gate1 comp2:CT1 TESTER gate2

  13. Test Description • 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 meta-model instead of a simple CompoundBehaviour • Question: Shall we introduce the notion of lifeline into the meta-model? Test Description name (params) Test Objective [ name ] Description: Reference: Configuration: name

  14. Behaviour of TestDescription • Left: all gates of the component (thick lifeline) • Right: gates individually (thin lifelines, gate symbols on top) Comp1 Comp1 G1 G2

  15. Single Combined Behaviour type type [ [ guard ] ] [ [ guard ] ] exceptional type

  16. Single Combined Behaviour - Compound, Optional compound compound [ [ guard ] ] [ [ guard ] ] optional optional optional [ [ guard ] ] [ [ guard ] ]

  17. Single Combined Behaviour - loops boundedLoop boundedLoop Iteration: value Iteration:value unboundedLoop unboundedLoop [ [ guard ] ] [ [ guard ] ]

  18. Multiple Combined Behaviour • type: alt, compound, parallel, etc. • Right side version preferable (blocks are not separate objects, they are integrated into CombinedBehaviour type type [ [ guard ] ] [ [ guard ] ] [ [ guard ] ] [ [ guard ] ] exceptional type

  19. Multiple Combined Behaviour - alt alt alt [ [ guard ] ] [ [ guard ] ] [ [ guard ] ] [ [ guard ] ]

  20. Multiple Combined Behaviour - Conditional conditional conditional [ guard ] [ guard ] [ [ guard ] ] [ [ guard ] ]

  21. Multiple Combined Behaviour - Parallel parallel parallel

  22. Atomic Behaviour break stop Can be mixed up with timer stop pass | fail | inconc pass | fail | inconc

  23. Atomic Behaviour - Actions actionactionname action body body actionrefactionname actionname Question: where to define actions?

  24. Test Description Reference refcalledTD(params) refcalledTD(params) calledTD(params)

  25. Exceptional Behaviour type type

  26. Exceptional Behaviour – Default, Interrupt default default optional interrupt interrupt

  27. Periodic Behaviour periodic periodic period: time period: time

  28. Interactions • Point-to-point • Point-to-multipoint (broadcast) • Ordering of receiving???

  29. Timer Operations – Start, Stop, Timeout timername (start value) timername(start value) timername timername timername timername timername timername

  30. Time Operations • Wait • Quiescence or time 5s 5s or time 5s 5s

More Related