Online travel point system 2014

Dire Dawa University Institute of Technology College of Computing

project on Online travel point system Group members Name ID Number

Advisor ፡ ____________________________________
1. Nahim Teferi………………………….1201004
2. Hannan Mohammed ………………1200552
3. Khalid Usman………………………….1200678
4. Henok Tassew…………………………1200609
5. Israel Bizuneh……………………..…..1200267
6. Haileyesus Abuhay…………………..1200585
7. Sara W.yohannes……………………1201230

2014

Page 1
 Online travel point system 2014

Acknowledgment
First of all we would like to thanks the almighty God that gives as strength, patience and courage
to do our project We would also like to express our heart full appreciation to all staff of computer
science and it department teachers and our friend 3rd year students for their help.

Page 2
 Online travel point system 2014

Table of Contents

Dire Dawa University Institute of Technology College of Computing project on Online travel point system
Group members Name ID Number ............................................................................................................... 1
Advisor ፡ ____________________________________ ................................................................................ 1
2014 .............................................................................................................................................................. 1
Acknowledgment .......................................................................................................................................... 2
List of figure .............................................................................................................................................. 5
List of table................................................................................................................................................ 7
Abbreviations ............................................................................................................................................ 8
Chapter One .................................................................................................................................................. 9
1.1 Introduction ............................................................................................................................................. 9
1.2Objective of the Project ......................................................................................................................... 10
1.2.1 General Objective .......................................................................................................................... 10
1.2.2 Specific Objective .......................................................................................................................... 10
1.3 Scope of the Project .............................................................................................................................. 10
1.4 Significance of the Project .................................................................................................................... 10
1.5 Target Beneficiaries of the System ....................................................................................................... 11
Chapter Two................................................................................................................................................ 12
2.0 Business Rules ...................................................................................................................................... 12
2.1 Requirements of the Proposed System.................................................................................................. 12
2.1.1 Functional Requirements ............................................................................................................... 12
2.1.2 Non-functional Requirement of the Existing System .................................................................... 13
Chapter Three.............................................................................................................................................. 15
3.1 Introduction of System Analysis .......................................................................................................... 15
3.2 System Requirement Specifications (SRS) ........................................................................................... 15
Use Case Identification ........................................................................................................................... 15
3.2.2 Use Case Documentation ........................................................................................................ 17
3.2.3 Sequence Diagram ......................................................................................................................... 25
3.2.4 Activity Diagram ........................................................................................................................ 34

Page 3
 Online travel point system 2014
 Activity diagram for log in form ..................................................................................................... 34
3.2.5 Analysis Level Class Diagram (conceptual modeling) .................................................................. 42
3.2.6 User Interface Prototyping ............................................................................................................. 43
3.2.7 Supplementary Specifications ........................................................................................................ 43
Chapter 4 ..................................................................................................................................................... 44
4.1 Introduction System Design .................................................................................................................. 44
4.2 Class Type Architecture ........................................................................................................................ 45
4.3 Class Modeling ..................................................................................................................................... 47
4.4 State Chart Modeling ............................................................................................................................ 48
4.5 Collaboration Modeling ........................................................................................................................ 56
4.6 Component Modeling ........................................................................................................................... 61
5.1 Conclusions ....................................................................................................................................... 62
5.2 Recommendations ............................................................................................................................. 62
References ............................................................................................................................................... 62
Internet Site reference:........................................................................................................................... 63

Page 4
 Online travel point system 2014

List of figure
Figure 2 :use case diagrams ......................................................................................................................... 16
Figure 3 : sequence diagram for login ......................................................................................................... 26
Figure 4 sequence diagram for registration ................................................................................................ 27
Figure 5 sequence diagram for browse information ................................................................................... 28
Figure 6 sequence diagram for update information .................................................................................... 29
Figure 7 sequence diagram for delete information ..................................................................................... 30
Figure 8 Sequence diagram for view profle ............................................................................................... 31
Figure 9 sequence diagram for generate report .......................................................................................... 32
Figure 10 sequence diagram select reservation .......................................................................................... 33
Figure 11 activity diagram for log in form ................................................................................................. 34
Figure 12 activity diagram for customer registration ................................................................................. 35
Figure 13 activity diagram for update customer info .................................................................................. 36
Figure 14 activity diagram for browse info ............................................................................................... 37
Figure 15 view profile ................................................................................................................................. 38
Figure 16 activity diagram for select reservation. ...................................................................................... 39
Figure 17 activity diagram for delete reservation........................................................................................ 40
Figure 18 activity diagram for generate report .......................................................................................... 41
Figure 19 analysis level class diagram ....................................................................................................... 42
Figure 20 user interface prototyping .......................................................................................................... 43
Figure 21 Class type architecture ............................................................................................................... 45
Figure 22 class modeling ............................................................................................................................ 47
Figure 23 state chart for login .................................................................................................................... 48

Page 5
 Online travel point system 2014
Figure 24 state charts for registration ......................................................................................................... 49
Figure 25 state chart for delete page........................................................................................................... 50
Figure 26 state chart for update page ......................................................................................................... 51
Figure 27 Browse info ................................................................................................................................. 52
Figure 28 select reservation ........................................................................................................................ 53
Figure 29 Generate report............................................................................................................................ 54
Figure 30 View profile ................................................................................................................................ 55
Figure 31 collaboration modeling for login................................................................................................ 56
Figure 32 collaboration modeling for registration ...................................................................................... 56
Figure 33 Collaboration modeling for delete reservation ........................................................................... 57
Figure 34 view profile page ......................................................................................................................... 58
Figure 35 Select reservation ....................................................................................................................... 58
Figure 36 Browse info............................................................................................................................... 59
Figure 37 update info .................................................................................................................................. 59
Figure 38 generate report ........................................................................................................................... 60
Figure 39 component modeling .................................................................................................................. 61

Page 6
 Online travel point system 2014

List of table
Table 1 team composation.............................................................................. Error! Bookmark not defined.
Table 2:- Materials cost for existing system .................................................. Error! Bookmark not defined.
Table 3 Materials cost for new system ........................................................... Error! Bookmark not defined.
Table 4Hardware costs ................................................................................... Error! Bookmark not defined.
Table 5:- Software Cost.................................................................................. Error! Bookmark not defined.
Table 6 schedule feasibility ............................................................................ Error! Bookmark not defined.
Table 7:- development tools ........................................................................... Error! Bookmark not defined.
Table 8 hotel registration form ....................................................................... Error! Bookmark not defined.
Table 9 use case documentation for “login”................................................................................................ 18
Table 10 use case documentation for “ registration”................................................................................... 19
Table 11 use case documentation for “update account” .............................................................................. 20
Table 12 use case documentation for “Browse Reservation”...................................................................... 21
Table 13 use case documentation for “view profile” .................................................................................. 22
Table 14 use case documentation for “delete reservation” ......................................................................... 23
Table 15 use case documentation for “select reservation” .......................................................................... 24
Table 16 Use case documentation for “generate report” ............................................................................. 25
Table 17 class type architecture .................................................................................................................. 46
Table 18 Testing ............................................................................................. Error! Bookmark not defined.

Page 7
 Online travel point system 2014

Abbreviations
 ARS Airline Reservation System
 HRS Hotel Reservation System
 CRS Car Rental System
 SRS System Requirement Specifications
 UNESCO United Nation Educational, Scientific and Cultural Organization
 MYSQL My structural Query Language
 OOA Object oriented Analysis
 OOD Object oriented Design
 PHP Hypertext Preprocessor
 UML Unified Modeling Language
 UI User Interface
 API Application Programming Interface.

Page 8
 Online travel point system 2014

Chapter One
1.1 Introduction
Today communication plays a vital role for day to day activities of human kind so, Ethiopia is
one of African country starting travel point service before some years ago
Online travel point is one of the largest system and nongovernmental organizations in Ethiopia
which provides many services such as Airline Reservation System (ARS), Hotel Reservation
System (HRS) and Car Rental System (CRS) for the customer, but currently there is no online
travel point system. The current system working on the point of traveling is still doesn’t satisfy
the customers need and doesn’t combine the three system. Now online travel point improves
these drawbacks and implements the new feature of building world class infrastructure.
Currently traveling uses manual system and separate for generating payment from its customer
by providing Airline Reservation, hotel reservation and car rental. Now we are doing to change
this manual system to web based system and Air line reservation system used to this web based
but still there are some problems.
Using this system guests will know their hotel and room, select car type and flights with whom
they are assigned before coming to airport, hotel and tour and Travel Company.
This project also covers various features like online registration of the users, modifying the
details of the website by the management staff or administrator of the website, by adding,
deleting or modifying the customer details, flights or packages information. In general, this
project would be designed to perform like any other ticket booking website available online.

Page 9
 Online travel point system 2014

1.2Objective of the Project

1.2.1 General Objective
The main objective of this project is to develop a web based system that provide a convenient
way for a customer to reserve tickets, hotel and a car rental being in one system .
1.2.2 Specific Objective
The specific objective of the project is to provide at any time at anyplace service for the
customer .To serve many people’s at a time and to increase the profit to obtain detail information
from the booking record and car rental services.
 To provide direct access to customers through web application system.
 Design scalable data base
 Design a system or module to generate reports for administrator
 Integration of all records of passengers & employees
 Create user friendly environment
 To provide report generation and analysis such as the car rental report and Statistic from
time to time.
1.3 Scope of the Project
The proposed system will provide airline ticket reservation, hotel reservation and renting car
online in one system.
Developing travel point system project is aimed to make a website for the airline ticket
reservation, hotel reservation and renting cars for the tourists.
Some functionality of the system include:-
 Customer registration
 Giving information about attractive places in Ethiopia
 Decides the type of car and hotel
 Updates information
 Select room type
 Generates report
 Cancel reservation
1.4 Significance of the Project
Some of the Significances of the proposed system are:-

Page 10
 Online travel point system 2014
 Reduce the passenger waiting time to buy tickets and to get the service.
 Avoiding improper resource consumption
 Avoids improper communication.
 Avoiding data loss
 Tourists can book the ticket for airline, to reserve hotel and rent car over the Internet, at
any time at anywhere.
 This online car rental solution is fully functional and flexible.
 It is very easy to use.
 This online travel point system helps in back office administration by streamlining and
standardizing the procedures.
1.5 Target Beneficiaries of the System
There are different beneficiaries of this project
 Owner and workers uses the software to controls the system. Owners of those companies
are benefited by the system because it reduces their employers, to give services for many
guests at a time by their online systems and they give full time service for the guest.
 Guest also benefited by the system, they can get more information from the system to
save the time, to get full information and to get service at any time.
 Workers those who use the system are benefited from the system can do their work
easily, fastly and accurately.

Page 11
 Online travel point system 2014

Chapter Two
2.0 Business Rules
Existing system has its own business rule and the proposed system take this rules as they are
some of them are:-
For Airline Reservation
 If Customers have child less than two years old child that go with them. They pay
10% of the total price only for his child and the child can’t get a sit.
 Customer pays 70% of the total price for 2- 12 years old children’s.
 Customers get discount if they buy ticket when they go and back to their
destination, but this discount vary depend on the time, that customers will back
and this rule work for international flight only.
 Ticket price vary based on time.
 There is also discount for spatial customers.
 Ticket value varies according to the class the customer chooses.
For Hotel Reservation
 Customer get discount when they book with his girl friend or wife.
 Customer must have an ID (identification card).
 The price of the room depends on their quality.
For Car Renting
 Customer must have license of driving.
 Customer must choice type of car.
 If any problem happens to the car, the customer must tell to renting company.
2.1 Requirements of the Proposed System
2.1.1 Functional Requirements
Once the guest makes a reservation, he/she must be provided with private codes (user name
&password.). If the code provided by the customer does not match, then would notify the person
by displaying error messages. The system will allow the customer to modify his/her reservation
provided correct code has been entered by him. The code will generate during reservation and

Page 12
 Online travel point system 2014
only for the person. If no reservations are made, then a message is displayed that no bookings
have been made. The system will allow the administrator to view all the details of the customer
who have made reservations
Performance Requirements
 The system capable to increase total throughput speed under an increased load when
resources are added
 Enable the users to create, modify, or even to delete his/her account if it is necessary
 The system can generate information and forms for user to access Friendly
Input Related Requirements: There will be accurate and flexible input mechanisms.
The input form must include name, date, time, code, customer login detail and others
Collecting the information of the guest who is going to reserve hotel, book airline ticket and rent
car. The administrator must enter the password so that access is given only to him to view the
details of the entire guest.
Process Requirements ፡There will be efficient storage and easy traceability/giving an outline/
and guest must have his/her own account to cancel or modify his/her reservation
During reservation the guest should fill full the appropriate information in the specified
Places and a code will generate used for access securely. If there is no code any one can delete
others persons reservations. Even for modifying your reservations the code is useful.
Output Related Requirements: Since the input is effective the output is also effective. There
will be accurate display of guest reports in accordance with the query process accessibility is
possible for whom who has an account and no one can view information unless matched
successfully. If the match is successful, account of the tourist will displayed and can view and
information. If the match is unsuccessful, inappropriate message displayed. A new code will be
generated for the guest.
Storage Related Requirements፡
There will be efficient storage and the entire entire processed system can stored in the data base.
2.1.2 Non-functional Requirement of the Existing System
Performance ፡-
Performance requirements define acceptable response times for system functionality.

Page 13
 Online travel point system 2014
Response time of the Airline Reservation System should be less than 2 second most of the time.
Response time refers to the waiting time while the system accesses, queries and retrieves the
information from the databases
 The load time for guest interface shall take no longer than two seconds.
 The log in information shall be verified within five seconds.
 Response time of the system will not take long almost in 10 seconds
 The system should support many user to reserve at a time
 The system is work 24 hours per day seven days in a week which means the system is
always work.
 The tourist’s information must save as class in the data base in few hours after the end of
registration.
User Interface:
The window format and the forms prepared for the information are easy to the guest they can
easily understand.
The system shall be design according to standards and the system shall replace existing system.
ARS (Air line reservation system) shall provide an easy-to-use graphical interface similar to
other existing reservation system so that the user does not have to learn a new style of
interaction. The best thing in the input design is to achieve all the objectives mentioned in the
simplest manner possible and creating reports for displaying and storing information
Security and Access Permissions:
Only system administer has the right to change system parameters, such as time change. The
system should be secure and must use encryption to protect the databases. Users need to be
authenticated before having access to any personal data.
Backup and Recovery:
 If the connection between the user and the system is loss the system will automatically
save the filled information and the remaining can enable by the administrator by
contacting the guest using phone.
 Both databases used for guest account and reservations are production databases. The
main operation used for the backup and recovery is Oracle's built-in cold backup.
 ARS shall be able to recover from hardware failures, power failures and other natural
disaster and rollback the databases to their most recent valid state

Page 14
 Online travel point system 2014
Resource
The main non functional resource is: - Server in back end and operating system in the
application of the system. In the other case on of the most and available resource is
internet access.

Chapter Three
3.1 Introduction of System Analysis
As mentioned in the previous chapter in this project, the team used an object oriented System
development methodology which incorporates two principal phases. In this chapter, what the
team will do is the object oriented analysis (OOA) in this phase we can identify the relationship
between objects and the interaction between each object. During Object Oriented Analysis the
following major activities are performed.
3.2 System Requirement Specifications (SRS)
Actor Identification
Customer: - someone books online for airline reservation and hotel reservation and car rental.
Administrator: - a special user of the system who can setup access right for other users.
Employee:-is a person who checks whether the customer reserve ticket or not.
Manager: - person who generate reports and manage employers.
Use Case Identification
Registration:-if the customer is a new user, he can request to register with the system. The
System displays a registration page. The customer is also required to enter their name and
address and other information's.
Update information: - the administrator can request to update their customer information.
View information: - the customer requests to view the flights, reservations, and information
about the company. The system will display the airline reservation, hotel reservation and about
the car rental.

Page 15
 Online travel point system 2014
Fill information:-the customer enter the necessary information
Specified place in the country.
Delete reservation:-the system administrator removes the reservation from the database after
Used.

3.2.1 Use case diagrams

Figure 1 :use case diagrams

Page 16
 Online travel point system 2014

3.2.2 Use Case Documentation

 Security Login
The following consecutive tables show the use case documentation for each of the use cases that
has identified in the above use case diagram.
Actors Administrator ,Employee, Manager

Use case name Login

Use case Id 01
Description Login to the system

Pre-condition The user has been registered.

Post condition The user has been authorized.

Basic course of Actor Action System Response

action

Page 17
 Online travel point system 2014
Step1: The user wants to login Step2: The System display user log in
form.

Step3: The user enter username

and password
Step4:The system validates whether the
username and password submitted is
correct (already in the data base)

Step5: The system display the user

account page

Step6: The use case ends

Alternative 01. The user enter wrong username and password
curse of action Step 4.1 The system indicates the user information invalid
Step 4.2 The use case continues Step 3 of the basic course of action

Table 1 use case documentation for “login”

 Registration
Actors Customer,Manager,Employee

Use case ID 02

Use case name customer Registration

Description This use case allows passengers to register in to the system

Pre-condition The passenger wants to reserve airline, hotel and car rental

Post condition The passenger registers into the system

Basic course of Actor Action System Response

action

Page 18
 Online travel point system 2014
Step1: The User wants to register Step2: The system Displays customer
in to the system. Registration page

Step3: The user enters the

necessary information in the
customer registration page. Step4: The system validates whether the
information submitted is correct or not.

Step5: The system register and displays

customer Registration Confirmation
page and leads to his or her account

Step6: The use case ends

Alternative 02. The input information invalid

curse of action Step 4.1 The system indicates the user information invalid
Step 4.2 The use case continues Step 3 of the basic course of action

Table 2 use case documentation for “ registration”

 Update Information

Actor Administrator
Use case ID 03
Use case name Update information

Description This use case allows To update user information

Pre-condition The administrator wants update user information

Post condition The administrator have information that will be updated

Basic course of Actor Action System Response

action

Page 19
 Online travel point system 2014
Step1: the administrator can request Step2: The system Displays user
to update the user information and information update page
other information in the database.

Step4: The system validates whether the

Step3: The administrator enters the information submitted is correct
necessary new information.

Step5: The system displays Confirmation

page and save the updated information.

Step6: The use case ends

Alternative curse 03. The input information invalid

of action Step 4.1 The system indicates the user information invalid
Step 4.2 The use case continues Step 3 of the basic course of action

Table 3 use case documentation for “update account”

Browse Information

Actors Administrator, Employee, Manager, Customer

Use case ID 04
Use case name Browse information

Description The user requests to view reservations of flights, hotel and car rent.

Pre-condition The user has been logged in.

Page 20
 Online travel point system 2014
Post condition The user has been viewed all reservations.

Basic course of Actor Action System Response

action
Step1: The user wants to view Step2: The System display view
reservation. reservation page.

Step3: The user enters select the

"reservation" button. Step4 : The system process selection

Step5: The system display the different

reservations select of the reservations
based on the need of the customer.

Step6: The use case ends

Alternative 04. The user selection is incorrect

curse of action Step 4.1 The system indicates the user information invalid
Step 4.2 The use case continues Step 3 of the basic course of action

Table 4 use case documentation for “Browse Reservation”

 View Profile
Actors Employee
Use case ID 05
Use case name Browse information

Description The Employee requests to view profiles of customers which can reserve
flights, hotel and car rent.

Page 21
 Online travel point system 2014
Pre-condition The Employee has been logged in.

Post condition The Employee has been viewed all reservations.

Basic course of Actor Action System Response

action
Step1: Employee wants to view
profile. Step2: The System display view profile
page.

Step3: Employee select from the

three reservations (flights, hotel
and car rent.).
Step4 : The system process selection

Step5: The system displays customer’s

profile which can book for that
reservation

Step6: The use case ends

Alternative 04. The user selection is incorrect

curse of action Step 4.1 The system indicates the customer’s information invalid
Step 4.2 The use case continues Step 3 of the basic course of action

Table 5 use case documentation for “view profile”

 Delete Reservation

Actors Administrator

Use case Id 06

Use case name Delete Reservation

Page 22
 Online travel point system 2014
Description This use case describe the canceling reservation process

Pre-condition In case the customer doesn’t want to ticket on that day

Post condition The selected reservation has been cancelled and updating the database
information
Basic course of Actor Action System Response
action
Step1: The administrator wants Step2:The system Displays Cancel
to cancel the reservation Reservation page

Step3: Enters the reservation

number

Step4: The system validates whether the

information submitted is correct

Step5: Selects the "Process

Cancellation" option.

Step6: The message "Reservation

Successfully Cancelled" is also
displayed.

Step7:The use case ends

Alternative 06. The input reservation number is invalid

curse of action Step 4.1 The system indicates the user information invalid
Step 4.2 The use case continues Step 3 of the basic course of action

Table 6 use case documentation for “delete reservation”

 Select Reservation

Actor Customer
Use case Id 07

Page 23
 Online travel point system 2014
Use case name Select reservation

Description This use case describes selection of reservation customer wants to get from
the three type of reservations.

Pre-condition Customer must be register.

Post condition Selecting reservation.

Basic course of action Actor Action System Response

Step1: The customer wants to

select the reservation.
Step2: The system Displays a page to
Step3: click on the Reservation select Reservation.
you want.

Step4: The system Displays Reservation

page for the selected type of reservation.

Step5: the use case ends.

Alternative curse of 07. The selection is invalid

action Step 4.1 The system display the selection value is incorrect
Step 4.2 Go to step 2 is basic course of action

Table 7 use case documentation for “select reservation”

 Generate Report

Actor Manager
Use case Id 08

Page 24
 Online travel point system 2014
Use case name Generate report

Description This use case gives information about sold tickets

Pre-condition In case the manager want to generate report on that day

Or for the week
Post condition The necessary report generated and saved to the database.
Basic course of Actor Action System Response
action
Step1: The manager wants to Step2:The system Displays generate
generate report report page

Step3:Manager enters the

generated report

Step4: The system checks whether the

report is correct or not

Step5: Selects the "Process of

report generation" option.

Step6: The message "report successfully

generated" is also displayed.

Step7:The use case ends

Alternative 08. The generated report is invalid

curse of action Step 4.1 The system indicates the user information invalid
Step 4.2 The use case continues Step 3 of the basic course of action

Table 8 Use case documentation for “generate report”

3.2.3 Sequence Diagram

 Sequence diagram for login

Page 25
 Online travel point system 2014

Figure 2 : sequence diagram for login

 Sequence diagram for registration

Page 26
 Online travel point system 2014

Figure 3 sequence diagram for registration

 Sequence diagram for browse information

Page 27
 Online travel point system 2014

Figure 4 sequence diagram for browse information

 Sequence diagram for update information

Page 28
 Online travel point system 2014

Figure 5 sequence diagram for update information

 Sequence diagram for delete information

Page 29
 Online travel point system 2014

Figure 6 sequence diagram for delete information

 Sequence diagram for view profile

Page 30
 Online travel point system 2014

Figure 7 Sequence diagram for view profle

Page 31
 Online travel point system 2014

Figure 8 sequence diagram for generate report

Page 32
 Online travel point system 2014
 Sequence diagram Select reservation

Figure 9 sequence diagram select reservation

Page 33
 Online travel point system 2014
3.2.4 Activity Diagram
 Activity diagram for log in form

Figure 10 activity diagram for log in form

Page 34
 Online travel point system 2014
 Activity diagram for customer registration

Figure 11 activity diagram for customer registration

Page 35
 Online travel point system 2014
 Activity diagram for update customer info

Figure 12 activity diagram for update customer info

Page 36
 Online travel point system 2014

 Activity diagram for browse info

Figure 13 activity diagram for browse info

Page 37
 Online travel point system 2014

 Activity diagram for view profile

Figure 14 view profile

Page 38
 Online travel point system 2014

 Activity diagram for select reservation

Figure 15 activity diagram for select reservation.

Page 39
 Online travel point system 2014

 Activity diagram for delete reservation

Figure 16 activity diagram for delete reservation

Page 40
 Online travel point system 2014

 Activity diagram for generate report

Figure 17 activity diagram for generate report

Page 41
 Online travel point system 2014

3.2.5 Analysis Level Class Diagram (conceptual modeling)

Figure 18 analysis level class diagram

Page 42
 Online travel point system 2014
3.2.6 User Interface Prototyping

Figure 19 user interface prototyping

3.2.7 Supplementary Specifications

Requirements applicable to the whole system or application such as security, conformance with
standards, or availability are inappropriate to capture in use cases.
All system errors shall be logged. Fatal system errors shall result in an orderly shutdown of the
system.
The system error messages shall include a text description of the error, the operating system error
code (if applicable), and the module detecting the error condition, a data stamp, and a time
stamp. All system errors shall be retained in the Error Log Database.
Page 43
 Online travel point system 2014

Chapter 4
4.1 Introduction System Design
This project is designed in a manner that solves the problems of the organization by minimizing
the work load that appears on the employees, because of the existing system is manual system. It
provides more efficient, reliable and time saving system. In this project design the team will be
 How the project is designed
 What are tasks done under the whole project
 The different modules and their way of functioning are described here.
Generally, the project will be designed by addressing all of the above criteria of project design. It
is designed to simplify functions of the manual system and it is capable of doing large amount of
works in short period of time with more accuracy and reliability.
This design system is to involve converting the description of the proposed system into logical
and then physical design specification. We expect one can understand our new system
implementation because it gives full description about whole system. Also one can understand
easily and enable to answer how the system developed and functioned in simplified manner.
The goal of system design according to the proposed project is to manage complexity by
dividing the system into smaller, manageable pieces.

Page 44
 Online travel point system 2014

4.2 Class Type Architecture

User Interface Layer

Process Layer

System Layer

Domain Layer

Persistence Layer

Data Source

Figure 20 Class type architecture

Page 45
 Online travel point system 2014
Layer Description

User interface This layer wraps access to the logic of our system. There are two categories of
interface class – user interface (UI) classes that provide people access to our
system and system interface (SI) classes that provide access to internal systems
to our system like database. The actors of this class are Administrator, Manager,
Employee and Customer.

Domain/Business This layer implements the concepts relevant to our business domain. The
Administrator has the major role in business domain.

Process The process layer implements business logic that involves collaborating with
several domain classes or even other process classes. The actors are administrator
and user.

Persistence Persistence layers encapsulate the capability to store, retrieve, and delete
objects/data permanently without revealing details of the underlying storage
technology in the system. Administrator has to update and delete database.

System System classes provide operating-system-specific functionality for our

applications. User can access the system by using user name and password.

Table 9 class type architecture

Page 46
 Online travel point system 2014

4.3 Class Modeling

Figure 21 class modeling

Page 47
 Online travel point system 2014

4.4 State Chart Modeling

 State chart for login

Figure 22 state chart for login

Page 48
 Online travel point system 2014
 State Chart for Registration

Figure 23 state charts for registration

Page 49
 Online travel point system 2014
 State Chart for Delete page

Figure 24 state chart for delete page

Page 50
 Online travel point system 2014

 State Chart for Update Page

Figure 25 state chart for update page

Page 51
 Online travel point system 2014

 State Chart for Browse info

Figure 26 Browse info

Page 52
 Online travel point system 2014

 State Chart for select reservation

Figure 27 select reservation

Page 53
 Online travel point system 2014

 State Chart for Generate report

Figure 28 Generate report

Page 54
 Online travel point system 2014

 State Chart for View profile

Figure 29 View profile

Page 55
 Online travel point system 2014

4.5 Collaboration Modeling

 Login

Figure 30 collaboration modeling for login

 Registration

Figure 31 collaboration modeling for registration

Page 56
 Online travel point system 2014
Delete Reservation

Figure 32 Collaboration modeling for delete reservation

Page 57
 Online travel point system 2014

 Employee view profile page

Figure 33 view profile page

Figure 34 Select reservation

Page 58
 Online travel point system 2014
 Browse information

Figure 35 Browse info

Figure 36 update info

Page 59
 Online travel point system 2014
 Manager generate report

Figure 37 generate report

Page 60
 Online travel point system 2014

4.6 Component Modeling

The component model illustrates the software components that will be used to build the system.
We build it up from the class model and written from scratch for the new system. Components
are high level aggregations of similar software pieces, and help us in providing a’ black box’
building block approach to software construction.

Figure 38 component modeling

Page 61
 Online travel point system 2014
5.1 Conclusions
Online travel point system provides many services such as Airline Reservation System (ARS),
Hotel Reservation System (HRS) and Car Rental System (CRS) and this project is designed in
order to meet the requirements of customer’s. Also the system combines the three systems which
are airline, car rental and hotel reservation systems.
Our project covers various features like online registration of the users, modifying the details of
the website by the management staff or administrator of the website, by adding, deleting or
modifying the customer details, flights or packages information, In developing this project all
group members contributed their full capability with maximum interest and all group members
get ways toward developing this project.
Finally our project solves the problem that occurred in the existing system.
5.2 Recommendations
According to scope of our project the team develops web application .Because of the time
Constraint we may have some limitations which should be taken in considerations, but in the
future the team believes that this system can be fully operational by having some functionalities
that are not included in the proposed system like paying online for the service we gate .
During the development of the project the group members faced many challenges However by
the cooperation of all the group members and an advisors the team is now able to reach to the
final result through this way we try to construct the road and hence this project has a big role in
Ethiopia.
Finally the team would recommend that further work should done on the system in order to make
the system perform better for interested organizations who would like to use online travel point
system in Ethiopia.

References
 Some paper material from tourist hotel and Ethiopian airline dire dawa branch

Page 62
 Online travel point system 2014
 Selameta magazine.
 BRC Budget tour and travel
 www.poshtravelethiopia.com
 Passion Ethiopia Tours (PET)
 For Travel to Ethiopia, Adventure, Guide and Information center
 Ethiopian tourism commission
 Fana Travel & Tours
 Ethio-Der Tour and Travel
 Eastern Travel & Tours Agency
 The Object Primer Second Edition book
Internet Site reference:
 www.tourismethiopia.com
 www.ethiopian airline.com
 www.adikatour&travel.com
 www.yamatoursethiopia.com
 www.elmitourethiopia.com
 www.ethiopiantourism.com

Page 63