Contact person: Business Client

Phone:Show

Email:Show

Location: Calgary, Canada

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"Project Description – Bullet Points
Overview

Stand-alone desktop Flight Reservation System built using Object-Oriented Analysis & Design.

Focuses on domain-driven design, UML modelling, and layered software architecture.

Implements a complete workflow of searching, booking, modifying, and cancelling flights.

Purpose

To design and develop a system that simulates flight reservation operations.

To practice applying OOP principles, design patterns, and system-level modelling techniques.

To demonstrate proper separation of concerns through a 3-layer architecture.

Supported User Roles

Customer – search flights, make/cancel bookings, view reservations.

Flight Agent – manage customer details, modify bookings, view schedules.

System Administrator – manage flights, routes, schedules, aircraft details.

Key Functionalities

Search flights by origin, destination, date, airline, seat availability, price.

View detailed flight information and schedules.

Make new reservations and generate booking confirmations.

Modify or cancel existing bookings.

Add/Edit/Delete flights (Admin only).

Manage customer profiles and payment records.

Simulated payment processing and receipt generation.

Monthly promotional news sent to customers.

Local database storage using MySQL/SQLite.

Non-Functional Requirements

Usability: Simple, user-friendly Java Swing GUI.

Portability: Runs on any desktop platform.

Maintainability: Modular, layered design with low coupling and high cohesion.

Scalability: Allows easy future extension (e.g., online booking, server-client model).

System Architecture

Presentation Layer: GUI screens, user inputs, and display components.

Business Logic Layer: Core entities (Flight, Customer, Reservation), controllers, operations.

Data Layer: Database access, file/record storage, CRUD operations.

Design Deliverables

System introduction and description of major workflows.

4 Activity Diagrams: Login, Browse/Select Flight, Book Flight, Payment Process.

Use-Case Diagram for all system features.

Use-Case Scenarios with underlined objects and operations.

4 Sequence Diagrams: For major booking-related use cases.

4 State Diagrams: System, Payment, Reservation, Flight.

Complete Class Diagram with entities, boundaries, and control classes.

Package Diagram showing 3-layer architecture and class placement." (client-provided description)