TASS: Timing Analyzer of Scenario-Based Specifications
Introduction Download Case Study 1 Case Study 2

Introduction

Overview  

TASS (Timing Analyzer of Scenario-based Specifications) is implemented for timing analysis of Scenario-Based Specifications (SBSs). Scenario-based specifications such as UML interaction models offer an intuitive and visual way of describing design requirements. Such specifications can describe concrete interactions among communicating entities and therefore are playing an increasingly important role in the design of software systems. The models analyzed by TASS consist of UML sequence diagrams (SDs) and UML2.0 interaction overview diagrams (IODs). We use the UML sequence diagram to describe exactly one scenario without alternatives and loops, and the UML2.0 interaction overview diagram which combines references to SDs to describe sequential, iterating and non-deterministic executions of SDs.

The following are some of the highlights of the tool: (Detailed technical background can be found in our recent publications)

  • We introduce general and expressive timing constriants in SBSs;
  • TASS can be used to solve three timing analysis problems: reachability analysis, constraint conformance analysis and bounded delay analysis;
  • TASS provides a path-oriented timing analyzer to check one single path, a bounded timing analyzer to check the whole SBSs in a given threshold, and a powerful loop-unlimited timing analyzer to check loop-unlimited SBSs.

 

Publications

 

Download

TASS is available now! You may download TASS via the download page. We have implemented two versions. One is an Eclipse plugin which is an integrated environment for modelling and analysis. The other is a Java standalone application which reads models generated by Rational Rose. We also provide details of two well-known examples which are the automatic teller machine (ATM) system and the global system for mobile communication (GSM). They can be found in the case study pages.

 

 


©2008 SEG CS NJU IntroductionDownloadCase Study 1Case Study 2