COURSE
BUSINESS
APPLICATION ANALYSIS AND DESIGN
|
SNO
|
CONTENTS
|
|
1.
|
ACKNOWLEDGEMT
|
|
2.
|
FUNCTIONAL
REQUIREMENTS
|
|
3.
|
NON
FUNCTIONAL REQUIREMENTS
|
|
4.
|
USE
CASE DIAGRAM
|
|
5.
|
FLOW
OF EVENTS
|
|
6.
|
ACTIVITY
DIAGRAM
|
|
7.
|
REALIZATION
OF USE-CASES
|
|
8.
|
SEQUENCE
DIAGRAM
|
|
9.
|
CLASS
DIAGRAM
|
|
10
|
ENTITY
RELATIONAL MODEL
|
ACKNOWLEDGEMENT
It
is our duty to acknowledge with gratitude the help we got from our
teacher
Sir
Ayub Latif in the completion of our project we take immense pleasure
in thanking him as he permitted us to carry out this project. We
would also like to thank our lab teacher Sir Aftab for his support
and guidance, they have been really helpful we would again like to
thank appreciate their assistance.
Finally
but most importantly we would like to thank all our friends and class
fellows who helped us in the project.
FUNCTIONAL REQUIREMENTS
The
functional requirements of Hotel management system are as under:
- The guests seek appropriate information from the receptionist and either makes reservation or leave.
- The receptionist checks for available rooms and can check in guest
- The customers must give all the details after checking in and the receptionist confirm all the details
- Bill is prepared, opened and closed by accounts department
- The customer must clear all his bills before checking-out
- Receptionist request room cleaning after guest checks-out
- The room is then available for reservation.
NON-FUNCTIONAL REQUIREMENTS
The
nonfunctional requirements of hotel management system are as under:
- 1. The hotel system has a database which holds the name along with other details of all the customers checking in
- 2. The receptionist can check in a guest 24 hours a day and 365 days a year
- 3. The data in the database can be updated but cannot be deleted.
- 4. There is a backup for the database in case it gets crashed.
- 5. The database is user friendly and can be easily used by the system users.
USE CASE DIAGRAM
ACTIVITY DIAGRAM
USE CASE REALIZATION
Seek Information
Guest;The
person who seeks information from receptionist.
Seeking;Guest
is seeking information from receptionist performing verb.
Information;It’s
a interface between guest and receptionist.
MAKE RESERVATION
Reserve;The
person whom makes reservation.
Reservation
Interface;Interface
between system and manager.
Reservation
Manager;Makes
reservation.
CHECK IN GUEST
Guest;The
person for whom receptionist check the room.
Data
Entry Form;Interface
between guest and receptionist.
Reception
Manager ;
checked room for guests.
CONFORM DETAILS
Details;
Having Information about guest.
Reception Manager; Create room
for guest.
Details Interface; Giving
information to guest.
OPEN BILL
Accountant;
Have record of bill.
Opening
Interface;GUI
path between accountant and receptionist.
Accountant
Manager;
Open and prepare final bill for guest.
Prepare Final Bill:
Bill;Having
information about bill.
Preparing
Interface;Path
between accountant manager and receptionist.
SEQUENCE DIAGRAM FOR CHECK IN
SEQUENCE
DAIGRAM FOR “MAKE RESERVATION”
CLASS DIGRAM
FLOW
OF EVENTS
MAKE
RESERVATION
|
USE CASE:
|
Make
reservation
|
|
INTRODUCTION:
|
Receptionist reserves a
room or rooms for guests
|
|
ACTORS:
|
Receptionist and guest |
|
PRE- CONDITIONS:
|
A
guest must give all the details to the receptionist at the time of
reservation
|
|
POST- CONDITIONS:
|
Guest checks-in |
|
BASIC FLOW:
|
Receptionist
reserves rooms for guests and enter all the details of the guests
in the database
|
|
RELATIONSHIPS:
|
Association
relation between guest and receptionist
|
|
|
|
|
CHECK-IN
GUEST
|
|
|
USE
CASE:
CHECK-IN GUEST
|
|
INTRODUCTION:
This use case is executed when reservation is made and
guest
checks-in |
|
ACTORS:
Guest and receptionist |
|
Pre- conditions:
Reservation must be made and receptionist looks for
the booked
o
rooms for that guest confirm details
|
|
|
|
POST- CONDITIONS:
Bill is opened when guest checks-in |
|
BASIC FLOW:
Guest after making reservation check-in,
receptionist looks
for the reserved room/rooms a new bill is opened by the
accounts department
|
|
|
|
RELATIONSHIPS:
Association relation between guest and receptionist |
PREPARE
FINAL BILL
USE
CASE : prepare final bill
INTRODUCTION:
final
bill is cleared by the guest at the time of check-out
ACTOR
: guest,
accountant and receptionist
PRE-CONDITIONS:
final bill must be cleared
POST
CONDITIONS -
BASIC
FLOW: customer
clears all the bills and hand over the room keys
at
the reception
RELATIONSHIPS
association
relation between receptionist and guest.
|
OPEN
NEW BILL
|
|
|
USE
CASE:
|
OPEN
NEW BILL
This
use-case is used by the accountant of hotel, when a guest check-in
a new bill is opened
|
|
ACTORS:
|
Accountant, receptionist |
|
PRE- CONDITIONS:
|
a
guest must check-in and provide all the details
|
|
POST- CONDITIONS:
|
The customer is informed
about the bill being opened |
|
BASIC FLOW:
|
A
new guest checks-in receptionist updates the information in the
system and a new bill is opened by the accountant.
|
|
RELATIONSHIPS:
|
Aggregation relation with
account |
|
|
|
|
|
|
Posts
0 comments:
Post a Comment