ADAMA SCIENCE AND TECHNOLOGY UNIVERSITY

SCHOOL OF ELECTRICAL ENGINEERING & COMPUTING

DEPARTMENT OF COMPUTER SCIENCE AND
ENGINEERING

Semester Project

iTOUR – an app for tour guidance and management

Group Members
Name ID
Abdurezak Shemsedin UGR/16680/11
Henok Belachew UGR/17210/11
Mahlet Sintayehu UGR/17329/11
Meron Muleta UGR/17369/11
Rediet Melaku UGR/17573/11

Advisor: Mr. Rabira Geleta

Submission Date: Jun 26, 2023
Adama, Ethiopia.

1
Submitted by
Abdurezak Shemsedin 26/06/2023
Signature Date
Student

26/06/2023
Henok Belachew
Date
Student Signature
Mahlet Sintayehu
26/06/2023

Student
Signature Date

26/062023
Meron Muleta

Student
Signature Date

Rediet Melaku 26/06/2023

Student Signature Date

Advisor

Mr. Rebira

Signature

2
Acknowledgement
First and foremost, we would like to express our warmest gratitude for our Advisor, Mr. Rabira Geleta, for all
his guidance, comments and suggestions during the development of this project. We learned a variety of topics
and tools while working on this project.
We would also like to express our heartfelt gratitude to the department and staff of Computer Science and
Engineering for all the support they have provided for us.

3
Table of Contents

List of Tables...............................................................................................I
List of Figures…..........................................................................................II
Key Words..................................................................................................III
Acronyms….................................................................................................IV
Preface.........................................................................................................V

Chapter One: Introduction

1.1 Introduction….........................................................................................1
1.2 Background of the project…...................................................................1
1.3 Statement of the problem......................................................................2
1.4. Objective of the project…......................................................................3
1.4.1 General Objective…..........................................................................3
1.4.2 Specific Objective….........................................................................3
1.5. Scope and Limitation…..........................................................................3
1.5.1 Scope of the study…........................................................................3
1.52 Limitation …......................................................................................3
1.6 Feasibility Study…...................................................................................4
1.6.1 Technical Feasibility…........................................................................4
1.6.2 Operational Feasibility.......................................................................4
1.6.3 Economic Feasibility…........................................................................4
1.7 Significance of the project…...................................................................5
1.8 Beneficiaries of the project…..................................................................5
1.9 Methodology...........................................................................................6
1.9.1 Data collection methodology…........................................................6
1.9.2 Conceptual modeling…....................................................................6
1.9.3 Secondary data collection methodology.........................................6
1.10 Development tools................................................................................6
1.11 Project deliverables…...........................................................................7
1.11 Cost breakdown....................................................................................7
1.13 Task and Schedule…..............................................................................8
1.14 Team Composition….............................................................................9

4
Chapter 2: Existing Systems
2.1 Description of existing system...............................................................10
2.2 Major function of existing system.........................................................10
2.3 Major function of current system..........................................................10
2.4 Drawback of current System................................................................11
2.5 Business rule…......................................................................................11

Chapter 3: Proposed System

3.1 Overview...............................................................................................13
3.2 Functional Requirement….....................................................................13
3.3 Non-functional Requirement….............................................................14
3.4 System Model…....................................................................................16
3.4.1 Scenario.........................................................................................16
3.4.2 Use case model…...........................................................................27
3.4.3 Use case Description......................................................................30
3.5 Object Model….....................................................................................39
3.5.1 Data dictionary…...........................................................................39
3.5.2 Class Diagram................................................................................43
3.6 Dynamic Model…..................................................................................44
3.6.1 Sequence Diagram........................................................................44
3.6.2 Activity Diagram............................................................................53
3.6.3 State chart Diagram.......................................................................62

Chapter 4: System Design

4.1 Overview of the System........................................................................65
4.2 Purpose of the System Design..............................................................65
4.3 Design Goals….......................................................................................65
4.4 Proposed System Architecture…............................................................67
4.5 Subsystem Decomposition…..................................................................67
4.6 Subsystem Description….......................................................................69
4.7 Persistent Data Management...............................................................70
4.8 Components Diagram...........................................................................75
4.9 Database Design...................................................................................77
41.10 Access Control..................................................................................78
4.11 User Interface Design.........................................................................79

5
Chapter 5: Implementation (Prototype)
5.1 Overview............................................................................................87
5.2 Coding Standard.................................................................................87
5.3 Prototype….........................................................................................87
5.4 Implementation Detail…....................................................................88
5.4.1 Client-side…...................................................................................88
5.4.2 Server Side.....................................................................................89
5.5. Deployment....................................................................................90
Chapter 6: Testing Plan
6.1 Overview............................................................................................92
6.2 Scope..................................................................................................92
6.3 resource…...........................................................................................92
6.4 Schedulel…..........................................................................................92
6.5 Test Case Scenario and requirements..............................................93
6.5.1 Test Case Scenario...................................................................94
Chapter 7: User manual
7.1 User manual and demo......................................................................96
7.2 Git structure andf version control......................................................99
Chapter 8: Conclusion and recommendation
8.1 Conclusion .........................................................................................103
8.2 Recommendation...............................................................................103

Reference.............................................................................................104

6
 List of Tables
Table 1.1 Software Development Tools
Table 1.2 Cost Breakdown
Table 1.3 Task and Schedule
Table 1.4 Team Composition
Table 3.1 Register Scenario.
Table 3.2 Log in Scenario
Table 3.3 Booking Scenario
Table 3.4 Add, update and delete Scenario.
Table 3.5 Search Scenario
Table 3.6 View Weather Condition Scenario
Table 3.7 View attraction place Scenario
Table 3.8 View Travel History Scenario
Table 3.9 Place Description Scenario
Table 3.10 View Location Scenario
Table 3.11 Review and Rate Scenario
Table 3.12 Update Profile Scenario
Table 3.13 Manage Reservations
Scenario Table 3.14 Register Use case
Description. Table 3.15 Login Use case
Description Table 3.16 Booking Use case
Description Table 3.17 Search Use case
Description
Table 3.18 Manage Reservation Use Case Description.
Table 3.19 View weather Condition Use case Description
Table 3.20 View Location Use Case Description
Table 3.21 View Place Description Use Case Description.
Table 3.22 View Travel History Use Case Description
Table 3.23 Manage Services
Table 3.24Review and Rate
Table 3.25 Data Dictionary
Table 4.1 Subsystem Decomposition Description

7
 List of Figures
Figure 3.1 Use Case Diagram
Figure 3.2 Class Diagram
Figure 3.3 Sequence Diagram for User registration
Figure 3.4 Sequence Diagram for Sign in
Figure 3.5 Sequence Diagram for update Profile
Figure 3.6 Sequence Diagram for Update service
Figure 3.7 Sequence Diagram for Delete Service
Figure 3.8 Sequence Diagram for Add Service
Figure 3.9 Sequence Diagram for Manage Reservation
Figure 3.10 Sequence Diagram for Booking
Figure 3.11 Sequence Diagram for Place Description
Figure 3.12 Activity Diagram for Sign in
Figure 3.13 Activity Diagram for Sign up
Figure 3.14 Activity Diagram for Add Service
Figure 3.15 Activity Diagram for Delete
Service
Figure 3.16 Activity Diagram for Manage Reservation
Figure 3.17 Activity Diagram for Place Description
Figure 3.18: update service activity diagram
Figure 3.19 Activity Diagram for Booking
Figure 3.20 State Chart Diagram 1 Figure 3.21 State Chart Diagram 2
Figure 3.22 State Chart Diagram 3
Figure 3.23 State Chart Diagram 4
Figure 3.24 State Chart Diagram 5
Figure 3.25 State Chart Diagram 6
Figure 4.1 Proposed System Architecture
Figure 4.2 System Decomposition
Figure 4.3 Mapping Hotel object
Figure 4.4 Mapping Transportation object
Figure 4.5 Mapping Notification object
Figure 4.6 Mapping User object
Figure 4.7 Mapping Admin object
Figure 4.8 Mapping Review object
Figure 4.9 Mapping Payment object
Figure 4.10 Mapping Tour Place object
Figure 4.11 Mapping Booking object
Figure 4.12 Mapping Search object

8
Figure 4.13 Component’s diagram
Figure 4.14 Database design
Figure 4.15 Splash screen and
onboarding.
Figure 4.16 Register and Login Page

Figure 4.17 Home page and

search
Figure 4.18 Booking, hotel
and payment
Figure 4.19 payment and hotel

Figure 4.20 Location Page

Figure 4.21 Transportation booking and payment

Figure 4.22 Favorite page

Figure 4.23 Notification
Figure 4.24 Personal profile
Page
Figure 4.25 change password
Figure 4.26 History and rating
Figure 4.27 Edit and delete page
Figure 7.1: landing page of our project
Figure 7.2 Search and hotels
Figure 7.3 Payment and confirmation
Figure 7.4 Location and maps
Figure 7.5 Favorite page of our system
Figure 7.6 personal and booking

9
Key Words
Architecture: the art and practice of designing.
Back end: is back part of or section of something.
Interface: An Interface is a program that allows a user to interact with computers in person or over a
network.
Mapping: The act or operation of making maps.
Subsystem: A system that is part of some larger system.
UML: Unified Modeling Language is a modeling language which helps to simplify the process of
software design.
Front-end: is the front part of or section of something. Mapping: The act or operation of making
maps. Relational database: Is a type of database that stores and provides access to data points that are
related to one another.
Subsystem: A system that is part of some larger system.

10
Acronyms
API - Application Programming Interface
UML - Unified Modeling Language
GPS - Global Positioning System
PC - Personal Computer
ASTU- Adama Science and Technology University

11
Preface
This document states the activities and operations of a travel agent system. It goes
in detail of how the current system works and how we plan to smoothly digitize the
existing system by means of mobile application and payment methods. After the
completion and implementation of the project we hope it positively affects the lives
of people and the operation of event management.

12
13