Project 2 - Project Description: Vehicle Hiring System (VHS)

The operations manager of a vehicle hiring company is currently using a paper based (manual) system to manage and keep track of the short term vehicle reservations made by registered customers. The company hires cars and light vans to its registered customers on a short term basis (daily) and due to the inefficiency of this system, the operations manager often faces problems in serving customers due to overbooking of hiring vehicles, inability to provide customers with the requested vehicle on time and inability to track vehicles that are not returned on time.

To overcome this issue, you are required to develop a console based application that will allow the operations manager to record and maintain reservations for hiring vehicles (currently there are only two types of vehicles, cars and light vans, later there can be more types).

The operations manager has provided a registered customer list and hiring vehicle list in text files.

The system should have a simple menu as below.

1. Show available vehicles

2. Reserve a vehicle for a customer

3. Show hires for a customer

4. Show hires for a vehicle

5. Show not returned (overdue) vehicles

6. Return vehicle from hire

7. Exit

The current manual system operates as follows.

1. Show available vehicles

Depending on the customer request all available cars or vans are shown with all details.

2. Reserve a vehicle for a customer

Having shown the list of available vehicles the customer requests to reserve his/ her preferred vehicle. The manager will check if the vehicle is available during the requested time and if so a vehicle reservation is made on behalf of the customer.

3. Show hires for a customer

The operations manager looks at the vehicle reservation sheets for each vehicle to check if a given customer id is present in those sheets and creates a report of vehicle hiring records for that particular customer.

4. Show hires for a vehicle

The operations manager looks at the reservation sheets for a particular vehicle (using the vehicle id) and creates a report of hiring records for that vehicle.

5. Show not returned (overdue) vehicles

To check for not returned vehicles, the operations manager looks at the vehicle reservation sheets, checks for vehicles not returned on time (returned date/time is empty) and creates a report including the reservation details and customer details of such overdue vehicles.

6. Return vehicle from hire

When the customer id, the vehicle id and hired date and time is given, the manager finds the correct hire from the list of reservations and records the returned date and time. Finally, the total charge for the hire is calculated (including late return penalty if applicable) and shown to the customer.

You may start your design with the following recommendations.

• You must include Company, Customer, Vehicle, Reservation objects in your design
• Currently there are two vehicle types, car and van. You must have objects to represent them.
• The company has a name, a registered customer list and a hiring vehicle list
• A customer has a customer id, name and category (premium, standard and budget).
• Each vehicle has a unique registration number, model name, year of registration, fuel type and the availability for hire status (For example, when a vehicle is under repair the status is false)
• In addition to the common fields a car has engine capacity
• In addition to the common fields a van has a maximum load capacity
• A vehicle may have zero or more reservations
• Multiple reservations can be placed for the same customer
• A reservation is associated with a vehicle and a customer
• Each vehicle reservation also maintains the vehicle pickup date, pickup time, pickup location, reservation period (number of hours), returned date and returned time (recorded once the vehicle is returned).
• A reservation can be made up to 30 days in advance or just 5 hours before the hire. However premium and standard customers can make reservations just 1 hour before the hire.
• Reservations can be made between 4.00 am to 12 midnight.
• Since the vehicles are available for short term hires, reservation period cannot extend 15 hours. However premium customers are allowed to make reservations up to 20 hrs.
• Reservations must be displayed sorted by pickup date and pick up time
• Late vehicle returns of less than 1 hour will not be charged. Any vehicle returns exceeding one hour grace period will be charged by the hourly rate of the vehicle (For example, if late by 4 hrs, late penalty = 4 * hourly rate of the vehicle)
• The hourly rate for a car is $10.
• The hourly rate for a van is $15.

Start with the above but revise and improve your design accordingly to improve usability.

Project 3 - Project Description: Vehicle Hiring System (VHS) - GUI

You are required to develop a GUI that will work with the objects you created in project 2 and provide the same level of functionality.

The Start class must be modified, so that the user can start the GUI or the Console Application, both must work with same set of business objects (one set only). Both the GUI and the console application must work well and changes made in one mode will be persisted (at exit of that mode) and appear when the other mode is run.

The GUI does not required to be fancy. It should be easy to use and organised.

The purpose of your task is to allow you to demonstrate skills mastered in the following areas.

Skills you are required to demonstrate

• Use of appropriate ActionListeners to capture events and respond properly
• Ability creating a GUI that is easy to use
• Use of JFrame
• Use of JPanel
• Use of JDialog
• Use of Layout Managers and any other required GUI components you wish (you must NOT use a GUI development IDE to generate these)
• Exceptions and error handling (use of custom exception objects and other Java built in exceptions)
• Achievement of all business goals/ requirements

Qualities

• GUI has the same level of functionality as the console application
• It is easy for the user to understand how to achieve each task.
• It is easy to understand what data must be entered
• Messages are displayed when the user makes an error
• The look of your design must be unique (Not shared with anyone else)

Rules

• There must still be only one set of classes that represent the business logic.
• The same classes are used by the GUI and by the console Application.
• When the program starts, the user should be allowed to select console mode or GUI mode.
• All changes made in one mode should be visible when the second mode is used.
• Only one mode will be used at a time.
• Strictly you must NOT use a GUI development IDE to implement the GUI

HELP

• Nil provided
• You must research and write this project your-self.

Starting point

• Fix any errors identified in project 2, make any improvements to meet functional requirements and improve usability
• Draw detailed sequence diagrams for the use cases, including GUI objects (use appropriate UML notations discussed in class)
• Improve code to manage errors effectively by using exceptions

This is to be done by:

• Writing your own exception class
• Identifying which business logic methods may cause your code to fail
• Throwing exceptions from the business logic methods with good error messages
• Logging errors to file (error log) where required
• Capturing errors at the user interface and taking corrective action
• Keeping the user well informed about any problems.

Design - I will do this as we have to follow the guidelines

• Structure chart for the GUI
• Sequence diagram for one use case (of your preference) including important GUI objects (if more than one diagram is included the first one in the document will be marked)

Code:

• The solution must be a Blue J Project.

You need to hand in a hard copy and a soft copy.

Attachment:- Assignment Files.rar