Main page Topics of the seminar Case study Program (TBA)

Themes and Goals The goal of this seminar is to understand scenario notations not merely as mathematical objects, but to foster a “look-and-feel” approach in the assessment of these notations. We will propose one or more case studies that participants in this seminar are requested to apply their particular approaches to. The objective of these case studies is to illustrate strengths and weaknesses of certain notations, analysis methods and tools without aiming at a  competitive comparison. The case studies are expected to reveal ways how different approaches could complement each other. To further emphasise the “look-and-feel” approach it is intended that participants will present CASE tools during the seminar and that working with these tools will be part of the seminar program.   The objective is to accomodate all the different uses that there are for the analysis of scenario description methods: model checking,  syntactic analysis,  timing analysis,  synthesis,  implied behavior,  implementability, etc. The case study should provide a common ground in which it would be able to see how the different scenario-based approaches complement each other. An intended outcome is a set of scenario-related techiniques that can be applied in a SE project. More specific goals for each example system will be posted later. Example systems We aim at examining two example systems from different domains to get a good understanding of the applicability of the different approaches: (1) Weather Record System (NASA) and Automonous Shuttle Transport System (University of Paderborn) CTAS (Center TRACON Automation System) is a set of tools designed to help air traffic controllers manage the increasingly complex air traffic flows at large airports. The project began in 1991 and prototypes are now deployed at Denver and Dallas/Fort Worth airports. Extensions to the core CTAS system are constantly being integrated and incorporate the latest developments from research into air traffic control systems. CTAS has been  used for a case study in the 2nd International Workshop on Scenarios and State Machines: Models, Algorithms, and Tools (May 2003). See the case study description of the workshop for more information. For the latest information on CTAS, see the official CTAS web page, http://ctas.arc.nasa.gov. These web pages contain an overview of the system as well as descriptions of the various processes that make up CTAS, e.g., TS (Trajectory Synthesizer), RA (Route Analyzer), CM (Communications Manager), PGUI (Planview Graphical User Interface) etc. The CM is the communications manager and most processes (e.g., RA, PGUI) are clients to CM, communicating with CM through sockets.  * The requirements document is available in pdf, see Requirements In the context of a series of new research projects at the University of Paderborn ("New rail-technology Paderborn", Graduate School of Dynamic Intelligent Systems, Collaborative Research Center SFB 614) a new rail-based transport system is being developed. The system is intended to enable individual traffic of people and goods, which today is mainly conducted by cars and trucks, by autonomously acting shuttles on rail. This autonomy shall eliminate the disadvantages of modern trains concerning individual transport. * The case study description is available in pdf, see Autonomous Shuttle Transport System . A more detailed description of the case study is available at http://www.uni-paderborn.de/cs/ag-schaefer/CaseStudies/ShuttleSystem/. Note! In this case study the participants are suggested to focus on the shuttle control software. Work on case studies First, the participants should give a very brief introduction to their appraoch and discuss strengths and weaknesses of it. During the case study work sessions (which takes few dats) they should find at least one other approach that they feel is related to their own. They should prepare couple of slides to describe how their approach relates/complements this other approach and sketch how the collaboration could be carried out. Participants should prepare a couple of slides to describe how their approach relates/complements this other approach and sketch how the collaboration could be carried out. All participants are encouraged to take part in the case study. As a preparation, the participants are recommended to: learn the requirements for the example systems (see above) download the materail avaiable  initially construct the scenarios (according to the notation expected by their appraoch) All suggestions for such systems are most welcome (email: Tarja Systä tsysta@cs.tut.fi)  We would like to invite all participants interested to collaborate with us in preparing the case study. All other suggestions are also weocome  (contact: Tarja Systä, tsysta@cs.tut.fi and/or Francis Bordeleau francis@scs.carleton.ca ).  The organizers like to thank Michelle Eshow, John Robinson, Richard Kwan, and Jon Whittle for the Weather Record System case study and Holger Giese, Wilhelm Schäfer, and Albert Zuendorf for the  Automonous Shuttle Transport System case study.