18-841/17-654 Team 7 Project Page

Team 7 Project Page

17-654: Analysis of Software Artifacts
18-841: Dependability Analysis of Middleware

Updates:

January 31, 2003 Interfaces
February 9, 2003 End to End Test
February 16, 2003 Baseline Application.
February 28, 2003 Basic failover.
March 14, 2003 Fault Tolerant Baseline. Instructions are here. Source codes package is here.
April 4, 2003 Graphs for Real-time measurements are here. !

Team Members:

Greg Bylenok gbylenok@cs.cmu.edu
Nishant Sinha nishants@ece.cmu.edu
Deepti Srivastava dsrivast@andrew.cmu.edu
Dehua Zhang zhangdh@cs.cmu.edu
Oksana Schubert okzay@cs.cmu.edu

Team Roles:

Testing -Person primarily responsible for deweloping and coordinating system and integration test suites.
Database -Person primarily responsible for integration with the database.
Server -Person(s) primarily responsible for the server.
Documentation -Person primarily responsible for producing reports and other documents.
Client -Person primarily responsible for client operation.
CORBA -Person primarily responsible for client-server communication.

Project Title:

ANGEL

Baseline Application Description:

This project will implement a basic air traffic control system. A number of clients, representing aircraft, will communicate with a centralized server. The server will build a complete picture of the airspace traffic to provide the following functionality:

Manage air traffic from the central location.
Coordinate air traffic among ground controllers.
Handshake between aircraft and aircraft controller

Configuration:

middleware - CORBA
operating system - Linux
language - Java on Server, C++ on Client

Third-party software, if any (databases):

MySQL or equivalent

Baseline Application Features:

required – Aircraft will register itself within a particular enroot flight center(zone)
required - Aircraft will request the location of other planes within a particular radius
optional - Aircraft will be warned of pending collisions based on its speed and location relative to other planes

Reliability Requirements:

required - Backup last known position of each aircraft
required - System will tolerate a single server failure
optional - System will tolerate a dual server failure(scalability)
optional - When the server fails backup will come online within 30* secs.

Real-Time Requirements:

required – Aircraft will register itself within a particular enroot flight center(zone) within 2* sec
required - Aircraft will receive reply for its request of the location of other planes within a particular radius within 10* sec
required - Aircraft will be warned of pending collisions based on its speed and location relative to other planes within 10* sec

Performance Requirements: