Professional Documents
Culture Documents
Submitted By
ANAKHA THOMAS T
Reg. No: 180021093331
2018-2021
CERTIFICATE
This is to certify that this Project work entitled “ONLINE HOTEL
MANAGEMENT SYSTEM” is a bonafide report of the mini project
done by Ms. ANAKHA THOMAS T (Reg.No:180021093331) under the
guidance of Mr. SHAN AUGUSTINE, M.Sc. CS., during the academic
year 2018-2021 for the partial fulfillment for the award of the Degree of
Bachelor of Computer Applications (BCA) from Mahatma Gandhi
University, Kottayam.
Place: Ramapuram
Date:
DECLARATION
Date:
ACKNOWLEDGEMENT
ANAKHA THOMAS T
CONTENTS
INTRODUCTION ................................................................................... 3
GENERAL INTRODUCTION .............................................................. 4
SOFTWARE INTRODUCTION ........................................................... 5
SYNOPSIS ............................................................................................. 6
SOFTWARE SPECIFICATION ............................................................ 6
SYSTEM STUDY .................................................................................... 7
SYSTEM STUDY .................................................................................. 8
EXISTING SYSTEM ............................................................................. 9
PROPOSED SYSTEM ......................................................................... 10
SYSTEM ANALYSIS ........................................................................... 11
FEASIBILITY STUDY ........................................................................ 12
TECHNICAL FEASIBILITY .............................................................. 13
ECONOMIC FEASIBILITY ................................................................ 13
BEHAVIORAL FEASIBILITY ........................................................... 14
OPERATIONAL FEASIBILITY ......................................................... 14
REQUIREMENT SPECIFICATION ................................................... 14
SYSTEM REQUIREMENTS ............................................................... 15
HARDWARE REQUIREMENTS ....................................................... 15
SOFTWARE REQUIREMENT ........................................................... 15
INTRODUCTION TO FRONTEND ANDBACKEND ...................... 15
PHP: HYPERTEXT PREPROCESSOR .............................................. 15
MySQL ................................................................................................. 16
WAMPSERVER................................................................................... 18
SQL CONSTRAINTS .......................................................................... 19
SYSTEM DESIGN ................................................................................ 20
INPUT DESIGN ................................................................................... 21
OUTPUT DESIGN ............................................................................... 22
DATABASE DESIGN ......................................................................... 23
NORMALIZATION ............................................................................. 24
THE NORMAL FORMS ...................................................................... 25
TABLES ............................................................................................... 27
DATA FLOW DIAGRAM ................................................................... 34
PROCESS ............................................................................................. 35
DATA STORE...................................................................................... 35
DATA FLOWS ..................................................................................... 35
EXTERNAL ENTITY .......................................................................... 35
LEVEL 0 DFD ...................................................................................... 37
LEVEL 1 DFD FOR USER .................................................................. 37
LEVEL 1 DFD FOR ADMIN .............................................................. 38
SYSTEM TESTING.............................................................................. 40
TESTING PROCEDURES ................................................................... 41
TESTING METHODOLOGIES .......................................................... 42
UNIT TESTING ................................................................................... 42
INTEGRATION TESTING ................................................................. 43
SYSTEM TESTING ............................................................................. 43
VALIDATION TESTING .................................................................... 44
SYSTEM IMPLEMENTATION ......................................................... 45
SYSTEM IMPLEMENTATION .......................................................... 46
CONVERSION..................................................................................... 46
USER TRAINING ................................................................................ 46
SYSTEM MAINTENANCE ................................................................ 47
SECURITY ........................................................................................... 47
BACK UP ............................................................................................. 47
DOCUMENTING THE SYSTEM ....................................................... 47
FUTURE SCOPE OF THE PROJECT ................................................ 49
CONCLUSION ...................................................................................... 50
BIBLIOGRAPHY ................................................................................. 52
APPENDIX ............................................................................................ 53
INTRODUCTION
INTRODUCTION
GENERAL INTRODUCTION
Accuracy
Storage
Speed of Response
Versatility
Diligence
Shoppers and traders are quickly changing the mode of operation from
the present way. The shopping can be done in a pretty fast and easier manner
than the usual operation.
SOFTWARE INTRODUCTION
SYNOPSIS
SOFTWARE SPECIFICATION
SYSTEM STUDY
SYSTEM STUDY
RECORD REVIEW:
Many kinds of records and reports can provide analysis with valuable
information about organizations and operations. In record reviews, analysts
examine information that has been recorded about the system and users.
Records include written policy manuals, regulations and standard operating
procedures used by most organization as a guide for managers and
employees.
OBSERVATION:
INTERVIEW:
EXISTING SYSTEM
It is highly time-consuming.
Accuracy is missing.
PROPOSED SYSTEM
ADVANTAGES
Listing of items.
SYSTEM ANALYSIS
SYSTEM ANALYSIS
INTRODUCTION
Because of these reasons the existing system needs a change, for the
easy and smooth running of the system.
FEASIBILITY STUDY
All projects are feasible given unlimited and resource and infinite
time. Unfortunately, the development of computer-based system is more
likely to be plagued by scarcity of resources and difficult delivery dates. The
main objective of feasible study is to test the technical, social and economical
feasibility of developing a computer system. This is done by investigating the
existing system in the area under investigation or generally ideas about a new
system. The proposed system was evaluated from a technical viewpoint first.
Being technically feasible, its impact on the organization was assessed. After
the proposed system was found to be social and technically acceptable, it was
tested for economic feasibility.
TECHNICAL FEASIBILITY
Development Risk
Resource Availability
Technology.
ECONOMIC FEASIBILITY
2. The cost of hardware and software for the class of application of the
project being considered.
BEHAVIORAL FEASIBILITY
OPERATIONAL FEASIBILITY
The system is operationally feasible as it very easy for the End users
to operate it. It only needs basic information about Windows platform.
REQUIREMENT SPECIFICATION
SYSTEM REQUIREMENTS
HARDWARE REQUIREMENTS
RAM : 1 GB or more
Monitor : VGA/SVGA
Keyboard : 104keys
Printer : Dot-matrix
SOFTWARE REQUIREMENT
sampled) and 2.1 million web servers. Originally created by Rasmus Lerdorf
in 1994, the reference implementation of PHP is now produced by The PHP
Group. While PHP originally stood for Personal Home Page, it now stands
for PHP: Hypertext Pre-processor, a recursive acronym.
PHP code can be simply mixed with HTML code, or it can be used in
combination with various templating engines and web frameworks. PHP
code is usually processed by a PHP interpreter, which is usually implemented
as a web server's native module or a Common Gateway Interface (CGI)
executable. After the PHP code is interpreted and executed, the web server
sends resulting output to its client, usually in form of a part of the generated
web page - for example, PHP code can generate a web page's HTML code,
an image, or some other data. PHP has also evolved to include a command-
line interface (CLI) capability and can be used in standalone graphical
applications.
PHP is free software released under the PHP License. PHP has been
widely ported and can be deployed on most web servers on almost every
operating system and platform, free of charge.
MySQL
The logical model, with objects such as databases, tables, views, rows,
and columns, offers a flexible programming environment. You set up rules
governing the relationships between different data fields, such as one-to- one,
one-to-many, unique, required or optional, and―pointers ‖between different
tables. The database enforces these rules, so that with a well-designed
database, your application never sees inconsistent, duplicate, orphan, out-of-
date, or missing data.
(for example, to generate reports), embed SQL statements into code written
in another language, or use a language-specific API that hides the SQL
syntax. SQL is defined by the ANSI/ISO SQL Standard. The SQL standard
has been evolving since 1986 and several versions exist.
The MySQL Database Server is very fast, reliable, scalable, and easy
to use. If that is what you are looking for, you should give it a try. MySQL
Server can run comfortably on a desktop or laptop, alongside your other
applications, web servers, and so on, requiring little or no attention. If you
dedicate an entire machine to MySQL, you can adjust the settings to take
advantage of all the memory, CPU power, and I/O capacity available.
WAMPSERVER
SQL CONSTRAINTS
You can place constraints to limit the type of data that can go into a
table. Such constraints can be specified when the table when the table is first
created via the CREATE TABLE statement, or after the table is already
created via the ALTER TABLE statement.
SYSTEM DESIGN
SYSTEM DESIGN
INPUT DESIGN
Input design features can ensure the reliability of the system and also
determines how efficiently the user can interact with the system. A good input
screen is clear and free from irrelevant information. Entered data has to be
checked for their accuracy and detection of errors. All the data entry screens
should be of interactive nature that user can directly input data according to
prompt messages. The input design determines whether the user can interact
directly with the computer.
All the input screens used here have script validations for null
checking and data types whereas required. All the programs inserting data to
the table checks the length of the values in addition to the data type
verification. They also prompt the entry of values in mandatory fields.
The goal of designing input data is to make it free from logical errors.
The input data is also used for easy calculation of necessary functions.
Different forms are used for data screens in order to input data into the
system. The screen formats have options like add, delete, edit and update with
buttons, which is used for easy input and retrieving information. All the fields
are validated. If the user enters invalid data, appropriate messages are
displayed.
Effectiveness Accuracy
Simplicity
Attractiveness
OUTPUT DESIGN
One of the most important features of the system for users is the output
it produces. Output design should improve the system relationship with the
user it produces and helps in decision making. Considering the future use of
the output required and depending on the nature, they are displayed on the
monitor for immediate need or obtaining the hardcopy.
The CRT displays can include a title, column heading, detailed data
totals; they must be described in detailed for programmers. In the case of
CRT displays layout design the area is limited by the size of the screen as the
amount of data that can displayed in the record.
Booking details
Feedback
Customer details
DATABASE DESIGN
Data Integration
Data Abstraction
Data Independence
of table design. The major aim of the process normalization is to reduce data
redundancy and prevent losing data integrity. Redundancy refers to unwanted
and unnecessary repetition of data. Data integrity has to be converted at all
levels. Poor normalization can access problem related to storage and retrieval
of data. During the process of normalization, dependencies can be identified
which cause serious problem during deletion and updating. Normalizing also
helps in simplifying the structure of tables.
NORMALIZATION
Benefits:
2. Improve performance
3. Query optimization
5. Index improvement
First normal form (1NF) sets the very basic rules for an organized
database:
Create separate tables for each group of related data and identify
each row with a unique column or set of columns (the primary key).
Remove columns that are not dependent upon the primary key.
The Boyce-Codd Normal Form also referred to as the "third and half
(3.5) normal form", adds one more requirement:
RULES OF NORMALIZATION
Rule 2: A field should have the same meaning in each row of the table.
Rule 3: Each table should represent at most one entity.
TABLES
TYPE
NAME
user
number
serial number
room number
number
address
whether there is
child
user is adult
date
date
PROCESS
Process shows in the work of the system. Each process has one or more
data inputs and produces one or more data outputs. Process are represented
by rounded rectangles in DFD. Each process has unique name and number
appears inside the rectangle that represents the process in a data flow
diagram.
DATA STORE
DATA FLOWS
Data flows show the passage of data in the system and are represented
by lines joining system components. An arrow indicates the direction of flow
and the line is labeled by name of the data flow.
EXTERNAL ENTITY
External entities are outside the system but they either supply input
data into the system or use other system output. They are entities on which
the designer has control. They may be an organization customer or other with
which the system interacts. It supply data into the system called source.
External entities that use the system data are sometimes called sinks. These
are represented by rectangles in DFD.
1. Process should be named and numbered for easy reference. Each name
should be representative of the process.
3. When a process is exploded into lower level details they are numbered.
LEVEL 0 DFD
ONLINE
HOTEL
ADMIN USER
MANAGEM
ENT
SYSTEM TESTING
SYSTEM TESTING
TESTING PROCEDURES
A good test case is one that has a high probability of finding an as- yet
undiscovered errors. A successful test is one such uncovers or finds such
errors. If testing is conducted successfully; it will uncover errors in the
software. It also demonstrates that software functions are being performed
according to specification and also behavioral and performance requirements
are satisfied. For this, test plans have to be prepared. The implementation of
a computer system requires that test data has to be prepared and that the book
stall management system as well as its elements is being tested in a planned
TESTING METHODOLOGIES
UNIT TESTING
In unit testing the analyst tests the programs making up a system. Unit
testing gives stress on the modules independently of one another, to find
errors. This helps the tester in detecting errors in coding and logic that are
contained within that module alone. The errors resulting from the interaction
between modules are initially avoided. Unit testing can be performed from
the bottom up, starting with smallest and lowest-level modules and
proceeding one at a time. For each module in bottom-up testing a short
program is used to execute the module and provides the needed data, so that
the module is asked to perform the way it will when embedded within the
larger system.
Unit testing deals with testing a unit as a whole. This would test the
interaction of many functions but confine the test within one unit.
when this environment is established can a correct evaluation of the test take
place. The scaffolding software may establish state and values for data
structures as well as providing dummy external functions for the test.
Different scaffolding software may be needed from one test to another test.
Scaffolding software rarely is considered part of the system. Sometimes the
scaffolding software becomes larger than the system software being tested.
Usually the scaffolding software is not of the same quality as the system
software and frequently is quite fragile. A small change in the test may lead
to much larger changes in the scaffolding.
INTEGRATION TESTING
This testing level can be simply defined as integrating and then testing.
i.e., here, many unit tested modules are combined into subsystems, which are
then tested. Integration testing aims at whether the modules can be integrated
properly. Hence, the emphasis is on testing interfaces between modules. This
testing activity can be considered testing the design.
Integration testing takes as its input modules that have been unit
tested, groups them in larger aggregates , applies tests defined in an
integration test plan to those aggregates, and delivers as its output the
integrated system ready for system testing. The purpose of integration testing
is to verify functional, performance and reliability requirements placed on
major design items.
SYSTEM TESTING
VALIDATION TESTING
SYSTEM IMPLEMENTATION
AND MAINTENANCE
SYSTEM IMPLEMENTATION
An import aspect of system analyst’s job is to make sure that the new
design is implemented to established standard. Implementation is used here
to mean the process of converting a new or a reversed system design into
operational one. There are three types of implementation,
CONVERSION
USER TRAINING
The analyst must have clear idea about the user’s capacity and
requirement. A well designed system may fail because of the way are
operated and used. So the user must be trained before using the new system
and the quality of the training must be high
SYSTEM MAINTENANCE
SECURITY
BACK UP
Backups for hardware, the data and the system are inevitable factor to
be considered. Data backup represents insurance against actual loss of data
due to equipment malfunction. Program failure or accident. Hence data can
be providing on hard disk or on floppy disk.
After the jobs of testing were completed the whole system as well
documented in clear, Understandable and simple language. This was to
ensure that if any updating has to be performed in the future the users would
not face any difficulties in performing tasks. An acceptance was made to
attain maximum perfection in documentation the software in a simple, precise
and self-explanatory manner. The documentations deal with the system
development with maximum clarity. Each and every process is explained in
details. The various tables used by the system with their fields are provided.
Different types of programs denoting various activities of the system are
included. The testing methods adopted also from a part of the document. The
output generated by the system constitutes another part.
CONCLUSION
CONCLUSION
It is believed that almost all system objectives have being met. A trial
run of the system has been made and is giving good results. The procedure
for processing is simple and regular in order.
For maximum utilization of the system, users should make sure that
all the data entries should be complete. This project work is not without
drawbacks even though 'it is unique in its nature.
BIBLIOGRAPHY
APPENDIX