home
CfP (PDF)
Case Studies
Submissions
Program
Committee
History
Other
Links:
-ICSE Home |
Case
Studies
To attract
submissions combining fundamental approaches with strong
application-orientation, we encourage to use your own or one of the
following provided case studies to evaluate your approach:
Case Study 1: Shuttle
System
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.
As
case study a simplified version of the system is considered. A short
overview about the overall
system, defining the constraints and general layout of the system as
well as a detailed description of the shuttle
behavior within the system by a set of scenarios are available here. More
details and an exeutable simulation environment are available on the
case study homepage http://www.upb.de/cs/ag-schaefer/CaseStudies/ShuttleSystem/.
Case
Study 2: Center TRACON Automation System
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.
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.
Contact: scesm04@upb.de |
