CONTENTS

CHAPTER-1 INTRODUCTION……………………………………………………………………………………………………………
1.1) Abstract of the Project…………………………………………………………………………………………………………….
1.2) Objective of Project………………………………………………………………………………………………………………….
1.3) Scope of the Project…………………………………………………………………………………………………………………
1.4) Introduction of the Project……………………………………………………………………………………………………….
1.5) Mission of the Project……………………………………………………………………………………………………………….
CHAPTER-2 LITERATURE REVIEW……………………………………………………………………………………………………..
2.1) Existing System………………………………………………………………………………………………………………………….
2.2) Drawbacks…………………………………………………………………………………………………………………………………
2.3) Advantages of Proposed System…………………………………………………………………………………………………
CHAPTER-3 DEVELOPMENT METHODOLOGY ……………………………………………………………………………………
3.1) System Development Life Cycle …………………………………………………………………………………………………
3.2) Agile Software Development………………………………………………………………………………………………………
3.3) Waterfall Methodology ……………………………………………………………………………………………………………..
3.4) Development Methodology ………………………………………………………………………………………………………
3.5) Observations and Report……………………………………………………………………………………………………………
CHAPTER -4 WEBSITE REQUIREMENTS ……………………………………………………………………………………………
SPECIFICATIONS………………………………………………………………………………………………………………………………
4.1) Functional Requirements……………………………………………………………………………………………………………
4.2) Non-Functional Requirements……………………………………………………………………………………………………
4.3) Website Specification………………………………………………………………………………………………………………..
CHAPTER-5 SYSTEM ANALYSIS AND DESIGN PHASE…………………………………………………………………………
5.1) Use Case Diagram……………………………………………………………………………………………………………………..
5.2) Sequence Diagram…………………………………………………………………………………………………………………….
5.3) Webpage Sitemap…………………………………………………………………………………………………………………….
5.4) Mockup……………………………………………………………………………………………………………………………………
5.5) A Rational Behind Design Decision……………………………………………………………………………………………
5.6) System Deployment Diagram……………………………………………………………………………………………………
5.7) Entity Relational Diagram…………………………………………………………………………………………………………
5.8) Database Design………………………………………………………………………………………………………………………
CHAPTER-6 IMPLEMENTATION AND TESTING…………………………………………………………………………………
6.1) FUNCTIONAL TESTING……………………………………………………………………………………………………………..
6.2) USABILITY TESTING………………………………………………………………………………………………………………….
6.3) HEURISTICS EVALUATION…………………………………………………………………………………………………………
CHAPTER-7 WEBSITE DEMONTRATION……………………………………………………………………………………………
CHAPTER-8 FUTURE SCOPE……………………………………………………………………………………………………………
CHAPTER-9 CONCLUSIONS……………………………………………………………………………………………………………..
REFERENCES …………………………………………………………………………………………………………… …………………….

----------------------------------------------------------------------------------------------------------------------------------------------
 CHAPTER 1: INTRODUCTION

ABSTRACT OF THE PROJECT

The purpose of Airbnb website is to automate the existing manual system by the help of computerized
equipment’s and full-fledged computer software, fulfilling their requirements, so that their valuable
data/information can be stored for a longer period with easy accessing and manipulation of the same. The
required software and hardware are easily available and easy to work with.

airbnb website, as described above, can lead to error free, secure, reliable and fast management system. It
can assist the user to concentrate on their other activities rather to concentrate on the record keeping. Thus, it
will help organization in better utilization of resources. The organization can maintain computerized records
without redundant entries. That means that one need not be distracted by information that is not relevant,
while being able to reach the information.

The aim is to automate its existing manual system by the help of computerized equipment’s and full-fledged
computer software, fulfilling their requirements, so that their valuable data/information can be stored for a
longer period with easy accessing and manipulation of the same. Basically, the project describes how to
manage for good performance and better services for the clients.

OBJECTIVE OF PROJECT

The main objective of the Project on airbnb website is to manage the details of Hotel, Rooms, Services,
Payments, Bookings. It manages all the information about Hotel, Customers, Bookings, Hotel. The project is
totally built at administrative end and thus only the administrator is guaranteed the access. The purpose of the
project is to build an application program to reduce the manual work for managing the Hotel, Rooms,
Customers, Services. It tracks all the details about the Services, Payments, Bookings.

SCOPE OF THE PROJECT

It may help collecting perfect management in details. In a very short time, the collection will be obvious,
simple and sensible. It will help a person to know the management of passed year perfectly and vividly. It also
helps in current all works relative to airbnb website. It will be also reduced the cost of collecting the
management & collection procedure will go on smoothly.

Our project aims at Business process automation, i.e. we have tried to computerize various processes of airbnb
website.

In computer system the person has to fill the various forms & number of copies of the forms can be easily
generated at a time. In computer system, it is not necessary to create the manifest but we can directly print it,
which saves our time. To assist the staff in capturing the effort spent on their respective working areas. To
utilize resources in an efficient manner by increasing their productivity through automation. The system
generates types of information that can be used for various purposes.

2|Page
INTRODUCTION OF PROJECT

Airbnb website is a website where the management of entire hotel is computerized. The Airbnb website is
designed using ruby on rails as the rich GUI for front end and SQL Server as the secured backend database.

In this project the details are maintained like customer details, reservation details, Booking details and billing
details The reservation process of reserving rooms for the customers, canceling the reserved rooms, booking
the rooms , vacating the rooms, the restaurant management, billing process, etc all are computerized and the
management is done without any difficulty.

The reports can be viewed completely and the head of the management daily or weekly or monthly can review
it. For company auditing it will be more useful. This Proposed System will be interactive, faster and user-
friendly for the end users. Using the Airbnb website, the following activities can be performed.

 Room Service
 Check In
 Check Out
 Nearby places
 Login

MISSION OF THE PROJECT

The mission is to facilitate easy management and administration of a hotel with capabilities to do Booking or
reservations of the rooms, Cancellation of the rooms, Cash billing, Room service, Restaurant service,
Restaurant billing, Total billing, Travels arrangement etc. using the automated Airbnb website. One can keep
detailed records or info on an unlimited number of customers. The system lets the user know which all rooms
are available for occupancy at any point of time. This makes the booking considerably faster. And thus, helps
the hotel in better management and reduce a lot of paper work as well as manpower.

3|Page
 CHAPTER 2: LITERATURE REVIEW

EXISTING SYSTEM

Airbnb website involves maintaining various operations of the hotel like Booking or reservations of the rooms,
Cancellation of the rooms, Cash billing, Room service, Restaurant service, Restaurant billing, Total billing,
Travels arrangement etc. The existing system is a manual one and there is lot of issues like erroneous data,
slow process, lack of security etc. Finding out the final payment amount completely relies on the hotel
manager and if he is absent, it takes a long time to find out the details during check out and is prone to errors.

DRAWBACKS OF THE EXISTING SYSTEM

 Manual entry consumes more time.

 It is difficult to maintain bulk of record in manual.
 Restrictions in the users.
 Not easy to prepare the daily reports.
 Lack of accuracy and error prone.
 Overall efficiency is less.
 Lot of paperwork.
 Non-secure.
 No perfect maintenance of report.
 No method to trace details.
 Human errors.
 The manual system is too slow.
 Searching is more time consuming.

ADVANTAGES OF PROPOSED SYSTEM

 Secure data.
 Faster process.
 Error Free.

4|Page
 CHAPTER 3: DEVELOPMENT METHODOLOGY
A methodology is a development system of methods that is used to plan, structure and control the process of
developing an information system. (Benda & Robertson 2006). A wide variety of published development
methodologies have evolved over the years, each with its own recognized strength and weakness. Different
types of system project use available methodologies that best suits a specific project based on the project’s
various technical development process. Below are the types of methodologies used in projects development.

SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)

System development life cycle (SDLC) is conceptual model that involves a series of steps or phases used in
project management to provide a model for development and life cycle of software or an application. (Alwan.
2015)
Each phase of the development life cycle has its own process and deliverables that feed into the next phase.
This type of methodology helps in producing a high-quality product that is cost-efficient and effective. The
SDLC phases consist of planning, analysis, design, implementation, testing and maintenance. All project
development must go through these phases before completion and deployment.

Advantages of SDLC

 Reviews are created at the end of each phase, which allows maximum management control.
 Uses a systematic approach that allows users plan thoroughly on contingencies, risks and finances.
 When there is clarity between each phase, the method helps users to have a structured plan with
accurate deadlines and deliverables.

Disadvantages of SDLC
 The system can only be tested in the testing phase with end-users
 The system users might get is mostly what the developers understood which might not be what the
users needed.
 It is difficult of keep track on every documentation due to changes been made every time which is
time-consuming and expensive

AGILE SOFTWARE DEVELOPMENT (ASD)

Agile development is a conceptual framework mostly applied in software engineering projects. This type of
methodology minimizes risk by developing software in short time boxes; this is known as iteration, which
normally last from one to four weeks. There are a number of ASD methodologies: Dynamic System
Development Model, Crystal Methods and Scrum.

When to Use Agile Model

 When end users or clients have the ability to change the scope of the project.
 When there is no clarity of what the final product of the system will look like.
 When the company hires skilled developers, who can think independently.
 When rapid production is more important than quality of the product.

5|Page
 Advantages of Agile Methodology
 Its saves time and money.
 Quickly identifies any mismatch and improve quality by finding and fixing defects at early stage.
 Allows for direct communication to maintain transparency
 Changes or new enhancements can be implemented during the development phase.

Disadvantages of Agile Methodology

 Difficult to determine effort estimation at the early stage of software development, this is mostly in
bigger and complex projects.
 The methodology pays less importance in designing and documentation
 High chances of getting off-track if requirements are unclear
 Only senior programmers are able of making and taking any decision required during the development
process.

WATERFALL METHODOLOGY
Waterfall methodology is a method used in software development projects, divided into sequential phases
where “Each phase must be completed before the next phase can begin” (Royce, 2006). This model is often
considered as the classic approach to SDLC and has distinct goals for each development phase.

When to use Waterfall Methodology

 When all requirements are properly captured.
 Clarity of the final product.
 Clients do not have ability to make any changes on the project.
 Defined product quality.

Figure 2: waterfall methodology process

Requirement Gathering
This is the first phase of the waterfall development. In this phase, all requirements is collected from users for
the project and system to be developed is been captured and documented.
System Design

6|Page
In this phase, the requirement collected from the previous phase is then implemented to design the system
software.
Implementation
After the system design, the generation of codes begins in this phase. Each requirement will be developed and
tested for its functionality in this phase.
Testing
The developed system is then tested with users of the system to ensure the system meets the requirements.
Deployment
Once the software is completely developed, it is then deployed into the market for customers but this is done
after the testing of both the functional and non-functional requirements.
Maintenance
Maintenance is usually done when there are issues in the system users are facing. A system update is released
to fix those issues

Advantages of Waterfall Model

 Errors in designs are captured before any software is written; this helps in saving time in implementation
phase.
 Excellent technical documentation, making it easier for programmers to speed in the maintenance phase
 The software system development is measurable
 Conserves resources needed for development of the system

Disadvantages of Waterfall Model

 Difficult to respond to changes that occur later in the software development.
 Errors are often not identified until stem testing.
 Once the software development is in testing phase it is difficult to correct or make any changes.
 Requirements are not consistent; some components for the system are often discovered during the
design and coding stage.

Development Methodology Chosen For This Project

The development methodology selected for this project is the Waterfall Development. This methodology was
chosen because its shows the flow of project process in a logical form. “Each phase must be completed before
the next phase can begin” (Royce, 2006). It is mostly use in the process of creating software and it is easy to
understand. One of the advantages that will benefit this project is the waterfall works for projects where
requirements are very well understood. The waterfall development allows departmentalization and control. The
cost of the project can be estimated once all requirements are gathered and defined.

7|Page
Observation on the customers and company
An observation was carried out at Airbnb is to see how guests make reservation and check-in. Firstly, to make a
reservation guests will have to come to the hotel in person and then complete the booking form. After this,
guests then proceed to finance department for payment and payment invoice is provided. When a guest is
checking in, the invoice is used as a reference to retrieve the customer’s reservation and then a room is given
to the guest. Retrieving customer details is done manually. This usually takes fifteen to twenty minutes on each
customer. Some customers get upset and find it inconvenient to stay at the hotel.

The Hotel manager was interviewed to know how the hotel handles any issue or complains from the any guest
and then discussed how the proposed system will convenient for customers to make reservation/booking at
anytime. From the interview the hotel manager was able to provide few requirements needed for the website
and a survey was carried out in the hotel with few guests who were willing to fill the questionnaires.

CHAPTER 4: PROPOSED WEBSITE REQUIREMENT SPECIFICATION

A requirement is a ‘statement regarding an intended product that specifies what it should do or how it should
perform’. (Rogers. 2011.). The two types of requirements are:

FUNCTIONAL REQUIREMENTS
A functional requirement is a function of a system and its components. It describes a set of input, the behavior
and output. The functional requirements for this project are:

For customer reservation /Booking

 RQ1, The system should allow customers to reserve room.

 RQ2, The system should record customer personal details (for example, first name, last name, passport
no).
 RQ3, The system should display room type availability
 RQ4, The system should record the room type and numbers of occupants.
 RQ5, The system should display the room rate by default
 RQ6, The system should allow customers modify any information provided earlier.

8|Page
  RQ7, The system should record expected check-in and check-out dates and time
 RQ8, The system should generate a unique customer confirmation number
 RQ9, The system should record any form of payment
 Rq10, The system should display any amount owned by customers
 RQ11, The system should allow space for customer feedback

For Managements

 RQ1, The system allow manager view feedback/review comments

 RQ2, The system should display a specific period of time of guest occupancy.
 RQ3, The system should allow manager to login and logout from the system
 RQ4, The system should display any overridden prices of food and rooms.
 RQ5, The system should allow duty manager generate daily reservation report

System Administrator
 RQ1, The system should allow the system administrator to add or delete room
 RQ2, The system should allow the system administrator to login and logout from the system
 QR3, The system should allow the system administrator to update hotel information.

NON-FUNCTIONAL REQUIREMENTS
A non-functional requirement specifies the properties of the information system itself. Some of the non-
functional requirements for this project are:

Security: Manager and customer representative on duty will be able to log into the system (Hotel
management system) and have access to the reservation/booking system but access to the various subsystems
will be protected by a user login screen that requires a username and password.

Availability: The system will be available during normal hotel operating hours

Reliability: the performance of the system is consistent according to its specifications

Speed:

 The system should respond to users request within 2-3 seconds

 The system must retrieve information

Usability: The system gives direct input on how real users use the system.

Portability: The system supports every operating system

Efficiency: The system provides appropriate output based on the list of inputs

RUBY ON RAILS

Ruby on Rails, or Rails, is a server-side web application framework written in Ruby under the MIT License. Rails
is a model–view–controller (MVC) framework, providing default structures for a database, a web service, and
web pages. It encourages and facilitates the use of web standards such as JSON or XML for data transfer,

9|Page
HTML, CSS and JavaScript for user interfacing. In addition to MVC, Rails emphasizes the use of other well-
known software engineering patterns and paradigms, including convention over configuration (CoC), don't
repeat yourself (DRY), and the active record pattern.

Ruby on Rails' emergence in the 2000s greatly influenced web app development, through innovative features
such as seamless database table creations, migrations, and scaffolding of views to enable rapid application
development. Ruby on Rails' influence on other web frameworks remains apparent today, with many
frameworks in other languages borrowing its ideas, including Django in Python, Catalyst in Perl, Laravel and
CakePHP in PHP, Phoenix in Elixir, Play in Scala, and Sails.js in Node.js.

ATOM TEXT EDITOR

Atom is a free and open-source text and source code editor for macOS, Linux, and Microsoft Windows with
support for plug-ins written in Node.js, and embedded Git Control, developed by GitHub. Atom is a desktop
application built using web technologies. Most of the extending packages have free software licenses and are
community-built and maintained.[9] Atom is based on Electron (formerly known as Atom Shell), a framework
that enables cross-platform desktop applications using Chromium and Node.js. It is written in Coffee Script and
Less.

HEROKU

Heroku is a cloud platform as a service (PaaS) supporting several programming languages. One of the
first cloud platforms, Heroku has been in development since June 2007, when it supported only
the Ruby programming language, but now supports Java, Node.js, Scala, Clojure, Python, PHP, and Go.[1][2] For
this reason, Heroku is said to be a polyglot platform as it has features for a developer to build, run and scale
applications in a similar manner across most languages

WEBSITE SPECIFICATION

 Front End : Ruby on Rails

 Back End : SQL Server

 Operating System : Windows XP or above

10 | P a g e
 CHAPTER 5: SYSTEM ANALYSIS AND DESIGN PHASE
USE CASE DIAGRAM
A use case diagram is an interaction between an information system and users of the system (Actors) that
enables the users achieve a goal. A Use Case Diagram shows what activities every actor conducts in the
system. The most important elements in UCD are actors and use cases.

Basic Model Element

Actor: An actor represents a role (someone) that directly interacts or uses the system.
Association: An association describes the relationship between an actor and a business use case in the use
case diagram.
Use Case: A use case is a functionality of how the system works, it describes the interaction between an actor
and the system.

Below is the use case diagram for this project Hotel Reservation System.

Figure 1: Airbnb Use case Diagram

11 | P a g e
Use Case Description
A use case was chosen and described in details to identify it functionality and how the actor related to that use
case interact within the system.

Assumptions
The assumption made in the use case above is the two actors (duty manager and manager). These actors were
assumed to be part of the use case diagram because the keep track of every operation and activity in the hotel
and are also responsible for guest who might have complains or enquiry regarding their reservation.

The use case utilized below is “Make a reservation” use case. This describes how an actor uses a use case to
interact with the system.

Use case name Make a Reservation

Actor Customer, Receptionist

User Action System Response

1. Search for rooms availability using the 2. Display room availability and rates per
check in and check out option night
3. Select room type and make payment 4. Confirms payment and send
confirmation number
5. Modifies and booking with booking 6. Update booking details and display new
number booking details
Figure 2: Make a Reservation usecase Description

Use case name Login

Actor Customer, Receptionist, System Administrator, Manager
Description The above users enter an authorized username and password to access the
system.
Basic Action User Action System Response
1. User opens login 2. Displays login form for users to fill(this
page accepts username and password)

3. Users enter login 4. The system searches the login details

details and clicks from the database and matches it with
login the password

12 | P a g e
 5. End use case 6. If login details is correct the system
display the next page else, displays
invalid login details

Figure 3:Login Usecase Description

SEQUENCE DIAGRAM
A sequence diagram is the interaction between objects in a sequential order that those interactions occur.
(Bell. 2004). in sequence diagram, each role is shown as lifeline and messages are shown as arrows between
lifelines. Below is the sequence diagram of this project Hotel reservation system.

5.3 Activity Diagram

An activity diagram describes the flow of actions that are part of larger activities in a chart of a system from on
activity to another activity. (Bell. 2003) An activity diagram is used in this project to model a use case in a
Figure 4: Ta'al Hotel Sequence Diagram
detailed level. The four basic elements in an activity diagram are: activities, association, constraints and
conditions. Below is an activity diagram for this project’s Hotel Reservation System.

13 | P a g e
Figure 5: Airbnb Activity Diagram

WEBPAGE SITEMAP
A site map is a visual or textually organized model of a website content designed to help users and search
engine to navigate through a site to find information available in the sites. (Buytaert. 2016). Below is a
hierarchical representation of this project site map of Ta’al hotel website with a booking system.

14 | P a g e
Figure 6: Website Sitemap

MOCKUP (USING BALSAMIC)

Balsamic was used in this project to show the different layers of the proposed system and different page
content the main website will have. Balsamic is a wire framing tool use for sketching mockups such as a
website or an app. This tool helps in producing faster and smarter sketches

HOMEPAGE
This page is also known as the index page (The main page on the website). It consists of the navigation bar
through all pages on the website, images, sign in and sign up, and the booking section to check for availability
and make reservation.

15 | P a g e
Figure 7: Homepage prototype 1

16 | P a g e
ACCOMMODATION
In this page on the website, different types of rooms and suite available in the hotel are displayed here with
descriptive explanation of every suite. This page helps customers or guest have an idea of the type of
room/suite the want for reservation.

Figure 8: Accommodation page prototype 2

17 | P a g e
GALLERY
This page comprises of mostly images of the hotel. It shows the facilities and equipment’s available at the
hotel. Images shown on this page help prospective guests have ideas of what the hotel looks like and it
environment.

Figure 9: Image gallery page prototype 3

18 | P a g e
SERVICES
In this page, the website shows all services provided by the hotel which include laundry, business meetings,
events (such as weddings, birthdays and party), the gym and the swimming pool area.

Figure 10: Service page prototype 4

19 | P a g e
DINING
In this page, the website shows the types of restaurants available in the hotel. It also shows the closet
restaurant around the hotel for guest that feel like eating outdoor. Restaurant’s Menu can be downloaded
from this page to have a proper view of every meal and drinks served at the restaurant.

Figure 11: Dining page prototype 5

20 | P a g e
CONTACT US
This page is for making enquiries about the hotel or related services, it also shows the location of the hotel and
how customers can reach through the hotel.

Figure 12: Contact us page prototype 6

21 | P a g e
MAKING RESERVATION

22 | P a g e
On this page, customer who will like to stay at the hotel can make their reservation here by providing their
name, email, contact, address, check in and check out dates with the number of rooms, adults and children
expected. After filling the booking form customers are then asked to process to payment using the credit or

23 | P a g e
debit master card.

24 | P a g e
Figure 13: Make Reservation page prototype 7

LOGIN
This is the login page; guests are required to log into this page before they can comment or give feedback
regarding their stay in the hotel. The page also shows images of upcoming events such as concerts in the hotel.
This page also keeps track of guest’s visits.

25 | P a g e
Figure 14: Login page prototype 8

Sign Up
This is the sign-up page were unregistered guests are required to create an account in order to give their
feedback and also enable them track their stay at the hotel. The page also shows images of upcoming events
such as concerts in the hotel.

26 | P a g e
Figure 15: Sign up page prototype 9

Rationale Behind Design Decision

Based on the requirement gathered a design pattern was used to make the mockups above. The design pattern
was reviewed from the two websites discussed earlier (refer to page 4-5 of this document). The website

27 | P a g e
showed the similarities and few comparisons were made between those websites to identify the best design
for the mockups. The design pattern is simple and easy to interact with; customers do not have to search for
item because the navigations and links on the mockups are directed to the mockup webpages as required from
the functional requirements.

System Deployment Diagram

A deployment diagram is used to visualize the physical component of a system which consists of nodes and
their relationship. (James,2009). Below is the hotel reservation system deployment diagram. This diagram
shows how users can access the website by using different web browsers as listed below, Apache will serve as
the web server and MYSQL will be used to store customer and hotel information in categorized tables in the
database.

Figure 16: Deployment Diagram

ENTITY RELATIONAL DIAGRAM

An entity-relational diagram (ERD) is the representation of entity that shows the relationship of entity sets
stored in a database or an information system (Martin 1076). The five main component of and ERD are:
 Entity: Entity is an object which allows information to be stored in.
 Actions: An action shows how two entities share information in the database.
 Attributes: An attribute is the unique character in an entity.
 Connecting lines: These are solid lines connecting to an attribute to show the relationships of entities
in the diagram.
 Cardinality: Specifies the number of occurrence of a relationship in the diagram.

Below is the Hotel Reservation system Entity Relational Diagram.

28 | P a g e
Figure 17: Entity Relation Diagram

Figure 18: Entity Relational Diagram

DATABASE DESIGN

Table: user-comment
This table is used to store review messages provided by users on the website

29 | P a g e
Field Name Data Type Length Description
id Int (Auto Increment) 11 P.K users id

username Varchar (50) username

Figure 19: Database design table 1

Table: Users
This table is used to store users information when the register their details on the website. It will also be used
to retrieve information when users try to login.
Field Name Data Type Length Description
id Int (Auto Increment) 11 P.K users id

username Varchar (50) username

email Varchar (50) Users email address

password Varchar (20) password

Confirm password Varchar (20) Verification of the first

password
Figure 20: Database design table 2

Table: Contact
This table is used to store information about users who make complains or want to make an enquiry about the
hotel or their reservation.

Field Name Data Type Length Description

id int 11 Users id (P.K)
email Varchar 50 Email address
message Varchar 50 Enquiry message
Figure 21: Database design table

Table: Reservation
This table is used to store customer’s reservation details.
Field Name Data Type Length Description
id int 11 Users id (P.K)
title Varchar 5 Gender title
username Varchar 20 username
email Varchar 20 email
contactnumber int 20 contact number

30 | P a g e
checkin Date check-in
checkout Date checkout
Meal selection Boolean Meal selection
address Varchar 30 address
states Varchar 20 states
city Varchar 10 city
paymenttype Varchar 10 payment type
Figure 22: Database design table 4

CHAPTER 6: IMPLEMENTATION AND TESTING

Series of testings’ and evaluation will be use on the developed system in order to avoid system errors and also
make sure every functional requirement gathered from the requirement stage is been implemented in the
system.
FUNCTIONAL TESTING

31 | P a g e
Functional testing is done by the developer to verify that each function in the system software operates with
the requirements specifications. Functional testing involves checking client/server application (This project will
use apache webserver), user interface, database and the system functionality which is tested by providing
required input and then verify the output and compare the results with the expected result. The functions that
will be tested in the section are:
 Mainline functions: This is the testing of the system main functions.
 Basic Usability: basic usability is usability testing of the system to check whether a user can easily
navigate through the webpages without any difficulties.
 Error Condition: This is to check or errors and whether error messages are displayed. Since the system
will be developed using PHP codes it is easier to identify an error once the developer runs the page.
USABILITY TESTING

This testing technique will be used to determine whether the developed system is accessible, findable, useful
and easy for end users to achieve the tasks for which it was designed. The goal of using this technique is to
know the effectiveness of the system, user friendliness, accuracy and efficiency. Usability testing process will
be used to develop the system evaluation results, analysis and any findings. The usability testing processes
consist of:

Figure 23: System evaluation process

After the testing participants, will be giving a user satisfaction survey to find out how users feel about using the
developed system, by asking them to rate the system on a scale. Possible tasks that will be asked or performed
during the survey may include:
 Search for specific items or information.
 Navigate through different menu on the webpages.
 Selecting images available to view it information.

HEURISTICS EVALUATION

Heuristics evaluation is a usability inspection method for finding problems in user-interface elements, such as
navigation structure, menus, and online help. (Nelson and Molich. 1990). This evaluation is done by experts,
guided by a set of usability principles known as heuristics.
After the system, has been developed, the supervisor will evaluate the system to see if the webpages are
consistent and other evaluation.

32 | P a g e
 CHAPTER7: WEBSITE DEMONSTRATION
Home Page
This is the first page users will interact with on the website. It provides a detail description about the hotel, a
booking form for customers to check room availability within selected date. The home page also has a Review
form for users to leave a feedback about their experience in the hotel. Users can register and the login on this
page in order to have full access of the website.

33 | P a g e
Accommodation Page
In this web page, users can view the types of accommodation available in the hotel on the website, they can
also click on these room types to have an idea or know more information about the room. It also has the
reservation form for users to book or check rooms’ availability on all pages of room types.

34 | P a g e
Gallery Page
The image gallery is one of the attractive pages on the website. In this page, users can view different type
images of the hotel to have an idea of what the hotel looks like.

35 | P a g e
Dining Page
This page shows the restaurants available in the hotel and where they are located. Users can download the
restaurant’s menu which has the prices and opening and closing hours. It also has a reservation form. This
form is consistent on every page of the website. This means that users can make a reservation on any webpage
on the website.

36 | P a g e
Services Page
This page allows users to view the services rendered by the hotel. It also has a number of links that links users
to the type of services on different pages.

Contact Us Page
On this page, users can leave an enquire message or any complains, which will be immediately directed to the
hotel and will be replied within twenty hours. This page also has the hotel’s address (location map), contact
number and all social media’s the hotel operates with.

37 | P a g e
Register (Sign Up) Page

This page allows new users to register their details into the hotel database. Without the sign up function, users
will not be able to make reservations in the hotel but can view other webpages available.

Login Page
This page allows user to register in to the website in order have full access to the website. Once users are
registered to the website, the login function allows the system to recover their details.

38 | P a g e
Booking Page
This page is for users who may wish to make a reservation with the hotel online, users are supposed to fill in
this form and click the submit button to confirm their reservation. After this a unique id is generated as a
confirmation number for customers who have confirmed their booking.

39 | P a g e
 CHAPTER 8: FUTURE SCOPE OF THE PROJECT

In a nutshell, it can be summarized that the future scope of the project circles around maintaining information
regarding:

• We can add printer in future.

• We can give more advance software for airbnb website including more

facilities We will host the platform on online servers to make it accessible worldwide Integrate multiple load
balancers to distribute the loads of the system Create the master and slave database structure to reduce the
overload of the database queries Implement the backup mechanism for taking backup of codebase and
database on regular basis on different servers

The above-mentioned points are the enhancements which can be done to increase the applicability and usage
of this project. Here we can maintain the records of Hotel and Rooms. Also, as it can be seen that now-a-days
the players are versatile, i.e. so there is a scope for introducing a method to maintain the airbnb website.
Enhancements can be done to maintain all the Hotel, Rooms, Services, Payments, Bookings.

We have left all the options open so that if there is any other future requirement in the system by the user for
the enhancement of the system then it is possible to implement them. In the last we would like to thanks all
the persons involved in the development of the system directly or indirectly. We hope that the project will
serve its purpose for which it is develop there by underlining success of process.

40 | P a g e
 CHAPTER-9 CONCLUSION
In conclusion, this report has been able to address the issues customers and hotels face when making a
reservation using a manual booking system by developing an online booking system for clients to make
reservation at their own comfort. It has also discussed on the past studies of online booking and the
integration of the internet by hotels to connect more to their customers. It has discussed on the types of
method used to gather the requirements needed, the type of development methodology selected for the
research and how UML diagrams were created to show the interface of the system. A detailed description of
pages on the website was discussed and the types of evaluation used to evaluate the website. In the course of
this research project, a few limitations were face and they are;

● In the website, customers can reservations but are unable to make online payments.

● During the heuristic’s evaluation, the desired numbers of experts could not be met; this would
have enabled more elaborate evaluation to be achieved.

● The environment used in conducting the usability testing was not completely controlled by the
researcher because it was a free lab for any university student to access.

41 | P a g e
REFERENCES

 https://rubyonrails.org

 https://github.com

 https://atom.io

 https://www.heroku.com

 https://www.drupal.org/project/site_map

 Bell, D. (2003) UML basics part II: The activity diagram. Available at:
http://www.ibm.com/developerworks/rational/library/content/RationalEdge/sep03/f_umlbasics_db.pdf
(Accessed: 10 January 2017).

 Bell, D. (2004) The sequence diagrams. Available at:

http://www.ibm.com/developerworks/rational/library/3101.html (Accessed: 5 January 2017).

 Bemile1, Richard, Akwasi Achampong, and Emmanuel Danquah. "Online Hotel Reservation
System". ijiset. N.p., 2014. Web. 15 Apr. 2017

 Buytaert, D. (2016) Site map. Available at: https://www.drupal.org/project/site_map (Accessed: 11

January 2017).

 Delizo, Glenda A., and Mischelle A. Esguerra. "Online Hotel Reservation And Management System
For The College Of International Tourism". research. N.p., 2013. Web. 14 Apr. 2017.

 Dennis, A., Wixom, B. and Roth, Roberta (2009) System Analysis and Design. Available at:
http://www.uoitc.edu.iq/images/documents/informatics-
institute/Competitive_exam/Systemanalysisanddesign.pdf (Accessed: 5 January 2017).

 Guru 99 (2017) FUNCTIONAL testing Tutorial: What is, process, types, & examples. Available at:
http://www.guru99.com/functional-testing.html (Accessed: 11 January 2017).

 Heywood, R. (2012) UML use case diagrams: Available at: https://www.andrew.cmu.edu/course/90-

754/umlucdfaq.html (Accessed: 5 January 2017).

 JIAN YU, YANG. "Reservation Systems". Jbnut. N.p., 2014. Web. 16 Apr. 2017.

 Louw, J. (2006) Description with UML for a hotel reservation system. Available at:
http://liacs.leidenuniv.nl/assets/Bachelorscripties/2006-08JanneLouw.pdf (Accessed: 2 January 2017).

42 | P a g e
--------------------------------------------------------------------------------------------------------------------------------------------------

43 | P a g e