SAMARA

UNIVERSITY

FACULTY OF ENGINEERING AND TECHNOLOGY

DEPARTMENT OF COMPUTER SCIENCE

PROJECT TITLE: HOTEL MANAGEMENT SYSTEM ON LUCY HOTEL

BY
GROUP MEMBER
id no
1.EBRAHIM YESUF
038/06
2. ATINAFU ABATE
018/06
3. ASCHALR YIRSAW
054/05
4.SELAM BISET
088/06
A PROJECT SUBMITTED TO THE DEPARTMENT OF COMPUTER SCIENCE OF SAMARA
UNIVERSITY FOR PROPOSAL PHASE

January 30, 2015

SAMARA UNIVERSITY

Table of Contents

page

Chapter one
1. Introduction.......................................................................1
Background of the organization.........................................................1
Literature Review (Review of Related work)..................................... 1
General definition of hotel................................................................... 1
1.2.2 Location of Samara...................................................................... 1
1.3 Statement of the Problem.................................................................... 2
1.4 Objective of the project........................................................................ 2
1.4.1General objective...........................................................................2
1.4.2 Specific objective................................................................................ 2
1.5 Methodologies........................................................................................ 3
1.5.2 System development tools................................................................. 3
1.5.3 Data collection methodology..............................................................3
1.5.4 System development methodologies..................................................3
1.6 Scope and Limitation.............................................................................4
1.6.1 Scope of the project............................................................................ .4
1.6.2 Limitation of the project................................................................... 4
1.7 Significance of the project.................................................................. .4
CHAPTER TWO

SYSTEM REQUIREMENTS SPECIFICATION................................ 5

2.1 INTRODUCTION.............................................................................. 5

2.2 Current system........................................................... 5

2.2.1 Overview of existed system............................................................ 5
2.2.2 Problem of current system........................................................ 5

2.3 business rule............................................................... 5

2.3 Proposed system................................................................................. 6

2.3.1 Overview..................................................................................... 6
2.3.2 Goals of the proposed system........................................................ 6

2.3.2 Functional requirements................................................................6

2.3.3 Non functional requirement.............................................................7

2.3.3.1 Look and feel requirements.......................................... .7
2.3.3.2 Usability requirements................................................. ...7
2.3.3.3 Security requirements......................................................7
2.3.3.4 Performance requirement...............................................7
2.3.3.5 Portability requirements........................................... ..7

I. 2.3.4 Constraints......................................................8
2.4 system models..............................................................8
2.1.1 Scenario.................................................................. ..8
2.4.2 Use case model......................................................11
UML diagram............................................................12
The actor purpose on the system....................................12
2.4.3 object model
2.4.3.1 Data dictionary ....................................................................15
2.4.3.2 Class diagram........................................................................16
Class description................................................................................. 17

2.4.4 Sequence diagram....................................................18

Chapter 3
1. Introduction................................................... ...26
3.1.1. design goal ..........................................................................29
Performance criteria.................................................................. 29
Maintenance criteria......................................................................29
3.1.2 .End user characteristics..........................................................30
3.3 Collaboration Diagram........................................................30
3.4 State Chart Diagram........................................................35

3.5 proposed Software Architecture of the system......................37

3.5.1 Subsystem decomposition..........................................................37
3.5.2 hardware/software mapping.............................................................39
3.5.3 persistent data management..............................................................40
3.5.4 access control and security................................................................41
4.Reference45

CHAPTER ONE
1. Introduction
Background of the organization
This project document is being prepared for analyzing, designing and implements software for
Hotel management system. The idea of implementing this system is to fulfil the gap between
work stations, service system and product providers in reaching the goal to achieve more
efficient and competitive system. The system uses to make facilitate the work time of the casher,
store keeper, finance and manager of the organization.
Lucy motel is one of the modern hotels in samara city, giving full services to the customers. It is
located in samara which is the capital city of Afar region found in the eastern Ethiopia.
Lucy Hotel was firstly established in 2001E.C, which makes it a newly revival or established
among the competitive hotels in the town.
It gives a full service of pension, restaurant, cafeteria and a big hall enough to hold 200 people in
a single meeting.
The location of the hotel is in a highway of taking from Djibouti to all other towns of Ethiopia
which makes at preferable.
As a result the hotel is expected to give a reliable and satisfactory service to the customers.
There is one of all reasons why the project is concerned with the efficient work of the Hotel. The
project is concerned with the Hotel management system of the motel.
Vision of the organization is to construct a standardized and competitive motel in Ethiopia
especially in Afar region. Additionally it constructs a building of a hall which is used for
meeting, wedding, and reception passenger.
The mission of the organization or the motel is to give good services for customers efficiently
and quality service. The hotel is gives a service for foreign passengers and the Ethiopian
drivers, they are moved from Djibouti to other different regions of Ethiopia.

1.2. Literature Review (Review of Related work)

1.2.1 General definition of hotel
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. Although hotels are classified
into 'Star' categories (1-Star to 5-Star), there is no standard method of assigning these ratings,
and compliance with customary requirements is voluntary.
1.2.2 Location of Samara
Samara is a new town found in Awash-Assb highway in north-east Ethiopia, planned to replace
Asaita as the capital of the Afar Region. Located in the Administrative Zone 1,
Hotel management system is developed in several hotels to point out some of them.
Sheraton Addis hotel
Sheraton Addis hotel is a 5 star hotel, which is followed in the capital city of Ethiopia Addis
Abeba. This hotel is the position in the mountains country side, 2,400 metres above seaside, and
the hotel represents Africa elegance.
The hotel stands opposite the national place and is only seven kilometres from the Bole
international airport.
The management system of the Sheraton Addis hotel is developed by two persons; they are
advanced in Addis Abeba university by computer science in visual basic and java programs and
MySQL, databases. The system is about the reservation of hotel management. It is very secured
and fast system. The home interface of the system is like this
Hawassa South Star Hotel
Hawassa South star hotel its category is a 5 star hotel, which is found in capital city of SNNP,
Hawassa. This is best hotel from hotels found in the SNNP region. The hotel management system
of Hawassa South star is developed by 4 group members in Hawassa university, they are
developed by used a php, java and c-sharp within MySQL database. The system is developed a
hotel management system within online registers.
1.3 Statement of the Problem
In the organization there are several drawbacks and problems of management system of the Lucy
hotel. When Comparing to the traditional management system to the new proposed computerized
management system has vast differences. The main drawback of the current system is exisisted
in hotel of Lucy are listed below: The cashiering system is not computerized works
Documents are not properly organized.
In all work stations the communication between them is in a piece of paper and it is so
slow.
There is lack of honesty between the employees and the managers.

 There is bore and tiredness to control the material that stores in the store place and to give
and take the material and the money from the cashier to the financial in each day.
1.4 Objective of the project
1.4.1General objective
The general objective of the project is to develop more secure and simple system to manage
Lucy hotel.
1.4.2 Specific objective
The specific objective of the project is to enables that, the following main specific object will be
accomplished.

To enable the management to see all reports that posted by the cashier, room and
hall, and store administrator.
To enable the manager to access the information of the employee record.
To enable the manager to post information to the room and hall, store
administrator and cashier.
To enable the cashier to see the posted by the manager.
To calculate the daily estimate of the income and outcome.
To enable the cashier post to the manager
To enable the cashier is to see remainder materials
To enable the receptor to count the reserved room.
To enable the receptor to post information to the manager
To enable the store administrator to control all the store materials
To enable the store administrator to control and register the expense materials and
import materials
To enable the customer to check room and hall are reserved or free.

1.5.1 Areas (site of the study)

The site area of our project is on hotel of Lucy found in Qafar regional state, in samara town.
Samara is a new town on the AwashAsseb highway in north-east Ethiopia, planned to replace
Asaita as the capital of the Afar Region. Located in the Administrative Zone 1.
1.5 Methodologies
1.5.1 System development tools
In the development of the new proposed, computerized system cashiering and management,
several hardware and software are necessary.

Hardware
Paper
Flash
Computer
Pen

Software
Php software
MS-WORD
Sql

Table 1. System development tools

1.5.2Data collection methodology
a. Interview
Since we are developing a project which doesnt have a real existing system we will try to gather
some important information by direct interview with the manager of the organization.
b. Discussion
The secondary our data collection is by discussion of our Group member.
C. observation
We observed all activity of the hotel workers, there is no existed system to facilitate, assist them
and there is simply a manual system is existed.
1.5.3 System development methodologies
The new proposed system is going to be developed with a computerized system which holds
interfaces with in. All the workers connected with the Hotel management system such as the
cashier, store administrator, finance (r-reception) are supposed to be networked together with the
manager. So those, the estimation of income and outcome of the motel are achieved. So to
achieve this new system there are different option like water fall, iterative, spiral, rational unified
process from those types of system development methodologies in software development
process, we selected the iterative system development methodology for our project. Because this
methodology is simple to implement by moving forward and backward direction from one phase
to other phase without interference.
1.6 Scope and Limitation
1.6.1 Scope of the project
Scope of the project in hotel management system of Lucy hotel is to facilitate, fast, secure, and
computerized jobs among the manager, cashier, store administrator and finance, with help of
computer technology. And we can list the purpose of Lucy hotel management system like,
The system store all the employee information in secure database
The system calculates daily all the income and outcome.
The system inform us the essential materials if it is used out
The system can register new employees and delete old employees
It can add new items
It can record the employees working hours and their payment

1.6.2 Limitation of the project

Our system is only focuses on the hotel management system of Lucy hotel. We focus on the
structure of the hotel which we get from the manager. May be the system is not suitable for other
hotels having different structure.
1.7 Significance of the project
The proposed system is expected to provide a better way of communication between the
manager, the casher, the store administrator and room and hall administrator. To share and to
control all daily income and outcome cost.
The project is also expected to save time, to estimate the prices daily outcome and income. In
other way it calculates the maximum and minimum of profits, generally to ignoring the previous
traditional servicing system or improving the performance of the hotel management system to
satisfy the customers need.
1.8 project team profile
All members involved or taking part in developing the system are putting their effort together
and sharing their ideas to full fill all the necessary steps taken to develop one better project work.
Most of the work are done together as one, but there is a work division given to each member we
have like

CHAPTER TWO
SYSTEM REQUIREMENET SPECIFICATION
2.1 INTRODUCTION
SRS:- Describe what the proposed software should do without how the software will do it and
also provide reference for validation of final product.
In the organization of this Lucy hotel, there are several drawbacks and problems of management
system of the Lucy hotel. Different problem are existed in this hotel like The cashiering system is
not computerized works, Documents are not properly organized, In all work stations the
communication between them is in a piece of paper and it is so slow, There is lack of honesty
between the employees and the managers, There is bore and tiredness to control the material that
stores in the store place and to give and take the material and the money from the cashier to the
financial in each day.

2.2 Current system

The current system of the hotel is focused its work by the manually system. The connection
between the manager, the cashier, the store administrator, reception and the finance is by the
piece of paper instead of computerized. The manager of the hotel is controlled each employee by
contact face to face. In the hotel manager and all the employees at the hotel decides a meeting
one day a week for the purposed of auditing and what looks like all the activity in the hotel.
The cashier activated its work by accepted/ collected money from the customers and saves the
money by the admit ion calculator to check its income and outcome. In another way the receptor
works by direct speech with the customers, when it is free room or not by the observation of the
rooms. The store administrator stores the materials by recording the name and the number of
material, the salary of the employees in help of paper. And also the finance records the all over
time of the employees and the new entrance of materials.
2.2.1 Overview of existed system
In this Lucy hotel there are many employers those are actively participated in the service of
hotel like cashier, store administrator, receptor including the manager by the system of
manual that is boring and tiredness to control everything in the hotel like described the
above.
2.2.2 Problem of current system
The current system of this hotel greatly affected all activities those serviced in this hotel in case
of this manual system and also affecting to save time, to estimate the prices daily outcome and
income and also to calculates the maximum and minimum of profits, improving the performance
of the hotel management system to satisfy the customers needs.

2.3 Business rule

Rule 1: Authorize to the system
Customer must have a valid user name and password.
Rule2: Correct information
The manager checks the filled employee information and the entered information
are correct.
Rule 3: Validate employee information
The authorized manager registers the customers information and the system validates
Rule 4 : providing correct service
The employer that provides service should wear their uniforms.
They must provide service to the customer politely and with required speed.
2.3 Proposed system
The proposed system of the management system of Lucy hotel is managed all the activity of the
employee by the manager means that the manager is controlled for the room and hall
administrator, store administrator, cashier and finance in a computerized form. The manager has
its own user name and password to get to the system. The cashier also has a user name and

password to store money that is accepted from customers in the daily activities. The room
administrator rents a room checking by the system free or not. The store administrator is the store
materials and control the input and output materials. The finance also records and gives salary to
the employee, to transfer money from the cashier to the manager, new materials to transfer to the
store administrator. Generally the manager is controlled all employee daily by the system.

2.3.1 Overview
The management system is easy to use, secure and fast after completed. Because the system is
computerized, so nothing is not lost time consume and disturbed between the employee and the
system.
2.3.2 Goals of the proposed system
The goal of this new proposed system is to achieved new management system in this hotel
means that This new system is expected to save time, to estimate the prices daily outcome and
income. In other way it calculates the maximum and minimum of profits, generally to ignoring
the previous traditional servicing system or improving the performance of the hotel management
system to satisfy all the customers need.

2.3.2 Functional requirements

A functional requirement defines a function of a software system or its component. A function
is described as a set of inputs, the behaviour, and outputs (see also software).
The plan for implementing functional requirements is detailed in the system design.
Functional requirements may be calculations, technical details, data manipulation and processing
and other specific functionality that define what a system is supposed to accomplish. Behavioural
requirements describing all the cases where the system uses the functional requirements are
captured in use cases
Data storage and retrieval: - The system stores data of the hotels, employee, total income of
the hotel, information that transferred materials. The retrieval of information should be early and
data should be saved properly in a well organized database server to that the process of data
retrieving would be simple and faster.

Enquires and report facilities: - The system must incorporate report

generalization facilities so that an administrator of the system can easily filter out
the report of each task. The function requirement of the will by system is to
reduce the degree of communication problems.
The system is computerized: - Since the existing system is manual that doesnt
consider communication will connection, the new system will have computer that
is feasible for the entire employee where they are.

2.3.3 Non functional requirement

5

Non-functional requirement is a requirement that specifies criteria that can be used to judge the
operation of a system, rather than specific behaviours. The plan for implementing non-functional
requirements is detailed in the system architecture.
Non-functional requirements are often called qualities of a system. Other terms for nonfunctional requirements are "constraints", "quality attributes", "quality goals", "quality of service
requirements" and "non-behavioural requirements".
2.3.3.1 Look and feel requirements
User interface
The system will be easy to understand and self-explanatory graphical user interfaces
that erase the interaction of the user with the system.
2.3.3.2 Usability requirements
2.3.3.3 Security requirements
Security is the main part of the system to control it. Allow the system only for
administrator. Administrator login restrictedly, that means with a password.
2.3.3.4 Performance requirement

The system should check data redundancy for adding and updating records
The system should check the total items
The system controls the workers of the hotel
The system should be check out the total income and outcomes
The system should be checked the free rooms
The system gives warning if it is close to empty items

Quality requirement
a. Reliability: - It will automatic (computerized) the employee hotel management
system as its final goal. There for it will computerized hotel management
system when it is finally completed.
b. Availability: - Factors required to guarantee the system availability are
Full requirement entrance by the employee (uses) and check points that check
the users needs.
When the system is busy the user must wait the program in patience until it
continues working properly back again.
2.3.3.5 Portability requirements
The system portability is on how it can easily be portable from one machine to
another machine.
Safety requirements

The system being prepared needs to be safe in all its application. Its copy of the
database needs to be stored in an external drive like hard disk or CDs in order to have
a safe back-up and have less chance of data loss.
Like other desktop application programs, emphasis should be given to the project to
protect it from viruses, that means the personnel computer should have virus
protection that is anti-virus or any other protection provided, by:

Upgrading the anti-virus or any other virus protection created continuously and
install or download new versions of virus protection on the computer being used.
Being concerned about the data inputs.
Use suitable operating system for the software

2.4 system models

2.4.1 Scenarios
Scenario 1
Name of use case: create account
Participating instance actor: manger, cashier
Entry condition:
1. manager login to the system by using his account.
2. The manager has the employee information (full name, employee id, e-mail).
Flow of events:
1. manager click on the create account link from the EHMS home page.
2. The system displays the create account form.
3. He/she fills the form and click on generate button.
4. The system generates new user account with username and password.
Alternate Case:
5. If he/she made error when he fill the form and click the generate button
with error, the system displays an error message and it allows to him to try
again.
6. He/she clicks on the clear button to clean the text field.
Exit condition: The system saves all necessary information in the employee account table.
Special requirement: when he/she performs this task connection should not be down.
Scenario 2
Name of use case: Register
Participating instance actor: manager, cashier, reception admin, store admin
Entry condition: all above actor logs in to the system using their own account.

Flow of events:

1. He/she clicks on the Registration link from the home page.

2. The system displays registration form for their own activity.
3. He/she fills the form and click on submit button.
4. The system displays successfully registered message
Alternate Case:
5. If the registered record exists in the database, the system displays the already
registered message.
6. If the input data has errors, the system display error message & allow him to try
again
Exit condition: The system saves his record.
Special requirement: when he performs this task connection should not be down.
Scenario 3
Name of use case: order
Participating instance actor: manager, cashier
Entry condition: The manager and cashier logs into the system using their account.
Flow of events:
1. both clicks on the link form from the home page.
2. The system displays the form to order.
Alternate Case:
3. If there is a mistake in the ,the system displays error message and it allows to
make correction
Special requirement: when the manger and cashier performed this task connection should not
be down
Scenario 4
Name of use case: manage hotel
Participating instance actor: manager
Entry condition: manager logs in to the system using her/his account.
Flow of events:
1. She/he clicks on the manager link form from the home page.
2. The System displays all employees those participate in the hotel.
3. The system displays the existing information of all activity
4. She/he clicks on the check button to view the activity.
5. The system displays everything existed,
6. She/he then clicks on order button.
7. The System displays the order form.
8. She/he fills the form and clicks manager button from report form.

Alternate Case:
9. If she/he made error when she update the information and submit with error,
the system displays an error message and it allows to her/he to try again.
5

Exit condition: The information modify successfully

Special requirement: when she/he performs this task connection should not be down.
Scenario 5
Name of use case: check
Participating instance actor: cashier, manager
Entry condition: both logs in to the system using his account.
Flow of events:
1. He/he click on the check slip link from the home page.
2. The System displays check slip form.
3. He/she fills the form and click on generate button.
4. The system generates the form.
Alternate Case:
5. If he/she made a mistake in the checking, the system displays error message
and allow making correction.
Exit condition: The form of check is generated successfully
Special requirement: when he/she performs this task connection should not be down.
Scenario 6
Name of use case: report
Participating instance actor: cashier, reception admin, store admin
Entry condition: all logs in to the system using her/she account.
Flow of events:
1. She/he clicks on report form link from the home page.
2. The system displays the report form.
3. She/he view the reported information
4. Finally she/he click on the submit button.
5. The system displays successful submit message.
Alternate Case:
6. If she/he made error when she fill the form and submit with error, the system
Exit condition: If the submission is successful, the system saves her/she reported data
successfully.
Special requirement: when she/he performs this task connection should not be down.

Scenario 7
Name of use case: feedback
Participating instance actor: customer

Entry condition: customer logs in to the system using his/her account.

Flow of events:
1. He clicks on feedback link form from the home page.
2. The system displays the feedback form.
3. He fills the form properly and click on submit button.
4. The system displays successful submit message.
Exit condition: If the submission is successful the system saves the record data successfully.
Special requirement: when he/she performs this task connection should not be down.

2.4.2 Use case model

UML diagram
Unified Modelling Language is a graphical visualisation language. It consists of a series of
symbols and connectors that can be used to create process diagrams and is often used to model
computer programs and workflows, additionally it is a standardized general-purpose modelling
language in the field of object-oriented software engineering. The Unified Modelling Language
includes a set of graphic notation techniques to create visual models of object-oriented softwareintensive systems.

Use case
A use case is a methodology used in system analysis to identify, clarify, and organize system
requirements. The use case is made up of a set of possible sequences of interactions between
systems and users in a particular environment and related to a particular goal. It consists of a
group of elements (for example, classes and interfaces) that can be used together in a way that
will have an effect larger than the sum of the separate elements combined. The use case should
contain all system activities that have significance to the users. A use case can be thought of as a
collection of possible scenarios related to a particular goal, indeed, the use case and goal are
sometimes considered to be synonymous.

Use case Diagram

The use case description of the proposed system is represented as a diagram.
The system has five actors
The manager, reception administrator, the store administrator, the finance and the cashier are the
actors that are in the system and they have their own username and password

LUCY HOTEL MANAGEMENT SYSTEM

Figure 1. Use case diagram

The Actor purpose on the system
The manager can be:

Login to the system that is only to the manager account

Register and delete employees
Check daily input and output
Check materials that are remain in the store
View all post
View employee monthly fee
Can post to any all work station
Views rooms information
Logout from the system

Cashier can be:-

Login to the system that is only to the cashier account

Check daily input
Store the outputs that are sells
Register materials that are received from the store administrator
View post when it is only to the cashier
Post to administrator
Order if items needed
Logout from the system

Reception administrator can be:

Login to the system only to see the allowed part

Check the used and unused rooms
View the posts that are when it is allowed
Check rooms that are used or unused
Register the rooms when a costumers
Logout from the system

Store administrator can be:

Login to the system that is only in the store administrator

Check the remaining materials that are in the store
Register new materials
Register output materials
View post and send post to the allowed parts
Logout from the system

Customer can be:

Check the room and hall

Order the room and hall
Write feed back

Use case description

1. Use case name:-order
2. Related requirements:-items, rooms and hall
3. Goal in context:-Makes the customer order to be managed correctly
4. Precondition:-getting order from customer
5. Successful end condition:-all orders from customers are successfully addressed
6. Failure end condition:-error will occur in managing orders
7. Actor:-cashier, customer
8. Main flow: -8.1) cashier open item order, customer open room or hall rent form
8.2) accepts customers order
8.3) fill the form based on customer order
8.4) Send to hotel controller as well save to database

8.5) close the page

1. Use case name: - register
2. Related requirements: - employees, items
3. Goal context: - to register the employees by manager and the items by cashier and store
administrator
4. Precondition:-register the items and the new employees
5. Successful end condition:-all items and employees are successfully addressed in the database
6. Failure end condition:-error will occur in register employees and items
7. Actor:-manager, cashier, store administrator
8. Main flow:8.1) manager open the register employee form, cashier and store administrator open the
item register form (different form)
8.2) fill full the information of the new employee or item
8.3) employees information saves to database and the items information send to cashier
and save to database
8.4) close the page
2. Related requirements:-items information, items, employees
3. 1. Use case name:-Report
Goal in context:-enables the manager to audit all the actions
4. Precondition:-the data must be store in database
5. Successful end condition:-able to see the report
6. Failure end condition:-failure will occur in viewing the report
7. Actor:-cashier, manager, room & hall administrator
8. Main flow:
8.1) the actors open the report form
8.2) full fill the form
8.3) send and save the form
8.4) close the page
1. Use case name:-check
2. Related requirements: - items, room and hall
3. Goal in context:-to check the new order sent from customers, cashier and store administrator
4. Precondition:-see the order and give response
5. Successful end condition:-after see the order received the customer, cashier and store
administrator response
6. Failure end condition: - failure will occur in viewing the order and response.
7. Actor:-room and hall administrator, cashier, customer and store administrator
8. Main flow:
8.1 The actor open the check form see the order
8.2 Check the order that is exist or not and give a response
5

8.3 Close the form

1. Use case name:-Manage Hotel
2. Related requirements:3. Goal in context:-enables the manager to manage the overall system in the hotel
4. Precondition:-give an order, take a report, manage hotel
5. Successful end condition:-manage the hotel
6. Failure end condition: - failure will occur in managing the hotel.
7. Actor:-manager
8. Main flow:
8.2 See and give order to the employees
8.3 Close the form
1. Use case name: - feedback
2. Related requirement:3. Goal in context: - enables the customer to write a feedback and manager see the feedback.
4. Precondition:-write comments.
5. Successful end condition:-write feedback and show the feedback.
6. Failure condition fill are in feedback.
7. Actor:-manager and customer.
8. Main flow:
8.1Open the feedback from
8.2 Full fill the form and send
8.3 The manager view comment
8.4 Close the form
1. Use case name:-create account
2. Related requirement
3. Goal context:-enables the casher and manager create account.
4. Precondition:-uses to get for the system.
5. Successful end condition:-cashier and manager create account successfully.
6. Failure condition:-error will occur in the account
7. Actor:-manager, cashier.
8. Main flow:8.1 Open the create account form
8.2Fulfill the form and click create
8.3 Close the form.

2.5.3 Object model

2.5.3.1 Data dictionary

 CUSTOMER is the central object in the module. the customer have the following
information
- Identification information includes first name, middle name, and date of birth and
place of birth.
- Contact information includes e-mail address, cellular phone.
- User authentication information includes customer ID, username, and password.
2.5.3.2 Class diagram
The class diagram is the main building block of object oriented modelling. It is used both for
general conceptual modelling of the systematic of the application, and for detailed modelling
translating the models into programming code. Class diagrams can also be used for data
modelling. The classes in a class diagram represent both the main objects, interactions in the
application and the classes to be programmed. In the diagram, classes are represented with boxes
which contain three parts
The upper part holds the name of the class
The middle part contains the attributes of the class
The bottom part gives the methods or operations the class can take or undertake
In the design of a system, a number of classes are identified and grouped together in a class
diagram which helps to determine the static relations between those objects. With detailed
modelling, the classes of the conceptual design are often split into a number of subclasses.
Class description

1.

Employee

Attributes
First name (Fname) and Last name (Lname): are a string type which holds the
first name and the last name of employees who are registering for the hotel.
Address and country are string type which holds the address and country of
employees respectively.
Gender is character type that holds the gender of employees
Id number and password are int and string type respectively which holds the
id and password for specific employees such as manager, casher, bill
controller, bar controller, restaurant controller.
Job description and hired date are string and int types respectively which hold
job type and hired date of the employee
Mobile number and salary are int and float types which hold mobile number
and salary respectively of the employee.

Operations

2.

Save, delete, update, and search which perform operations that concern the
system.
Accepts and save orders.

Customer
Attributes
First name and last name are string types which hold first name and last name of
the customer who is taking service from the hotel.
Id and country are in and string types which hold id and country of the customer.
Date in, date out and nationality is int, int, and string type respectively which
holds such information of the customer.
Operations

3. Food

Order- which enables the customer orders item, hall rent or/and room.

Attributes
Food name and food types are string types which hold information about the
name and type of each food.
Food price is afloat type which holds the price of each food.

Operations
Take order, update order, search order, delete order and search order are
operations which abeles such operation concerning the food.

3.

Room
Attributes
Room type and room number are string and integer types respectively that hold
the type and number of the room
Room price has a float type which holds the price of the room for the reserved
room
Operations
Perform reservation and check out operations

4.

Hall
Attributes
Hall Type with string type for holding type of the room
Operations
Reservation and freeing the hall

5.

Drink

 Attribute
Drink Type and Drink Name are string types for holding the type and name of the
drink
Drink Price with float type for holding the price of the drink
Operations
Accept drink, save and update orders and send orders

6.

Manager
Attributes
Id-number with integer type for holding Id number of a manager
User name and password are sting types that hold user name and password of a
manager
Operations
Save, update, search, and delete everything that concerns him or her

Dynamic models
Sequence Diagrams
Sequence diagram are used to represent flow of messages, events and actions between the
objects or components of a system. Time is represented in the vertical direction showing the
sequence of interactions of the header elements, which are displayed horizontally at the top of
the diagram. Sequence diagrams are used primarily to design, document and validate the
architecture, interfaces and logic of the system by describing the sequence of actions that need to
be performed to complete a task or scenario and also it is useful to design tools because they
provide a dynamic view of the system behaviour.

FOR MANAGER

For cashier

FOR CUSTOMER
5

For store administrator

For reception administrator

Chapter 3
1. Introduction
The system design is a building block of the system and also transforms the analysis
model in to system design model. During this the team member will define the design goal of the
project and decompose the system in to smaller sub system that can be realized by the individual
members. The result of the system design is model that includes the clear description of each
strategy, sub system decomposition and collaboration.
Generally the purpose of this design phase is to determine how wear going to build our system
and to obtain the information needed to device the actual implementation of our system.
A formal review of the high-level architectural design is conducted prior to detailed design of the
automated system/application to achieve confidence that the design satisfies the system
requirements, is in conformance with the enterprise architecture and prescribed design standards.
to raise and resolve any critical technical and/or project-related issues, and to identify and
mitigate project, technical, security, and/or business risks affecting continued detailed design and
subsequent lifecycle activities.
During the Design Phase, the initial strategy for any necessary training is also begun. Estimates
of project expenses are updated to reflect actual costs and estimates for future phases. In
addition, the work planned for future phases is redefined, if necessary, based on information
acquired during the Design Phase
In general System Design helps
1. Identifying Design Goals
2. Mapping Objects to Subsystems
3. Hardware/Software Mapping
4. Persistent Data Management
5. Global Resource Handling and Access Control
6. Software Control and Concurrency
7. Boundary Conditions

Tells the customer and programmers what the system will do What will happen to the data in the
system?

What will the system look like to users?

What choices will be offered to users?

What is the timing of events?

What will the reports and screens look like?

major hardware components and their function

hierarchy and functions of software components

data structures and data flow

3.1 Design Goals of the system

The goal of the system which will developing is to enhance /to minimize the time and resource
loss for different application that was applied when the city workers work their work manually
through the use of pen and paper only for their work application. This will also help to facilitate
the work to accomplish a specific work in short period of time i.e. a small number of people can
do more efficient work in a limited period of time.
The following are the main goals system will be developing for:
3.1.1. Performance criteria
The system will complete tasks quickly to allow easy input of large amounts of data and
to retrieve data from the server.. This project will powerful to give a good service for the
people who will use it to facilitate their activities. The system will be accessible from any
computer with internet and will be accessible anytime a user would want to use the
program.
3.1.2. Maintenance criteria
The system will require minimal upkeep and maintenance to stay working at optimal
levels. The system will better and will not highly suffered by damages therefore there is
no need to think about its maintenance features simply the database /system can maintain
it if it fails in some extent. It does not need expertise user instead it needs some
professional user in using of computers who can use database and internet very well. The
system will require minimum maintenance to stay working at optimal condition.

3.1.3.End user characteristics

This project will very simple to use. This system will have a well defined and
easily understood interface. The processes will be easy to understand and
useable by a user of
any level. Anyone who can read English can use the system,because, to use the
system only navigating through the system parts by clicking a button is the only
required thing from the system users. It does not need to write any command and think
how to use this command. The processes will be easy to understand and to use for the
system users.
In addition to ease of usability this system will be very low cost and will have minimal
upkeep costs for users. Users will need only pay for internet connectivity only.

4. Collaboration Diagram
Collaboration diagram is an interaction diagram emphasized the structural organization of
the object that participates in an interaction. Collaboration diagram usually drown in parallel
with class and sequence diagrams. It provides a birds eye view of the interaction between
objects. With this collaboration diagram we will show
-The objects
-The relationship between the object
-The message passed between the object

47

For manager

Fig: collaboration diagram for create account

47

Fig: collaboration diagram for employee registration

47

Fig: collaboration diagram for create account

Fig: collaboration diagram for employee registration

Fig: collaboration diagram for report.

47

Fig: collaboration diagram for all materials report registration.

47

Fig: collaboration diagram for new materials report.

47

Fig: collaboration diagram for hall and room registration.

47

Fig: collaboration diagram for all hall and room report registration.

Fig: collaboration diagram for feedback registration.

3. State Chart Diagram
47

In state chart diagram, we classified the following points:- Identifying important aspect to be analyze
- Identifying the states
-Identifying the events
The first starting point is an idle state form where the process starts. The next state is
arrived from event like send request, confirm request and dispatch order. These events are
responsible for state changes of order object.
During the life cycle of an order object it goes to the following states and there may be
some abnormal exists also this abnormal exist may occur due to same problem in the
system.

Fig: State chart diagram of an order object for Lucy Hotel Management
System.

47

Fig: State chart diagram for register /delete.

47

fig: State chart diagram for adding employee

3.5 .proposed Software Architecture

of the system
47

The term system architecture is used to describe the overall design and structure of a computer
network or system. It includes a wide range of physical devices, a method is required to organize
and connect these items together in a cohesive manner. The term is also used to describe complex
computer_ software tools. Systems Architecture is a generic discipline to handle objects (existing
or to be created) called "systems", in a way that supports reasoning about the structural
properties of these objects. A system architecture or systems architecture is the conceptual
model that defines the structure, behavior, and more views of a system.
There are three main components to any system architecture of the system theses includes:
storage, connectivity, and user experience. It is important to note that system architecture must
be flexible and able to meet changing needs quickly. A structure should not be very rigid and it
will not be able to support or facilitate new software or hardware.
Processing power is based on the computer or server. This hardware is akin to the brain of the
system. Purchasing and installing the correct allocation of processors to the system must be
based on the software specifications, number of concurrent users, strength of the connection, and
applications. When designing a system, scalability is critical. The system architecture must allow
additional processors to be added without any interruption to the current structure.

3.5.1 Subsystem decomposition

The importance of decomposing the system in to subsystems in any software development side
is we can easily understand what the system we are developing and what its main uses are. At the
time of project we may create many subsystems and finally we combine them to form a system.
We have decomposed our system to the following sub system:

Log In Module

Employee Info Module

Administration Module

Reports Module
Login Module

The log in subsystem checks whether the user name and password match. This sub system also
contains the access levels by separating as manager and users. manager can create account and

47

guaranteed to access (manipulate) all the data. On the other hand, the manager can changes the
password in the case users forget their password.
q

Fig login process.

47

Employee Info Module

This subsystem deals with the management of the employee information such as registering the
personal details name, qualification, skill, experience etc. All these employee information will be
saved on the database. In addition, under this subsystem creating account, filling attendance and
evaluation are included.
Management Module
This subsystem deals with the management of the employee information such as the hiring of the
eligible candidate, payments criteria, his personal information maintenance etc. These means
performing like searching employee information by Employee ID when needed and updating the
employee information, recording the new employee.

47

Fig Administrator Responsibility

Reports Module
This subsystem is specified for the purpose of the report generation for the HRMIS on desired
requests. Those reports are:
Employee talent Report- reports employee capacity, activity and experience
Employee Info Report- to view track of each employee
3.5.3 Hardware/software mapping
The proposed system composed of: My SQL Server 2008 for database.
Windows XP/ Windows 7 / Windows 8 or any 32 bit Multi operating system
47

 1.80 GHz of Dual CPU, 100 GB of hard disk

2 GB of RAM for high performance

3.5.4 Persistent data modelling

Since aim of this project is to handling the employee information on the database and retrieving
as needed, there is lots of information to store and manage. We will use a relational database to
store all the personal data, user accounts and other employee information. So, retrieval of the
information that user requests will be fast and retrieved information will be permanent. Input
information and named entities in that forms are also stored in the database without losing the
relations between input information and named entities after information extraction

Persistent data management

Persistence layer provides the infrastructure for the storage and retrieval of objects. This helps to
isolate our application from changes to permanent storage approach. The persistence layer
increases the maintainability, extensibility and portability of your application. And it also
provides access to permanent storage but it is not a permanent storage mechanism itself. The
goal of persistence layer is to reduce the maintenance effort that is required whenever changes
are made our system.
Persistence models also called data models are used to communicate the design of a database,
usually a relational database, to both users and other developers.

Persistence are used the schema of database. The strength of persistence models is that data
entities are conceptually the same as the table of relation data base and that attributes are the
Log In Form
No.

Field Name

Data type

1
2
3

Username
Password
LevelOfaccess

Varchar(20)
Varchar(20)
Varchar(20)

EMPLOOYEE REGISTRATION

47

No.
1
2
3
4
5
6

Fieldname
EmpID(pk)
First Name
Middle Name
Last name
Sex
Bith year

Data Type
varchar(20)
varchar(20)
varchar(20)
char(5)
varchar(20)
Year

7
8

Level of education varchar(50)

Year
Of Integer

9
10

employment
Type of employee
Varchar(30)
month
of Varchar(10)

11
12

employment
Marriage status
Char(10)
Type
of Varchar(10)

13

employment
Skill

of Varchar(5)

employment

Employee skills

No.

Fieldname

Data Type

1
2
3
4

First Name
Qualification
Experience
Skills

varchar(20)
varchar(20)
Integer
varchar(20)
47

3.5.5 Access control and security

The Lucy hotel management system is the system that all covers the system like staffing, and
reporting. As a result, our system accessed by different account levels.
The manager can access all the data as needed including adding, updating, searching and
other anomalies.
The other employees have also guaranteed to view the data allowed for them like
viewing, reporting.
Multiple levels of security protect sensitive documents and files from unauthorized
viewers. Each user has a security access level and each document has a sensitivity level.
Depending upon the access level of the user, they will see only the list of documents that
is appropriate for their security access level.
Generally, the system manager controls all user names, passwords, security access levels and
document sensitivity level.

3.4 Subsystem Services

We try to describe the services of each subsystem as follows
Service Name
Log In Module

Service Input
User name and

Service Output
If the user name and

Service Description
Authenticates and

password to enter in

the password matches

authorizes the user

to the system

the main form will be

displayed if not
47

Employee Info

correct notify the user

Employee information Saving to the database

Register the employee

Module
Manager Module

recorded
Enters needed

information
Takes action on all the

Manipulated data

information to
Report Module

manipulate the DB.

Id, date, year, etc

data
Report information

Reports the employee

required in the

information from the

specified year, month,

database

and date

4.Reference
1.S. Koolmanojwong, "Analysis and Design of B to C
E Marketplace for Tourism with UML " M.S. Thesis, Faculty of
Science and Technology, Assumption
University, Bangkok, Thailand 2000.
2.M. J. O'Fallon and D. G. Rutherford. (2011). Hotel Management
and Operations | CA College of Ayurveda.
Available: http://www.ayurvedacollege.com/amazon_store /item /
0470177144
3.S. Koolmanojwong and P. Santiprabhob, "Intelligent
Electronic Marketplace for Tourism."
4.E. W. T. Ngai and F. K. T. Wat, "Design and development of a
fuzzy expert system for hotelselection," Omega, vol. 31, pp. 275286, 2003.
5.G. Jingzhi, et al., "Alibaba International: Building a
Global Electronic Marketplace," in e-Business
Engineering, 2006. ICEBE '06. IEEE International
Conference on, 2006, pp. 545 -548.
6.W. S. Grayand S. C. Liguori, Hotel and Motel
Management and Operations, Fourth Edition ed.: Prentice Hall,
2002.

47