1 / 7

I NTERVA L Extensions to MSC (& TTCN)

I NTERVA L Extensions to MSC (& TTCN). Helmut Neukirchen Institute for Telematics (ITM) University of Lübeck. Status quo: MSC2000. MSC2000 allows to attach quantified time bounds to MSC events. E.g.:. MSC2000 is to a certain extent usable to describe Real-Time requirements….

qamra
Download Presentation

I NTERVA L Extensions to MSC (& TTCN)

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. INTERVALExtensions to MSC (& TTCN) Helmut Neukirchen Institute for Telematics (ITM) University of Lübeck

  2. Status quo: MSC2000 • MSC2000 allows to attach quantified time bounds to MSC events. E.g.: • MSC2000 is to a certain extent usable to describe Real-Time requirements… • but there are still some problems. INTERVAL Extensions to MSC (& TTCN)

  3. Obvious corrections to MSC2000 • Rework grammar of MSC2000: • concrete textual and concrete graphical grammar for constraining absolute time points are contradictory (upper/lower bounds vs. single time points only) • the time marks “@” and “&” are no lexical symbols • other minor errors in the grammar... INTERVAL Extensions to MSC (& TTCN)

  4. Isochronicity • Periodic occurrence of events with a fixed frequency INTERVAL Extensions to MSC (& TTCN)

  5. Soft RT/probabilistic requirements: • “At least 90% of the messages must arrive within 3ms after being sent.” Extension of the MSC2000 guard concept: INTERVAL Extensions to MSC (& TTCN)

  6. Status quo: TTCN-2/3 • No real support for testing RT requirements: • Time is just reflected by functional timers (e.g. for testing long term timeouts) • Functional timers might be “misused” for testing non-functional/RT requirements: • not very elegant • time critical events (e.g. receive/timeout) might get summarized into one snapshot • order of time critical events is not determinable INTERVAL Extensions to MSC (& TTCN)

  7. RT extension to TTCN • Real-time extensions are still under study: • Extensions will be based on TTCN-3 • Snapshot semantics will be refined to allow deterministic real-time testing • Support for distributed real-time testing/clock synchronization of parallel test components • CATG will mainly be based on RT requirements specified using (extended) MSC2000 INTERVAL Extensions to MSC (& TTCN)

More Related