Module: System Development for Business Processes

You should hand in one copy of your assignment/project by the time and date mentioned above to the appropriate 'hand-in location' at the Gulf College. Fill in the front cover (staple together with your assignment). MAKE SURE that you fill in all the relevant details on this form. An acknowledgement will be given to you upon receiving your assignment. This is your receipt, keep it.

You can submit work by post, but you must send also a recorded delivery. It must be postmarked within two days before the deadline date and a copy must be kept by you in case it is lost in the post. Faxed assignments will not be accepted.

This assignment will assess the following learning outcomes:

1. ANALYSE A GIVEN CASE STUDY USING OBJECT- ORIENTED MODELLING TECHNIQUES
2. DESIGN AND IMPLEMENT A PROTOTYPE OBJECT- ORIENTED APPLICATION USING AN OBJECT-ORIENTED PROGRAMMING LANGUAGE

The Task

You must design and implement in Java a Bus Ticket Management System corresponding to the attached scenario. You are not required to implement the entire scenario, but the more functionality your system has, the higher the mark you can obtain (see assessment criteria below for details). This assignment is expected to be done individually by all students. You will be given ample guidance and support on the modelling and implementation of the system in your lectures and tutorials.

Scenario - Bus Ticket Management System

A bus ticket management system enables a bus company cashier to browse buses in the system, select a bus and create a ticket for a customer. The system will also automatically compute the total bill and the cashier will process the necessary payment.

The System

The bus ticket management system should do what regular bus ticket management systems can do, which includes entering bus together with the details in the system and creating a customer ticket, etc. The system should allow the bus company cashier to login into the system, browse for bus, select a bus and process the necessary payment for a particular customer ticket using the system.

The bus ticket management system must support easy administration, so the bus company administrator can manage cashiers' data, customer tickets, bus details, etc. It also keeps a list of cashiers' data, customer tickets, bus details, sales, etc. It also keeps an inventory of available buses and information on buses such as bus number, bus name, bus type, total seat capacity, etc.

Users of the bus ticket management system should be able to:

- add, delete and update a bus company cashier with personal details (identification number, name, age, address and telephone number, etc.) and login details (user name and password).

- add, delete and update a bus together with its details (bus number, bus name, bus type, total seat capacity, etc.

- add, delete and update a bus ticket together with its details (ticket number, date and time of departure, bus number, route, ticket price, etc.)
- list bus company cashier's personal details
- list bus details
- list ticket details
- find a bus given its bus number or bus name.
- simulate a bus ticket system based on the following scenario:
o The customer buys a bus ticket to the bus company cashier
o The bus company cashier takes the customer's preference
o The bus company cashier enters the ticket details into the system by creating a new ticket in the system.
o The bus company cashier uses the system to display the total ticket amount and tells the customer the total amount for the ticket. The system should automatically calculate the total ticket amount.
o The customer pays the ticket.
o The bus company cashier enters the payment details into the system and prints the receipt.
Conditions: - If a transaction is adding a new bus item a bus company cashier must successfully add, delete and update a bus record to the system together with the bus details.
- If a transaction is creating a new ticket, a bus company cashier must successfully add, delete and update the ticket number, date and time of departure, bus number, and route and ticket price.
- If a transaction is payment, the system must successfully calculate the total amount to be paid by a particular customer.

Deliverables

Your system must be object-oriented and programmed in Java. You must submit:
- design documentation for the system you have implemented with the corresponding explanation on the processes that you have undertaken in coming up with the following diagrams:
o Use Case diagrams
o Class diagrams, showing all the classes and their relationships together with the attributes and methods for each class
o Sequence diagrams
o Collaboration diagrams
- a soft copy of your complete report and Java files
- a hard copy of the report including code snippets with detailed explanation
- The body of the report should include the following:

I. Introduction and Objectives
Write a short description of the program and its objectives

II. Review of Existing Systems
- Include a brief explanation of at least two existing systems and the solutions that they are offering.

III. UML and Screen Design
- Include all the diagrams with a brief description of each diagram
- Display the screenshot of each form
- Label the different objects of each form
- Give a brief description of each form

IV. Implementation
- Identify important code snippets for discussion in each form

V. Testing
- Write at least 2 test cases for each form

VI. Critical Analysis
- Write a detailed review of the things that you have learned and accomplished in the assignment. Include also the things that you did not do due to some constraints.

Demonstration Periods
You have to agree with your tutor on an interview date to discuss your assignment. The date should be at least a week before the submission deadline. This may be supported by the draft documentation of work carried out to date. In this interview you need to address design considerations on the basic functionalities of the assignment. At this stage you are expected to have a clear idea about aspects of your implementation.

The second stage will involve a demonstration of your implementation. You can change the codes based on the feedback coming from your tutor but the marks for the demonstration will be final.

A. To obtain a mark of 70 -100%, your work should:
- Fulfill all the criteria for B (below). The system should therefore fully implement the Bus Ticket Management System scenario.
- Calculate the total amount to be paid by a particular customer.
- be a three-tier system implementing
o a Graphical User Interface
o Persistence, either to a file or database system. If you persist to a database you need to comment on the sample data in the application and insert it in your database prior to running the code.