Professional Documents
Culture Documents
DECLARATION
This Information System Project is the Original work of the author and has not been submitted for any other Diploma or Degree program in any University. I therefore declare that, no other person apart from the undersigned has submitted this project.
Date..
This project was assessed and approved by the supervisor who oversaw the completion of this work whose signature appears at the bottom of this page.
Signed. MR. EMMANUEL KWEYU Lecturer, Faculty of Information Technology Strathmore University
Date
ii
ACKNOWLEDGEMENT
The following people have played a special role in enabling the completion of this system to its current level: First of all, GOD, for giving me the strength to keep going even when I thought everything was too hard and I felt like giving up. Secondly, Strathmore University for providing me with resources needed to do complete my project.ie. Free access to the internet which was an invaluable source of information that made my project a success Fourthly, my classmates in the DBIT class of April 2009, especially Evans who constantly came with new ways of solving programming problems and my desire to outsmart him made me decide to work on this project. Last but not least, my lecturers especially Mr. Emmanuel Kweyu who has been my supervisor and has taken me through the entire project development phase, giving me ideas on how to improve my project, and Mr. Nelson Ochieng who introduced me to object oriented programming in java and ever since I have aspired to master it. Thank you ALL!
iii
Contents
DECLARATION ........................................................................................................................ ii ACKNOWLEDGEMENT.......................................................................................................... iii 1.0 INTRODUCTION ............................................................................................................- 1 1.1 Background to the Organization ....................................................................................- 1 1.2 Description of the problem ................................................................................................ 1 1.3 Objectives and Terms of Reference ................................................................................... 1 1.4 Project Plan, Environmental and operational constraints of proposed system. ................. 2 A) Software requirements. ................................................................................................... 2 B) Hardware requirements ................................................................................................... 2 C) System users................................................................................................................... 2 2.0 SYSTEM ANALYSIS .......................................................................................................... 3 2.1 Summarized description of the current System................................................................... 3 2.1 Current System Models ..................................................................................................... 4 Current Bus Reservation Use Case Diagram ........................................................................ 4 Current Parcel delivery system use case............................................................................... 5 Sequence diagram of the current bus booking system .......................................................... 6 3. SYSTEM DESIGN ................................................................................................................. 9 3.1 Translation to Logical data model. ..................................................................................... 9 3.2 Database Schema ............................................................................................................ 10 3.2.2 Data Dictionary ............................................................................................................ 10 Bus Table .......................................................................................................................... 10 Bus_Assign Table ............................................................................................................. 11 Client Table ...................................................................................................................... 11 Client_Accounts Table. ..................................................................................................... 11 Crew Assignment Table .................................................................................................... 12 Parcel Table ...................................................................................................................... 12 Parcel Category Table ....................................................................................................... 12 Payment Table .................................................................................................................. 13 Receipt Table .................................................................................................................... 13 Route Table....................................................................................................................... 13 Staff Table ........................................................................................................................ 13 Ticket Table ...................................................................................................................... 14 Trip Table ......................................................................................................................... 14 3.3 Process Descriptions........................................................................................................ 15 3.3.1 The Pseudo-Code...................................................................................................... 15
iv
3.4 Interface Designs ............................................................................................................. 16 3.4.1 Input Screens ............................................................................................................ 16 3.5 Crud Matrix .................................................................................................................... 18 4.0 Implementation and Testing ................................................................................................ 19 4.1 Description of development Environment/tools................................................................ 19 4.2 Description of the main system functionalities. ................................................................ 19 4.3 Sample Test data and Error handling. .............................................................................. 19 4.4 Interesting Sample Scripts ............................................................................................... 20 5.0 CONCLUSIONS AND RECOMMENDATIONS................................................................ 21 5.1 Problems and challenges encountered .............................................................................. 21 5.2 Solutions to the problems and challenges encountered ..................................................... 21 5.4 Self -Evaluation of the system and work done. ................................................................. 21 6.0 BIBILIOGRAPHY.............................................................................................................. 22 6.1 Listing of work Consulted in alphabetical of Authors Surname ....................................... 22 7. APPENDICES ...................................................................................................................... 23 i) Installation Guide .............................................................................................................. 23 ii) Supervision Slip................................................................................................................ 23
Table of Figures Figure 1: Current bus reservation use case diagram ..................................................................... 4 Figure 2: Current parcel delivery use case diagram...................................................................... 5 Figure 3:Sequence Diagram for the current bus booking system .................................................. 6 Figure 4: ..................................................................................................................................... 6 Figure 5:Proposed bus booking use case diagram ........................................................................ 7 Figure 6: proposed seat reservation sequence diagram ................................................................. 8 Figure 7: Current System class diagram ...................................................................................... 8 Figure 8: Database relationships .................................................................................................. 9 Figure 9: Trip lookup input screen............................................................................................. 16 Figure 10: Parcel Status input screen ......................................................................................... 17 Figure 11: Currently reserved seats ........................................................................................... 17 Figure 12: Current balance ........................................................................................................ 18 Figure 13:Main menu ................................................................................................................ 23
1.0 INTRODUCTION
-1-
1.4 Project Plan, Environmental and operational constraints of proposed system. The project was meant to take approximately three months using the following tools and environment variables:
A) Software requirements. o o MySQL 5.1 as the SQL server. Apache 2.2 with PHP 5.0 as the server.
B) Hardware requirements o o A java enabled Mobile phone with MIDP 2.0 and CDLC 1.0. Internet connectivity via WAP,GPRS or EDGE.
C) System users. Any person with basic knowledge in using a java enabled mobile phone.
However, despite the obvious efforts made to make the system as effective as possible, it still has numerous drawbacks. These include: o Clients have to give their names ID number every time they come to book even though the company might be having that information. o Booking is done from a central place and all clients (passengers) have to physically go to the booking office even though it might be time/money consuming. o The consignee is not able to know of the parcels delivery status. o The consignor is not informed when his/her parcel is ready for collection.
Figure 4:
3. SYSTEM DESIGN
3.1 Translation to Logical data model.
Field Name
Reg_No
Data Type
Varchar
Field size
12
Description
Primary Key that uniquely identifies a bus Capacity of the bus Chassis number of the bus Bus model Bus name
2 24 15 15
10
Bus_Assign Table This table contains the details of buses and the routes they are assigned to operate on.
Field Name
Reg_No
Data Type
Varchar
Field size
12
Description
Primary Key that uniquely identifies a bus A valid route ID which cannot be null Date the bus was assigned
Route_ID Date_Assigned
Int Date
Field Name
Client_No
Data Type
Int
Field size
6
Description
Primary key that uniquely identifies a client Clients surname Clients first name Clients middle name Clients gender Clients address Clients postal code Clients phone number
25 25 25 6 15 6 10
Client_Accounts Table. This table contains clients usernames and passwords as well as their account details.
Field Name
Client_No
Data Type
Int
Field size
6
Description
Primary key that uniquely identifies a client Clients account balance in KSH. Clients last account recharge date Recharge transaction number
12
11
Crew Assignment Table This table contains details of trips and staff assigned to each trip.
Field Name
Staff_ID Trip_ID Date_Assigned
Data Type
Int Int Date
Field size
6 6
Description
Date the assignment took place
Field Name
Parcel_ID
Data Type
Int
Field size
6
Description
Primary key that uniquely identifies a parcel Identifies the type of parcel Identifies the category to which the parcel belongs Identifies the consignor from among the registered clients Identifies the consignee from among the registered clients The date when the parcel was send City of origin of the parcel Destination city of the parcel Delivery status of the parcel
Type Category_ID
Varchar Tinyint
14 2
Consignor_ID
Int
Consignee_ID
Int
Parcel Category Table This table contains categories of parcels, their weight limits and charges.
Field Name
Category_ID
Data Type
Tinyint
Field size
3
Description
Primary key that uniquely identifies a category Lower weight limit of the parcel category Upper weight limit of the parcel category
Lower_Weight_Limit Upper_Weight_Limit
Tinyint Tinyint
3 3
12
Cost
Table 7: parcel category table
Float
Payment Table This table contains trip payment details including the ticket number and amount paid.
Field Name
Ticket_no Amount Date_Paid Time_Paid
Table 8: Payment table
Data Type
Int Double Date Timestamp
Field size
6 8
Description
Timestamp transaction
of
the
Receipt Table This table contains payment details and receipt numbers of parcels.
Field Name
Parcel_ID Receipt_No
Data Type
Int Int
Field size
6 6
Description
Primary key that uniquely identifies a parcel Date the parcel was received by the clerk Cost of sending the parcel
Date_Received Amount
Table 9: Receipt table
Date Double 8
Field Name
Route_ID
Data Type
Tinyint
Field size
2
Description
Primary key that uniquely identifies a route The route name The final destination for the route Date the route was created.
30 25 25
Staff Table
13
Field Name
Staff_ID
Data Type
Int
Field size
6
Description
Primary key that uniquely identifies a staff member Staff members surname Staff members first name Staff members middle name Staff members gender Staff members address Staff members postal code Staff members phone number Staff members position
25 25 25 6 15 6 10 10
Ticket Table This table contains details of all seats and trips reserved by clients.
Field Name
Trip_ID Ticket_No
Data Type
Int Int
Field size
6 6
Description
Primary key used to uniquely identify a reservation or ticket Identifies the registered client reserving a seat for a given trip Date the ticket was issued Identifies the seat a client has booked. Current status of the ticket or reservation .
Client_No
Int
Trip Table This table has the details of all scheduled trips.
Field Name
Data Type
14
Field size
Description
Trip_ID
Int
Date_Added Bus_Reg_No
Date Varchar 6
Route_ID
Table 13: Trips table
Tinyint
Primary key which uniquely identifies a trip Date scheduled for the trip Time scheduled for the trip Fare to be paid for the trip in KSH Maximum number of passengers to be allowed for the trip Date on which the trip was added Registration number of the bus to be used for the trip Valid route to be used for the trip.
16
Parcel Status form This is a form where the user enters the parcel ID so as to view its delivery status.
3.4.2 Output Screens Reserved Seats Shows a list of the currently reserved seats for a given client
17
Client
Bus
Trip
Ticket
Parcel
Route
Staff
CRU
CRU
CRU
CRUD
CRUD
CRUD
CRUD
18
19
20
5.2 Solutions to the problems and challenges encountered o The author became a member of www.j2meforums.com from where he was able to find
help in challenging areas.
21
6.0 BIBILIOGRAPHY
22
7. APPENDICES
i) Installation Guide The system can be downloaded from the Easy Coach website via your mobile phone browser. The installation details vary depending on the phone model you are using but in most cases it is automatic. However before you download the system, you must fill in your registration details and be given your username and password. For more instructions on how to use the system, go to Im stuck on the main menu of the system.
23