Comprehensive Report: Analysis and Design of Hotel Reservation System

This report presents a comprehensive analysis and design of a hotel reservation system for the "Meda Midula" hotel. It begins with an organizational analysis, examining the hotel's current manual reservation system and its drawbacks. The report then justifies the suitability of a computerized system, identifying the advantages of using a standard software development lifecycle model. The core of the report focuses on designing the data model using ER diagrams, detailing entities, attributes, relationships, and cardinalities. A data dictionary is included to clarify the data structure. Furthermore, the report designs the functional model using Data Flow Diagrams (DFDs), illustrating the system's processes, data flows, and external entities at both context and level 0 diagrams. The assignment fulfills the requirements of the Higher National Diploma in Computing & System Development, SEC4203 module, and demonstrates a strong understanding of system analysis and design principles, including data modeling, functional modeling, and the application of the software development lifecycle.

Assignment Cover Sheet
Qualification Module Number and Title
Higher National Diploma in Computing & System
Development
SEC4203
System Analysis & Designing
Student Name & No. Assessor
SAHAN WIJEBANDARA KG/HDCSE/12/25 M.G. Asanka Dinesh
Hand out date Submission Date
Assessment type
Assignment 1
Assignment 2
Duration/Length of
Assessment Type
Group Presentation: 15
mins (750 words
equivalent)
WRIT1-Coursework:
2250 words equivalent
Weighting of Assessment
100%
25 %
75%
Learner declaration
I, SAHAN WIJEBANDARA KG/HDCSE/12/25, certify that the work submitted for this assignment is
my own and research sources are fully acknowledged.
Marks Awarded
First assessor
IV marks
Agreed grade
Signature of the assessor Date
FEEDBACK FORM

INTERNATIONAL COLLEGE OF BUSINESS & TECHNOLOGY
Module:
Student:
Assessor:
Assignment:
Strong features of your work:
Areas for improvement:
Marks Awarded:
Coursework
Learning outcomes covered
1. Understand system designing methodologies, tools and the techniques

2. Evaluate different systems development life cycle models
3. Analyze the system by using appropriate fact-finding techniques.
4. Design the analyzed system by using appropriate system design techniques.
Scenario and Tasks
Introduction
System Analysis & designing is a very important subject domain related to
Information systems. Information systems’ durability, Validity, efficiency & accuracy
depends on how well the system investigation & designing activities are accomplished during
the system development life cycle. Learning & making use of the best tools such as Entity
Relationship Diagram, Data Flow Diagram, Flowchart and Unified Modelling Language
Diagrams for aforementioned activities are very much essential for a system analyst.
Clear understand ability of Software Development Life Cycle model stages &
unique duties assigned to those enables software development team to maintain product
quality, track progress, project budget and the nature of the product, according to higher
satisfactory level. Selecting the best Software development process model for an information
system project is crucial since success or failure of the product can be decided by the process
model & its systematic approach.
When the subject domain is concerned it is always imperative to attention to be paid in
applying creativity and innovation for system designing in a manner that modern world man
kind’s requirements are supported by considering not only how their lives are further
improved with sophistication but also focusing on how does ethical and professional issues
are mitigated as much as possible.
Scenario
“Meda Midula” is a hotel consisting of 100 rooms needs to computerize their manual Hotel
Reservation System. The systems analyst who was assigned to this project has visited the
Hotel and he has gathered the following information about the system. The following text
describes his findings.
The 100 rooms available are categorized into different room types and each room type has
different rates. The number of rooms in different types and the corresponding rates are as
follows:
Room Type Room No. from/to Rate/Night;
 Single 1 to 60 Rs. 1000

 Double 61 to 89 Rs. 1800
 Suite 90 to 100 Rs. 5000
A Customer can reserve a room by calling the hotel receptionist. The receptionist will answer
customer’s queries regarding the room types, room rates, modes of payments available and
any discounts the customer is entitled to etc. The receptionist will then take the following
particulars from the customer, if customer wishes to proceed with the reservation.
Customer’s name, contact address, Country, Sex, Type of accommodation, the period of
stay, expected check in date.
Subsequently the receptionist will check the room availability. If a room is available, the
customer is informed about the room availability. If customer accepts the reservation, a room
number is allocated at the same time. The customer is also informed if a room is not
available. A customer can cancel the reservation at any time. It can be done by calling or by
sending a fax. The receptionist is also responsible for handling the cancellations. When the
customer checks-in at the hotel on the reserved date, the receptionist will obtain the
customers desired mode of payment. The customer may be entitled to a discount based on the
payment mode selected. The different payment modes and their discounts are as follows:
Payment Modes Discount
 Cash - No discount
 Traveler’s Cheque - 2% e.g. AMEX, Cooks etc.
 Credit Card - 3% e.g. Diners, Master Etc.
 Company - Depend upon the company (E.g. NEC 12%, IBM 10% etc.)
The Customer can checks-out from the hotel at any time by informing the receptionist. The
receptionist will immediately inform the billing Clerk to handle the billing. The details about
the Payments such as discounts given, company name, kind of traveler’s cheques used, and
credit card details etc. are preserved for any future reference.
If the customer needs to extend the stay he/she may do so by informing the receptionist.
Receptionist will check the room availability and extension is accepted if rooms are available.
Imagine that you have been assigned as a system Analyst by the e-Builders Systems
Development PLC to prepare a fully descriptive documentation comprised of Hotel
Reservation System analysis & designing information. In order to begin with user
requirement gathering & system environment analysis you are free to choose any higher
educational institute to conduct interviews & site observations. In prior commencing with
system investigation activities proper approval should be given to you by authorized officials
of the tourist category hotels that you are visiting. In order to get the approval you can
forward ICBT Campus official request letter to them.

General Guidelines for Students
1. With knowledge gain from the case study/Real world Scenario, analyse the facts
carefully and try to understand the association between each entity in the
environment. Also identify the data that is, needed to be stored for each entity and its
relationships. Any applicable assumptions made, should be clearly mention with
proper justification.
2. Final report should be in professional manner and with proper formatting.
3. The student needs to give priority in designing the software product of the
information system.
4. Organizational visits & information gathering can be done in both individual and
group basis which not exceeding 4 members per group.
5. Before organizational / Work site visits students are expected to obtain ICBT official
letter requesting the relevant company for conducting information gathering work
within their premises.
6. Please note that students are expected to maintain backup copies of work in different
media. Due to any hardware, software malfunctions or virus attacks, assignment
deadline will not be lifted.
Assignment 1
Group – (Viva and Document Submission)
Task
Conduct an organizational analysis and report the findings of the organization/
institution to what the information system will be implemented. Further justify
suitability of the information system for the same according to the present situation.
(LO1 & LO3 - 30 Marks)
Assignment 2 (70 Marks)
Individual – (Document Submission)
Tasks
1. Identify the advantage of using a standard software development lifecycle a model for
developing the software solution what is proposed for the organization/ institution.
(LO2- 30 Marks)

2. Design the data model of the software solution that will be implemented in the
organization / institution by considering all required data / information requirements
and explain briefly what is the best technique is to carry out data model designing of
the system. (LO4- 20 Marks)
3. Design the functional model of the system software solution that will be
implemented in the organization / institution having concerned all the features
/facilities, data collection, transitions, transfers and dissemination requirements and
explain briefly what is the best technique is to carry out functional model designing
of the system. (LO4-20 Marks)

Assignment 1(LO1 and LO3 –30 Marks)
Criteria Marks Marks
obtained
by the
student
for the
answer
provided
Out of
30
Poor
 Very brief introduction about the selected
organization
 Vision and mission statement for the selected
organization.
0 - 5
Satisfactory
 Provide clear introduction about the
organization and mention vision, mission,
objectives and goals of the selected
organization.
 Management hierarchy of the organization is
included
 Description About the current system and its
drawbacks.
 Use of appropriate fact-finding techniques to
identify requirements of the proposed solution
 Participating for the presentation.
6 - 11
Good
 Provide clear introduction about the
organization and mention vision, mission,
objectives and goals of the selected
organization.
 Management hierarchy of the organization is
included
 Clear description about the current system
and its drawbacks.
 Use of appropriate fact-finding techniques to
12 - 20

identify requirements of the proposed
solution
 Description with regarding the proposed
solution.
 Participating for the presentation session
and responding for the questions in a smart
manner
Excellent
 Provide clear introduction about the
organization and mention vision, mission,
objectives and goals of the selected
organization.
 Management hierarchy of the organization is
included
 Clear description about the current system
and its drawbacks.
 Use of appropriate fact-finding techniques to
identify requirements of the proposed
solution
 Clear Description with regarding the proposed
solution by explaining how does the proposed
solution supports to overcome current
drawbacks.
 Participating for the viva session and
responding for the questions in a smart
manner Use of standard level (Open Ended/Close Ended)
Questionnaire or Interview Guide.
 Samples of the Questionnaire & Interviews
attached.
21 - 30

Assignment 2 (LO2 and LO4 – 70 Marks)
Task 1 (LO2 – 30 Marks)
Criteria Marks Marks
obtained
by the
student
for the
answer
provided
Out of
30
Fail
 System Development life cycle explained
such as Communication, planning,
Designing, Development & Testing,
Implementation but no mapping has been
done with system implemented.
0-5
Pass
 At least Five stages of the System
Development life cycle explained such as
Communication, planning, Designing,
Development & Testing, Implementation.
 Every stage has been mapped with proposing
system development & designing activities.
6-11
Good
 At least Five stages of the System
Development life cycle explained such as
Communication, planning, Designing,
Development & Testing, Implementation.
 Every stage has been mapped with proposing
system development & designing activities.
 The description based on Prescriptive,
Incremental, Evolutionary, Agile &
Specialized Process Models
12-20
Excellent
 At least Five stages of the System
Development life cycle explained such as
Communication, planning, Designing,
Development & Testing, Implementation.
 Every stage has been mapped with proposing
system development & designing activities.
 The description based on
Prescriptive,Incremental,Evolutionary,Agile
& Specialized Process Models
 Justifications have been done based on the
21-30

qualities of the proposing system.

Task 2 (LO4 – 20 Marks)
Criteria Marks Marks obtained
by the student
for the answer
provided
Out of 20
Poor
 Use ER diagrams to design data model of the
proposing system but some errors exists. 0-8
Satisfactory
 Use ER diagrams to design data model of the
proposing system.
 Find entities, Attributes, relationships, Primary
keys, , different cardinalities, , composite keys,
and other entities.
 Attributes, Entities, Relationships &
Cardinalities properly selected & illustrated.
9-12
Good
 Use ER diagrams to design data model of the
proposing system.
 Find entities, Attributes, relationships, Primary
keys, proper relationships with cardinality ratios.
 Attributes, Entities, Relationships &
Cardinalities properly selected & illustrated.
 Write a data dictionary for the ER diagram.
13-15
Excellent
 Use ER diagrams to design data model of the
proposing system.
 Find entities, Attributes, relationships, Primary
keys, proper relationships with cardinality ratios.
 Attributes, Entities, Relationships &
Cardinalities properly selected & illustrated.
16-20

 Write a data dictionary for the ER diagram.
 Has been used standard format for the Data
dictionary.
Task 3 (LO4 – 20 Marks)
Criteria Marks Marks obtained
by the student
for the answer
provided
Out of 20
Poor
 Draw context level Data Flow Diagram to
illustrate functional model of the proposing
system with some errors.
0-7
Satisfactory
 Draw context level Data Flow Diagram to
illustrate functional model of the proposing
system.
 External Entitles, Main Information System &
Information Initial flow between External
Entities & Main Information System have been
identified & illustrated.
 Proper Process & data flow labeling used
8-12
Good
 Draw context level Data Flow Diagram to
illustrate functional model of the proposing
system.
 External Entitles, Main Information System &
Information Initial flow between External
Entities & Main Information System have been
identified & illustrated.
 Draw Level 0 Data Flow Diagram to illustrate
functional model of the proposing system.
showing at least five different transaction
processors
13-15

 External Entities, Major Processes, Data
Storages & initial Data Flows & Intermediate
Data Flows in between them have been
Identified & illustrated.
 Draw a Level 1 Data Flow Diagram to illustrate
functional model of the proposing system
considering detailed analysis.
 External Entities, Sub Processes, Data Storages
& initial Data Flows & Intermediate Data Flows
in between them have been Identified &
illustrated.
 Proper Process & data flow labeling used
Excellent
 Draw context level Data Flow Diagram to illustrate
functional model of the proposing system.
 External Entitles, Main Information System &
Information Initial flow between External Entities &
Main Information System have been identified &
illustrated.
 In order to further explain internal logic of the
major processes’ of the information system,
Structured English, Decision Trees & Decision
Tables properly used for DFD level 0 processes.
 Process specifications have been included using
standard process specification format
 Object type, Data Type, Data Inflow & Data Out
Flow have been described.
 Write a data dictionary for the DFD level 0 using
standard format.
 Top down designing technique & the bottom up
designing technique should be properly explained
considering the functional design.
 UML diagrams (USE-CASE and CLASS) should be
tally with system’s functionalities.
16-20

Assignment 1: Document Format:
 Submission format: PPT
 Words: 750 words
 Printing Margins: LHS; RHS: 1 Inch
 Binding Margin: ½ Inch
 Header and Footer: 1 Inch
 Basic Font Size: 12
 Line Spacing: 1.5
 Font Style: Times New Roman
Assignment 2: Document Format:
 Submission format: Document
 Paper Size: A4
 Words: 2250 words
 Printing Margins: LHS; RHS: 1 Inch
 Binding Margin: ½ Inch
 Header and Footer: 1 Inch
 Basic Font Size: 12
 Line Spacing: 1.5
 Font Style: Times New Roman

Acknowledgement
First of all, I would like to express my appreciation to all those who provided me the to
complete this report. A special gratitude I give to my lecture in System Analysis and
Designing, Asanka Dinesh whose contribution in suggestions and encouragement helped me
to coordinate my Assignment.
I would like to pay my gratitude to the websites that I have referred to in completing this
assignment. As well as I give my deepest appreciation for my family members for
encouraging and helping me in several aspects when completing this work.

ABBREVIATION
Abbreviation Meaning
SDLC Software Development Life Cycle
ER Entity Relationship
UML Unified Modeling Language
DFD Data Flow Diagram
SRS System Requirement Specification
UAT User Acceptance Testing
ID Identity Number
DOB Dato of Birth

Executive Summery
World is fast developing with technologies. Therefore, our all system should be developed
with technologies. Why people are attracted to this field, it is the most interesting filed in the
world. If we want to produce an efficient and accuracy, good service, we need to information
technology. This scenario explains their old manual system are most problem, therefore this
Meda Midula Hotel need to computerized system. This report includes feasibility study
reports, what is the most suitable SDLC model in this system. DFD diagrams, UML
diagrams, and other documentation.
I have identified the advantages of using a standard software development lifecycle model for
developing the software solution what is proposed. In the task I have implemented the
suitable data model of the software solution.
Last task is done by considering the requirements and specification of the information system
with benefits and future requirements and recommendations.

Table of Content
Contents
Task 1......................................................................................................................................21
1.0 Software Development Life Cycle..........................................................................21
1.1 Advantages and Disadvantages...................................................................................22
1.2 Waterfall Model...............................................................................................................24
1.4 Proposed Hotel Reservation System...............................................................................25
2.2 Hotel Reservation System............................................................................................26
Task 2......................................................................................................................................27
2.1 ER Diagram..................................................................................................................27
2.2 Data Dictionary............................................................................................................28
2.2.1 Employee Table.....................................................................................................28
2.2.2 Customer Table.....................................................................................................28
2.2.3 Booking Table........................................................................................................28
2.2.4 Room Type Table..................................................................................................29
2.2.5 Room Table............................................................................................................29
2.2.6 System Admin Table.............................................................................................29
2.2.7 Receptionist Table.................................................................................................29
2.2.8 Invoice Table..........................................................................................................29
Task 3......................................................................................................................................30
3.1 Data Flow Diagram (DFD)..........................................................................................30
3.1.1 Data Dictionary.........................................................................................................30
3.1.1.1 Receptionist Table..............................................................................................30
3.1.1.2 Manager Table..............................................................................................30
3.2 Unified Modeling Language (UML)...........................................................................31
3.2.1 Use Case Diagram.................................................................................................31
SCOPE....................................................................................................................................32
CONCLUSION.......................................................................................................................32
GANTT CHART....................................................................................................................32
REFERENCE.........................................................................................................................33
Table 1......................................................................................................................................22
Table 2......................................................................................................................................29
Table 3......................................................................................................................................29
Table 4......................................................................................................................................30
Table 5......................................................................................................................................30

Table 6......................................................................................................................................30
Table 7......................................................................................................................................30
Table 8......................................................................................................................................30
Table 9......................................................................................................................................30
Table 10....................................................................................................................................31
Table 11....................................................................................................................................32
Figure 1....................................................................................................................................21
Figure 2....................................................................................................................................22
Figure 3....................................................................................................................................24
Figure 4....................................................................................................................................25
Figure 5....................................................................................................................................26
Figure 6....................................................................................................................................27
Figure 7....................................................................................................................................28
Figure 8....................................................................................................................................31
Figure 9....................................................................................................................................33

Introduction
Now days, technology is rapidly growing. Therefore, humans go to update for the new
technology. In this case we are going to find a solution to human problems. This hotel system
wants for computerized. The manager of Meda Midula he wants to apply hotel reservation
system to their hotel instead their computerized reservation system.
The computerized reservation system of Meda Midula does when customer go to the website
and search what kind of available room in this hotel and the system answered for the
customer queries and is there any available room this online booking room get customer
details. Any time customer can cancel online.
This organization need to be traveling from hotel to specialty that is their vision. They are
wanting their works makes very efficiently and fast and increase their customer base. The
organization mission is their services serve to customer. They are trying to quick service
given for the customers. And goal is their customer base developed and offer good services
for the customer. Due to these factors, they need a computerized system.

Task 1
1.0 Software Development Life Cycle
Figure 1
Software development life cycle is the application of standard business practices to building
software applications. It's typically divided into six to eight steps.
 Planning
 Requirements
 Design
 Build
 Document
 Test
 Deploy
 Maintain
Some project managers will combine, split or omit steps, Depending on the project's scope.
These are the core components recommended for all software development project.

Figure 2
1.1 Advantages and Disadvantages
Advantages Disadvantages
User friendly and that any of the
members can see the report and status
of the company. Customer attraction is
in a satisfactory level.
Database should protect hackers and
virus.
Backup plans also available. At the beginning little bit confused
operators.
Operations wise it more effective. Cost high for software and security
system.
Table 1
maintenance
requirement
gathering & analysis
Design
Implementation &
coding
Testing
deployement

Stage 1: Planning and Requirement Analysis
Planning for the quality assurance requirements and identification of the risks associated with
the project is also done in the planning stage. The outcome of the feasibility study is to define
the various technical approaches that can be followed to implement the project successful
with minimum risks.
Stage 2: Defining Requirements
Once the requirement analysis is done the next step is to clearly define and document the
product requirement and get them approved from the customer or the market analysts. This is
done the through SRS (Software Requirement Specification) document which consists of all
the product requirements to be designed and develop during project life cycle.
Stage 3: Designing and Product Architecture
This DDS is reviewed by all the important stakeholders and based on various parameters as
risk assessment, product robustness, design modularity, budget and time constraints, the best
design approach is selected for the product.
A design approach clearly defines all the architectural modules of the product along with its
communication and data flow representation with the external and third-party module (If
any).
Stage 4: Building or Developing the Product
In this stage of SDLC the actual development starts and the product is built. Developers must
follow the coding guidelines defined by their organization and programing tools like
compilers, interpreters, debuggers, etc. are used to generate the code. Different high level
programing languages such as C, C++, Pascal, Java and PHP are used for coding.
Stage 5: Testing and Product
The testing activities are mostly involved in all the stages of SDLC. However, this stage
refers to the testing only stage of the product where defects are reported, tracked, fixed and
retested, until the product reaches the quality standards defined in the SRS.
Stage 6: Deployment in the Market and Maintenance
Sometimes product deployment happens in stages as per the business strategy of that
organization. The product may first be released in a limited segment and tested in the real
business environment (UAT- User Acceptance Testing). Then based on the feedback, the
product may be released as it is or with suggested enhancements in the targeting market
segment. After the product is released in the market, its maintenance is done for the existing
customer base.

1.2 Waterfall Model
This is the first process model introduce and widely followed in software engineering. Here
the process flow in largely in one direction through the phases. To use waterfall model
requirements are very well documented, clear and fixed. Firstly, the requirement gathering
needs to be done. The requirement gathering and the feasibility report is done in the
previously.
Figure 3

1.3 Feasibility Study
Any new project should implement and based on as an operational part of their current
system. This Hotel switched to a new system it should analysis through the operation of
earlier system. This entire document is consisted with Hotel Reservation System. Feasibility
study provides the process for this analysis.
A feasibility study is defined as an estimate or analysis of the possible impact of a proposed
system. In the other hand this can say whether decision makers can implement the project
according to customer’s requirements or not. The feasibility study will include wide data
associated to financial and operational impact. It also consisted with advantages of new
system and draw backs of current system.
1.4 Proposed Hotel Reservation System
This proposed system has frond end and back end.
Figure 4
These are the most basic functionalities that appear in front end.
Figure 5
These are the basic functions that include in back end system.
Frond End
Check In
Date
Check Out
Date Rooms
Back
end(Reservation
Staff)
Arrival List Availability Follow Up
Report

2.2 Hotel Reservation System
The primary proposed of the Entity Relationship Diagram is to represent data object and their
relationship.
Figure 6

Task 2
2.1 ER Diagram
Figure 7

2.2 Data Dictionary
2.2.1 Employee Table
Field Name Data Type Field Length Constrain Description
Employee ID Int 12 Primary Key Unique Identify
Employee
ID NO Int 12 NOT NULL Unique Identify
Employee
Name Varchar 50 NULL Name of the
Employee
Address Varchar 50 NULL Address of the
Employee
DOB Int 10 NULL Birthday of the
Employee
Phone Number Int 10 NOT NULL Contact Number
Department Name Varchar 20 NOT NULL Department of the
Employee
Job Title Varchar 20 NOT NULL Job of the
Employee
Table 2
2.2.2 Customer Table
Field Name Data Type Field Length Constrain Description
Customer ID Int 10 Primary key Unique Identify
Customer
Name Varchar 50 NOT NULL Name of the
Customer
Address Varchar 50 NOT NULL Address of the
Customer
Country Varchar 20 NULL Live in the
Country
Postcode Int 10 NULL Address Postcode
Passport No Varchar 20 NOT NULL Passport Number
of Customer
Phone No Int 10 NOT NULL Contact Number
Email Address Varchar 20 NULL Email address of
the Customer
Table 3
2.2.3 Booking Table
Field Name Data Type Field Length Constrain Description
Booking No Int 10 Primary Key Hotel Booking
Code
No of Date Int 10 NOT NULL Booking Room
Date
No of Guest Varchar 10 NOT NULL Name of the
Customer
Checkout Varchar 50 NULL
Check in Varchar 50 NULL
No of Room Varchar 10 NOT NULL Room No
Room Type Varchar 20 NOT NULL Room Type in
Hotel

Table 4
2.2.4 Room Type Table
Field Name Data Type Field Length Constrain Description
Room No Int 10 Primary Key Booking No of
Hotel Room
Single Varchar 10 NOT NULL
Double Varchar 10 NOT NULL
Suite Varchar 10 NOT NULL
Table 5
2.2.5 Room Table
Field Name Data Type Field Length Constrain Description
Name Varchar 50 NOT NULL Name of the
Customer
Address Varchar 50 NULL Address of the
Customer
Room Type Varchar 10 NOT NULL Room Type
Room No Varchar 10 PRIMARY KEY Booking No of
the Room
Table 6
2.2.6 System Admin Table
Field Name Data Type Field Length Constrain Description
Employee ID Int 10 PRIMARY KEY ID of the
Employee
Department Name Varchar 20 NOT NULL Name of the
Department
Table 7
2.2.7 Receptionist Table
Field Name Data Type Field Length Constrain Description
Employee ID Int 10 PRIMARY KEY ID of the
Employee
Department Name Varchar 20 NOT NULL Name of the
Department
Table 8
2.2.8 Invoice Table
Field Name Data Type Field Length Constrain Description
Room ID Int 10 NOT NULL Booking No of
the Room
Customer ID Int 12 PRIMARY KEY ID of the
Customer
Invoice NO Int 10 NOT NULL Invoice NO
Payment Date Int 10 NOT NULL Payment Date of
Booking
Table 9

Task 3
3.1 Data Flow Diagram (DFD)
Figure 8
3.1.1 Data Dictionary
3.1.1.1 Receptionist Table
Field Name Data Type Field Length Constrain Description
Customer ID Int 10 PRIMARY KEY Id of the
Customer
Customer Name Varchar 50 NOT NULL Name of the
Customer
Room No Int 10 NOT NULL Booking Room,
No
Room Type Varchar 10 NOT NULL Room Type
Payment Method Varchar 10 NULL Payment Method
in Bank
Invoice No Int 10 NOT NULL Payment Receipt
No
Payment Date Int 10 NULL Payment Date
Table 10
3.1.1.2 Manager Table
Field Name Data Type Field Length Constrain Description
Customer ID Int 10 PRIMARY KEY Id of the
Customer
Invoice No Int 10 NOT NULL Payment Receipt
No
Table 11

3.2 Unified Modeling Language (UML)
3.2.1 Use Case Diagram
Figure 9

SCOPE
Utmost care and back-up procedures must be established to ensure 100% successful
implementation of the computerized hotel system. In case of system failure, the organization
should be in a position to process the transaction with another organization or if the worst
comes to the worst.
Now a day’s hotel is providing many other facilities, this project can also be improved with
the improvement in the Hotels.
Utmost care and back-up procedures must be established to ensure 100% successful
implementation of the computerized banking system. In case of system failure, the
organization should be in a position to process the transaction with another organization or if
the worst comes to the worst
CONCLUSION
The system is having some benefits for customers too. In home page customers can put their
email address or phone number for contact hotel the booking on their phone. Besides,
customers can also book online without registering into the system. Again, customers no need
to worry for payment. But for reservation they need to key in their credit card details for
verification purposes. It will not charge them promptly. So, overall, this system will give the
customers a better user-friendly environment to book contact hotel.
GANTT CHART
Task 1
Task 2
Task 3
24-Jan 29-Jan 3-Feb 8-Feb 13-Feb 18-Feb 23-Feb 28-Feb 5-Mar 10-Mar 15-Mar
GANTT CHART
Days to Complete Start Date

REFERENCE
Jevtic, G. (2021, February 10). What is SDLC? Phases of Software Development, Models, &
Best Practices. PhoenixNAP Blog. https://phoenixnap.com/blog/software-
development-life-cycle#:%7E:text=Software%20Development%20Life%20Cycle
%20is,%2C%20Test%2C%20Deploy%2C%20Maintain.
Rungta, K. (2021, March 8). What is Waterfall Model in SDLC? Advantages &
Disadvantages. Guru99. https://www.guru99.com/what-is-sdlc-or-waterfall-
model.html
SDLC - Quick Guide - Tutorialspoint. (2010). Tutorialspoint.
https://www.tutorialspoint.com/sdlc/sdlc_quick_guide.htm#:%7E:text=Software
%20Development%20Life%20Cycle%20(SDLC,and%20test%20high%20quality
%20softwares.&text=It%20is%20also%20called%20as,in%20the%20software
%20development%20process.