1

WOLLO UNIVERSITY (KIOT)

COLLEGE OF INFORMATICS
DEPARTMENT OF INFORMATION TECHNOLOGY
STUDENTS FINAL PROJECT
2011 E.C
PROJECT ON: HOTEL MANAGEMENT SYSTEM FOR YEGOFEVIEW HOTEL

Developed By:

1. Mohammed Tegegne ………………………………Wour/1986/08

2. Yohannes Fisiha ……………………………………….Wour/2061/08
3. Zehara Gudayu…………………………………………..Wour/2067/08
4. Zeneb Tadesse……………………………………………Wour/2069/08
1 5. Yirgedu Workye…………………………………………...Wour/2059/08 Wednesday, December 27, 202
3
 Content overview
2
 Introduction
 Statement of problem
 Work flow of the existing system
 Objective
 Class responsibility collaborator
General objective  System analysis
Specific objective  System use case diagram
 Scope of the project  Sequence diagram
 Limitation of the project  Activity diagram
 Significance of the project  Conceptual Class diagram
 Software requirement specification  System design
 Design goals
 Class modeling
 Collaboration Modeling
 Deployment modeling
Wednesday, Decemb
er 27, 2023
3
Introduction

 Hotel is a commercial establishment providing, lodging, meals and other guest services.

 In general, to be called a hotel, an establishment must have a minimum of six letting bedrooms, at
least three of which must have attached private bathroom facilities.

 A Hotel Information Management System (HIMS):- is an automated system for the hotel
management; it thus creates standards in hotels according to customer needs, satisfying their
general comfort.

1 Wednesday, Decemb
er 27, 2023
4 Statement of the Problem
We have too many problems associated with the manual system used which include:
 It takes more time to reserve room. So performance of the current system is slow.
 Difficulty in handling data accurately, security of data, data lost and viewing by
unauthorized person.
 Retrieving information like reports and queries is very time consuming and almost
impossible practicably if time is considered.
 Searching records of individual guest or customer takes time. (Update, Delete), these
types of method are not accessible using the manual method.

1 Wednesday, Decemb
er 27, 2023
 Objective

5 General objective

 The main objective of this project is to design and develop web based management system

for yegofeveiw hotel.

Specific objective
 Reviewing how the current system works and operates.

 Investigating how the existing system is operating.

 Design a new system that can overcome the problem of the current system

 Identify functional and non functional requirements for the new system.

 Develop and implement the new system .

1 Wednesday, Decemb
er 27, 2023
 Methodology
6
Data collection method
Interview
Observation
Design Methodology
Among different design methodology we will develop our system by
 Object oriented design Paradigm
Feasibility
Technical feasibility
Operational feasibility

1 Wednesday, Decemb
er 27, 2023
 Scope of the project
7

The new system should provide the following services.

 Search Rooms information.
 updates room,
 delete room
 search customer information
 register,
 update employee, add employee, view comment
Limitation of the project
The main limitations of the project are mentioned as follow:-
 It is not integrated with the bank.
 There is no online payment.
 Our project is depends on internet.
1 Wednesday, Decemb
er 27, 2023
8
Significance of the project

The advantages that are using this web based hotel management
system are:-
 The system efficient in improving time management
 The system reduces workload.
 The operation is computerized hence able to perform the tasks
easily and efficiently.
 It also reduces the number of staff members that can be required to
perform a task.
 The use of computers ensures that the making of errors is reduced.

1 Wednesday, Decemb
er 27, 2023
9 Proposed solution for the new system

 Provide easy access to clients (customers) and employee

information.
 Satisfy customer’s needs and demands.
 Ensure fast and accurate record keeping mechanisms.
 Provide system simplicity, reliability, fast, user friendly and reliable
work.

1 Wednesday, Decemb
er 27, 2023
10 Software requirement specification
Functional Requirements
 Functional requirements describe the relationship between the system and the
user.

Customer
 RQ1, The system allows Customers to search for available room.

 RQ2, The system allows Customers to leave comment as a feedback for

manager.

 RQ3, The system allows Customers to register.

1 Wednesday, Decemb
er 27, 2023
11 Cont..
Manager
 RQ1, The system allows the Manger to view comment.

 RQ2, The system allows the Manager to login the system.

 RQ4, The system allows the Manager to logout from the system.

 RQ5, The system allows the Manager to view employees.

 RQ5, The system allows the Manager to view account.

Receptionist
 RQ1, The system allows the Receptionist to search for available room.
 RQ2, The system allows the Receptionist to search customer information
 RQ3, The system allows the Receptionist to leave comment.
1 Wednesday, Decemb
er 27, 2023
12 Nonfunctional requirement

 Security: should allow login to only authorized users.

 Accuracy: proposed system will be better due to reduction of error.

 No redundancy: in the proposed system can be avoided reputation of

data any where in the database.

 Availability: all data in the system will be available .

 Error handling exception: the system must recover immediately when

a user enters incorrect (error) data.
1 Wednesday, Decemb
er 27, 2023
13 Use case diagram
.

1 Wednesday, Decemb
er 27, 2023
14 Sequence diagram
Sequence Diagrams are interaction diagrams that detail how
operations are carried out.
Register
SD# 3
Customer Main menu Register
Database
<<actor>> <<UI>> <<UI>>

1: click()

1: open()

1:fill the form

1: [if incorect]
try again

1 Wednesday, Decemb
er 27, 2023
15 Activity diagram
Register
AD#3

the customer open home page

The customer open for memeber ship page

The customer fill all the required filled

The system check that all the fields have filled properly

{incorrect}

{correct}

Registered successfully

1 Wednesday, Decemb
er 27, 2023
16 Conceptual Class diagram

1 Wednesday, Decemb
er 27, 2023
17 System design

 The purpose of designing is to show the direction how the web page is built
and to obtain clear and enough information needed to drive the actual
implementation of web page.
 System design is the transformation of the analysis model into a system design
model. System design is the first part to get into the solution domain in a
software development.

1 Wednesday, Decemb
er 27, 2023
18 Design goals

The objectives of design are to model the system with high quality.
The design goals are derived from non-functional requirements that
means non-functional requirement is the description of the feature
characteristics and attribute of the system as well as any constraints
that may limit the boundary of the proposed solution.

1 Wednesday, Decemb
er 27, 2023
19
Class modeling

 Class modeling is used to model the static part of the systems

 This model is derived from the analysis class diagram.
 The only difference is system class diagram include access modifier.
 There are two main access modifiers in our project.
 (-) symbol describes private and protects attribute.
 (+) symbol used to describe the method or attribute is accessible
for all (public).

1 Wednesday, Decemb
er 27, 2023
20 Class modeling diagram

1 Wednesday, Decemb
er 27, 2023
 Collaboration Modeling
21

 Collaboration diagram is another form of interaction diagram.

 It represents the structural organization of a system and the messages sent/received.

Structural organization consists of objects and links.

1 Wednesday, Decemb
er 27, 2023
 collaboration diagram for add employee
22

Wednesday, December 27, 2

023
 Component Modeling
23

1 Wednesday, Decemb
er 27, 2023
 Deployment modeling

24

1 Wednesday, Decemb
er 27, 2023
25 conclusion

 As we come to end of our system development, it is time to reiterate

the work previously have been done and check against our success
indicators set at the beginning of the project to determine whether
the endeavor was a success.
 The project began by laying out the foundation that dictates the
development process. This involved defining the system
development methodology, identifying resource requirements, and
setting the project schedule.

1 Wednesday, December 27,

2023
26

U
YO
K
AN
TH

1 Wednesday, December 27, 2023