1 / 6

Tplan Graphical Notation

Tplan Graphical Notation. Stephan Schulz. History. STF 346 (IMS Network Conformance ATS) developed test purposes in textual TPLan TISPAN6 (Telekom Austria & Deutsche Telekom) review test purposes and claims “test purpose [syntax] is not readable”

landonm
Download Presentation

Tplan Graphical Notation

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. Tplan Graphical Notation Stephan Schulz

  2. History • STF 346 (IMS Network Conformance ATS) developed test purposes in textual TPLan • TISPAN6 (Telekom Austria & Deutsche Telekom) review test purposes and claims “test purpose [syntax] is not readable” • STF 346 (FOKUS) makes a graphical/tabular proposal which is accepted by TISPAN6 • Included development of a Java prototype tool (oogenie) which is able to generate an open office document from a specific style of textual TPLan test purposes (some manual work is still needed) • Textual notation remains reference and is attached in electronic annex • Same notation is the also used in INT IMS core network interoperability test specifications • Here maintenance has been an issue, i.e., sometimes only graphical notation is updated but textual is neglected

  3. About the format • Objective was to find a format which is more MSC or GFT like and “reasonably easy” to generate from textual TPs • Avoid “programming like feel”, i.e., no curly brackets or underscores • Defined a simple mapping basic TPLan keywords into graphical symbols • Required certain “style” of Tplan writing • Example: specify stimuli and response always starting with “IUT sends” or “IUT receives”

  4. An example

  5. Another example

  6. Open Issues • For some time now there has been a request to discuss at MTS level how to proceed with this • Extend TPLan standard to include a graphical format – yes or no? • Standardize this graphical format? Or another? • What needs to be taken into consideration is that the trigger for this has been another ETSI TC! • A general resistance in edithelp towards tabular or graphical specification of main standard text • This is not a problem when we talk about annexes • So far issues have been mainly encountered with test descriptions (see IMS NNI IOT TDs)

More Related