CHAPTER FOUR: DESIGN PHASE

4.1 INTRODUCTION
In this design phase we discuss aspects like physical, architectural, interface, and database designs. This
stage describes how data will be managed, how user input will be incorporated into the proposed
system, and how output will be provided to end users. Moreover, this phase encompasses the flow of
data, the method of user input, and the manner in which data will be delivered to end users. As it is the
system development process it shifts the focus of problem definition to solution design. Its objective is to
specify the realization of the requirements. The design phase describes the interaction between the
system components and how operations are coordinated within it.

4.2 SYSTEM DESIGN

According to Gamma et al (1995), design system is described as the phase that
focuses on assessing the proposed system and the interfaces that allow users to
use the system. The user interface login clients so that they can search for the
accommodation they want. This stage describes how the functions of the system
are used.
4.2.1 Flow Chart
It is a diagrammatical representation of a system’s elements. It illustrates both the
tangible and external characteristics of the system, along with the order in which
the system functions, within the flow chart of the system. It is an illustration of
visual events as shown on the diagram below.

4.2.2 Context Diagram

According to Karim, (2011) a context diagram is defined as the representation of
the system that is made up of a single process. It explains how each entity in the
system interacts/combines with the other entity as well as the system boundaries.
4.2.3 DATA FLOW DIAGRAM

A data flow diagram is described as the flow of information within an organization

and also the processes which are done too (Bagui,2005). It can explain how new
system can work without providing a lot of information. The data flow diagram
shows the movement of information from one entity to the other, it’s an overview
of how information will be conveyed into the system.
4.3 Architectural design
The architectural design represents the highest level of abstraction for a system,
viewing software as a system composed of multiple interconnected elements. At
this stage, designers gain a comprehensive understanding of the proposed
solution. Through the design process, a description of the software architecture is
produced. The architectural design process focuses on constructing a foundational
structural framework that identifies the key components of a system and their
interrelationships.
4.3.1 Components
 Customer’s devices
 Server
 Routers
 Laptops
 Server
The architecture of the system
the proposed system is designed using a client-server architecture, which
represents a system model where services, servers, and users are organized into a
cohesive structure. This architecture establishes a protective barrier between the
server layer and the user layer to prevent unauthorized access. Whenever a user
intends to access data on the server side, they are required to provide authorized
credentials, such as a username and password. In the event that the entered
credentials are incorrect, the system will deny access.

Draw
4.4 PHYSICAL DESIGN
The physical design describes the flow of information within a system by outlining
the system’s inputs, processes, and outputs, as well as the ways in which these
elements are interconnected. It explains how data enters the system, how it is
processed, and how the resulting output is presented to the user. In the case of
the hospitality management service system, the following components will be
addressed:
4.4.1 INPUTS
It refers to the data and information that is entered into the system:
 Name
 Email
 Password
 Contact details
 Search criteria
 Dates
 Price range
 Selected accommodation
4.4.2 PROCESSES
The specific actions and activities that are performed by the system to achieve the
desired outputs.
 Creation of account
 Validation of user inputs
 Checking availability of the selected accommodation for the specified dates
 Validation of payment details
 Recording check-in and check-out times
 Validation of review content
4.4.3 OUTPUTS
It refers to the information, services, or results that the system produces for the
users.
 Confirmation message
 Confirmation of booking with a unique booking reference number
 Confirmation of successful payment or a transaction receipt
 Confirmation of successful check-in and check-out

4.5 DATABASE DESIGN

According to Churcher, (2007) database design refers to procedures which make
the system design, development, maintenance easier. It uses schemas for the
processes of organizing data. It maintains data integrity and consistency. For this
system we are going to use SQL sever which allows multiple users at the same
time.
4.5.1 PHYSICAL DATABASE DESIGN
The physical database design translates the theoretical database scheme, which is
comprised of entities, instances and characteristics, into actual database structure
consisting of tables, rows, and columns. The ANSI-SPARC model, which is a
standard framework for database design, defies the three-layer approach
(conceptual, physical and external) that maps the database schema into the
physical presentation of data. This process is critical for ensuring that the database
is well-structured, efficient and able to support intended data management tasks.
4.5.1.1 EXETERNAL LEVEL
It is the highest level in the database and allows user-database interactions. Here
a data management system is used. It is the one which allows users to interact
with the database without any disturbance with other users to their data.
4.5.1.2 CONCEPUTAL LEVEL
It is responsible for setting out the relationships all the database entities. It
displays the characteristics, data limitations, security, the entities and also their
relationships.
4.5.1.3 PHYSICAL LEVEL
Here it is at the bottom of the three-tire database design. This level will show how
data is physically stored and displayed. This level is in charge of data compression
of encryption and also the physical storage.
Draw
4.5.2 LOGICAL DATABASE DESIGN
This process is integral to the logical database and involves identifying entities
within the system along with their relationships. The system encompasses the
following entities;
 Room
  Customer
 Reservations
 Services
 Payments
4.5.2.1 ENTITY RELATATIONSHIP DIAGRAM
The relationship between the hospitality management service system entities and
how they interact is defined as entity relationship diagrams which is shown below
diagrammatically;

Draw
4.5.2.2 DATA DICTIONARY
The data dictionary consists of the core tables within the database,
where rows represent tuples and columns represent attributes.
CUSTOMERS DETAILS
(Email, username, password, permission)
CUSTOMER REGISTRATION
(Name, email, full name, address, phone number, gender)
SEARCH ENGINE
(Rooms, price range, room images, booking avilability)
BOOKING DETAILS
(Booking id, guest name, check-in and check-out dates, room type, number of
guest)
CONFIRMATION DETAILS
(Confirmation number, room, total price)

4.6 DESIGN INTERFACE

According to Dennis, Wixom and Roth (2012), the design interfaces is described as
the interactive elements that users interact with to operate the system. User
interfaces are there so as to manage and control the system. The graphical user
interface (GUI) serves as a user-friendly platform for interacting with computers.
Its simplicity makes it an effective tool for constructing the interface of the
proposed system. Even users with limited or no experience can easily grasp how
to navigate and utilize the system. Switching between tasks is seamless and
efficient, allowing users to swiftly transition from one workflow to another. With
immediate and comprehensive access, users can promptly engage with various
programs and information.

4.6.1 BLOCK DIAGRAM

A block diagram visually illustrates the components within a subsystem and the
interconnections between modules.
DRAW

4.6.2 INPUT DESIGN

It is the face of the system to which the data is inputted in so that all the users of
the hospitality management service system. All the data entered into the system
must correctly authenticated and validated.
LOGIN FORM
All the users of the system must generate passwords and usernames so as to acess
the system, it will be for the benefit of security purposes. The design of the login
form for our system is shown below;
CUSTOMER REGISTRATION FORM
For new customers they will have to get registered so tat they can be
acknowledged as the users of the hospitality management service system. So, the
customer will be asked to fill up their personal details and then will be used for
authentication.
SEARCH ENGINE
This is a form to which the customers search for the services which they want
which is the accommodation.