Project Page

Team #6: Team Slackers

18-749: Fault-Tolerant Distributed Systems
Spring 2006

Team Members:

Hyunwoo Kim hyunwook@andrew.cmu.edu
Karim Jamal kfj@andrew.cmu.edu
Puneet Aggarwal puneetpal@cmu.edu
Tanmay Sinha tanmay@cmu.edu
Steven Lawrance steven@moonlightdesign.org

Team Roles:

Responsibility	Hyunwoo	Karim	Puneet	Tanmay	Steven
Project Management				X	X
Requirements Specification	X		X
Architecture Design	X	X		X
Database Design		X	X		X
Implementation - Client			X	X
Implementation - Server	X	X			X
Testing	X	X	X	X	X
Tool Support					X
Performance Analysis		X		X	X
Real-time Analysis	X	X	X
Reliability Analysis	X		X	X
Presentation	X	X	X	X	X

Project Title: Park'n Park

Baseline Application Description: A system that manages parking lots by keeping track of how many spaces are available in lots and recommends other lots when the lot a driver is at is full

CVS:

CVS Root: :ext:yourusername@yourcolor.ece.cmu.edu:/afs/ece.cmu.edu/class/ece749/public_html/teams-06/team6/cvs
Eclipse:

Connect method: SSH
Host name: yourcolor.ece.cmu.edu
Path: /afs/ece.cmu.edu/class/ece749/public_html/teams-06/team6/cvs

Configuration:

Enterprise Java Beans (EJB) / CORBA
Linux for the database and middle tiers
Windows, Mac OS X, and Linux for the multiplatform client tier
Java 5.0

Third-party software, if any (databases):

MySQL 5
Eclipse
JBoss
CVS

Baseline Application Features:

The system will let the driver know at the entrance whether there is space available in the lot or not.
If there is space available in the lot, the system will let the driver know which levels have available spaces.
If no space is available in the lot, the system will let the driver know the nearest parking lots that have available space.
If no space is available in any of the lots, the system will display an appropriate message.

Reliability Requirements:

The driver will experience at most a five second delay upon a single server failure. Service will continue after the five second delay.
The system will be available 24x7 without any critical system failures, defined as failures that prevent the system from performing its duties to its clients.
Every hour, the system will perform an integrity check to make sure that each lot's total counter synchronizes with its level counters.
The result displayed to the driver will be within plus or minus one parking space of the actual physical state of the lot.

Real-Time Requirements:

At a parking lot entrance gate, the driver will receive a result within at most five seconds.
The system will update a lot's counter within one second upon a car entering or leaving that lot.
The system will automatically update a parking lot level's counter within one second of a car leaving that level.

Performance Requirements:

The system will support at least 50 simultaneous entry and exit transactions under normal working conditions.
The system will allow at least 120 cars to enter each lot in one hour under normal working conditions, given that the lot does not become full.
The system will support at least 25 parking lots.

Baseline Application

Interfaces

Tiers

Database server: One database server
Parking server(s): One or more middleware servers
Client: At least one entry/exit gate and level enty/exit sensor for one or more parking lots

Methods (Entry Stateless Session Beans)

void verifyAvailabilityCounts(int clientID, int sequence, int lot) throws AvailabilityOutOfSyncException, LotNotFoundException, DatabaseException
void removeCar(int clientID, int sequence, int lot) throws LotEmptyException, LotNotFoundException, DatabaseException
int[] getOtherLotAvailability(int clientID, int sequence, int lot), LotNotFoundException, DatabaseException
void addCarToLevel(int clientID, int sequence, int lot, int level), LotNotFoundException, LevelNotFoundException, DatabaseException
void removeCarFromLevel(int clientID, int sequence, int lot, int level) throws LevelEmptyException, LotNotFoundException, LevelNotFoundException, DatabaseException
int[] addCarAndGetAvailableLevels(int clientID, int sequence, int lot) throws LotFullException, LotNotFoundException, DatabaseException

Attributes

carCount – Number of cars in a lot

capacity – Number of parking spaces in a lot

lotDistances – Distances between the lots

carCount (Level) – Number of Cars in a level

capacity (Level) – Number of parking spaces on a level

Exceptions

AvailabilityOutOfSyncException – If the sum of car count of each levels does not equal to the number of cars in the lot, then system throws this exception

DatabaseException – This gets thrown to the client when an unrecoverable SQLException on the server side

LotFullException – System throws exception when the lot is full

LotEmptyException – System throws exception when the lot is empty

LotNotFoundException – Lot number not found in the database

LevelEmptyException – System throws an exception when the level is empty

LevelNotFoundException – Level number not found in the database

Servers and Ports

Database

mahjongg:3306

Application

clue:7779 for IIOP

Naming Service

boggle:7777 for bootstrap and 7778 for IIOP

Database Tables

Level

LotID INTEGER NOT NULL UNSIGNED: The ID number of the lot that this level belongs to
Level INTEGER NOT NULL UNSIGNED: The level or floor number of this lot's level
CarCount INTEGER NOT NULL UNSIGNED: The number of cars currently in this level, parked or unparked. This can be higher than Capacity if the level is full and extra cars are on the lot looking for parking or passing through
Capacity INTEGER NOT NULL UNSIGNED: The number of parking spaces in the parking lot
Description VARCHAR(100) NOT NULL: Description of this level, such as "Ground Floor" or "Mall Entrance"
Primary Key: LotID, Level

Lot

ID INTEGER NOT NULL UNSIGNED AUTO_INCREMENT: The ID number of this parking lot
CarCount INTEGER NOT NULL UNSIGNED: The number of cars currently in the parking lot. Note that this should not be allowed to exceed the lot's capacity
Capacity INTEGER NOT NULL UNSIGNED: The capacity of the parking lot
Description VARCHAR(100) NOT NULL: The description of the parking lot
Name VARCHAR(30) NOT NULL: A short name for this parking lot
Primary Key: ID

LotDistance

Lot1ID INTEGER NOT NULL UNSIGNED: A parking lot ID
Lot2ID INTEGER NOT NULL UNSIGNED: A parking lot ID of another parking lot
Distance INTEGER NOT NULL UNSIGNED: The distance between the two parking lots represented by Lot1ID and Lot2ID
Primary Key: Lot1ID, Lot2ID

Team #6: Team Slackers

Team Members:

Team Roles:

Project Title: Park'n Park

Baseline Application Description: A system that manages parking lots by keeping track of how many spaces are available in lots and recommends other lots when the lot a driver is at is full

Configuration:

Third-party software, if any (databases):

Baseline Application Features:

Reliability Requirements:

Real-Time Requirements:

Performance Requirements:

Baseline Application

Interfaces

Database Tables

Scenarios/Interactions

Current Status

Downloads

Fault-Tolerant Baseline Application

Scenarios/Interactions

Current Status

Downloads

Real-Time Fault-Tolerant Baseline Application

Scenarios/Interactions

Current Status

Downloads

High-Performance Real-Time Fault-Tolerant Baseline Application

Scenarios/Interactions

Current Status

Downloads