DESIGN AND DEVELOPING ONLINE IRAQI BUS RESERVATION SYSTEM BY USING UNIFIED

MODELING LANGUAGE

Asaad Abdul-Kareem Al-Hijaj 1 Ayad Mohammed Jabbar 2

Hayder Naser Kh 3

Basra University, Iraq1

Shatt Al-Arab University College, Basra, Iraq2,3

Abstract: The Online Iraqi Bus Reservation System (OIBRS) is a web-based system. It allows customer to check

the ticket availability and search for the most possible prices. Our system is available in online twenty four

hour and seven days per a week. The most advantages of this system are allowing the customers to search

and choose his/her seat position and ticket payment procedure. In this research, we gather the information

to define the requirements of the new application. In addition to design and develop OIBRS the Unified

Modeling Language (UML) used to model the software and Entity Relationship Diagram (ERD). Both have

been established to describe a plan which executes the requirements. The scope of this paper covers

customer services to book bus ticket and company daily management work. Furthermore, this work use C#

as programming language and Microsoft SQL server 2008 for Data Base implementation .In order to

evaluate the Usability of the system, we used Computer System Usability Questionnaires (CSUQ) as

application to achievement of this task.

Keywords: Web Technology, Online Reservation System, Booking Bus Application. Web application

development. Software Engineering Unified Modeling Language.

1. INTRODUCTION

Nowadays the internet becomes one of the most important sectors around the world. The internet has changed the way that people look at the life. Using the internet makes the reservation systems the easiest way to do this task. The in-ternet booking to travel throw airplane or bus is now in the reach of our hand at home [1] . The online booking gives us extra details about the company and lets the customers check the avail-ability of the bus ticket before they buy it. Be-

sides that, customer suffering will rid off by easy way to save time and money[2]. The prob-lems with manual system when users have to stand up in a long queue to buy bus ticket or asking for some information. In Iraq, The State Company For Travelers And Delegates Trans-portation company in the Ministry of Trans-portation is still using the manual system .The problems with manual booking items appear when the system lay off at the same time in par-ticular day with different user, the redundancy

of data which cannot be automatically updated, the paper works can be easy lost, the storage space and costs[3].In fact, the disadvantages of having no electronically system not only effect the public transporter sector but they will cer-tainly affected Health care, Telecommunica-tions, Educations water and electricity, etc. It will delay our county from the rest of the world. “Our experience points are very important for Iraq today: Difficulties and suffering of the cur-rent Iraqi constituencies systems will affect new Iraq.

By survey sample of travelers at Garage Baghdad bus station in Basra city / Iraq the re-sult shows an average 97 % of passengers are not happy with transportations system. Also by survey the registration operation in the Iraqi garage stations the majority of drivers suffer when they register for a new root. In the other hand the customer can deal easy with our friendly website application[4].

Furthermore the website application will help the company employees in daily work by making their work more arranged and more connected to the other company branches. In fact, there are many similar systems in the dif-ferent countries, but they do not exist in Iraq.

2. FRAMEWORK

Our Framework contains a lot of features, which are well-organized in five modules shown in the diagram below. We will discuss each of the modules in turn.

Figure 1: Framework for Online Iraqi Bus Reser-vation System process

3. THE PROBLEM IDENTIFICATION

The problem identification is the first phrase of our research framework. It focused on how to understand the objectives and the problem as well as how to create our OIBRS applications using the C# language and MS SQL server 2008. The outcome for this phrase is the project awareness of problem which gives the clear and full view about the detail problem, especially in a manual system.

4. SUGGESTION

The second phrase aims to understand all the requirements, high level design and the general task to develop the prototype. It is focuses to reach the required levels of quality in the analy-sis. The outcome of this step is gathering the re-quirements, design the ERD for database and analysis the system using (UML) as well as to develop web based application.

5. SYSTEM DEVELOPMENT

In the development stage, we start with re-quirement then we defined the system compo-nents and we determined the relationship be-tween them. The database has been design de-pended on relational entities, Normalization and implemented in MS SQL 2008. Then, we used system analysis in order to develop a web based application. Microsoft Visual Studio 2005 is the development tools and C# is programming lan-guage for this prototype. The step for system developments of this system as following:

5.1 REQUIREMENTS GATHERING:

The task started with requirement collecting

to develop bus reservation prototype Table 1

and 2 shows the result below which is the func-

tional requirements and non-functional require-

ment of the system[7]. In the priority column,

the following short hands are used:

M – mandatory requirements (something the system must do)

D – desirable requirements (something the system preferably should do)

O– optional requirements (something the system may do)

Table 1: OIBRS functional requirementsNo. Requirement Description P

riority

Register Member

1. Customer must register before Log in the system. M

2. Customer must fill all fields in the registration form , otherwise the system will show an error message .

D

Log in

3. Administrator can log in to enter the system M

4. Customer can log in the system to make his/her booking. M

5. The user must enter the valid user name and password, otherwise the system will show an error message.

D

Search Destination

6. Administrator can search a Destination, date, number of passengers and select the trip type (one way or return).

M

7. Customer can search a Destination, date, number of passengers and select the trip type (one way or return).

M

8. The User must fill all the searching field before press search button , otherwise the system will show an error message .

D

Booking Ticket

9. Administrator and Customer can select the coach. M

10. Administrator and Customer can select a bus seat. M

11. Administrator and customer can confirm booking. M

Print Receipt

12. Customer can print his / her Receipt O

Manage System

13. Manager can create a new coach (include all coach details). M

14. Manager can Edit the coach (include all coach details). M

15. Manager can Delete the coach (include all coach details). M

16. Manager can update customer profile if he/she has any wrong in it. M

Table 2: OIBRS Non-functional requirementsNo. Requirement Description Priority

Reliability issues

17. If the system should crash no more than once per 24 hours. M

18. If the system has been crashed, it should not be more than 20 Min-utes

M

19. If the systems has been crashed, it should behave perfectly normal when reloaded again

M

Usability issues

20. That means we should make sure that the system stay working smoothly without any interruption

M

Security issues

21. Only Administrator will be able to enter the system to make main-tenance.

M

Performance

22. The system must have a high speed of manipulation data and reply to the user request

M

5.2 SOFTWARE ADVANCED ANALYSIS

TECHNIQUES:

In our research we highlight the use of

(UML) to design the web-based application. We

design both sequence diagrams which is used to

show the dynamic behavior of application design

and class diagrams which it is application stati-

cally structure [8]. The sequence diagram present

interactions between the objects that arranged in

a time sequence.

A CLASS DIAGRAMS

The class diagram is used to show graphi-

cally the visual model as a static view which

presents the collection of static elements of this

field[9]. The class diagrams are probably the

most important and best understood among all

UML models [10]. The main constituents of this

static view are classes and their relationships.

Relationships among classes include associations

and generalizations. The class diagram of

OIBRS as shown below in Figure2 represent the

set of customers who used the system and the as-

sociation between booking, bus, seat, and etc.

B SEQUENCE DIAGRAM

sta

ff

Re

gis

terC

usto

mer(

)b

oo

k_

tic

ke

t()

prin

t_re

cip

t()

Ma

na

ge

r

cre

ate

_ro

ute

()fill_

route

_in

fo

rmati

on()

sele

ct_

route

()S

ea

rch_

rou

te()

De

lete

_ro

ute

()E

dit

_ro

ute

()

ad

min

sta

ffN

OfullN

am

eA

dd

ress

nam

eT

elp

ho

ne

No

DO

Bp

os

itio

ns

ala

ryE

mail

con

tactN

oId

enti

fic

ati

onN

oS

ex

OIB

RS

In

terf

ace

Dis

pla

y_

regis

tera

tio

n_

fo

rm()

Se

nd_

Re

gis

rtra

tion

_in

fo

rma

tio

n()

dis

pla

y_

log

in_

fo

rm()

sen

d_

ID_a

nd

_pa

ss

wo

rd()

dis

pla

y_

rec

ov

ery

_ p

ass

wo

rd()

sen

d_

us

er_

Em

ail()

Se

nd_

route

_d

eta

ils

()s

ho

w_

route

s_

list(

)s

en

d_

se

lec

ted

_ro

ute

()d

ispla

y_

bo

ard

_ o

f_

av

ailab

le_

se

ats

()s

en

d_

se

lec

ted

_s

ea

t_in

fo

rmati

on

()D

ispla

y_

pa

ym

en

t_form

()s

en

d_

se

lec

ted

_p

ay

me

nt_

meth

od

()d

ispla

y_

pa

ym

en

t_m

ode

()d

ispla

y_

tec

kit

_d

eta

ils

()v

iew

_re

que

st(

)d

ispla

y_

all_

route

s()

dis

pla

y_

cre

ate

_ro

ute

_fo

rm()

cre

ate

_c

om

ple

tin

g()

dis

pla

y_

Ed

it_

ro

ute

_ f

orm

()E

dit

_c

om

ple

tin

g()

sen

d_

th

e d

ele

te_ r

ou

te_

inform

atio

n()

Se

at

Tota

lNum

ber

Bu

sN

o

Bu

s_R

ou

tero

ute

No

rou

te_

fro

mro

ute

_to

pric

e

1

1..

*

1

1..

*

Ma

na

ge

OIB

RS

co

ntr

oll

er

ve

rify

_re

gis

tera

tion

_in

fo

.()

Re

trie

ve

_ID

()v

erf

iy_th

e_

ne

wID

()c

reate

_n

ew

_a

cc

oun

t()

ve

rfiy

_ID

()R

etr

iev

e_ r

ou

te_

de

tails

()v

erf

iy_ro

ute

_av

aila

bilty

()re

triv

e_a

va

ila

ble

_s

ea

ts_

fo

r_ t

he

_ s

ele

cte

d_

ro

ute

()B

oo

k_

se

lec

ted

_s

ea

t_ f

or_

5m

in()

Ve

rify

_s

ea

t_a

va

ila

bilty

()re

que

st_

cre

dit

ec

ard

_d

eta

ils

_ f

rom

_ t

heb

an

k()

ve

rify

_ b

an

k_

de

cis

ion

_a

bo

ut_

cre

dit

_in

fo

()a

sk

_to

_d

ed

uc

t_ti

ck

et_

am

oun

t()

ve

rify

_b

an

k_

dec

isio

n_a

bou

t_cre

dit

_b

ala

nc

e()

Cre

ate

_T

icke

t()

retr

iev

e_

all_ro

ute

s_

inform

atio

n()

ve

rify

_d

up

lic

ate

_ro

ute

()c

reate

_a

_n

ew

_ro

ute

()D

ele

te_th

e_ro

ute

_in

fo

rmati

on

()v

eri

fy

_d

up

lic

ate

_ro

ute

()E

dit

_th

e_ro

ute

()

1..

*

1

1..

*

1

Ma

na

ge

Sy

ste

m

sen

d r

eq

ue

st

Cu

sto

me

r_IN

FO

ID pas

wo

rdF

ullna

me

Em

ail

con

tactN

oA

dd

ress

Ide

nti

fic

ati

onN

OS

ex

Re

gis

ter(

)L

og

in()

retr

iev

e_

pas

sw

ord

()s

ele

ct_

route

()B

oo

k_

Tic

ke

t()

sele

ct_

sea

t()

sele

ct_

pay

men

t_ m

eth

od()

ente

r_cre

dit

e_

ca

rd_

de

tails()

prin

t_re

cip

t()

1..

*

1

1..

*

1

Re

gis

te

Bu

sB

us

No

rou

teN

oM

ode

lB

us

_s

tatu

sd

riv

erN

am

eD

ate

1..

*

1 1..

*

1

1..

*1

1..

*1

Tic

ket

Tic

ke

tNo

cus

tom

er_

IDB

us

No

rou

te_

fro

mro

ute

_to

pric

eD

ate

Bo

okin

g_

Tic

ket

Bo

okN

oB

oo

kd

ate

boo

k_

tic

ke

t()

sele

ct_

sea

t()

sele

ct_

pay

me

nt(

)

0..

*

1 0..

*

1

Do

Bo

ok

ing

0..

*1

0..

*1

11

..*

11

..*

11..

*

11..

*

has

A sequence diagram is a kind of interaction

diagram that shows how processes operate with

one another and in what order. It is a construct of

a Message Sequence Chart [11]. The interaction

process involves in this project are system user.

The booking ticket and the manage system se-

quence diagram for use case are shown in Figure

3,4 below

.

User

Interface Controller

Bank System :

Booking ticket

A-1: return back

A-2:Cancel

E-2: Credit Info. incorrect

E-3:credite balance insufficient

Book the selected seat for 5 min

Verify seat availability

E-1:The seat

blocked by other or exceed 5 min

press "book " button

User select seat

press next bottom

user select payment method

user press " proceed to payment"

enter credit card details

press submit button

send selected route

display board of available seats form

Display payment page

send selected payment method

display payment mode page

send credit card details

display ticket details page

send selected seat info.

check bank decision about credit info

check bank decision about credit balance

request credit card details from the bank

ask to deduct ticket amount

bank reply

bank reply

retrieve available seats for the selected route

Book ticket

Figure 2: Classes Diagram for OIBRS

ManagerInterface Controller Bus_route

E1: the information are duplicate or not complete.

A1 : Search

A2: Edit

A3: Delete

A4: Back

A5: Cancel

press create route button

display create route form

Fill the route information

press Add button

Press manage OIBRS button

send the route information

verify duplicate route

create completing

display all routes in manage page

view request

retrieve the route information

create a new route

retrieve all routes information

Figure 3: Sequence Diagram for Use-Case Manage System

Figure 4: Protocol for Booking Bus Ticket

5.3 ENTITY RELATIONSHIP DIAGRAM

(ERD)

Entity relationship diagram (ERD) is a kind of

graph for presenting visually the entity set, attribute

and the relationships between entities in a data-

base[5]. ERD is top down approach to database de-

sign that begins by identifying the important data

called entities and relationships between the data

that must be represented in the model. We design

ERD if figure 5 of OIBRS by using the technique

of normalization. Normalization is formal tech-

nique of analyzing base on their primary key. At

the end of ERD design we validate and check the

model to ensure it is capable to support the required

transaction given in the user requirement specifica-

tion[6].

Figure 5: Entity Relationship Diagram

(ERD) of OIBRS applications

The last phase in the system develop-

ment is implementing of the system inter-

faces. The system interfaces is a web

based application has been programming

using C#. Our system meets all the func-

tional requirements which have been col-

lected in the requirement gathering step.

Figure 6: OIBRS Web Based Applica-

tion

5.4 EVALUATION

This part explains the analysis of the evaluation that has been done for this application. After the proto-

type development is finalized, The System has been tested by the actual users and through Computer Sys-

tem Usability Questionnaire (CSUQ) Web Based Application, which measures usability and system satis-

faction[12]. The questionnaire is taking from Lewis (1995) [13]. It contains of 19 questions and 7 degrees

of likert scale (1-strongly disagree – 7-strongly agree). The questionnaires address evaluation at both a

global overall system level and at a more detailed scenario level .The result of the study was analyzed by

using MS Excel 2010 software and the result confirmed that the prototype is satisfying by the users. Ac-

cording to the Figure 7 there is no questions that has disagree as the highest rate, the majority of the rate

fall into agree scale .The data analysis result has been showed a positive result in both usability and system

satisfaction with how easy it is to use this system. Finally, descriptive mean and Std. Deviation statistics

for related questions to our application shows in figure below.

Figure 7: Descriptive Mean Statistics and Std. Deviations

6 CONCLUSION AND FUTURE WORK

The Online Iraqi Bus Reservation System is

company online web-based system which enable

users to check ticket online other than queue up to

buy it ,and provide service at any time or anyplace

for the customer. This is the first system for Iraqi

company which can be the key and the guide for

the other companies to develop its own application.

The development has been divided into four sec-

tions; the first step is identifying the problem of

Iraqi Transportation Company. Secondly, it focused

on how to aggregate the requirements, analysis the

system and design the database ERD .Next the de-

velopment of our application has been done based

on the requirements captured in required analysis

phases and proposed design model. Moreover the

system usability one of the important thing we had

been focus on it in the system evaluate by using

Computer System Usability Questionnaire which

show the system is satisfied in term of usability .

The user gets an interface with easy way to access

for all pages with one click to book and simple reg-

istration. The system is reliable in the security side

and detection of the errors which will be more

trusted by the company and the user as well. In the

future work, we plan to design and develop and

complete an intelligence system that includes on-

line analytical process to keep track of performance

growth in this sector.

7 REFERENCES

[1] R. Gauld And S. Derrett, "Solving The Surgical Waiting List Problem? New Zealand's ‘Booking System’," The International Journal Of Health Planning And Management, Vol. 15, Pp. 259-272, 2000.

[2] M. Niemann, M. Mochol, And R. Tolksdorf, "Improving Online Hotel Search-What Do We Need Semantics For," In International Conference On Semantics Vienna, Austria 2006, Pp. 1-9.

[3] W. Lu, "An Analysis Of Airline E-Commerce Strategies In Ticket Distribution," In International Conference On Service Systems And Service Management 2007 2007, Pp. 1-5.

[4] R. Law And C. H. C. Hsu, "Importance Of Hotel Website Dimensions And Attributes: Perceptions Of Online Browsers And Online Purchasers," Journal Of Hospitality & Tourism Research, Vol. 30, Pp. 295-312, 2006.

[5] H. Gracia-Molina, J. D. Ullman, And J. Widom, Database Systems The Complete Book, Second Edition Ed. Usa,Stanford: Pearson Education 2009.

[6] T. Connolly And C. Begg, Database Systems A Practical Approach To Design , Implementation And Management ., Fifth Edition Ed. Usa,New York: Pearson Education 2010

[7] H. Gomaa, Designing Software Product Lines With Uml. Usa: Addison-Wesley Boston, 2004.

[8] X. Li, Z. Liu, And H. Jifeng, "A Formal Semantics Of Uml Sequence Diagram," In Software Engineering ConferenceAustralia, 2004, Pp. 168-177.

[9] N. Koch And A. Kraus, "The Expressive Power Of Uml-Based Web Engineering," In Second International Workshop On Web-Oriented Software Technology (IWWOST02)Germany, 2002.

[10] M. Krotzsch, S. Rudolph, And P. Hitzler, "Complexity Boundaries For Horn Description Logics," In Proceedings Of The National Conference On Artificial Intelligence, London, 2007, P. 452.

[11] Asaad A.Al-Hijaj, Haidar M. Abdul-Nabi, Aziz S., "Using of Software Reuse Approaches to Develop UGELIB Web Application," Journal of College of Education, Thi-Qar University,Vol 1, PP 51-59, 2010

[12] T. S. Tullis And J. N. Stetson, "A Comparison Of Questionnaires For Assessing Website Usability," In Usability Professional Association Conference, 2004.

[13] J. R. Lewis, "Ibm Computer Usability Satisfaction Questionnaires: Psychometric Evaluation And Instructions For Use," International Journal Of Human-Computer Interaction, Vol. 7, Pp. 57-78, 1995.