ASSOSA UNIVERSITY

COLLEGE OF COMPUTING AND INFORMATICS

Department information technology

Course title: HOTEL MANAGEMENT SYSTEM

Group Assignment: ITPM

Name Id

Melkamu Tesfay …………………………………………2037/13

Baka Shferaw ..……………………………………….. 1897/13

Abdulafiz Taju …………………………………………3191/13

Geteta Tisgaye ………………………………………………1412/13

Elias Tilahun …………………………………………………1125/13

Submitted To: MSc

 Submission date:

Ethiopia, Assosa

Content overview

 Introduction

 Statement of problem

 Objective

 General objective

 Specific objective

 Scope of the project

 Limitation of the project

 Significance of the project

 Software requirement specification

2|Page
 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 ho-
tel management; it thus creates standards in hotels according to customer needs, sat-
isfying their general comfort.

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 unau-
thorized 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.

 The main objective of this project is to design and develop web based management
system for yegofeveiw hotel.

3|Page
 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 nonfunctional requirements for the new system.

 Develop and implement the new system.

Methodology
 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

Scope of the project

4|Page
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

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.

5|Page
 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.

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.

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

6|Page
  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.

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 anywhere

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.

Use case diagram

7|Page
8|Page
 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

9|Page
 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

Conceptual Class diagram

10 | P a g e
 System design
 The purpose of designing is to show the direction how the web page is built and to ob-
tain 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 de-
velopment.

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.

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).

11 | P a g e
 Class modeling diagram

12 | P a g e
 Collaboration Modeling
 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.

collaboration diagram for add employee

13 | P a g e
 Component Modeling

14 | P a g e
 Deployment modeling

15 | P a g e
 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 re-
quirements, and setting the project schedule

16 | P a g e
 THE END

17 | P a g e