ALPHA UNIVERSITY

HARGEISA SOMALILAND

……………………………..........................................................................................................................................

A RESEARCH PAPER

“Guest house management system”

(Naima Guest house)

Submitter for the partial fulfillment of the degree Of Bachelor of information

communication technology

“FACULTY”
Information communication technology

I.C.T

………………………………………………………………………………..

BY:
1. Libaan Arab Ege ID. 18/017
2. Abokor Muse Nuur ID. 18/549
3. Saed Ediris Mohamed ID. 18/014

(AUGUST…..2021)
CERTIFICATE:

This is to certify that the project report entitled “Guest house management system “done by
“Libaan Arab Ege”, id no: 18/017, “Saed Ediris Mohamed”, ID no 18/014and Abokor Muse
Nur”, id no: 18/549 under the guidance: “Mr Mubaarik Ali”, supervisor: Alpha university.
The matter embodied in this project work has been submitting earlier for the award of any degree
to the best of my knowledge and belief.
DECLARATION
We, Libaan Arab Ege, Abokor Musa Nur and Saed Edirs Mohamed hereby declare that this
thesis is our original work and has not been presented for the award of any degree in any other
university.

SIGNATURES & DATES

1: Libaan Arab Ege 2: Abokor Muse Nur 3: Saed Ederis Mohamed

Signature……………… Signature: ……….… Signature: …………….

Date: ………………….. Date: ………………….. Date: …………………..

This thesis has been submitted with my approval as supervisor & head of the department

Supervisor: Head of the department:

MR: MUBAARIK ALI MR: RASHIID

Signature: ……...……….. Signature……………..……..

Date…………….............. Date…………………………
 ACKNOWLEDGEMENT

In the name to Allah, the most merciful , the most compassionate all praise be to Allah first and
foremost we must acknowledge my limitless thanks to Allah ,the Ever Magnificent; the Ever-
Thankful, for His help and bless. We are very sure that this work would have never become
truth, without His guidance.

We thankful the people working in Naima guest house, those participated, provide the valuable
information, and encouraged to develop our project.

We are grateful Mr. Rashiid, Head of the department computer science for his valuable guidance
in carrying our work under his effective supervision, encouragement, enlightenment and
cooperation.

We are very grateful to our project supervisor Mr. Mubaaric Ali for the guidance’s, inspirations
and constructive suggestions that helpful we in the preparations of this project.

In addition tribute are made to the entire academic staff in the Department of Computer science
and president (Alpha University Collage) for the knowledge’s imparted to us during the years we
studied at the university All in all we appreciation every person who will encourage, support and
take part to written or develop our project directly or indirectly.

We also would like to thank to all our beloved friends, who have been so supportive along the
way of doing our thesis at large for their moral and financial supports to funding the project to
ensure successful completion of our project. We also thank our families for their generous
support they provided us throughout our entire lives and particularly through the process of
pursuing the Bachelor Degree. Because of their unconditional love and prayers, we have the
chance to complete this thesis.

v
 ABSTRACT

This is the document of the project proposal for developed a Guest house management
system for Naima guest house. It consist of the current background of the guest house
and problems having due to present system and how we are going to overcome those
matters through our proposed system.

After gathering requirements we have found that Naima guest house is using a manual
file based system for their processes. They are keeping a huge amount of file to handle
room details, etc. search for a record in the file system is really harsh. Although they
are not well secured there is probability of getting damaged due to a fire or any other
kind of a disaster.

The project aimed to build fully functional system in order to achieve the efficiency in
the hotel management. The overall mission of system developed is to mistake the guest
house Manager a quickly and easily complete the guest house management task.

vi
 LIST OF FIGURES

Figure 1 AGILE LIFE CYCLE.......................................................................................................3

Figure 2 LEVEL 0 DIAGRAM.....................................................................................................14
Figure 4 LEVEL 1 DIAGRAM.....................................................................................................14
Figure 5 USE CASE DIAGRAMS............................................................................................... 15
Figure 6 ACTIVITY DIAGRAMS............................................................................................... 16
Figure 7 SEQUENCE DIAGRAMS............................................................................................. 17
Figure 8 ER DIAGRAM............................................................................................................... 18
Figure 9 Architectural Design.......................................................................................................20
Figure 10 Admin Login.................................................................................................................21
Figure 11 ADMIN DASHBOARD...............................................................................................22
Figure 12 CUSTOMER RESERVATION....................................................................................23
Figure 13 ROOM.......................................................................................................................... 24
Figure 14 CONTACT....................................................................................................................25
Figure 15 Database Schema.......................................................................................................... 26

vii
TABLE OF CONTENTS

CHAPTER PAGE

ONE THE PROBLEM AND ITS SCOPE

1.0 Introduction ----------------------------------------------------------------- 1

1.1 Problem Background ------------------------------------------------------- 1

1.2 Problem Statement --------------------------------------------------------- 2

1.3 Objectives of the Project -------------------------------------------------- 2

1.3.1 General objective ----------------------------------------------------- 2

1.3.2 Specific objective ----------------------------------------------------- 2

1.4 Scope of the Project ------------------------------------------------------- 2

1.5 Procedure/Methodology --------------------------------------------------- 3

1.6 Expected outcome --------------------------------------------------------- 3

1.7 Schedule -------------------------------------------------------------------- 4

TWO REVIEW OF RELATED LITERATURE

2.0 Introduction ---------------------------------------------------------------- 5

2.1 Background information -------------------------------------------------- 5

2.2 Current system/domain analysis ---------------------------------------- 6

2.3 Comparison of similar system ------------------------------------------- 7

2.3.1 Technology with the proposed solution -------------------------- 7

2.3.2 Strategic objectives of the organizational Community ---------- 8

2.3.3 How it will work with other systems or the environment. ------ 8

2.4 similarities of systems ----------------------------------------------------- 8

viii
 2.5 work with other system --------------------------------------------------- 8

Three SYSTEM ANALYSIS

3.0 Introduction --------------------------------------------------------------- 9
3.1 Existing System Description -------------------------------------------- 9
3.2 Requirements specification of the to be system --------------------- 9
3.2.1 Functional Requirements ----------------------------------------- 10
3.2.2 Non-Functional Requirements ----------------------------------- 11
3.2.3 Hardware Requirements -----------------------------------------12
3.2.4 Software Requirements ------------------------------------------12
3.3 Requirements (Functional) modeling of the to be system --------- 12
3.3.1 Data flow Diagram (DFD) ---------------------------------------- 13
3.3.1.1 Context Diagram ------------------------------------------------ 13
3.3.1.2 Level 0 Diagram ------------------------------------------------- 14
3.3.1.3 Level 1 Diagram ------------------------------------------------- 14
3.4 Use Case Diagrams ------------------------------------------------------ 15
3.4.1 Use Case Descriptions -------------------------------------------- 16
3.4.2 Activity Diagrams -------------------------------------------------- 16
3.4.3 Sequence Diagrams ----------------------------------------------- 17
3.4.4 Data modeling of the to be system (Conceptual data
Modeling using ERD) ----------------------------------------------------- 18
FOUR SYSTEM DESIGN
4.0 Introduction---------------------------------------------------------------19
4.1 Architectural Design------------------------------------------------------ 20
4.2 User Interface Design---------------------------------------------------- 21
4.3 Database Design-------------------------------------------------------- 26
4.3.1 Database Schema---------------------------------------------------- 26
4.3.2 Data Normalization--------------------------------------------------- 27
4.3.3 Data Dictionary (Tables)-------------------------------------------- 28

ix
FIVE IMPLEMENTATION AND TESTING

5.0 INTRODUCTION----------------------------------------------------------- 30
5.1 DATABASE CODE---------------------------------------------------------- 30
5.2 PSEUDOCODE FORM------------------------------------------------------ 33
5.3 TESTING-------------------------------------------------------------------- 39
5.3.1 SYSTEM TESTING---------------------------------------------------- 40
5.3.2 UNIT TESTING------------------------------------------------------- 40
5.3.3 MODULE TESTING--------------------------------------------------- 40
5.3.4 INTEGRATION TESTING-------------------------------------------- 40
5.3.5 ACCEPTING TESTING----------------------------------------------- 40
SIX SUMMARY AND CONCULUSION.
6.0 INTRODUCTION---------------------------------------------------------- 41
6.1 FACTORS THAT FACILITATED YOUR THESIS PROJECT
COMPLETION----------------------------------------------------------------- 41
WHAT WE HAVE LEARNED DURING YOUR
6.2 PROJECT-------------- 41

6.3 LIMITATIONS------------------------------------------------------------ 42
6.4 PROJECT OBJECTIVES THAT ACHIEVED---------------------------- 42
Appendix ------------------------------------------------------------------------------------- I

REFERENCE---------------------------------------------------------------------------------I

x
 CHAPTER ONE

THE PROBLEM AND ITS SCOPE

1.0 INTRODUCTION

This chapter cover the background, problem statement, research objective, and scope of study,
methodology, expected outcome and schedule of the project, this study will occur at Naima
Guest House, Hargeisa Somaliland.

1.1 PROBLEM BACKGROUND

Since the emergence of electronic computer, decision making and processing of information has been
very easy. Data can now be stored on computer in a considerable low space and retrieved with in a
short period of time compared with the manual method which is tedious and time consuming as the
size of the file increases (Kennedy, k, 2001).

The application stores customer record and daily activities performed in the hotel such as
customer details, reservation details, creating a new room, vacating the rooms, etc. all are
computerized and the management is done without any difficulty. It also generate report for
authorized user on a daily basis and weekly report, thereby reducing the time and stress that will
be undergone using the manual method.

One major challenge in Business management in Somaliland is ineffective utilization of

resources and lack of proper record keeping leading to wastages and outright fraud by the staff.
The Guest house management information system is a system that aids the management of the
Customers data, guest house staff data, customer registration, Customer accommodation or
allocation into specific rooms, room reservation and Personnel staff management.

Guest house uses manual method for Customer registration and allocation and record keeping by
filling up the forms provided by the Guest house Staff and then the filled forms are kept in file-
folders. For the Guest house staff to know which rooms are free and available they would have to
check through their various files or keys and this system is a bit cumbersome and even more so
for a business that is trying to expand . The registration

1
 is based on manual work and all the processes are done manually. The same manual process is
involved in staff record, roster keeping and payroll.

1.2 PROBLEM STATEMENT

Guest house deals with problems that using manual system. The problems are those, which are
affecting the guest house in its daily routine work. So every problem must be solved with least
amount of time and energy. The problems faced by the existing system and hope to be solved by
the Guest house Management System are described below: and all records deals with manual
system that Time consuming, No security of data, Lack of efficiency. We will generate
computerized system Guest house.

1.3 OBJECTIVES OF THE PROJECT

1.3.1 GENERAL OBJECTIVE

The aim of the proposed system is to build Guest house Management system for Naima guest
house, Hargeisa, Somaliland.

1.3.2 SPECIFIC OBJECTIVE

 To check available rooms.

 To design a program which is user friendly and used easily by anyone
 To make electronic record booking.
 To provide secure system.
 Customer satisfaction.
1.4 SCOPE OF THE PROJECT

The scope of this project concerns Naima Guest House in Hargeisa Somaliland
This system will be cover which of the flowing functions:
 To check available rooms.
 To make electronic record booking.
 To provide secure system.
 Customer satisfaction.

2
1.5 PROCEDURE/METHODOLOGY
The methodology using our proposal project is agile development model is also a type of Incremental
model. Software is developed in incremental, rapid cycles. This results in small incremental releases
with each release building on previous Functionality. Each release is thoroughly tested to ensure
software quality is maintained. When new changes are needed to be implemented, Agile methodology
is a type of project management process, mainly used for software development, where demands and
solutions evolve through the collaborative effort of self-organizing and cross-functional teams and
their customers.

Figure 1 AGILE LIFE CYCLE

1.6 EXPECTED OUTCOME

We expectation our system to do the all tasks of the East Naima guest house such as facilitate the
book roomed , customer satisfaction, record of transaction in the system and we expect to be
effective, efficiency, high performance and security.

3
 1.7 SCHEDULE
Schedule is a listing of a project's tasks, usually with intended start task and end task dates.
Those items are often estimated by other information included in the project schedule of resource
allocation and task duration.

No Start Duration Task End Duration Resource

Libaan, Abokor
1 05/5/2021 Chapter one 10/5/2021
and Saeed

Abokor and Saeed

2 31/5/2021 Chapter two 05/6/2021

Libaan and Saeed

3 16/6/2021 Chapter three + Project phase 1 19/6/2021

4 20/6/2021 Chapter four +phase 2 24/6/2021 Libaan, Abokor

and Saeed

Abokor and Libaan

5 26/6/2021 Chapter five +phase 3 01/7/2021

Saeed, Libaan
6 10/7/2021 Chapter six + phase 4 14/7/2021 And Abokor

Abokor,Saeed,

7 18/7/2021 Submission for project 20/7/2021 And Libaan

4
 CHAPTER TWO

REVIEW OF RELATED LITERATURE

2.0 INTRODUCTION

The literature review deals with the topics and the researches that would help to understand
Guest house Booking System the existing systems that are similar to Hotel Reservation System.
The objective of this literature review is to analyze the related work to this project and
mechanisms used in previous studies.

2.1 BACKGROUND INFORMATION

They use a range of computer programs from everything to bookings, communications, security
and payments. If a hospitality establishment does not use some sort of advanced technological
system in its operations, it is deemed to be out of date and disorganized. Indeed, James Bardi
begins to outline the importance of these programs by claiming that “a well-organized
reservation system allows guest houses to ensure a steady flow of guests into their properties”.
Furthermore, “Profitable business ventures rely on effective marketing, which includes
reviewing people who require hotel products and services, determining their specific needs,
developing products and services that meet those needs, and making a profit on the sale of those
products and services” (Bardi, 2010, p. 136)

Louw, Door Janne, (2006, May 10, 2006). Description with UML Guest house Reservation
System. Create and develop a system that enables the customer to reserve Guest house room
online. The system can query the customer for date of arrival as well as length of stay, display
the available rooms and provide the customer an option to choose one or more rooms, calculate
the availability of rooms in the database, ask how many will be staying in the room, calculate
costs for the customer’s knowing and ask for additional service/s to acquire like dinner and
breakfast, and renting bikes. The researcher also uses figures accompanied with detailed
explanation for a better understanding of the readers.

5
(Oribiana and Cerafica), (2015) ) Study about Online Reservation System of Sallie Ville Resort
states that the system they developed helps the resort owner in terms of improving and updating
their current system. It is designed to have a user-friendly interface for the customer’s benefit to
have a more easy way and hassle free online reservation. Another study was conducted locally
by Agbanlog et.al (n.d.) on Web-based Guest house Reservation Management System for Tune.
It has similar problems to the studies mentioned above that the response to inquiries, reservation
process and the likes are slow. And in order to solve these, the system was developed for the
better operation of the guest house.

One of the existing websites for hotel is the Little guests. (Softwareadvice.com, 2018) “Little guests
is a cloud-based guest house management solution designed for small and midsize guests. It also
offers management services such as front-desk management, online booking, payment management
and channel management within a suite. It is suitable for bed, independent hotels and condos. Little
guests lets users to manage reservations, hotel check-ins and check-outs. It synchronizes availability
information across booking channels such as guest house websites and third-party booking websites.
It also enables users to design their guest house websites using templates which are fitted to their
preferences. It also offers direct booking, which allows users to accept online bookings from the
website. Users can also take payments via online through the website.

2.2 CURRENT SYSTEM/DOMAIN ANALYSIS

The current system of Naima Guest House is used in traditional manual system which was used
in before the technology and most of guest houses is used at the current time is manual so if you
need a Room for the guest house to your work place you must be go to the Guest house or call
the manager of to get which Room you want and ask him/her kinds Room of available in Guest
house. Guest House Management System normally use a note book and paper that take time to
collect and Difficulty in maintenance of records.

6
2.3 COMPARISON OF SIMILAR SYSTEM

We are similar the computerized systems and manual systems. The computerized systems are
better than manual system. The computerized systems provides easy management, it takes less
cost, time, raw materials, components, labor, or some other important input. The computerized
systems also increasing the customer satisfactions and reducing delay time or other costs. In
addition our project proposal has a lot of benefits are:

 To check available rooms.

 To make electronic record booking.
 Easy to manage customer record and activities.
 Easy to use GUI that does not requires specific training.
 Customer satisfaction.

2.3.1 TECHNOLOGY WITH THE PROPOSED SOLUTION

The proposal system is an automated interconnected all levels of organization such as owners,
managers, staffs and customers. This system provides every member a specific role and specific
tasks. The owners and managers Is easily to know the process of work using inside the system and
system permit owners and manage to checks and retrieve data outside of the organization because the
system is an online and responsive. The System will create and controls the flow of data, provides
data security, and manages network operations and will create the booking so customers can access.
The system reduces the tasks doing the staffs also to reduce operating costs and improve efficiency.

7
2.3.2 STRATEGIC OBJECTIVES OF THE ORGANIZATIONAL COMMUNITY

Our proposed system has several advantages that helps the community and the customer to adapt
easily:

 Easy and high performance and accuracy.

 To design a program which is user friendly and used easily by anyone.
 Fast access to database.
 Less error.

2.3.3 HOW IT WILL WORK WITH OTHER SYSTEMS OR THE ENVIRONMENT.

The new system is a simpler system for communication than the existing system. This system
will work through a storing the information of the customers, and record transactions, to enhance
the reliability of the service. This system provides every member a specific role and specific
tasks. It will also have the same functionality as the Hana Guest House.

2.4 SIMILARITIES OF SYSTEMS

The computerized systems are better than the manual systems. The computerized systems provided
market share advantage or preferential access to components, Manager or some other important
Adequate Record Keeping, Reduced Incidence of Fraud, Naima Guest House allows customers to
register and make booking Rooms online, Provide Data Security, Reduced Time Consumption, You
can fine the customers information easily.

2.5 WORK WITH OTHER SYSTEM

Naima Guest House doesn’t work have any connection with the other system. The proposed
solution system is not working with other system, because Naima Guest House is not connecting
restaurant and other Guest house.

8
 CHAPTER THREE

SYSTEM ANALYSIS

3.0 INTRODUCTION

This chapter is an important of the project proposal and it will be describes the existing system of
the organization and proposal system. This chapter is including requirement of proposal system
such functional and non-functional requirement, model requirement explain existing system
models and project proposal system models such as context diagram, level zero, level one. We
will be describing this chapter the connectivity and relationship between tables of the project
proposal system called Entity Relationship Diagram (ERD).

3.1 EXISTING SYSTEM DESCRIPTION

We discuss the Naima Guest House existing system. Using a manual system the users are
maintaining ledgers, books etc.To store the information customers, it is very difficult to maintain
historical data. So manager using the manual forms to fill up the customer orders, The manager
are tells the information orders to the costumers using through social media or telephone, after
that the manager prepared the latter called Invoice to write price then informing the customers
and they tell the final result the price if the customer is satisfying they make a complete.

3.2 REQUIREMENTS SPECIFICATION OF THE TO BE SYSTEM

The requirement specification document is produced at the end of Analysis of the system. This
document is a very comprehensive document and contains all the User requirements, Customer
requirement, and also Analysis diagrams. The Requirements are broadly divided into two groups:

 Functional requirements
 Non-functional requirements

9
3.2.1 FUNCTIONAL REQUIREMENTS

The main purpose of functional requirements within the requirement specification document is to
define all the activities or operations that take place in the system. These are derived through
interactions with the users and other parts of the system. Since the Requirements Specification is
a comprehensive document and contains a lot of data, it has been broken down into different
parts in this report. The functional requirements in the system are include:

Admin requirements

 Manage room

 Manage booking

 Manage guest house

 Check room availability

 Change password or add something

Customer requirements

 Registration

 Room booking

10
3.2.2 NON-FUNCTIONAL REQUIREMENTS

The non-functional requirements of the Guest Management systems areas described below:

1) Security

 The system must have protection from unauthorized users. By using phone number and
password.
 Also system show error if the phone number or password is not correct.
 To use the system, every user has to login by key in their username and password.
 The users permit to change their passwords for increased security.

2) Performance

 The time system required to process and respond when a user key in the Identification
that is phone number and password.
 The system is supposed to respond in less than 1seconds.
 The system should display a user friendly menu for users to choose from.

3) Availability

 Services of the system required be available 24 hours.

 There should be no limitation about the hardware platform that is to be used to run
the system.
 The system is available over the internet so that the Users like the managers and
customer can use the system from their respective locations which could be anywhere
in the organization.

11
3.2.3 HARDWARE REQUIREMENTS

Hardware Minimum system required

Processor Intel Celeron ®M CPU 420 1.60 GHZ
Ram 2GB
Hard disk 2GB
Monitor CRT or LCD size 15 or above
Keyboard Standard QWERT
Printer Laser printers of any time

3.2.4 SOFTWARE REQUIREMENTS

Software Minimum system required

Operating system Windows 7/8/10
Database MySQL (Back End
Programing language PHP (Front End)
Mark Up Language HTML5, JavaScript
Cascading Style Language CSS, Bootstrap

3.3 REQUIREMENTS (FUNCTIONAL) MODELING OF THE TO BE SYSTEM

The functional requirement modelling helps to visualize and explain how the components of the
system communicate and interact with each other and we represent conceptual into modelling.
This models can be directly connected to a variety of business process and explain the how they
interact into the system.

12
3.3.1 DATA FLOW DIAGRAM (DFD)

A DFD shows what kind of information will be input to and output from the system, how the
data will advance through the system, and where the data will be stored. It does not show
information about process timing or whether processes will operate in sequence or in parallel,
unlike a traditional structured flowchart which focuses on control flow, or a UML activity
workflow diagram, which presents both control and data flows as a unified mode.

13
3.3.1.2 LEVEL 0 DIAGRAM

Figure 3 LEVEL 0 DIAGRAM

3.3.1.3 LEVEL 1 DIAGRAM

Figure 3 LEVEL 1 DIAGRAM

14
3.4 USE CASE DIAGRAMS

Figure 4 USE CASE DIAGRAMS

15
3.4.1 USE CASE DESCRIPTIONS

This module maintains all the information related to users function and roles to permit the
proposal system. Users are divided into two categories to tell the above figure.

Admin

Customer

Admin manage room, manage booking, manage guest and manage payment.

Customer is registration, make payment, room booking, cancel booking and check room
availability.

16
3.4.3 SEQUENCE DIAGRAMS

Figure 5 SEQUENCE DIAGRAMS

17
3.4.4 DATA MODELING OF THE TO BE SYSTEM (CONCEPTUAL DATA
MODELING USING ERD)

Figure 6 ER DIAGRAM

18
 CHAPTER FOUR

SYSTEM DESIGN

4.0 Introduction

Database design is the process of producing a detailed data model of a database. Logical model
this stage is concerned with developing a database model based on requirements. The entire
design is on paper without any physical implementations or specific DBMS considerations.

Physical model this stage implements the logical model of the database taking into account the
DBMS and physical implementation factors.

So our database is online to available anytime and anywhere that network is available, our
database is MYSQL database.

MySQL is the world’s most popular open source database. With its proven performance,
reliability, and ease-of-use, MySQL has become the leading database choice for web-based
applications.

MySQL creates a database for storing and manipulating data, defining the relationship of each
table. Clients can make requests by typing specific SQL statements on MySQL. The server
application will respond with the requested information and it will appear on the clients' side.

This chapter will cover the all system design including database design, Architectural Design,
User interface design, Database schema and Database dictionary.

19
4.1 Architectural Design

Architecture design is the conceptual model that defines the structure, behavior, and more views
of a system. An architecture description is a formal description and representation of a system,
organized in a way that supports reasoning about the structures and behaviors of the system.

The below Architecture Diagram is a logical diagram that shows how each of the components in
a system is connected with each other and how are the data flowing between. We draw this
architecture diagram for a typical PHP based web application Naima Guest house management
system and it will be like the below diagram.

Figure 7 Architectural Design

20
Figure 8 Admin Login

21
Figure 9 ADMIN DASHBOARD

22
Customer Reservation
Figure 10 CUSTOMER RESERVATION
23
ROOMS

Figure 11 ROOMS

24
CONTACT

Figure 12 CONTACT

25
4.3 DATABASE DESIGN

4.3.1 DATABASE SCHEMA

Figure 13 Database Schema

26
4.3.2 Data Normalization
Normalization is the process of organizing data in a database. This includes creating tables and
establishing relationships between those tables according to rules designed both to protect the
data and to make the database more flexible by eliminating redundancy and inconsistent
dependency.

Redundant data wastes disk space and creates maintenance problems. If data that exists in more
than one place must be changed, the data must be changed in exactly the same way in all
locations. A customer address change is much easier to implement if that data is stored only in
the Customers table and nowhere else in the database.

Normalization is important for many reasons, but chiefly because it allows databases to take up
as little disk space as possible, resulting in increased performance. There are three main normal
forms and they are:

FIRST NORMAL (1NF)

The first normal form is the normal form of database where data must not contain repeating
groups. The database is in First normal form

 Eliminate repeating groups in individual tables.

 Create a separate table for each set of related data.
 Identify each set of related data with a primary key.
 And the order in which data is stored, does not matter.

SECOND NORMAL (2NF)

For a table to be in the Second Normal Form,

 Tables should be in the First Normal for

 Create separate tables for sets of values that apply to multiple records.
 Relate these tables with a foreign key.
 And, it should not have Partial Dependency.

27
THIRD NORMAL (3NF)

A table is said to be in the Third Normal Form when,

 It is in the Second Normal form.

 Eliminate fields that do not depend on the key.

4.3.3 Data Dictionary (Tables)

Room
Field Name Null key Description
Id No pk Its stored Room ID
Type Yes Its stored Room type
Bedding Yes Its stored Room bedding
Place Yes Its stored Room place
Cusid Yes Its stored Room cusid

RoomBook
Field Name Null key Description
Id No pk Its stored Customer ID
Title Yes Its stored customer title
Fname Yes Its stored customer fname
Lname Yes Its stored customer lname
National Yes Its stored customer National
Country Yes Its stored Customer country
Phone Yes Its stored customer phone
Troom Yes Its stored types of Room
Cin Yes Its stored cin
Cout Yes Its stored cout
Stat Yes Its stored stat
Nodays Yes Its stored number of days

28
Payment
Field Name Null key Description
Id No pk Its stored Customer ID
Title Yes Its stored customer title
Fname Yes Its stored customer fname
Lname Yes Its stored customer lname
Troom Yes Its stored types of Room
Tbed Yes Its stored Room bedding
Cin Yes Its stored check-in
Cout Yes Its stored check-out
Ttot Yes Its stored Ttot
Fintot Yes Its stored Fintot
Btot Yes Its stored Btot
Noofdays Yes Its stored number of days

Login
Field Name Null key Description
Id No pk Its stored admin ID
Usname Yes Its stored admin name
Pass Yes Its stored admin password

Contact
Field Name Null key Description
Id No pk Its stored Customer ID
Fullname Yes Its stored Customer name
Phoneno Yes Its stored Customer phone
Email Yes Its stored Customer email
Cdate Yes Its stored date
Approval Yes Its stored Customer approval

Newsletterlog
Field Name Null key Description
Id No pk Its stored Customer ID
Title Yes Its stored Customer title
Subject Yes Its stored subject
News Yes Its stored news

29
 CHAPTER FIVE

IMPLEMENTATION AND TESTING

5.0 INTRODUCTION
This chapter illustrates the system testing and implementation phases. The testing phases
Involves some modification to the pervious design phase and system testing has been done to
minimize the programming and system error. At the implementation phase, system requirements
such as hardware and software will be defined.

5.1 DATABASE CODE

Table Login

CREATE TABLE IF NOT EXISTS `login` (

`id` int(10) unsigned NOT NULL,
`usname` varchar(30) DEFAULT NULL,
`pass` varchar(30) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=3 ;

Table Newsletterlog

CREATE TABLE IF NOT EXISTS `newsletterlog` (

`id` int(10) unsigned NOT NULL,
`title` varchar(52) DEFAULT NULL,
`subject` varchar(100) DEFAULT NULL,
`news` text
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

30
Table Payment

CREATE TABLE IF NOT EXISTS `payment` (

`id` int(11) DEFAULT NULL,
`title` varchar(5) DEFAULT NULL,
`fname` varchar(30) DEFAULT NULL,
`lname` varchar(30) DEFAULT NULL,
`troom` varchar(30) DEFAULT NULL,
`tbed` varchar(30) DEFAULT NULL,
nroom` int(11) DEFAULT NULL,
`cin` date DEFAULT NULL,
`cout` date DEFAULT NULL,
`ttot` double(8,2) DEFAULT NULL,
`fintot` double(8,2) DEFAULT NULL,
`btot` double(8,2) DEFAULT NULL,
`noofdays` int(11) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

Table Room

CREATE TABLE IF NOT EXISTS `room` (

`id` int(10) unsigned NOT NULL,
`type` varchar(15) DEFAULT NULL,
`bedding` varchar(10) DEFAULT NULL,
`place` varchar(10) DEFAULT NULL,
`cusid` int(11) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=16 ;

31
Table Roombook

CREATE TABLE IF NOT EXISTS `roombook` (

`id` int(10) unsigned NOT NULL,
`Title` varchar(5) DEFAULT NULL,
`FName` text,
`LName` text,
`Email` varchar(50) DEFAULT NULL,
`National` varchar(30) DEFAULT NULL,
`Country` varchar(30) DEFAULT NULL,
`Phone` text,
`TRoom` varchar(20) DEFAULT NULL,
`Bed` varchar(10) DEFAULT NULL,
`NRoom` varchar(2) DEFAULT NULL,
`cin` date DEFAULT NULL,
`cout` date DEFAULT NULL,
`stat` varchar(15) DEFAULT NULL,
`nodays` int(11) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=2 ;

Table Contact

CREATE TABLE IF NOT EXISTS `contact` (

`id` int(10) unsigned NOT NULL,
`fullname` varchar(100) DEFAULT NULL,
`phoneno` int(10) DEFAULT NULL,
`email` text,
`cdate` date DEFAULT NULL,
`approval` varchar(12) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

32
5.2 PSEUDOCODE FORM

LOGIN
<?php
session_start();
if(isset($_SESSION["user"]))
{
header("location:home.php");
}

?>
<!DOCTYPE html>
<html >
<head>
<meta charset="UTF-8">
<title>NAIMA GOUEST HOUSE ADMIN</title>
<link rel="stylesheet" href="css/style.css">
</head>
<body>
<div id="clouds">
<div class="cloud x1"></div>
<!-- Time for multiple clouds to dance around --> <div
class="cloud x2"></div> <div class="cloud
x3"></div>
<div class="cloud x4"></div>
<div class="cloud x5"></div>
</div>
<div class="container"
<div id="login">
<form method="post">
<fieldset class="clearfix">

<p><span class="fontawesome-user"></span><input type="text"

name="user" value="Username" onBlur="if(this.value == '') this.value =
'Username'" onFocus="if(this.value == 'Username') this.value = ''"
required></p> <!-- JS because of IE support; better: placeholder="Username" -
->
<p><span class="fontawesome-lock"></span><input type="password"
name="pass" value="Password" onBlur="if(this.value == '') this.value =
'Password'" onFocus="if(this.value == 'Password') this.value = ''"
required></p> <!-- JS because of IE support; better: placeholder="Password" --
>
<p><input type="submit" name="sub" value="Login"></p>

33
 </fieldset>
</form>
</div> <!-- end login -->
</div>
<div class="bottom"> <h3><a href="../index.php">EAST AFRICA
HOMEPAGE</a></h3></div>
</body>
</html>
<?php
include('db.php');
if($_SERVER["REQUEST_METHOD"] == "POST")
{ // username and password sent from form

$myusername = mysqli_real_escape_string($con,$_POST['user']);
$mypassword = mysqli_real_escape_string($con,$_POST['pass']);

$sql = "SELECT id FROM login WHERE usname = '$myusername' and pass =

'$mypassword'";
$result = mysqli_query($con,$sql);
$row = mysqli_fetch_array($result,MYSQLI_ASSOC);
$active = $row['active'];

$count = mysqli_num_rows($result);

/ If result matched $myusername and $mypassword, table row must be 1 row

if($count == 1) {
$_SESSION['user'] = $myusername;
header("location: home.php");
}else {
echo '<script>alert("Your Login Name or Password is invalid") </script>';
}
}
?>

ROOM
<?php
session_start();
if(!isset($_SESSION["user"]))
{
header("location:index.php");
}

34
?>
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<title>NAIMA GUESDT HOUSE</title>
<!-- Bootstrap Styles-->
<link href="assets/css/bootstrap.css" rel="stylesheet" /> <!--
FontAwesome Styles-->
<link href="assets/css/font-awesome.css" rel="stylesheet" /> <!--
Custom Styles-->
<link href="assets/css/custom-styles.css" rel="stylesheet" /> <!--
Google Fonts-->
<link href='http://fonts.googleapis.com/css?family=Open+Sans' rel='stylesheet'
type='text/css' />
</head>
<body>
<div id="wrapper">
<nav class="navbar navbar-default top-navbar" role="navigation"> <div
class="navbar-header">
<button type="button" class="navbar-toggle" data-toggle="collapse" data-
target=".sidebar-collapse">
<span class="sr-only">Toggle navigation</span>
<span class="icon-bar"></span> <span class="icon-
bar"></span>
<span class="icon-bar"></span>
</button>
<a class="navbar-brand" href="home.php">MAIN MENU </a>
</div>

<ul class="nav navbar-top-links navbar-right">

<li class="dropdown">
<a class="dropdown-toggle" data-toggle="dropdown" href="#" aria-
expanded="false">
<i class="fa fa-user fa-fw"></i> <i class="fa fa-caret-down"></i> </a>
<ul class="dropdown-menu dropdown-user">
<li><a href="usersetting.php"><i class="fa fa-user fa-fw"></i> User
Profile</a>
</li>
<li><a href="settings.php"><i class="fa fa-gear fa-fw"></i>
Settings</a>

35
 </li>
<li class="divider"></li>
<li><a href="logout.php"><i class="fa fa-sign-out fa-fw"></i>
Logout</a>
</li>
</ul>
<!-- /.dropdown-user -->
</li>
<!-- /.dropdown -->
</ul>
</nav>
<!--/. NAV TOP -->
<nav class="navbar-default navbar-side" role="navigation"> <div
class="sidebar-collapse"> <ul class="nav" id="main-menu">

<li>
<a href="settings.php"><i class="fa fa-dashboard"></i>Rooms
Status</a>
</li>
<li>
<a class="active-menu" href="room.php"><i class="fa fa-plus-
circle"></i>Add Room</a>
</li>
<li>
<a href="roomdel.php"><i class="fa fa-desktop"></i> Delete
Room</a>
</li>
</div>
</nav>
<!-- /. NAV SIDE -->

<div id="page-wrapper" >

<div id="page-inner">
<div class="row">
<div class="col-md-12">
<h1 class="page-header">
NEW ROOM <small></small>
</h1>
</div>
</div>

<div class="row">

36
 <div class="col-md-5 col-sm-5">
<div class="panel panel-primary">
<div class="panel-heading">
ADD NEW ROOM
</div>
<div class="panel-body">
<form name="form" method="post">
<div class="form-group">
<label>Type Of Room *</label>
<select name="troom" class="form-control" required>
<option value selected ></option>
<option value="FAMILY ROOM">FAMILY ROOM</option>
<option value="DOUBLE BED ROOM">DOUBLE BED ROOM</option>
<option value="VIP SINGLE ROOM">VIP SINGLE ROOM</option>
<option value="SINGLE ROOM">SINGLE ROOM</option>
</select>
</div>

<div class="form-group">
<label>Bedding Type</label>
<select name="bed" class="form-control" required>
$sql ="INSERT INTO `room`( `type`, `bedding`,`place`) VALUES
('$room','$bed','$place')" ;
if(mysqli_query($con,$sql))
{
echo '<script>alert("New Room Added") </script>' ; }else
{
echo '<script>alert("Sorry ! Check The System") </script>' ;
}
}
}

?>
</div>
</div>
</div>

<div class="row">
<div class="col-md-6 col-sm-6">
<div class="panel panel-primary">
<div class="panel-heading">
ROOMS INFORMATION
</div>
<div class="panel-body">

37
 <!-- Advanced Tables -->
<div class="panel panel-default">
<?php
$sql = "select * from room limit 0,10";
$re = mysqli_query($con,$sql)
?>
<div class="panel-body">
<div class="table-responsive">
<table class="table table-striped table-bordered table-
hover" id="dataTables-example">
<thead>
<tr>
<th>Room ID</th>
<th>Room Type</th>
<th>Bedding</th>

</tr>
</thead>
<tbody>

<?php
while($row= mysqli_fetch_array($re))
{
$id = $row['id'];
if($id % 2 == 0)
{
echo "<tr class=odd gradeX>
<td>".$row['id']."</td>
<td>".$row['type']."</td>
<th>".$row['bedding']."</th>
</tr>";
}
else
{
echo"<tr class=even gradeC>
<td>".$row['id']."</td>
<td>".$row['type']."</td>
<th>".$row['bedding']."</th>
</tr>";

}
}
?>
</tbody>

38
 </table>
</div>

</div>
</div>
<!--End Advanced Tables -->
</div>
</div>
</div>
</div>
</div>
<!-- /. PAGE INNER -->
</div>
<!-- /. PAGE WRAPPER -->
</div>
<!-- /. WRAPPER -->

<!-- JS Scripts-->
<!-- jQuery Js -->
<script src="assets/js/jquery-1.10.2.js"></script> <!--
Bootstrap Js -->
<script src="assets/js/bootstrap.min.js"></script> <!--
Metis Menu Js -->
<script src="assets/js/jquery.metisMenu.js"></script> <!--
Custom Js -->
<script src="assets/js/custom-scripts.js"></script>

</body>
</html>

5.3 TESTING
The testing phase involves the testing of the developed system using various kinds of data. An
elaborated testing of data is prepared and a system is tested using the test data. While testing,
errors are noted and corrections remade, the corrections are also noted for future use.

39
5.3.1 SYSTEM TESTING
Testing is a set of activities that can be planned in advance and conducted systematically. The
proposed system is tested in parallel with the software that consists of its own phases of analysis,
implementation, testing and maintenance. Following are the tests conducted on the system.

5.3.2 UNIT TESTING

During the implementation of the system each module of the system was tested separately to
uncover errors within its boundaries. User interface was used as a guide in the process.

5.3.3 MODULE TESTING

A module is composed of various programs related to that module. Module testing is done to
check the module functionality and interaction between units within a module.

It checks the functionality of each program with relation to other programs within the same
module. It then tests the overall functionality of each module.

5.3.4 INTEGRATION TESTING

Integration testing is a systematic technique for constructing the program structure while conducting
tests to uncover errors associated with interfacing. The objective is to take unit-tested module and
build a program structure that has been dictated by design.

5.3.5 ACCEPTING TESTING

The software has been tested with the realistic data given by the customer. The customer
satisfying all the requirements specified by them has also developed the software within the time
limitation specified. A demonstration has been given to the client and the end-user giving all the
operational features

40
 CHAPTER SIX

SUMMARY AND CONCLUSION

6.0 INTRODUCTION

In this chapter we focusing summary and conclusion of project focusing including factors that
facilitate completion of project, learning development team, limitations, project objectives that
achieved.

6.1 FACTORS THAT FACILITATED YOUR THESIS PROJECT COMPLETION

The factors that facilitated our thesis project completion is

 Group cooperation.
 All process can be done automatically.
 Planning the process of the project.
 Updating of information becomes to easier.

6.2 WHAT WE HAVE LEARNED DURING YOUR PROJECT

The main point that we learn:

 Time Management.
 Using system analysis and design techniques like data flow diagram in designing the
system.
 Understanding the database handling and query processing.
 How to fixed error system.
 How to create a web application.
 Create ER Diagram.

41
6.3 LIMITATIONS

The problem faced was conducting staff interviews. The questions to be ask needed to be
structure according to the job description. Every question answered by different staff members
was different according to their own problems and issues and their way of solving them.
Summarizing those answers identifying entities and relations was not easy, either

The challenges we faced during the project work have increased my confidence on tackling
challenges that we us face during my work life in the same field. The time management was one
of the greatest challenges during the project work. The time that we had for the project was very.
Managing the time for studies, planning the project work, and starting to do the work was very
challenging.

6.4 PROJECT OBJECTIVES THAT ACHIEVED

The main objective of this project is to develop Guest house management system for
Naima guest house to reduce the drawbacks of the manual system.

The aim of the project is:-

 To check available rooms.

 To design a program which is user friendly and used easily by anyone.
 To store, retrieve and manage customer details.
 To make electronic record booking.
 To provide secure system.
 Record of transaction.
 Customer satisfaction.

42
Appendix A

Budget frame

No Description Monthly
1 CHAPTER ONE JULAY
2 CHAPTER TWO JULAY
3 CHAPTER THREE JULAY
4 CHAPTER FOUR OUGUST
5 CHAPTER FIVE OUGUST
6 CHAPTER SIX OUGUST

Appendix B
Time frame

No Description Unit Cost

1 TRANSPORTATION $50
2 BREAKS $40
3 ACCESSORY $35
4 TELEPHONE $30
5 INTERNET $45
6 TOTAL $200

I
REFERENCE

th
1] Bardi J.A (2010). Wiley: Guest house Office Management 5 Edition. [Online]. Available:

http://eu.wiley.com/WileyCDA/WileyTitle/productCd-
th
EHEP0001784.html?filter=TEXTBOX [Accessed 27 May 2010]

[2] Oribiana and Cerafica. (2015). Online Reservation system.

[3] Kennedy, k, (1999). & KuljitKaur, Pooja. (1982). New business models in online guest
house distribution: emerging private sales versus leading IDS. Service Business, 7(2), 183-
205.

[4]Louw, D. J. (2006). Description with UML for a Guest house Reservation System

http://www.liacs.nl/assets/Bachelorscripties/2006-08JanneLouw.pdf

[5] Dennis, A., Tegarden, D., Wixom, B. “Systems Analysis and Design with UML
Version 2.0”, John Wiley & Sons, Inc., Second edition, 2005.

[6] MySQL, 2013. Top reasons why use SQL. Retrieved from SQL:
http://www.mysql.com/why-mysql/topreasons.html.

[7] xamp server URL: https://www.apachefriends.org/index.html/docs.

[8] Afred Winter 2nd edition. Health Information System architecture and strategies.

[9] O’Docherty, M. “Object-Oriented Analysis and Design Understanding System

Development with UML 2.0”, John Wiley & Sons, Inc., First edition, 2005. [6] ERD
designing diagram online.

URL:
https://online.visualparadigm.com/diagrams.jsp#diagram:proj=0&type=ERDiagram.

II