Академический Документы
Профессиональный Документы
Культура Документы
INTRODUCTION........................................................................................................ 2
1.2.1Challenges of the current system................................................................................3
1.4Justifications........................................................................................................... 4
1.5 Scope.................................................................................................................... 4
1.6Methodology........................................................................................................... 5
CHAPTER 2.................................................................................................................. 7
2.0 Literature review......................................................................................................... 7
Features..................................................................................................................... 7
Horizon Coach............................................................................................................. 7
RESOURCE AND BUDGET ESTIMATES FOR THE PROJECT:............................................8
Chapter3........................................................................................................................ 9
SYSTEM REQUIREMENTS AND SPECIFICATION...............................................................9
3.0 INTRODUCTION....................................................................................................... 9
3.1 Purpose................................................................................................................. 9
3.2Scope.................................................................................................................. 10
3.3 Definition of The Acronyms and Abbreviations..............................................................10
3.4 Overview............................................................................................................. 11
3.5 THE OVERALL DESCRIPTION..................................................................................11
3.5.1 The Perspective Of The Products............................................................................. 11
3.6.1 Software Interfaces........................................................................................... 12
3.7 User Characteristics................................................................................................ 13
3.8 Apportioning of Requirements...................................................................................13
3.9 Assumptions and Dependencies.................................................................................13
3.10
SPECIFIC REQUIREMENTS.................................................................................14
1
Purpose............................................................................................................. 20
b)
System overview................................................................................................. 20
c)
Intended users.................................................................................................... 20
a)
Main Inputs:................................................................................................... 21
b)
Outputs......................................................................................................... 21
Assumptions...................................................................................................... 23
b)
Development tools............................................................................................... 24
b)
Design methodology............................................................................................ 24
Database design..................................................................................................... 25
c)
Conceptual design............................................................................................... 25
d)
e)
Identification of relationships.............................................................................25
f)
Data normalization.......................................................................................... 26
Physical data design............................................................................................ 26
g)
a)
a.
Context Diagram................................................................................................ 33
b.
CHAPTER 1
INTRODUCTION
BUS BOOKING MANAGEMENT SYSTEM is aimed at reducing paper work for the bus
industry and hence improving its efficiency and speeding up of all processes.
The database can be accessed by the passengers from any computer terminal connected through
LAN to a server where the system has been installed. Hence, all the related information about a
passenger is available to Admin and Employees. Thus this software saves the entire passengers
long queue and hassle.
1.1 Background
Horizon coach is a transport company Located in CBD Nairobi Kenya along Accra road. It was
started in 1958. The company is most well known passenger, courier, parcel delivery and
transport company operator in East Africa which provide the safest, most comfortable luxury
buses on Kenyan roads today.
i.
ii.
iii.
Lack of prompt updating- various changes to information like passenger details are
difficult to make as paper work is involved
iv.
v.
vi.
vii.
Inability to retain records as they are lost if they are kept on wrongly. e.g change of
office file storage.
1.4Justifications
The purposes of this system is to help easily capture the information of all patients and to reduce
the time taken through manual system in order to maintain all the records.
1.5 Scope
This system is helpful to reduce the time and complexity of maintaining the records. It also helps
in accurate maintenance of passengers and drivers.
-It can be used in any transport company for maintaining Passenger details.
1.6Methodology
1Research method
Data collection methodologies
Horizon coach uses a manual system but is not efficient on passengers detail. So I thought there
was a need to improve on passenger registration system to overcome some problems.
Data collection tools
They include the following
1. Observation-I observed that their system is not efficient on keeping a passenger
registration details this give the passenger a hard time if one loses receipt issued.
2. Documentation review- all the documents used to record transactions and capturing of
information were available. These gave me views of what kind of data is involved in the
current system to enable me borrow from it.
Problems identified in the collected data:
1. Security: -data stored in database can be access by unauthorized person because of using
access database which is weak and it cannot prevent unauthorized people from access it.
This lead to information stored in their database being interfered and damaged.
2. The system is slow: - because its users keeping information manually in books which
development process not moving on to the next stage until the previous stage has been
completed.
CHAPTER 2
2.0 Literature review
This is an evaluation report of information found in the field related to the selected area of study.
It describes the kind of system that is to be developed. Unfortunately, I have no idea whether
there have been attempts to implement new and more efficient IT solutions for developing a Bus
Booking management system to be able to improve on the current systems being used in
transport industry.
Features
I.
II.
III.
IV.
V.
VI.
Horizon Coach
The reason for developing this system was to come with a system that would be able to track
information of all passengers who comes to book a service. A system that will be able to register
passengers and give them a random number to prevent any data duplication. This system will
also be able to retain passenger details in the database.
Resources/requirements
1. Computer machine
2. External disk
3. Microsoft office 2007
10
4. Printer
5. Printing material
6. Visual basic 6.0
RESOURCE AND BUDGET ESTIMATES FOR THE PROJECT:
Requirement
Specifications
Computer machine
i3
or
Actual cost
i7speed Kshs.100000
Estimated COST
Kshs.64,000
processor,
2.0 GB memory
capacity,
500GB
storage
2010
Kshs.1000
Kshs.800
Kshs.2000
Kshs.1000
MS word
Printer
Laser printer
Kshs.15000
Kshs.10000
External disk
8 GB Flash disk
Kshs.1000
Kshs.800
Printing materials
Kshs.800
toner
11
Chapter3
SYSTEM REQUIREMENTS AND SPECIFICATION
3.0 INTRODUCTION
The below subsections is the Systems Requirements Specifications (SRS) document and it
provides an overview of the entire system.
3.1 Purpose
The System Requirements Specification (SRS) will provide a detailed description of the
requirements for the Bus Booking Management System (BBMS). This SRS will allow
for a complete understanding of what is needed for the hotel management system
construction. The clear understanding of the HMS and its functionality will allow for the
correct software to be developed for the end user and thus will be used for the
development of the future stages of the project. This SRS will also provide the foundation
for the project. From this SRS, the BBMS can be designed, constructed, and finally
tested.
This SRS will be used by the software engineers constructing the BBMS and the Bus end users.
The software engineers will use the SRS so that to fully understand the expectations of this
BBMS to construct the appropriate software. The hotel end users will be able to use this SRS as
a test to see if the software engineers will be constructing the system to their expectations. If it
is not to their expectations then the end users can specify their choice and the software engineers
will change the SRS to fit the end users needs.
3.2Scope
12
The system product to be produced is a Bus Booking Management System which will automate
the major Bus operations. The first subsystem is a Bus Reservation and as well as advance
Booking System to keep tracks of reservations and seats availability. The second subsystem is
the Tracking and Selling tickets System that charges the current journey. The third subsystem is
a General Management Services and Automated Tasks System which generates reports to audit
all bus operations and allows modification of subsystem information. These three subsystems
functionality will be described in detail in section 2-Overall Description.
There are two accounts for the BBMS. The end users are the Bus staff (customer service
representative) and administrator the Bus managers. Both user types can access the Reservation
and Booking System and the ticket Tracking and Selling System. The General Management
System will be restricted to management users.
The objective of this Bus Management System is to provide a system that can manage a bus that
has increased in size to a total of 60 seats. Without automation the management of the bus has
become an unwieldy task. The end users day-to-day jobs of managing a bus will be simplified
by a considerable amount through the automated system. The system will be able to handle
many services to take care of all passengers in a quick manner. The system should be user
appropriate, easy to use, provide easy recovery of errors and have an overall end user high
subjective satisfaction.
3.3 Definition of The Acronyms and Abbreviations.
SRS Systems Requirements Specification
BBMS Bus Booking Management System
Subjective satisfaction The overall satisfaction of the system
End users The people who will be actually using the system
3.4 Overview
13
The SRS is organized into two main sections. The first is The Overall Description and
the second is the Specific Requirements. The Overall Description will describe the
requirements of the BBMS from a general high level perspective.
The Specific
requirements, which are defined in section 3, and makes them easier to understand.
3.5.1 The Perspective Of The Products
The BBMS is an independent standalone system.
The passenger information database will contain all the information of the
passenger such as first name, Surname, ID Number, Gender and phone Number.
3.6.2 Product Functions
Reservations and Advance Booking System
When a passenger makes reservation, the seat will changed color from blue to
either yellow or pink.
Records payment
16
3.10SPECIFIC REQUIREMENTS
This section contains all the software requirements in a more detailed manner, that when
combined with the system context diagram, use cases, and use case descriptions, is sufficient to
enable designers to design a system to satisfy those requirements, and testers to test that the
system satisfies all the requirements.
Keyboard
Mouse
Monitor
Printer
17
Description
Login
Reservation
Travel
Bus Payment
Accept payment.
Room Service/Restaurant
Passenger Record
Administer seats
Availability
Administer User
Reports
18
3.14Communication Interfaces
This system shall be a standalone product that does not require any communication interfaces in
whatsoever.
2.15 Functional Requirements
Functional requirements define the fundamental actions that system must perform.
The functional requirements for the system are divided into three main categories,
Reservation/Booking, travel, and Management. For further details, refer to the use cases.
3.15.1 Reservation/Booking
1.1. The system shall record reservations.
1.2. The system shall record the passengers first name.
1.3. The system shall record the passengers Surname name.
1.4. The system shall record the number of passenger.
1.5. The system shall record the seat number.
1.6. The system shall record the passengers phone number.
1.7. The system shall generate a unique confirmation number for each reservation.
1.8. The system shall record the expected travel date and time.
1.9. The system shall record the expected destination date and time.
1.9.1. The system shall record that the seat is empty.
1.9.2. The system shall record the payment.
1.9.3. The system shall record the payment type.
19
The load time for user interface screens shall take no longer than two seconds.
Passenger Surname
Passenger ID Number
Assigned seat
Payment received
Payment type
Total Bill
20
System.
Passenger
Service
Representatives
will
have
access
to
the
21
22
CHAPTER 4
System Design overview
4.1 INTRODUCTION
Software design is the process of implementing software solutions to one or more set of
problems. The software design (SDS) document contains a statement of the design of inventory
management system. The design contains an explanation of a way to carry out each of the
product specification written in the Software Requirement Specification (SRS).The design will
serve as a guide to the developer. The SDS also shows how the program is separated into
modules, how the modules interact with each other, and how users see the program.
a) Purpose
This document is designed to be a reference for any person wishing to implement, or any persons
interested in the design architecture of the Horizon coach Management system. This document
describes each applications architecture and its associated interfaces and database design. This
design will detail the implementation of the requirements as defined in the BBMS system
specification design.
b) System overview
This document includes but is not limited to the following information for the Horizon Coach
Booking management system; system overview, design consideration, architectural strategies,
system architecture, policies and tactics, database schemas, detailed system design.
c) Intended users
This document should be read by an individual with a technical background and has experience
reading data flow diagrams DFDs, control flow diagrams CFDs, interface design and
development experience in event driven programming or as describe in the BBMS System
Requirement Specification 1.2.
23
Passenger name
Driver ID/Passenger ID
Passenger address, phone number, Gender
Travel date and time for passenger
b) Outputs
i.
ii.
iii.
iv.
i.
ii.
c) Design Map
The system design will take the following mapping when ready.
Splash Form
24
Main Form
Login
ADMIN
MAKE
RESERVATI
ON
ADD/DELE
TE
DRIVER
ADD NEW
USER
ADD NEW
BUS
USER
CHECK
SEATS
AVAILABLE
MAKE
RESERATIO
N
ADD NEW
BUS
SEARCH
ADD/DEL
ETE
DRIVER
CHECK
SEATS
AVAILABLE
SEARCH
Both the database and the user application make the following assumptions about the operating
environment.
The system can be described by the operating requirements associated with this document and in
the SRS. The system application in execution will have the necessary resources availed as
required. This entails sufficient memory and permanent storage space and the adequate CPU for
the application. The user application makes the following assumptions about its operating
environment. The user machine will have Microsoft access database components installed, as
they are required for the system implementation. The machine will also have necessary database
setup.
b) Goals and guide lines
The major goal of the Bus Booking Management System is to help automate the current manual
process of Horizon Coach making it extremely simple and easy to use. The system is meant for
the firms employees some of whom are not technically advanced. It is very important that the
prompts for the user be clear and concise since this will be the highest level of interaction
between the system and the user.
It is also important the series of prompts and responses be tested with the users before being
deployed.
The user should get a response in a timely fashion since users tend to lose interest if they have to
wait too long for the system to respond.
In this design, a minimum of data is transferred between the user and the database so as to
retrieve the necessary information and return the requested data to the user.
Other goals of BBMS include;
This system attempts to keep the user interface and application as independent as possible. All
the prompts and responses on the user are completely driven.
26
c) Database design
Database design refers to a process of modeling the information so as to meet the user
requirements. The process will be accomplished in three stages.
d) Conceptual design
Conceptual design refers to a process of constructing an abstract model of data to be included in
a database.
In creating the conceptual design for Horizon Coach, the following activities will be involved.
Identification of the entities: the various entities included in the BBMS are;
TRAVELL DETAILS
RESERVATION DETAILS
27
LOG IN
HOMEPAGE
e) Identification of relationships
This refers to an association between the entities.
For Horizon Coach, a passenger makes reservation as wishes. The Management therefore records
all details of the passenger and as well as those of the driver who will be on duty.
Passenger makes reservation
CUSTOMER
Checks
IN
Orders
Management
Delivers
Records
DETAILS
Delivered
SERVICE
f) Logical design
This part of the database design will entail selection of database model which is a collection of
concepts and rules for the description of the structures of the database. A relational database
28
model will be used for this case as it defines a database as a collection of tables containing all
data and their related properties.
f) Data normalization
This is a process of removing redundant data from the tables in order to improve storage
efficiency, data integrity and data scalability.
i.
Users table
This table stores users username and password which they use to log in to the system.
ii.
Service Information Table
To record place of departure and destination of a passenger.
29
iii.
Seat Reservation Table
To reserve passenger seats
30
vi.
Bus Table
To store bus information
31
File Security is defined by personal or sensitive data that is stored in files on the database. It is a
vital part of every data storage system. The administrative team will handle this for the BBMS
project by defining user groups and assigning permissions. This is a requirement of the system
because the staff will be using/sharing applications and files.
The User groups will be defined and consist of system administrators, managers, and staff.
Basically three levels of access. These levels will allow certain privileges and be controlled by
the rank in group permissions. Permissions will stem between read, write, and execute broken
down into access and ability to perform file/application manipulation. The categories are as
follows.
32
Decision -Indicate a point where the outcome of a decision indicates the next step.
User
Validate
username
&
password
Search
record
requested
33
Display
the
record
Start
System Flowchart
Enter to
Admin/Employee
Form
Enter
details for
the task
Validate/verify
details
Another
task
Database
Display
reports
YES
Update details &
process report
Print report
34
Exit
a. Context Diagram
The first level of DFD shows the main process within the system
Data store
Source
(sink)
-The nature of process is entered in the box along with the actor
Bus
Process reserve
Passenger
1.
1
Reserves
Staff (employee)
Sort Services
Passenger
1.2
Staff
1.3
Staff
Passnger file
Locate seats
36
1.
2.
3.
4.
5.
6.
7.
Login Form
Bus Form
Driver Form
Reservation Form
Passenger information Form
Service Information Form
Main Menu Form
LOADING BAR
The loading bar gives user some information before the program has started.
MAIN MENU FORM
37
The main menu is the homepage of the program. User can use it for navigation.
Login Form
38
User needs to enter his username and user full names should appear if his username is in
database. Then, user has to enter password correctly to login. If user enters incorrect password,
he will receive an error message as "Invalid Password". Finally, user can quit this program.
ADMIN FORM
39
If user logs in as Administrator, Admin Form will appear. This Form shows capabilities of
Admin.
EMPLOYEE FORM
40
If user logs in as system user, Employee Form will appear. This form shows capabilities of
Employee.
If user (Admin or Employee) clicks Make Reservation button, Service Information Form
needs to be filled.
42
After user fills Service information form, Passenger Information Form will appear. The
passenger information will be filled.
RESERVATION FORM
43
In this form, user needs to select an available seat. Seats color will change according to gender
in the Reservation Form. If it is reserved for a man, color will yellow; if it is reserved for a
woman, color will be pink.
PAYMENTS FORM
44
Payment form is used to make payment. Passenger can make payment using either cash or by Mpesa.
PAYMENT VERIFICATION(mpesa)
45
If passenger decides to pay using M-pesa, this form appears where he/she is given pay bill
number.
DRIVER FORM
46
If user clicks Add new driver button; Driver Form needs to be filled.
BUS FORM
47
When the company buys a new bus, the following form is used to keep the bus record in
database.
48
Admin can add new Employee into the system using the above form.
CHANGE PASSWORD
49
If user decides to change password, he can use the change password form
CHAPTER 5
TESTS PLAN
50
5.1Introduction
This is aimed at identifying and correcting errors. The major objective of this activity is to ensure
that the processing done by the application is correct and meets the objectives of the
organization. Test plan aids in effective and systematic testing of the system and it aims at
checking the errors of omission and commission that hinders the realization of the objectives. It
takes the bottom up testing approach.
5.2Importance of testing
1. Testing is used to find program errors on the system.
2. It is used to find undercover errors in a program through the use of defect testing.
3. Testing is also used to uncover new types of errors associated with new inventions and
technology
4. Testing aims at assuring quality by enforcing consistency and reliability.
5. It is used for both validation and verification to develop a product that meets user
requirement.
6. It is used to identify the best component combination for effective error identification.
5.3Test Plan Strategies
The importance of the test plan is to show how the system is to be tested and also gives precise
procedures to be followed during the test plan. The test date is identified, what is being tested
and the expected output as well as the actual input. Test plan is one of the standard documents
that should be produced in most software engineering projects. If the project does not have any
test plan this means that the software produced is of low quality. This may not be acceptable to
the user since it will not satisfy their needs. The test plan should be written as soon as you have
identified the requirements.
The system will be tested with sample data to see how it would handle input and output functions
as well as extreme data or conditions to determine the system behavior in overloaded situation
which will directly slow the system that behaves in failure or extreme situations.
51
Unit testing
Module testing
System testing
Integration testing.
5.3.1Unit testing
In this type of testing, the smallest testable parts of the system I.e. units are individually tested
and independently examined for correct functionality. This type of testing involves both the
positive testing and negative testing. This is important so as to make sure that the system
functions properly when used both correctly and incorrectly. In this case, the forms in visual
basic as well as the tables for the database will be tested individually to ensure that they are
compatible. This also applies to the operating system and the software applications.
5.3.2Integration testing
This is where two or more related programs are tested. The test will involve two types of
approaches i.e. the bottom-up approach that begins with the simplest task to the most complex
part .e.g. from passenger information table to the database and top-down approach that tests the
system from the complex task to the simplest unit of all.
We seek to verify that all the hardware function together without conflicting.
All the forms linked to the database should be connected well without any issue.
Ensure that all the programs work well to avoid interruption and there is no issue whatsoever
affecting database update.
5.3.3System testing
I this type of testing we shall test the entire system for functionality to ensure that the system can
process and handle large volumes of data quickly and efficiently. The test will be done with a
52
sample of some users who will use the system under test in its actual capability environment.
Possible problems are corrected before really conversion.
5.3.4Acceptance testing
This test will complete the formal testing process where all the users and the administrator will
use the system so as they get familiar with it. The users test the system before it is rolled out to
be fully used.
i.
Beta testing-Carried out at bus company premise. This involve delivering the system to
number of potential clients to use the system and report back to developer key
malfunctions with an understanding that the product is still being tested.
ii.
Alpha testing-It takes place at the developer site. It is the final testing before the
software is about to be released to the hospital for use.
5.4Test plan
Type of test
Test data
Tested area
53
Expected output
Result
Unit
testing Interface
and
logical
is interactive
to
use
testing
system users.
of
usability hence
increases
of accuracy.
accept Should perform
Numerical fields
Should
Text fields
numbers only.
Should accept
as expected.
only Should perform
text characters.
Login
Username
level
as expected.
and Security
password
Module testing
The
MDI Navigation
FORM
password is given.
of Sub menu to open
system
The
system
should
accessed
be
from
CODE
system
lowest level.
should Ensure
the
System
The
implementation
functions
as
required without
Command
Should
expected
operation
perform
problem.
as The files should
be manipulated
easily by use of
commands.
5.5Conclusion
54
All testing was done carefully and each test was up to the required standards of the users .error
tests may be suggested but the above mentioned are just sufficient to test. Testing is an essential
phase in system development and therefore it should be taken with a lot of interest.
CHAPTER 6
IMPLEMENTATION PHASE
6.1Introductions
The system has been developed using visual basic 6.0 and ms access database.
6.2Purpose
55
The document contains overviews of system, description of the major tasks that are required to
be done before the system is put into use.
6.3System description
This system will manage all bus booking activities, it will cover all passenger details and
maintaining all record about the drivers. This will be facilitated in the database which will
preserve their record for future reference. The system will processes data into useful information.
6.4System organization
In this section it provides a brief description of system components necessary to the
implementation of the system. The system will be installed in all causality offices head quarters
where all passengers can get access to the system.
The main functions that will be carried out by the application will be
1. Registering passengers
2. Booking and reservation of travelling tickets
3. Assigning passenger the available seats
4. Paying for services
5. Keeping booking record
6. Generating reports
7. Generating number which will be used for passenger identification
6.5 Implementation strategy
Direct conversion
This the best method of implementing the system by direct conversion .This was done because
the travelling company does not have a stable system at the moment as they still run their things
manually.
56
Justification
I.
The system will be implemented immediately after testing is done in team work.
II.
Currently there is no system that is used so there is no much cost that will be lost in
replacing the old system.
6.6Installations
A 150 GB
Core i3 and above processor
2 GB or 4 GB ram
Printer e.g. laser
Window exp or window 7
Microsoft access
6.8Review
The system developer and the users will analyze and compare the two systems and will come up
with changeover method used.
6.9Maintenance plan
The maintenance plan include all those thing that will be need for the project output once the
management has accepted them and how they will be achieved.
Identification of computer system
Hardware and other peripherals
57
Duration
installation 4days
preparation
Setting
Contact person
all
requirement in place
Installation
Reviewing
Objective
2days
and 3days
verification
Training
Installing
software
System developer
Measuring
system performance
4days
6.11Conclusions
The implementation of this system will help in handling daily operation efficiently and good
performance of the travelling agencies. It will improve record storage as all data will be stored in
the database.
6.12Recommendation
The system being a stand-alone it does not need to be online as all need that will be required for
a passenger you can book seats.
58
CHAPTER 7
7.0Codes
Codes for validating passwords and user name in the login form
Private Sub Cmdlogin_Click()
If rs_bus.State = adStateOpen Then rs_bus.Close
rs_bus.Open "Select * from users WHERE username='" & TxtUserName.Text & "'", datacon,
adOpenKeyset, adLockOptimistic
If rs_bus.RecordCount < 1 Then MsgBox ("User Not Defined"): Exit Sub
With rs_bus
If txtPassword.Text = .Fields("password") Then
If TxtUserName = "admin" Or TxtUserName = "ADMIN" Then
59
Unload Me
MDIForm1.Show
End If
End Sub
Sample codes for the admin form
Private Sub cmdadduser_Click()
MsgBox "Please Add New User", vbOKOnly
frmadduser.cmdsave.Enabled = False
frmadduser.Show
End Sub
Private Sub cmdseats_Click()
frmreservation.cmdok.Visible = False
Unload Me
frmreservation.Show
End Sub
Private Sub Cmdsearch_Click()
Unload Me
frmsearch.Show
End Sub
Private Sub Cmdactualservice_Click()
Unload Me
frmactualserviceinfo.Show
End Sub
Private Sub Cmdservice_Click()
Unload Me
61
frmservice.Show
End Sub
Private Sub Cmdserviceinfo_Click()
Unload Me
frmserviceinfo.Show
End Sub
62
Unload Me
frmadduser.Command1.Visible = False
frmadduser.cmdmovenext.Visible = False
frmadduser.cmdmoveprevious.Visible = False
frmadduser.cmddelete.Visible = False
frmadduser.cmdsave.Visible = False
frmadduser.cmdchange.Visible = True
frmadduser.txtfullnames.Enabled = True
frmadduser.txtPassword.Enabled = True
frmadduser.TxtUserName.Enabled = True
frmadduser.txtsearch.Enabled = False
frmadduser.txtfullnames = ""
frmadduser.txtPassword = ""
frmadduser.TxtUserName = ""
frmlogin.TxtUserName.Text = frmadduser.TxtUserName.Text
frmadduser.Show
End Sub
Private Sub cmdseats_Click()
frmreservation.cmdok.Visible = False
Unload Me
frmreservation.Show
End Sub
Private Sub Command1_Click()
Unload Me
64
MDIForm1.Frame2.Visible = True
MDIForm1.Label1.Visible = False
End Sub
Private Sub Command2_Click()
Unload Me
frmsearch.Show
End Sub
Private Sub Command3_Click()
Unload Me
frmserviceinfo.Show
End Sub
Private Sub Command4_Click()
Unload Me
frmdriver.Show
End Sub
Private Sub Command5_Click()
Unload Me
frmbus.Show
End Sub
Private Sub Command6_Click()
Unload Me
frmactualserviceinfo.Show
End Sub
Private Sub Image1_Click()
65
If MsgBox("Are you sure you want to LOG OUT", vbOKCancel, "Bus Booking Management
System") = vbOK Then
Unload Me
MDIForm1.Show
frmlogin.txtPassword = ""
frmlogin.TxtUser = ""
frmlogin.TxtUserName = ""
MDIForm1.cmdloggedin.Visible = False
MDIForm1.Command1.Visible = True
MDIForm1.Text1 = ""
MDIForm1.Frame2.Visible = True
MDIForm1.Label1.Visible = False
Else
frmemployee.Show
End If
End Sub
Sample codes for the add user form
Option Explicit
Dim rs_bus As New ADODB.Recordset
Private Sub fill()
txtfullnames.Text = rs_bus!FullNames
txtpassword.Text = rs_bus!Password
txtusername.Text = rs_bus!UserName
End Sub
Private Sub cmdcancel_Click()
rs_bus.Close
If frmlogin.txtusername = "admin" Or frmlogin.txtusername = "ADMIN" Then
66
Unload Me
frmadmin.Show
Else
frmemployee.Show
Unload Me
End If
End Sub
Private Sub cmdchange_Click()
cmdcancel.Visible = False
cmdexit.Visible = True
If rs_bus.State = adStateOpen Then rs_bus.Close
rs_bus.Open "Select * from users WHERE username='" & txtusername.Text & "'", datacon,
adOpenKeyset, adLockOptimistic
'If rs_bus.RecordCount > 0 Then MsgBox ("username Already Exists"): Exit Sub
With rs_bus
.Update
.Fields("password") = txtpassword.Text
.Fields("FullNames") = txtfullnames.Text
.Update
MsgBox ("Record updated Successfully")
End With
End Sub
Private Sub cmddelete_Click()
On Error Resume Next
Dim reply, optn As Boolean
With rs_bus
67
.MoveFirst
Do Until .EOF
If txtusername.Text = rs_bus!UserName Then
optn = True
Exit Do
End If
.MoveNext
Loop
If optn = True Then
reply = MsgBox("Do you want to delete this User?", vbYesNo + vbQuestion, "Delete")
If reply = vbYes Then
.Delete
txtfullnames.Text = ""
txtpassword.Text = ""
txtusername.Text = ""
End If
reply = MsgBox("User Deleted!", vbOKOnly + vbExclamation, "Delete")
End If
End With
End Sub
Private Sub cmdexit_Click()
rs_bus.Close
If frmlogin.txtusername = "admin" Then
Unload Me
frmadmin.Show
Else
frmemployee.Show
Unload Me
68
End If
End Sub
Private Sub cmdmovenext_Click()
On Error Resume Next
rs_bus.MoveNext
If rs_bus.EOF Then
MsgBox "You have reached the end of file!", vbApplicationModal, "End of file"
End If
If rs_bus.EOF Then
Exit Sub
End If
fill
End Sub
Private Sub cmdmoveprevious_Click()
On Error Resume Next
rs_bus.MovePrevious
If rs_bus.BOF Then
MsgBox "you have reached the end of file!", vbApplicationModal, "End of file"
End If
fill
End Sub
Private Sub cmdsave_Click()
If rs_bus.State = adStateOpen Then rs_bus.Close
rs_bus.Open "Select * from users WHERE username='" & txtusername.Text & "'", datacon,
adOpenKeyset, adLockOptimistic
If rs_bus.RecordCount > 0 Then MsgBox ("username Already Exists"): Exit Sub
With rs_bus
.AddNew
69
.Fields("username") = txtusername.Text
.Fields("password") = txtpassword.Text
.Fields("FullNames") = txtfullnames.Text
.Update
MsgBox ("Record Saved Successfully")
End With
cmdsave.Enabled = False
cmdcancel.Visible = False
cmdexit.Visible = True
Command1.Enabled = True
End Sub
Private Sub Command1_Click()
txtusername.Enabled = True
txtpassword.Enabled = True
txtfullnames.Enabled = True
txtusername = ""
txtpassword = ""
txtfullnames.Text = ""
cmdsave.Enabled = True
Command1.Enabled = False
End Sub
Private Sub Command2_Click()
Unload Me
frmadmin.Show
End Sub
70
End Sub
Sample codes for passenger information form
Option Explicit
Dim rs_bus As New ADODB.Recordset
Private Sub Command1_Click()
If rs_bus.State = adStateOpen Then rs_bus.Close
rs_bus.Open "Select * from passengerinformation WHERE id_number='" & txtIDnumber.Text &
"'", datacon, adOpenKeyset, adLockOptimistic
If rs_bus.RecordCount > 0 Then MsgBox ("Passenger Already Exists"): Exit Sub
With rs_bus
.AddNew
.Fields("id_number") = txtIDnumber.Text
.Fields("first_name") = txtfirstname.Text
.Fields("surname") = txtsurname.Text
72
.Fields("gender") = txtgender.Text
.Fields("phone_number") = txtphonenumber.Text
.Update
MsgBox ("Record Saved Successfully")
End With
End Sub
Private Sub Command4_Click()
Command1.Enabled = True
Command4.Enabled = False
txtfirstname.Enabled = True
txtIDnumber.Enabled = True
txtphonenumber.Enabled = True
txtsurname.Enabled = True
Option1.Enabled = True
Option2.Enabled = True
End Sub
Private Sub Image1_Click()
If MsgBox("Are you sure you want to LOG OUT", vbOKCancel, "Bus Booking Management
System") = vbOK Then
Unload Me
MDIForm1.Show
frmlogin.txtpassword = ""
frmlogin.TxtUser = ""
frmlogin.txtusername = ""
MDIForm1.cmdloggedin.Visible = False
MDIForm1.Command1.Visible = True
MDIForm1.Text1 = ""
MDIForm1.Frame2.Visible = True
MDIForm1.Label1.Visible = False
Else
frmpassengerinfo.Show
End If
74
End Sub
Private Sub Option1_Click()
txtgender.Text = "Male"
End Sub
Private Sub Option2_Click()
txtgender.Text = "Female"
End Sub
75
End Sub
Private Sub cmd10_Click()
Text1.Text = "Seat No 10"
If Label6.BackColor = vbYellow Then
cmd10.BackColor = vbYellow
ElseIf Label6.BackColor = &HFF00FF Then
cmd10.BackColor = &HFF00FF
End If
Label6.BackColor = &HC00000
End Sub
Private Sub cmd11_Click()
Text1.Text = "Seat No 11"
If Label6.BackColor = vbYellow Then
cmd11.BackColor = vbYellow
ElseIf Label6.BackColor = &HFF00FF Then
cmd11.BackColor = &HFF00FF
End If
Label6.BackColor = &HC00000
End Sub
Private Sub cmd12_Click()
Text1.Text = "Seat No 12"
If Label6.BackColor = vbYellow Then
cmd12.BackColor = vbYellow
ElseIf Label6.BackColor = &HFF00FF Then
cmd12.BackColor = &HFF00FF
End If
Label6.BackColor = &HC00000
End Sub
76
77
cmd24.BackColor = vbYellow
ElseIf Label6.BackColor = &HFF00FF Then
cmd24.BackColor = &HFF00FF
End If
Label6.BackColor = &HC00000
End Sub
Private Sub cmd25_Click()
Text1.Text = "Seat No 25"
If Label6.BackColor = vbYellow Then
cmd25.BackColor = vbYellow
ElseIf Label6.BackColor = &HFF00FF Then
cmd25.BackColor = &HFF00FF
End If
Label6.BackColor = &HC00000
End Sub
Private Sub cmd26_Click()
Text1.Text = "Seat No 26"
If Label6.BackColor = vbYellow Then
cmd26.BackColor = vbYellow
ElseIf Label6.BackColor = &HFF00FF Then
cmd26.BackColor = &HFF00FF
End If
Label6.BackColor = &HC00000
End Sub
Private Sub cmd27_Click()
Text1.Text = "Seat No 27"
If Label6.BackColor = vbYellow Then
cmd27.BackColor = vbYellow
81
cmd3.BackColor = &HFF00FF
End If
Label6.BackColor = &HC00000
End Sub
Private Sub cmd30_Click()
Text1.Text = "Seat No 30"
If Label6.BackColor = vbYellow Then
cmd30.BackColor = vbYellow
ElseIf Label6.BackColor = &HFF00FF Then
cmd30.BackColor = &HFF00FF
End If
Label6.BackColor = &HC00000
End Sub
Private Sub cmd31_Click()
Text1.Text = "Seat No 31"
If Label6.BackColor = vbYellow Then
cmd31.BackColor = vbYellow
ElseIf Label6.BackColor = &HFF00FF Then
cmd31.BackColor = &HFF00FF
End If
Label6.BackColor = &HC00000
End Sub
Private Sub cmd32_Click()
Text1.Text = "Seat No 32"
If Label6.BackColor = vbYellow Then
cmd32.BackColor = vbYellow
ElseIf Label6.BackColor = &HFF00FF Then
cmd32.BackColor = &HFF00FF
83
End If
Label6.BackColor = &HC00000
End Sub
Private Sub cmd33_Click()
Text1.Text = "Seat No 33"
If Label6.BackColor = vbYellow Then
cmd33.BackColor = vbYellow
ElseIf Label6.BackColor = &HFF00FF Then
cmd33.BackColor = &HFF00FF
End If
Label6.BackColor = &HC00000
End Sub
Private Sub cmd34_Click()
Text1.Text = "Seat No 34"
If Label6.BackColor = vbYellow Then
cmd34.BackColor = vbYellow
ElseIf Label6.BackColor = &HFF00FF Then
cmd34.BackColor = &HFF00FF
End If
Label6.BackColor = &HC00000
End Sub
Private Sub cmd35_Click()
Text1.Text = "Seat No 35"
If Label6.BackColor = vbYellow Then
cmd35.BackColor = vbYellow
ElseIf Label6.BackColor = &HFF00FF Then
cmd35.BackColor = &HFF00FF
End If
84
Label6.BackColor = &HC00000
End Sub
Private Sub cmd36_Click()
Text1.Text = "Seat No 36"
If Label6.BackColor = vbYellow Then
cmd36.BackColor = vbYellow
ElseIf Label6.BackColor = &HFF00FF Then
cmd36.BackColor = &HFF00FF
End If
Label6.BackColor = &HC00000
End Sub
Private Sub cmd37_Click()
Text1.Text = "Seat No 37"
If Label6.BackColor = vbYellow Then
cmd37.BackColor = vbYellow
ElseIf Label6.BackColor = &HFF00FF Then
cmd37.BackColor = &HFF00FF
End If
Label6.BackColor = &HC00000
End Sub
Private Sub cmd38_Click()
Text1.Text = "Seat No 38"
If Label6.BackColor = vbYellow Then
cmd38.BackColor = vbYellow
ElseIf Label6.BackColor = &HFF00FF Then
cmd38.BackColor = &HFF00FF
End If
Label6.BackColor = &HC00000
85
End Sub
Private Sub cmd39_Click()
Text1.Text = "Seat No 39"
If Label6.BackColor = vbYellow Then
cmd39.BackColor = vbYellow
ElseIf Label6.BackColor = &HFF00FF Then
cmd39.BackColor = &HFF00FF
End If
Label6.BackColor = &HC00000
End Sub
Private Sub cmd4_Click()
Text1.Text = "Seat No 4"
If Label6.BackColor = vbYellow Then
cmd4.BackColor = vbYellow
ElseIf Label6.BackColor = &HFF00FF Then
cmd4.BackColor = &HFF00FF
End If
Label6.BackColor = &HC00000
End Sub
Private Sub cmd40_Click()
Text1.Text = "Seat No 40"
If Label6.BackColor = vbYellow Then
cmd40.BackColor = vbYellow
ElseIf Label6.BackColor = &HFF00FF Then
cmd40.BackColor = &HFF00FF
End If
Label6.BackColor = &HC00000
End Sub
86
87
cmd52.BackColor = vbYellow
ElseIf Label6.BackColor = &HFF00FF Then
cmd52.BackColor = &HFF00FF
End If
Label6.BackColor = &HC00000
End Sub
Private Sub cmd53_Click()
Text1.Text = "Seat No 53"
If Label6.BackColor = vbYellow Then
cmd53.BackColor = vbYellow
ElseIf Label6.BackColor = &HFF00FF Then
cmd53.BackColor = &HFF00FF
End If
Label6.BackColor = &HC00000
End Sub
Private Sub cmd54_Click()
Text1.Text = "Seat No 54"
If Label6.BackColor = vbYellow Then
cmd54.BackColor = vbYellow
ElseIf Label6.BackColor = &HFF00FF Then
cmd54.BackColor = &HFF00FF
End If
Label6.BackColor = &HC00000
End Sub
Private Sub cmd55_Click()
Text1.Text = "Seat No 55"
If Label6.BackColor = vbYellow Then
cmd55.BackColor = vbYellow
91
cmd58.BackColor = &HFF00FF
End If
Label6.BackColor = &HC00000
End Sub
Private Sub cmd59_Click()
Text1.Text = "Seat No 59"
If Label6.BackColor = vbYellow Then
cmd59.BackColor = vbYellow
ElseIf Label6.BackColor = &HFF00FF Then
cmd59.BackColor = &HFF00FF
End If
Label6.BackColor = &HC00000
End Sub
Private Sub cmd6_Click()
Text1.Text = "Seat No 6"
If Label6.BackColor = vbYellow Then
cmd6.BackColor = vbYellow
ElseIf Label6.BackColor = &HFF00FF Then
cmd6.BackColor = &HFF00FF
End If
Label6.BackColor = &HC00000
End Sub
Private Sub cmd60_Click()
Text1.Text = "Seat No 60"
If Label6.BackColor = vbYellow Then
cmd60.BackColor = vbYellow
ElseIf Label6.BackColor = &HFF00FF Then
cmd60.BackColor = &HFF00FF
93
End If
Label6.BackColor = &HC00000
End Sub
Private Sub cmd61_Click()
Text1.Text = "Seat No 61"
If Label6.BackColor = vbYellow Then
cmd61.BackColor = vbYellow
ElseIf Label6.BackColor = &HFF00FF Then
cmd61.BackColor = &HFF00FF
End If
Label6.BackColor = &HC00000
End Sub
Private Sub cmd7_Click()
Text1.Text = "Seat No 7"
If Label6.BackColor = vbYellow Then
cmd7.BackColor = vbYellow
ElseIf Label6.BackColor = &HFF00FF Then
cmd7.BackColor = &HFF00FF
End If
Label6.BackColor = &HC00000
End Sub
Private Sub cmd8_Click()
Text1.Text = "Seat No 8"
If Label6.BackColor = vbYellow Then
cmd8.BackColor = vbYellow
ElseIf Label6.BackColor = &HFF00FF Then
cmd8.BackColor = &HFF00FF
End If
94
Label6.BackColor = &HC00000
End Sub
Private Sub cmd9_Click()
Text1.Text = "Seat No 9"
If Label6.BackColor = vbYellow Then
cmd9.BackColor = vbYellow
ElseIf Label6.BackColor = &HFF00FF Then
cmd9.BackColor = &HFF00FF
End If
Label6.BackColor = &HC00000
End Sub
Private Sub cmdok_Click()
If rs_bus.State = adStateOpen Then rs_bus.Close
rs_bus.Open "Select * from seatReservation WHERE seat_number='" & Text1.Text & "'",
datacon, adOpenKeyset, adLockOptimistic
If rs_bus.RecordCount > 0 Then MsgBox ("Seat Already Booked"): Exit Sub
With rs_bus
.AddNew
.Fields("seat_number") = Text1.Text
.Fields("seat_color") = Label6.BackColor
.Update
MsgBox ("Record Saved Successfully")
End With
Unload Me
frmpassengerinfo.Visible = False
frmpayments.Show
End Sub
95
Label6.BackColor = &HC00000
End Sub
Private Sub Form_Load()
rs_bus.CursorType = adOpenKeyset
rs_bus.LockType = adLockOptimistic
rs_bus.Source = "seatReservation "
rs_bus.ActiveConnection = datacon
rs_bus.Open
rs_bus.MoveFirst
fill
End Sub
Sample codes for module
Global datacon As New ADODB.Connection
Public dbpath As String
Public Sub ConnectDB()
dbpath = App.Path & "\database\BBMS.mdb"
With datacon
.CommandTimeout = 5
.ConnectionString = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source = " & dbpath & ";Persist
Security Info=False"
.CursorLocation = adUseClient
.Open
End With
'MsgBox ("Connected to the database")
End Sub
97
USER MANUAL
INTRODUCTION
Horizon Coach Booking Management system is developed using Visual Basic 6.0(VB) to assist
the administrator and users on their day to day operations in running of the company. The user
manual is designed to assist the user in the effective use of the system and to assist in user
registration showing all operations performed in the system and how to perform.
Specifications
This system has been built on specifications and some assumptions have been made which must
be known to the user.
Features of the system:
a) The system is capable of holding the passenger, driver as well as payment details and be
retrieved.
b) Records can be deleted or amended from the database to update records or edited the
system after a given period of time.
Requirements
Installation of the valid software is needed before user can interact with the system.
Hardware requirements
a) Pentium IV computer
b) Dual core or Intel Pentium processor(1.8 GHz)
c) 256 MB of RAM
d) 50 GB Hard Disc.
98
Software requirements
a) Windows 7 operating system
b) Microsoft Access
c) Microsoft Word
Running setup:
1. Switch on the computer.
2. Insert the CD/DVD containing the program in the disk drive.
3. The setup screen automatically appears on the screen, follow the instructions given that
guide you through the setup.
4. In the start menu click and go to the program, select the folder containing the system and
double click to open.
Getting started
99
Login
When you click on login button, Login form appears requesting one to enter a valid username
then after you press tab key, full names are displayed and you are now suppose to enter
password to get access to the system.
100
Navigation Buttons
Previous- It moves to the previous record.
CONCLUSION
Despite the hardships encountered in the entire development process the system has been
developed for Horizon Coach, thus enabling it improves its efficiency and effectiveness.
101
Maintenance and usage of the system will be easy as the documentation and user manual of the
system will be available to all users. Also there will be room for enhancement as this was
considered during development.
The system will offer better functionalities than the manual system, where the users of the
system will have to be computer literate so as to use the system effectively.
102
APPENDIX
Glossary
a) BBMS: is an abbreviation for Bus booking Management System
b) ADD- refers to a command that is used to include an item in the system.
c) SEARCH- used to find passenger, driver or user in the database.
d) RAM- refers to Random Access Memory i.e. type of memory that can be accessed
e) Scalability -refers to the ability to expand.
f) Debug -is the process of correcting errors generated during program execution.
g) An error- refers to a defect in a given program.
h) Run a program- is to initiate the execution of the set instructions.
i) Prompts will be defined as the point at which the computer and the user interact. These
are decision points in the control flow of the program, allowing the program to branch
based on the user response.
j) Commands- are the legal responses the user may make at any given prompt.
k) Administrator:- the personnel who are mandated with administrating and creation of
user accounts besides ensuring system security
l) Users: The personnel who interact with the current system as well those expected to
interact with the proposed system.
103
Gnatt chart
Task/deliverable
Number of weeks
1
Proposal document
Proposal
presentation
SRS document
System
design
specification
Logical design n
document
Physical
design
document
Implementation
and
test
plan
document
User
manual
documentation
Final document
Final Presentation
TROUBLE SHOOTING
104
10
11
12 13
Problem
Software not responding
Possible cause
Many processes re-scheduling
Remedy
Check your memory space and
use
Install an Anti-virus software
the screen.
Deletion
of
spontaneously
Pc shutdown
data
website
Ensure there is power on
Check cable.
Check your power supply unit
Effect
Mitigations
System Crash
Lose of data
Backups
Software Failure
Unexpected result
Program tests
Uncompleted Tasks
Activity schedule
Virus Attack
Corruption of files
REFERENCES
Shelly, B, G, Cashman, J, T and Rosenblatt, J, H, 2006, System Analysis and Design, sixth
edition, Thomson Course Technology, Massachusetts.
Software engineering 4th edition by Ian Somerville 2004 publisher Pearson education
international.
106