Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/aravinda-1402/wolf-parking-database-management-system

The Wolf Parking Management System oversees campus parking, managing lot availability, zone specifications, permit assignments, and citation tracking. Administrators handle space, permits, citations, and generate reports for efficient parking management.
https://github.com/aravinda-1402/wolf-parking-database-management-system

java mariadb mariadb-server sql

Last synced: about 10 hours ago
JSON representation

The Wolf Parking Management System oversees campus parking, managing lot availability, zone specifications, permit assignments, and citation tracking. Administrators handle space, permits, citations, and generate reports for efficient parking management.

Awesome Lists containing this project

README

        

# šŸŗ Wolf Parking Management System

[![Project Status](https://img.shields.io/badge/Status-Completed-brightgreen.svg)](https://yourprojectstatuspage.com)
[![License](https://img.shields.io/badge/License-MIT-blue.svg)](https://opensource.org/licenses/MIT)

The **Wolf Parking Management System** šŸš—šŸ…æļø was developed as a part of the **CSC 540 Database Management System** course requirement.

## Project Overview

It aims to model the Wolf Parking Management System based on insights from the university parking manager and is designed to oversee campus parking lots and users. This project handles parking lot availability, zone specifications, permit assignments, and citation tracking.

Administrators manage space availability, assign permits, track citations, and generate reports for efficient parking management.

## Key Aspects

### Driver Information šŸš¦

Including names, statuses denoted as ā€˜Sā€™ (Student), ā€˜Eā€™ (Employee), or ā€˜Vā€™ (Visitor), and respective IDs or phone numbers as unique identifiers.

### Parking Lot Information šŸ…æļø

Details encompassing lot names, addresses, zones, and spaces within the lots.

### Zone Information šŸžļø

Defined by IDs (A, B, C, D, AS, BS, CS, DS, V) indicating various categories, primarily distinguishing zones for employees, students, and visitors.

### Space Information šŸš€

Involving space numbers, types (e.g., "electric," "handicap," "compact car," defaulting to "regular"), and availability status.

### Permit Information šŸŽ«
Covering permit IDs, lot details, zone IDs, space types, car license numbers, validity period, associated driver IDs or phone numbers, and permit types (such as "residential," "commuter," "peak hours," "special event," and "Park & Ride").

### Vehicle Information šŸš—
Encompassing license plate numbers, vehicle models, colors, manufacturers, and manufacturing years.

### Citation Information šŸšØ
Tracking citation numbers, car details, citation dates, times, lots, categories (e.g., "Invalid Permit," "Expired Permit," "No Permit"), fees, and payment statuses.

### System Capabilities āš™ļø
The system administrators will be able to manage parking lots, zones, spaces, permits, and citations. They can assign permits, manage vehicle lists, alter space availabilities, and verify permit validity within their respective lots.

### Security šŸ”
Additionally, security personnel can create/update/delete citations for parking violations, modifying payment statuses as required. Database records will encompass driver, parking lot, permit, and citation data.

---
***Note:** Students and visitors are limited to one vehicle per permit, while employees can have up to two. Specific allowances are made for special events or Park & Ride scenarios. Tasks involving information processing, permit management, citation handling, and report generation will drive system functionalities. These tasks encompass diverse operations, such as managing driver and lot information, assigning permits, tracking citations, and generating reports.*

## Project Reports šŸ“Š

The Project Report has information about the database schema and its design.
It consists of 3 parts:

1. **Report 1**: ER Diagrams and APIs
2. **Report 2**: Database Schema and SQL statements that create the tables
3. **Report 3**: Transactions used in the Database and how the code was structured

---

**Note**: Not all information provided may need explicit capture in the database. Hence, part of the project's effort involves discerning what to retain or discard, making assumptions, and addressing potential inconsistencies while documenting these decisions and assumptions. šŸ“