DEBRE MARKOS UNIVERSTIY BURIE CAMPUS

DEPARTMENT OF COMPUTER SCIENCE

PROJECT TITLE: ONLINE WEB BASED VEHICLE

MANAGEMENT SYSTEM FOR BURIE BUS STATION
NAME ID.NO

1. DESALEGN ABEWA……………..…………TER/141/10
2. YADESA GIRMA………………...………… TER/ 170/10
3. ESKEDAR FENTA……………………. ……..TER/144/10
4. DEREJE DEMISS …………………………..TER/140/10
5. MESFIN BIRHAN…………………………....TER/159/10
6. GETNET FENTA………………………….….TER/148/10
7. AGERBEJISH TEGEGNE …………………TER/121/10
8. BITIR AJANAW………………………………TER/089/09
9. BEWKET MENGISTIE ……………………TER/132/10
10. DIRIGU BEKELE ……..………………TER/142/10

1
Contents
CHAPTER ONE..............................................................................................................................................4
1.1. Introduction.................................................................................................................................4
1.2. Problem Statement............................................................................................................................4
1.3 .OBJECTIVE OF THE PROJECT.....................................................................................................5
1.3.1 General objective........................................................................................................................5
1.3.2 Specific objective...........................................................................................................................5
o Modeling software.....................................................................................................................6
o Designing Software....................................................................................................................7
o Implementation Software..........................................................................................................7
 To write android java and xml codes and PHP codes..................................................................7
1 .6 Data collection and Methodology and approaches........................................................................7
1.7.1 Operational feasibility..............................................................................................................8
1.7.2. Technical feasibility.......................................................................................................................8
1.7.3. Economic feasibility................................................................................................................8
2. System analysis........................................................................................................................................9
2.1. Overview of existing system........................................................................................................9
Proposed system....................................................................................................................................10
2.2. System requirement specification...................................................................................................11
2.2.1. Functional requirements...........................................................................................................11
The system shall allow:-....................................................................................................................11
2.2.2. Non- functional requirements..................................................................................................12
2.2.3. Business rules.........................................................................................................................13
2.2.4. Change cases............................................................................................................................13
2.3 .System Requirement Analysis........................................................................................................14
2.3.1 .Actors and use case identification.....................................................................................14
2.3.2. Activity Diagram.....................................................................................................................28
CHAPTER THREE........................................................................................................................................32
3 .system Design........................................................................................................................................32
3.1. Design of Class Diagram................................................................................................................32

2
4.0 INPLEMENTION....................................................................................................................................44
5.0 TESTING...............................................................................................................................................64
6. Conclusion and Recommendations.......................................................................................................66
6.1 Conclusion.......................................................................................................................................66
6.2Recommendation.............................................................................................................................66
References.................................................................................................................................................67

3
CHAPTER ONE
1.1. Introduction

Online vehicle management system is a system which concerned with how vehicles could be
managed and controlled in android based way by the employees of the organization. Currently,
the vehicle gives service use manual way of information gathering and documenting, no reliable
communication between different offices, as well as there is lack of security, difficult to
coordinate, and to identify the owner of the vehicle.

This project will intend to advocate for the need of bus station to change the manual system to
automated system vehicle management system.

Automated systems make it possible to have a better accuracy, to increase the quality of the
work, to reduce the time it takes, to minimize cost, to keep the security and organization of data
in most advantageous condition, to make data transfer easier and also make it possible to save
and back up all transactions in case of vehicle management to keep the data in a centralized way
which is available to all the users simultaneously.

1.2. Problem Statement

In the current vehicle management system, information exchange and service control is process
in manual way. There are various problems that vehicle management system faces due to the file
manual handling of its daily activity.

 Not sequenced flow of information during retrieve.

 It’s a time-consuming process to assign vehicles and to generate required reports.
 Difficulty to get the required detailed information about specific vehicle.
 Employees and customer couldn’t get high satisfaction .
 There is no effective coordination between various employers.

4
 1.3 .OBJECTIVE OF THE PROJECT
1.3.1 General objective
The main objective of this project is to develop online web based for Vehicle Management
System.

1.3.2 Specific objective

The specific objectives of the project, which will be done in order to achieve the general
objective are.

 Identifying existing System work flow

 Analyzing the existing systems problem
 Analyze gathered information using VMS document.
 Develop the proposed system.
1.4. Scope of the project

The system contains modules that can handle vehicle and service requester like:

 Login page: The login page contains the user name and password and users should enter
the correct username password and their privilege correctly to get the page that he wants.
 Emergency report: allows the passengers and the drivers to report emergency conditions
remotely which are happened in anywhere of their action.

 Generate and send reports: It allows manager generating report for the tasks performed
and if there is any difficult problem.

 View notification and comment: It allows manager to see the comments that are
submitted from the driver.

 Vehicle maintenances: Vehicles should be maintained when they are damaged or based
on schedule.
 Vehicle registration: Allow the Manager to register vehicle.

5
  Manage user account: Manager create & deactivate account for users and users can
update their account.

 Make reservation:-the system supports the actors of the system i.e. managers to make
reservation for passengers.
 Show availability of ticket:-the proposed system of the project is support the passengers
to see availability of tickets in the system.
 Show availability of seat:-the system show availability of seat numbers of the
passengers so the passenger see his/her own seat numbers based on the
System required personal information from users.

Out scope of this project are the functions such as detecting current location, sensing
coming car and arriving car as these functions require sensor and GPS technology.

 1.5 System requirement

1.5.1. Hardware Requirement
 Computer: To develop the documentation as well as the application.
 Flash: Used as move data from one to other.
 CD: Used as a backup.
1.7.1.2. Software requirement
o Modeling software
EDRAW Max and visual paradigm.

 Used to draw diagrams like use case diagram and activity diagram.

o Designing Software
MySQL server

 This software will used for designing Database.

o Implementation Software
Operating System: Windows 10

 To have good speed of operations or execution time of tasks.

6
 Notepad++

 To write PHP codes.

1 .6 Data collection and Methodology and approaches.
 Interview
 Existing scenarios
We gathered information by asking person in vehicle management offices at BURIE bus station.
 Document analysis
To get more secondary source information and ideas about the vehicle
management systems, we referred project report documents and other reading
materials that is helpful to develop this system.

 Practical observation
We observed all the activities that are performing and notice down how they
did. It helps us to get real information how the organization performs its
function and this helps to strength the data that gathered through interview and
document analysis. Feasibility analysis

1.7. Feasibility study

Here we are going to see whether our project is technically, economically and operationally
feasible or not which enables us to decide to continue or halt the project.

1.7.1 Operational feasibility

This vehicle management system is operationally feasible and it doesn’t affect the organization
structure. It transforms the current manual transportation activities to a well-organized system
by reserving seats, sending maintenance request, reporting emergencies and other common
activities. The system is also operationally feasible in terms of reliability, maintainability,
supportability, usability and flexibility. The system will be:-
 Operated by any users
 User friendly

7
 Easier for navigate the page

1.7.2. Technical feasibility

Our project is technically feasible, because it can generate outputs in a given time, easy to
communicate and generally it satisfies the end-user’s requirement. And also our system can
work with the current technology and our focus is to develop well organized dynamic
application that is technically efficient and effective for managing the transportation sector.

1.7.3. Economic feasibility

In existing manual vehicle management system the stakeholder’s have to maintain a large
number of papers or forms. This can be avoided by putting the data in the computer format that
is cheaper and reliable. Since the cost of resources for development of system satisfies the
organization, the software is economically feasible. It has two benefits.
 Tangible benefits:-
 Reduction of resource wastage
 Reduction of space needed to record data.
 Intangible benefit:-.The system we are developing has many intangible benefits that revolve
around mental satisfaction of users. those are:-
 Give better and effective service
 Error reduction.
 Increase efficiency
 Increase security

1.8 Significance of the project

After development of the new system: it gives the following advantages.

 Passengers get high satisfaction.

 High coordination between various employers.
 To have good authentication and security.

 To make easy and fast report generate

 Easy to process requests.

 Easy to manage historical data in secure manner.

8
 Minimizes cost of operations and the work load.

 Avoiding improper resource consumption and data loss.

 To make easy vehicle assignation.

 Easy to get the required detailed information about specific vehicle.

Chapter two
2. System analysis
2.1. Overview of existing system
 Currently Vehicle Management system uses paper based documentation

or manual system approach to record and report its file. There are
activities and tasks that can be taking care off by the Ticket seller, driver
and technician like:
 Report preparation:-Report can be prepared in the form of paper documentation.
 Document collection:-document can be collect from the prepared report according to
their function and submitted time to allocated place (it may be shelf).
 Order driver:-based on the request service the manager order the driver by giving the
word command or written command.
 Order technician:-The manager orders the mechanics by looking the car that need
repair and maintain service for proper function.

9
  The officer Evaluate the requester question forward evaluated question to manager.
 Assign Car:-when the service requested, the manager arranges and assign the car to
provide service.
 The staff request the car service to officer for his/her student for the Purpose of
Training, trip and journey for the practical learning.
 The messenger circulates the forms and documented report from one office to
another.

Users of the existing system

The followings are players/actors in the existing system:

 MANAGER: The listed below are the duties of the manager.

 Order driver
 Give commands for mechanics according to their task.
 Register the car
 Calculate fuel balance
 Prepare exit permission
 Driver: The duty of driver listed below
 Drive
 Check the vehicle regularly
.

Proposed system
In basis of understanding the current manual system and identifying all the problems occurred
during over all activities of the existing system, the project team has decided to design an
automated system model as solution. Since the client server model fully flagged online at any
time, it will solve the problem and limitation of the current manual system of vehicle
management system.
 The administer manages all works related to the system like creating and deleting
manager, driver, officer, staff and mechanics account, generate report and register
employee.
 The Vehicle manager in system register vehicle, update vehicle record, view vehicles
information, manage request, assign vehicle(i.e. the system give commands and response
for the drivers, mechanics and officer).

10
  The one who drives the car, in this system the driver views notification and request
maintenance record for the mechanic.
 Mechanics view maintenance request and generate maintained report.

2.2. System requirement specification

2.2.1. Functional requirements

The functional requirements of the system describe the necessary functions for which the system
is expected to fulfill. The system describes a single and well defines goal of android application

for vehicle management system, and the steps involved to reach this goal. A function is
described as a set of inputs, the behavior and output. The requirements specified are helpful to
clearly understand the scope and the objective of the system, and consequently this will be
helpful for designing the system effectively. The proposed system meets the following
functionalities:-

The system shall allow:-

 Account management:
 Create account
 Update account
 Delete account

 Registration
 Register vehicle
 View information
 View notification
 View maintenance request
 View comment
 View seat reservation
 Request service.
 Request maintenance.

 Approve request
 Send notification.
 Give comment

 Assign vehicle.

11
  Reserve ticket:-
 Generate report.
 Send comment and View comment.
 See availability of seats.

2.2.2. Non- functional requirements

Non-functional requirements that specify criteria’s that can be used to judge the technical
operation of a system, rather than specific characters. This should be opposes with that of
functional requirement that define specific behavior.

In General, non-functional requirement

 Security:
 Authentication and authorization: deals with identifying a user
and what a user is allowed to do respectively.
 Session: once the user’s logout from the system then the session do not
enable to return to the previous page
 The information provider by the user should be authentic which protect
the system from external attack and spamming.

 Performance:

The response time for loading and processing a given task is very fast
and triggered by a single click.
 The system should provide the services in considerable time interval.

 Reliability:
 Increase reliability of the system by removing commonly made errors and
feeding correct inputs for processes.
 Provides to the user correct information.
 The system notifies users to correct the input data when they enter wrong
inputs.
 The system will be able to meet specified objectives as well as the
expectations of the customer.

 Usability: User interface will be user friendly, so user can familiar to the system and
easy to use.
 Flexibility: The system is flexible for all users when they inter the correct.

12
2.2.3. Business rules
It is the collection of rules and regulations of the vehicle management system that tells the users
follow the activities.

 Rule 1: Users of the system must have proper user name and password in order to login
the system.
 Rule 2: The manager should check the fuel balance of the car while the car
travelled.
 Rule 3: The manager must generate report in case of some conditions occur.
 Rule 4: Vehicles should be maintained when they are damaged or based on
schedule maintenance report.
 Rule 5: The manager should approve the request of the officer and staff.
 Rule 6: System assigned the vehicle and automatically sends notification for driver
and requester office.

2.2.4. Change cases

 Likely future changes (update) to either the system, in terms of its capabilities and
properties are computable with the new version.
 The system will promote related international rules and regulations.
 Used to describe new potential requirement for a system or modification to
existing requirements.
 Describes a potential requirement that your system may need to support in the
future.

2.3 .System Requirement Analysis

2.3.1 .Actors and use case identification
Table 1: actors table

List Of Actors With Function

13
 Admin Manager Driver Officer Staf Mechanic passengers
f

Request  
service

Manage  
request

Payment 
status

Assign 
vehicle

Manage 
account

Register 
vehicle

Submit  
comment

View 
comment

Check fuel 
balance

Update      
account

14
Maintenance 
request

View 
maintenance
request

Route of 
information

Create user 
account

Manage 
account

View route 
of
information:

Give 
comment

Generate  
report

Get exit 
permission

See 
availability
of tickets.

15
See 
availability
of seats.

Send report 

View   
response

 Use case identification

Each Use Case describes the functionality to be built in the proposed system, which can include
another Use Case's functionality or extend another Use Case with its own behavior.

The most important and basic use cases of this system are the following:-

 Login
 Create account
 Delete account
 Update account
 Check fuel balance
 Register vehicle
 View vehicle Information
 Generate report

16
 View request maintenance
 Request service
 View Response
 approve request
 Assign vehicle
 Get exit permission
 Request maintenance
 Send report
 View notification
 Sea availability seat
 Sea availability of tickets
 View route information
 Payment status
 Submit comment
 View comment
 Logout

17
Use case Descriptions

Create
Extend Request
Maintenance
Extend
Manage Delete
Account Account Send
Logout Include
report
Extend
Driver
Include
Include
Register Submit
Extend
Vehicle comment
View Include
vehicle Include

Informatio Include
View
n Include response
Assign Login
Vehicle Include Officer
Include
Include
Approve
Request Include
Include
Include View
Include
Notificatio
Include
Manager Include n
Check fuel
Balance
Update
account
Generate Includ
Report e

Request
Get exit service
Permission Mechanics

View
comment

18
Figure 1: use case diagram

Use case description for Passenger

Give comment
Include

Report Login
emergency Include

Include

Passenger Submit
comments
Include

See availability of
seats Include

See availability of Tickets

Figure : use case diagram

19
Use case description includes use case Id, use case name, particular actors, descriptions of the
use case, preconditions, basic course of action(actor action and system response), post
conditions, flow of event and whatever which is important in modeling the user go.
Use case name Login

UC ID UC 1

Actor Administrator, Manager, driver, officer, passenger, staff and mechanics

Precondition They must have user account, user name and password.

Basic course of User action System response

action

1.Users click on login button .

3.User insert user name and password 2. The system displays the
login form.
4. User click login button.
5. System checks the user
6. The system displays the name and password.
appropriate user page. 7. Use case ends.

Alternative course 5.1. If username and password is not validating, the system display
of action login fail and return to basic course action 3.

Post condition The authenticated user gets the appropriate page.

Table 2: Use case description of login

20
 Use Case ID: UC-ID2 Use Case ID: UC-ID2

Use Case Name: See availability of seats.

Actor: Passenger Actor: Passenger

Description: Description: The User must know detail of seat availability

Preconditions: First The user must login into the system and know the information

Post conditions: The availability of seat information must added into the database

User action System action

1.User opens the 2. The system will display documented

documented page of page seats availability.

seat. 4. The system checks the correctness of

3. User clicks the view the input data.

button 5 The system display availability seats.

Normal Course of 6. Use case end.

Events:

Alternative Courses: A4: User enters invalid data

A4:1The system displays error messages

A4:2 Go to step 2

Table 3:use case description for availability of seats

21
Use case name: Manage account

Use case ID: UC 2.

Actor: Administrator

Description Administrator r creates account for deriver, officer, mechanics, and staff.

Pre-condition: Administrator open and login into the system

User action System response

1. Administrator select create user
account link.
Basic course of
action 3. Administrator enters user information.
2.System display creates
4. Administrator click submit button.
Account form.
7. Use case end
5. System checks user information.

6. System creates successfully user

account.

Alternative 5.1. The system display error messages that the input values are incorrect return

22
course of to step 3.
Action
Post-condition: User account is created.

Table 4: Use case description of create account

Use Case ID: UC-ID5 UC-ID5

Use Case Name Use Case Name: view route information

Actor Passenger

Description The User should view the route information.

Preconditions The user must be registered and login into the system

Post conditions The route information details must added into the database

User action System action

1. User opens the 2. 2. The system wills the documented

documented page information.

of route 4. The system checks the correctness of th

information. input data.

3. User fills the 5. The system display “fills successfully”

Normal Course of form and submits.

Events: 6. Use case end.

23
 Alternative Courses: A4: User enters invalid data

A4:1The system displays error messages

A4:2 Go to step 2

Table 5:use case description of view route information

Use case name: Update account

Use case ID: UC 3

Actor: Manager, driver, officer, staff, passenger , and mechanics

Description Manager, driver, officer and staff update their account

Pre-condition: User open and login into the system

User Action System Response

1. User select update user account link.

Basic course of action 3. The user inserts account type, user name 2. System display updates
account form.
e, password, and other user information.
5. System checks the new
4.User click update button
account information with the
6. The systems save the new account existing account in database.

to the existing the database.

7.Use case end

Alternative course of 5.1. The system display error messages that the input values are incorrect.
Action

24
Post-condition: Account is updated

:
Table 3 Use case description of update account

Use case name: Delete account

Use case ID: UC 4

Actor: Administrator

Description It allows the Administrator to delete user account from the system.

Pre-condition: The Administrator activates and login in to the system

User action System

response

1. Administrator Select deactivate

account link.
Basic course of action
3. Administrator select users and click
2.System displays
deactivate button.
Deactivate user account
5. Administrator click yes button.
information.

4.System display
7.Use case end recommend page.

6.Systems deactivate
user account

25
Alternative course of 5.1. If Administrator click no button, then system back into basic course
Action of action 3.
Post-condition: Account is deactivated.

Table 4: Use case description of delete account

Use case name: View Vehicles info.

Use case ID: UC 5

Actor: Manager

Description It allows manager to see the detail information of the vehicles.

Pre-condition: Manager open and login into the system.

User action System response

1. Manager click on view 2. The system displays the
vehicle Information link. vehicle form.
Basic course of action
3. Manager fills the required 5. The system displays the detail
fields. information about the vehicles.
4...Manager click search
button.

6.Use case end

26
Alternative course of 5.1The system display error messages that the input values are
Action incorrect or fill input value and display Basic course of action 4.
Post-condition: The managers get vehicle information.

Table 5: Use case description of view vehicle information

Use case name: Register vehicle

Use case ID: UC 6

Actor: Manager

Description Allow the Manager to register vehicle.

Pre-condition: The manager activates the system and login to the system.

User action System response

1. The manager 2.The system will display

Basic course of action Selects the register car link. the vehicle registration form.

3. The manager fills the required fields.5.The system checks the

4. Manager click submit button. input data.

7. Use case ends. 6.The system displays

the successful notification

Alternative course of 5.1. The system displays incorrect entered data message and return
Action to path 3
Post-condition: The vehicle is registered.

27
 Table 6: Use case description of register vehicles

Use case name: Assign vehicle.

Use case ID: UC 7

Actor: Manager

Description It allows the manager to assign car for the requested service

Pre-condition: Manager open and login into the system

User Action system response

1. The manager click assign 2. System display assign vehicle

vehicle link. page .
Basic course of action
3.Manager selects and inserts 5. System validates selected and
required data inserted data.

4.The manager click assign 6. System assigned the vehicle and

button. automatically sends notification for
driver and requester office.

7. Use case ends.

Alternative course 5.1.The

of system displays error message incorrect entered data message
Action and return to path 3

Post-condition: Vehicle will be assigned.

28
Table 7 : Use case description of assign vehicle

Use case name: Calculate fuel balance

Use case ID: UC 8

Actor: Manager

Description The fuel balance form takes and compares two reading of current
entry and the previous saved reading and produces fuel balance data.
Pre-condition: Manager must get information of vehicles status.
User action System response
1. Manager enters username and 2. System checks the
password. validity of username and
Basic course of action
4. Manager enters input value. password and then
6. The system save the difference checks for authentication
and store the status of fuel. and authorization.
7. Use case ends. 3.System display fuel
balance page
5. System checks the
validity the input data.
.

Alternative course 2.1

of If the user name and password is not validated and verified then
Action the system responds error message and return.
5.1 If the input is invalid or incorrect the system displays “invalid
input” message and return.
Post-condition: The fuel balance will be calculated.

29
 Table 8: Use case description of check fuel balance

Use case name: Request maintenance

Use case ID: UC 9

Actor: Driver

Description A driver formulate request to repair vehicle. The request describes briefly the vehicle
problem.
Pre-condition: Driver is registered.
User action System response
1The driver click request maintenance 2.System display vehicle
link. maintenance form
Basic course of action
4.System checks validity of the
.
information
3. Driver enters information related to
5.System stores the data in the
the maintenance request for the
database.
vehicle.
6.Use case ends.
Alternative course 4.1.
of If the data is invalid or incorrect the system displays “invalid input” message.
Action

Post-condition: Maintenance record will be created.

:
Table 9 Use case description of request maintenance

30
Use case name: Request vehicle service

Use case ID: UC 10

Actor: Officer and staff

Description It allows the staff (i.e. employee under officer) request service to
officer and the officer directly request vehicle service to manager.
Pre-condition: Officer and staff enter user name and password.

1. Officer and staff enter user name and 2. System checks the
password. validity of username and
Basic course of action
3. The officer and staff click the password and then checks
request service button. for authentication and
5.Officer and staff fill required vehicle authorization.
information on displayed form. 4. The system displays
6. User clicks send request button. request service form.
8. Use case ends. 7.System checks validity
of the information
8. The system displays
sent message
acknowledgement.

Alternative course 2.1.

of If the user name and password is not validated and verified
Action then the system responds error message and return.
7.1 If the data is invalid or incorrect the system displays “invalid
input” message.
Post-condition: The request is sent.

31
 :
Table 10 Use case description of request services

Use case name: Generate report

Use case ID: UC 11

Actor: Manager

Description It allows administrator and manager generating report for the tasks
performed and if there is any difficult problem.
Pre-condition: The admin and manager open the system and login to the system
User action System response
1. The user must log to his/her 3. The system displays the
page options (criteria).
Basic course of
2. The user select generate 5. System check selected
action
report link. criteria by the user.
4. The user selects the criteria 6. The system displays the
from the given options and clicks information to the user.
on Display button.
7. Use case ends.

Alternative course5.1.
of The system displays error message as invalid selection.
Action

Post-condition: The report will be generated.

32
Table 12: Use case description of generate report

33
Use case name: View maintenance request

Use case ID: UC 12

Actor: Mechanic

Description This use case describes viewing maintenance request to repair the vehicle.

Pre-condition: The mechanics open the system and login to the system
User action System response
1. User enters username and password. 2. System checks the validity
4. Mechanic click approve button. and then authentication and
Basic course of action
6.Users click ok button authorization of username and
password.
8. Use case ends. 3. System display viewing
maintenance request page.
5. System display
recommended page.
7. System automatically
updates the vehicle condition
and sends response to driver.

Alternative course 2.1.

of If the username and password is not validated and verified, system
Action displays error message
7.1. If user click cancel button, the system not update and send .
Post-condition: The Vehicle’s problem will be viewed.

:
Table 11 Use case description of view maintenance request

34
Use case name: Submit Comment

Use case ID: UC 13

Actor: Driver, officer

Description The driver and officer can give comment or feedback to manager.

Pre-condition: Driver and officer must have valid Email address.

User action System response
1. The driver and officer initiates to give
3. The system displays the form.
comment.
Basic course of action 5. The system validates the entered
2. The driver and officer click on the comment
information.
link.
6. The system display as your comments
4. The driver and officer insert all the required
has been been sent.
fields.

7. Use case ends.

35
Alternative course 5.1.
of The system display error message and give a chance to retype.
Action

Post-condition: The driver and officer sends comment to the manager.

Table 12: Use case description of submit comments

Use case name: View Comment

Use case ID: UC 14

Actor: Manager

Description It allows manager to see the comments that are submitted from the driver.

Pre-condition: Manager must have a full privilege to read the comments.

User action System response
3. The system reorders the
1. User log to his/her page. comments according to the time of
Basic course of action
2. User clicks on view comment link. delivery.

4. User starts to view the comments.

5.Use case ends

Post-condition: The managers view the submitted comments.

Table 13: Use case description of view comments

36
Use case name: Logout

Use case ID: UC 15

Actor: Admin, manger, driver,passenger, officer and staff

Description The user logouts when he/she wants to

back home page or exit from the system

Pre-condition: Users finish their activities.

User action System response

Basic course of action 1. User clicks the log out 2.The system
button responds to the
4.Use case ends requested action.
3.System returns the
users to the login
page.

Post condition User logs out or sign out.

37
Table 14: Use case description of logout2.3.2. Sequence Diagram

A sequence diagram shows object interactions arranged in time

sequence. It is dynamic model of use cases, showing the interaction
among classes during a specified time period. A sequence modeling in
our system is used to formalize the behavior of the system and to
visualize the communication among objects. It helped us to identify
additional objects and participate in the use case. This phase of the
document ties uses cases with objects and shows the behavior of a use
case is distributed among its participating objects.

38
Figure 2: Sequence diagram for create account

39
Figure 3 : Sequence diagram for login

40
Figure 4: Sequence diagram for register vehicle

41
42
Figure 5: Sequence diagram for view vehicle information

43
Figure 6 Sequence diagram for logout

44
2.3.2. Activity Diagram

Activity diagram is another important diagram in UML to describe dynamic aspects of the
system. Activity diagram is basically a flow chart to represent the flow form one activity to
another activity. The activity can be described as an operation of the system. So the control flow
is drawn from one operation to another. This flow can be sequential, branched or concurrent.
Activity diagrams deals with all type of flow control by using different elements like fork, join
etc.

The purposes of activity diagram can be described as:

 Draw the activity flow of a system.

 Describe the sequence from one activity to another.
 Describe the parallel, branched and concurrent flow of the system.

Home page
Home page

Admin login page

Enter user name and

Password

Submit

45
System display creates account form.
Incorrect Validate Correct
Figure 7: Activity diagram for create account

Home page

User login page

Enter user name and 46

password
Figure 8: Activity diagram for Login

Home page

Manager login page

Enter user name and

Password

Submit

47

Incorrect Validate Correct Display vehicle registration page

Figure 9: Activity diagram for register vehicle

CHAPTER THREE
3 .system Design
3.1. Design of Class Diagram
The class diagram is a static model. It represents the static view of an application. Class diagram
is not only used for visualizing, describing and documenting different aspects of a system but
also for constructing executable code of the software application. The class diagram describes
the attributes and operations of a class and also the constraints imposed on the system. The
classes diagrams are widely used in the modeling of object oriented systems because they are the

48
 only UML diagrams which can be mapped directly with object oriented languages. The class
diagram shows a collection of classes, interfaces, associations, collaborations and constraints.

Request
maintenances

-Full
Assign vehicle User Reservation
User name: :varchar(45)
-Request:varchar(35) Seat
Date:Datetime
Comment -Request -sid:int
- Reason: :varchar(45) -seatno:int
-Name:string -Vehicle
user_id:varchar( -user_id:string Status:varchar -reservedate:date
45) -sex:string
-phone no:string -name:string M
+get sid() -reservetime:time
+get seatno() -email addres:string
-plate -username: string -email: :string -phone int
Manage account -passward:string -date;datetime
no:varchar(45) ticket amount:int
ticket no :int
+view request()
-Full +mainteinance_reque
name: :varchar( st()
+send_response()
submitcomment ()
M
45) view comment()
Search
- +login ()
-create account +update account () M
-update account Submit 1
-delete account +assign vehicle() M request M Reserve
View
M
+send notification()
M 49
Assign
I
manages n Give
1 1
1 1 h View 1 1
e
r
Attribute Purpose type
Table17:
User-id To identify the user Varchar(20)
Description of
Full Represents the name of Varchar(15) Assign vehicle
the user class
Name

Starts Represent where the Varchar(15)

car starts

Arrival Represents the Varchar(15)

destination place of the
car

Times Represents when it Varchar(15)

reaches from starts to
arrival 50

Reason It describes for what Varchar(15)

purpose it go
Table 15: table of Assign vehicle method

Method Purpose

assign vehicle() Used to assign vehicle

send notification() Used to send notification for

users

Table 16: description of comment class

attribute Purpose type

Name Represent lame of the user Varchar(45)

email Represent the address of the user Varchar(25)

message Represent the idea of the sender Varchar(250)

Date Describes the date Varchar(45)

:
Table 17 description of comment method

method Purpose

51
submit comment() Used to send comment

view comment () To view comment

Table 18: description of vehicle registration class

attribute Purpose type

model Used to describe the model of the car Varchar(20)

Plate no Used to identify the car from the other car Varchar(30)

Owner Used to owner of the car varchar(18)

Capacity Used to describe the speed of car varchar(23)

Production date Used to when it is made varchar(30)

insurance Used to help the owner of car during emergency varchar(30

Table 19: vehicle registration method

Method Purpose

register car() Used to register car

View vehicle info() Used to view vehicle info

Table 20 : Ticket seller class

Attribute Purpose type

Name Represent manager name Varchar(30)

User-id Used to identify the manager Varchar(15)

Sex Used to gender of manager Varchar(8)

52
Phone no manager phone no Varchar(20)

Username Used to describe user name Varchar(30)

Password Used to log into the system Varchar(80)

:
Table 21 Ticket seller method

Method Purpose

login() To enter the system

Table 22: driver class

Attribute Purpose type

Name Describes the driver name Varchar(30)

User-id Used to identify the driver Varchar(15)

Sex Tells the gender of the driver Varchar(8)

Phone no Used to know the phone no Varchar(20)

Username Identify the username of the driver Varchar(30)

Password Used to login and access the system Varchar(80)

Table 23 : driver method

Method Purpose

submit comment() Used to send comment

send report() Used to send report

Maintenance request() Used to ask maintenance request while

vehicle damaged

53
Emergencyreport() Used to send emergeny conditions

:
Table 24 Send report class

Attribute Purpose Type

Full name Describes the sender name Varchar(30)

Plate no which identifies where the vehicle varchar(30)

was registered

Date This identifies when the report sent. Varchar(45)

:
Table 25 Send report method

Methods Purpose

Update User status Used to update the user status

Update vehicle status Used to update the vehicle status

3.3 User Interface Design

54
Fig 3.1 welcome page

55
Fig 3.2 log in as page

56
Fig 3.3 first officer page

57
CHAPTER 4
4.0 INPLEMENTION

4.1 PROGRAMING LANGUAGE USED

 We use MYSQL database for storage of data.

 We used php for communication with the server

4.2 ALGORITHM USED For Log in

Login (Username, password):- that pass/checks three arguments for login function.
 If length of username and password==0:- Check that Zero length is not allowed.
Display error message “username and password cannot be empty”.
Stay in the same page and the actor fills the form after he or she knows the field is required.
The system retrieves username and password which the actor submits.
 If username! =username or password! =password or status! =active: - Authentications for
the right actor.
Display error message “Invalid username or password or your account is deactivate”.
 If his/her account detail is correct access the required page.

4.3 SAMPLE CODES

Sample code
<?php

include("connection.php");

session_start();

if(isset($_SESSION['user_id']))

$mail=$_SESSION['user_id'];

58
} else {

?>

<script>

alert('You Are Not Logged In !! Please Login to access this page');

alert(window.location='login.php');

</script>

<?php

?>

<html>

<head>

<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

<title>Vehicle Management System</title>

<link href="tooplate_style.css" rel="stylesheet" type="text/css" />

<link rel="shortcut icon" HREF="12.jpg" />

<!-- Start WOWSlider.com HEAD section-->

<link rel="stylesheet" type="text/css" href="engine1/style.css" />

<script type="text/javascript" src="engine1/jquery.js"></script>

<!-- End WOWSlider.com HEAD section -->

<SCRIPT language=Javascript>

59
 <!--

function isNumberKey(evt)

var charCode = (evt.which) ? evt.which : event.keyCode

if (charCode > 31 && (charCode < 48 || charCode > 57)){

return false;

else{

return true;

//-->

</SCRIPT>

</head>

<body>

<div id="tooplate_wrapper">

<div id="tooplate_header">

<div id="site_title"><h2 id="hheader"style="margin-left:180px;margin-top:40px;font-

size:22px;font-family:Cooper Black;"><b><span style="font-size:36px;color:white"> Burie Town
Bus Station</span><br/><br/></b>Online Vehicle Management System</h2></div>

</div> <!-- end of forever header -->

60
 <div id="tooplate_menu">

<ul>

<li><a href="manager.php" class="current">Home</a></li>

<li><a href="registervehicle.php">Register Vehicle</a></li>

<li><a href="vehicleinfo.php">View Vehicle info</a></li>

<li><a href="manage_requests.php">Manage Request</a></li>

<li><a href="assign.php">Assign Vehicle</a></li>

<li><a href="fuel.php">Check Fuel Balance</a></li>

<li><a href="#">Generate Report</a>

<ul style="margin-left:10px;padding-right:4px;">

<li><a href="reportuser.php">Report For

Users</a></li>

<li><a href="reportvehicle.php">Vehicle
Report</a></li>

<li><a href="FuelReport.php">Fuel
Information</a></li>

</ul>

</li>

<li><a href="permission.php">Get Exit permission</a></li>

<li><a href="update.php">Update account</a></li>

<li><a href="viewcomment.php">View Comment</a></li>

61
 <li><a href="logout.php">Logout</a></li>

</ul>

</div> <!-- end of tooplate_menu -->

<div id="tooplate_main" class="shadow">

<div id="tooplate_content">

<form name="form1" method="post" action="registervehicle.php">

<fieldset><table align="center"style="color:black">

<legend align =center><h2 align="right" style="color:Blue">Register Vehicle</h2></legend>

<tr>

<td style="padding-top:12px;">Plate Number:</td>

<td style="padding-top:12px;"><input type="text" name="pno" id="pno" size="20" pattern="\

d{3,7}"onKeyPress="return isNumeric(event)" required x-moz-errormessage="Please Enter
Number Only between 2 and 8 digit ! " title="Please Enter Number Only between 2 and 8
digit !"/></td>

</tr>

<tr>

<td style="padding-top:12px;">Vehicle Type :</td>

<td style="padding-top:12px;"><select name="vtype" required maxlength="8">

<option ></option>

62
 <option value='Nissan patrol'>Nissan patrol</option>

<option value='Toyota PRADO'>Toyota PRADO</option>

<option value='Toyota single cub'>Toyota single cub</option>

<option value='Nissan pick up'>Nissan pick up</option>

<option value='Cacciamali bus'>Cacciamali bus</option>

<option value='Daewoo bus'>Daewoo bus</option>

<option value='Mercedes benz bus'>Mercedes benz

bus</option>

<option value='Fiat-mini-bus'>Fiat-mini-bus</option>

<option value='Other-Type'>Other Type</option>

</select></td>

</tr>

<tr>

<td style="padding-top:12px;">Model :</td>

<td style="padding-top:12px;"><select name="model" required maxlength="5">

<option ></option>

<option value='TVTSLEFY61NRA'>TVTSLEFY61NRA</option>

<option value='KUN25L-PRMDHV'>KUN25L-PRMDHV</option>

<option value='HZJ79LTJMRS'>HZJ79LTJMRS</option>

<option value='CVRULCFD22NWN'>CVRULCFD22NWN</option>

63
 <option value='IHZJ105L-GMRS'>IHZJ105L-GMRS</option>

<option value='KB 7TNJNML'>KB 7TNJNML</option>

<option value='BE637JLSH'>BE637JLSH</option>

<option value='BF120'>BF120</option>

<option value='9BM3840883B'>9BM3840883B</option>

<option value='Other-Model'>Other Model</option>

</select></td>

</tr>

<tr>

<td style="padding-top:12px;"> Engine Number:</td>

<td style="padding-top:12px;"><input type="text" name="eno"

id="eno" size="20" pattern="\w{2,20}" required x-moz-errormessage="Please Enter engine
Number from 2-20 digit ! " title="Please Enter Engine Number From 2-20 digit !"/></td>

</tr>

<tr>

<td style="padding-top:12px;"><font size="4">Owner :</font></td>

<td style="padding-top:12px;"><input type="text"pattern="\D{3,15}" required x-moz-

errormessage="Please Enter Only Letter! at least 3 characters required" title="Please Enter
Letter at least 3 characters required " name="owner" id="error12"size="20"/></td>

</tr>

64
 <tr>

<td style="padding-top:12px;"> <font size="4">Capacity:<font></td>

<td style="padding-top:12px;"><input type="text" name="cap" id="cap"

size="5" pattern="\d{1,2}"onKeyPress="return isNumeric(event)" required x-moz-
errormessage="Please Enter Number of Capacity From 1-65 number! " title="Please Enter
Number of Capacity From 1-65 number !"/></td>

</tr>

<tr>

<td style="padding-top:12px;"><font size="4">Productive

Date:</font></td>

<td style="padding-top:12px;"><input type="date" name="date" title="Enter Id for

search " id="date-pick" placeholder ="year-month-date" class="search"
autocomplete="off"/></td>

</tr>

<tr>

<td style="padding-top:12px;"><font size="4">Insurance :</font></td>

<td style="padding-top:12px;"><select name="ins" style="width:148px;" required

maxlength="5">

<option ></option>

<option value='Insured'>Insured</option>

<option value='Uninsured'>Uninsured</option>

</select></td>

</tr>
65
 <tr> <td></td>

<td style="padding-top:12px;"><input type="submit" name="submit"

value="Save" class="button_example" /></td>

</tr>

</table>

</form></fieldset>

<?php

if(isset($_POST['submit']))

//geting values

//$username=$_SESSION['user'];

$pno=$_POST['pno'];

$vtype=$_POST['vtype'];

$model=$_POST['model'];

$eno=$_POST['eno'];

$owner=$_POST['owner'];

$cap=$_POST['cap'];

$ins=$_POST['ins'];

$status=1;

$date=$_POST['date'];

66
$query="SELECT * FROM vehicleregister where Plate_no='$_POST[pno]'";

$resultw=mysql_query($query);

$count=mysql_num_rows($resultw);

if($count==1){

while($row=mysql_fetch_array($resultw)){

$Plate_no=$row[0];

if($Plate_no==$_POST['pno']

if($Plate_no==$_POST['pno'])

if($Plate_no==$_POST['pno'])

echo "<script>alert(' Plate_no is used by another vehicle!');</script>";

echo'<meta content="3;registervehicle.php" http-equiv="refresh" />';

else

67
if($pno==$pno)

$sql="insert into vehicleregister

values('$pno','$vtype','$model','$eno','$owner','$cap','$date','$ins','$status')";//

//echo"$insert";//

if (!mysql_query($sql,$conn))

echo "<script>alert(' Already Registered!');</script>".mysql_error();

echo' <meta content="6;registervehicle.php" http-equiv="refresh" />';

else

echo "<script>alert(' Vehicle Register is successfully!');</script>";

echo' <meta content="6;registervehicle.php" http-equiv="refresh" />';

?>

68
CHAPTER FIVE

5.0 TESTING

Testing is a trial experience in which the deliverables of the project are checked with acceptable
Standards in the project. We used unit testing, system testing to test the correctness of each
Module and the compiled program.

Table 26 .Unit testing.

Tested Form Test Case Expected Result
Display a message when
validate user name and user didn’t fill user name or
Login Form password entry as an input password and also when
from each end users there is user name or
password error.
Display a message when
user left some text fields,
controlling the proper radio buttons, combo boxes
All other forms
insertion of data or date and time unfilled and
insert improper data in to the
form try to save.

Integrated testing: - all the modules will be combined together and tested it for its fitness
with each other and with the systems functionality. If error occurs in combining them, the
module with problem will be identified and recombined.

Table 27. Integrated testing

Tested Form Test Case Expected Result
Check the correctness of the
Display administrator or
Login Form form to be displayed after
system members menu
login is succeeded
Administrator menu check proper display of Display the selected form
selected options to be from the administrator form

69
 accessed as menu
check whether the report The selected report will be
Report from
will be generated or not displayed
check the navigation The form required Will be
All forms
functionality displayed
1.
System testing: - the team member to performs over all functional testing by checking
whether it meets the required target or not. Here the system is partially functional and
reached its requirement.

Table 28.System testing

Tested from Test case Expected result Actual result
To validate the proper ser will be authenticated
functionality of login To authenticate and if user is authorized
Login form
by inserting username user enter to the system else
and password confirm invalidity
If the requested record
To validate the exist display the result else
Search from functionality Search result if it doesn’t exist display
of search form the message about the
status
generate the requested
To validate the report if the request is
To generate
Report from functionality valid, if request is invalid
report
of report form display message box that
describes the invalidity
To provide
To validate the The form is presented and
the function
All forms functionality the required function can
required by the
of each form operated using the form
form

70
CHAPTER 6

6. Conclusion and Recommendations

6.1 Conclusion
As the scope of this project described we developed the vehicle management system for bus
station by making it more reliable and efficient. The system would register vehicles and perform
additional task that would be performed by the system.
So the system would:-
 Minimize the time required to perform task
 Minimize the work load of employees
 Increase customer satisfaction
This document use the object oriented technology called UML (unified modeling language) that
enable the user to understand the software easily.
We finally concluded that bus station vehicle management system would be benefited by the
system developed, and accept it cheerfully. During working on this project, we members of the
team had learned a lot.

6.2Recommendation
The system that we have developed involves online based vehicle management system for
bus station. We recommend the following features need to be included in any further revision
and extension attempt.

 May used the android or mobile based application.

 Use uninterruptible power supply or UPS if electric power is not available in
university.
 Integrate with the traffics system.
 Adding the chatting system.
 Include GPS.
 They done all system in organization are automated
 Update this system to android based system or integrate with android and PHP.

71
Therefore, others who are interested to develop a new system on vehicle management system for
bus station or other related systems can get some initial idea about the system. By focusing on
the limitation and functional areas of the system they can also develop a better vehicle
management system that automates all files managed in vehicles management office and other
related thin.

References

1.Jeffery A.Hoffer, Joey F.George. Modern systems analysis and design. 2005.

2. Jeffery L.Whitten, Lonnie. Systems analysis and design methods . 2004 G.C.

3. Bahrami, Ali. Object oriented systems development . (1999 G.C).

4. http://www.setha.info/docs/ict/course/0001/chap08.pdf. [Online]

5. Object Oriented and the UML.2nd rev. Ed England: The Cambridge University Press.

6. Bahrami, Ali. Object oriented systems development . 1999G.C.

72
73
74