Download Project Mocha E-Ticket Airline Reservation System

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts
no text concepts found
Transcript
Project Mocha
E-Ticket Airline Reservation System
Programmers: Kevin, Iris, Brad
Package Structure
(Application Organization)
The main package
The database
package
The logging
package
The model package
The user interface
package
The utility package
The xml package
The main
application class
Quick Update
Current class hierarchy contains 17 classes and
growing… (predicted 20 – 30)
Presentation Classes are an extremely high level view
Current CRCs DO NOT account for anonymous classes,
inner classes, abstract classes and interfaces
Classes DO NOT account for classes used in the Java
API except by stating “Common Java Classes”
The methodology used is rapid prototyping, thus class
structure changes with each examination of the
application. Iterative development plan, with small
releases
The main package
edu.fullerton.cpsc461
ETRS (b)
•starts application
•closes application
•displays main frame
•displays available
flights
•handles search ui
•handles payment ui
•handles user help
•handles about dialog
•SearchView shows
searchui
•PaymentView shows
payment ui
•SplashWindow shows
splash screen
•(Logger)
•(HelpView)
•(AboutDialog)
•Common Java Classes
The database package
edu.fullerton.cpsc461.db
ETRSDb
Queries for flight
information
Queries for Airport
information
Queries for
Common Java Classes
The model package
edu.fullerton.cpsc461.model
Airplane
Common Java Classes
The model package
edu.fullerton.cpsc461.model
Airport
Common Java Classes
The model package
edu.fullerton.cpsc461.model
AvailableFlight
Common Java Classes
Airplane
The model package
edu.fullerton.cpsc461.model
Customer
Common Java Classes
The model package
edu.fullerton.cpsc461.model
FlightSchedule
Common Java Classes
The model package
edu.fullerton.cpsc461.model
PaymentForm (b)
•contains payment data
Common Java Classes
The model package
edu.fullerton.cpsc461.model
SearchForm (b)
•contains search data
Common Java Classes
The model package
edu.fullerton.cpsc461.model
FlightTableModel (b)
•contains table data
Common Java Classes
The model package
edu.fullerton.cpsc461.model
Transaction
Common Java Classes
The ui package
edu.fullerton.cpsc461.ui.splash
SplashWindow (b)
displays splash screen
Common Java Classes
The ui package
edu.fullerton.cpsc461.ui.view
SearchView * (b)
•Displays search ui
•Handles basic search
information validation
•Handles search for
available flights
•SearchEngine handles
searching for available
flights
•SearchEngine handles
searching for airports
•SearchForm (Model)
contains Search data
•ETRSUtil handles input
validation and valid date
generation
The ui package
edu.fullerton.cpsc461.ui.view
PaymentView* (b)
•Displays payment ui
•Handles basic user
information validation
•Handles credit card
authorization
•CreditCardManager
handles credit
authorization
•PaymentForm (Model)
contains the
PaymentView data
•ETRSUtil handles input
validation
•Common Java Classes
The utility package
edu.fullerton.cpsc461.util
ETRSUtil (b)
•Validates user input
Common Java Classes
• Name
• Address
• City
•Validates search criteria
•Validates payment
information
The utility package
edu.fullerton.cpsc461.util
SearchEngine (b)
Retrieves flights based
on search criteria
Retrieves airports
Retrieves customer
information
Retrieves transaction
information
ETRSDb
SearchForm
Airport
Airplane
Transaction
Customer
Common Java Classes
The utility package
edu.fullerton.cpsc461.util
CreditCardManager (b)
Communicates with the
Credit Card vendors to
authorize credit card
purchases
ETRSDb
PaymentForm
Book
Common Java Classes
Additional Classes
Testing




Package test.edu.fullerton.cpsc461
All classes have an associated test class
Test classes have the same name as the class with
“Test” pre-pended to the beginning of the class name.
Tests initial methods
Testing Methodology


After each development cycle
Guarantees functionality of the previous cycle
Related documents