Академический Документы
Профессиональный Документы
Культура Документы
CHAPTER 1: INTRODUCTION
Project Introduction
Problem Description
Tools and Technology Used
CHAPTER 6: CODING
Entire System Coding
CHAPTER10: BIBLIOGRAPHY
CHAPTER
Introduction
PROJECT INTRODUCTION
Chapter1
Introduction
Hotel Management System was designed with only a single driving idea in mind
- Make it easy, make it fast and make it highly customizable to suite our customers'
requirements.
Our initiative required us to be seamless and structured in delivery, while at the same
time we had to be flexible in our offering to our clients. We smoothly integrated our
fluid management system with our base software so that we could deliver the final
product exactly like you want it, and at the price you want it to be.
The project will have the following distinctive area for development-Front End (Microsoft Visual Basic 6.0)
-Back End (Microsoft Access 2003)
There need to addition of a table and a store procedure to implement the
personalization feature.
HARDWARE REQUIREMENTS:
Processor
Memory
: 512 MB RAM
Hard Disk
Printer
Mouse
:Optical Mouse
CD/RW
: DVD-RW
Keyboard
: Multimedia
SOFTWARE REQUIREMENTS:
5
Component
Operating System
Windows
Back-end-tool
CHAPTER
SYSTEM STUDY
Chapter2
System Study
for the single hotel but for all that are still using manual system and want a change in
system. It is very user friendly and easy to use system.
In comparison to the present system the proposed system will be less time
consuming and is more efficient.
Analysis will be very easy in proposed system as it is automated
This project intends to introduce more user friendliness in the various activities
such as record updation, maintenance, and searching.
The searching of record has been made quite simple as all the details of the
customer can be obtained by simply keying in the identification of that customer.
The entire information has maintained in the database or Files and whoever
wants to retrieve cant retrieve, only authorization user can retrieve the
necessary information which can be easily be accessible from the file.
The main objective of the entire activity is to automate the process of day to day
activities of Hotel like:
11
1. Room activities,
2. Registration of a New Customer,
3. Assign a room according to customers demand,
4. Checkout and releasing the room
5. Finally compute the bill etc.
This project has some more features:
System Connectivity
No data duplication
No Paper Work Required
Time Efficient
Cost Efficient
Automatic data validation
User friendly environment
Data security and reliability
Fast data insertion & retrieval
Easy performance check
SCOPE:
Scope of this project is very broad in terms of other manual hotel management
system. Few of them are:1. This can be used in hotel/motel as well as in corporate world.
2. It is userfriendly and easy to operate.
12
CHAPTER
FEASIBILITY STUDY
Chapter3
Feasibility Study
13
Feasibility Study:
Feasibility is the determination of whether or not a project is worth doing. The
process followed in making this determination is called feasibility study. This type of
study determines if a project can and should be taken. Once it has been determined that
a project is feasible, the analyst can go ahead and prepare the project specification
which finalizes project requirement.
Normally feasibility studies culminate in a written or oral feasibility report. The
contents and recommendations of such a study will be used as a sound basis for
deciding whether to proceed, postponed or cancel the project. Thus since the feasibility
study may lead to the commitment of large resources, it becomes necessary that it
should be conducted competently and that no fundamental errors of judgment are made.
In the conduct of feasibility study, the analyst will usually consider six distinct but
interrelated types of feasibility. They are: -
14
15
Is there sufficient support for the project for management? From users?
Will the system be used and work properly if it is being developed and
implemented?
Will there be any resistance from the users that will undermine the possible
Application benefits?
16
CHAPTER
SYSTEM ANALYSIS
17
Chapter4
System Analysis
Introductions
E-R Diagram
Data Dictionary
18
4.1 ER Diagram:
An entity-relationship (ER) diagram is a specialized graphic that illustrates the
interrelationships between entities in a database. Entity-relationship model is a data
modelling method used to model a system and its requirements in a top down approach.
This approach is commonly used in Database design. The diagrams created using this
method are called ER diagrams.
An entity-relationship model (ERM) is a representation of structured data;
entity-relationship modeling is the process of generating these models. The endproduct of the modeling process is an entity-relationship diagram (ERD) or ER
diagram, a type of conceptual data model or semantic data model. The first stage of
information system design uses these models during the requirements analysis to
describe information needs or the type of information that is to be stored in a database.
The data modeling technique can be used to describe any ontology (i.e. an overview and
classifications of used terms and their relationships) for a certain universe of discourse
(i.e. area of interest). In the case of the design of an information system that is based on
a database, the conceptual data model is, at a later stage (usually called logical design),
mapped to a logical data model, such as the relational model; this in turn is mapped to a
physical model during physical design.
ER diagrams often use symbols to represent three different types of information.
Boxes are commonly used to represent entities. Diamonds are normally used to
represent relationships and ovals are used to represent attributes. The symbols used in
the E-R diagram have its own meanings. They are given below:
Symbol
Meaning
19
Entity
Relation
Weak Entity
Attribute
Key Attribute
20
21
customer-id
c-name
date-of-deparature
room-no
room-type
purpose
city
room-charge
bill-no
age
room-no
state
country
22
check-out
rent
status floor
days
book
rent
BILLING
Check-date
customer-id
total-room-chg
date-of-arrival
address
rcv-amnt
gender
CUSTOMER
image
total-rent
M
people
advanced
booked
23
Extra-charge
1
ROOM
room-type
room-no
floor
bubble with input and output data indicated by incoming and outgoing arrows
respectively. Additional processes and information flow paths are represented as the
Level-0 is partitioned to reveal more details
3. Data Flow:The flow of the data is denoted by the arrows. The arrowhead indicates
the direction of flow of data.
25
4. Data Store:A repository of data that is to be stored for use by one or more processes
may be simple buffer or sophisticated database. The following shape denotes it-
Context Diagram
In this model we show the whole system in single process. It shows all the
external entities that interact with the system data flow between these external entities
and the system. It is a top level diagram. It contains a single process. Expanding the
context diagram we get the Data Flow Diagram for the system.
USER
26
Hotel Management
System
(Process 0)
Administrator
1.0
User Login Process
27
Login
details
login_tabl
2.0
Availability Check
process
Accept Customer
Roo
m
Room booked
3.0
Customer
Registration
Process
4.0
Get Cash Memo
Check Room
details
Store Customer
Check Room
Entry
Billing Process
custom
Cleared Room
Billing
Store the Bill
Details
2. 1 LEVEL DFD
4.3: Data Dictionary
It is a structured place to keep details of the contents of data flows, processes and
data store, a data dictionary is a structured respiratory of data about data. It is a set
of rigorous definition of all data elements and data structures used in the candidate
28
system and serves as a valuable document to the organization at the time of future
enhancement and data warehousings.
There are three classes of items to be defined in the data dictionary.
1.
Data Element
The smallest unit of data that provides for no further decomposition is
called data element.
2.
Data Structures
It consists of a group of data elements handled as a unit.
3.
Data Type
Size
Source Table
1.
user name
Text
10
login_table
2.
password
Text
login_table
3.
customer_id
Text
255
customer
4.
c_name
Text
255
customer
5.
address
Text
255
customer
6.
City
Text
255
customer
7.
State
Text
255
customer
8.
country
Text
255
customer
9.
Gender
Text
255
customer
10.
Age
Number
Long Integer
customer
29
11.
purpose
Text
255
customer
12.
date_of_arrival
Date/Time
13.
People
Number
255
customer
14.
Days
Number
Long Integer
customer
15.
date_of_diperatur
e
Date/Time
16.
room_type
Text
255
customer
17.
room_no
Number
Long Integer
customer
18.
floor
Number
Long Integer
customer
19.
rent
Currency
customer
20.
total_rent
Currency
customer
21.
advanced
Currency
customer
22.
image
Text
23.
status
Yes/No
24.
room_no
Number
Long Integer
Room
25.
room_type
Text
255
Room
26.
floor
Number
Long Integer
Room
27.
rent
Number
Long Integer
Room
28.
book
Yes/No
29.
bill_no
Text
255
Billing
30.
customer_id
Text
255
Billing
31.
room_no
Text
255
Billing
32.
room_charge
Currency
Billing
33.
Extra_charge
Currency
Billing
customer
customer
255
customer
customer
Room
30
34.
total_room_chg
Currency
Billing
35.
CheckDate
Date/Time
Billing
36.
rcv_amnt
Currency
Billing
37.
customer_id
Text
255
CHAPTER
SYSTEM DESIGN
SYSTEM DESIGN
31
Billing
32
Chapter5
System Design
5.1 Introduction:
System design is the solution of a how to approach to the creation of the new
system. It is composed of several steps. It facilitates the understanding and provides the
procedural details necessary for implementation of the system recommended in the
feasibility study. Emphasis is given on translating the performance requirements into
design specification. Design goes through logical and physical stages of development.
Logical design reviews the present physical system; prepares input and output
specification;
make
editing;
security
and
control
specification;
details
the
33
The database tables that are used in Hotel Management System are
shown below:
34
login_table:
Field name
user name
Datatype
Text
Size
10
password
Text
Key
Primary key
customer:
Field name
Datatype
Size
customer_id
Text
255
c_name
Text
255
address
Text
255
city
Text
255
35
Key
Primary key
state
Text
255
country
Text
255
gender
Text
255
age
Number
Long Integer
purpose
Text
255
date_of_arriva
l
Date/Time
people
Number
255
days
Number
Long Integer
date_of_diper
ature
Date/Time
room_type
Text
255
room_no
Number
Long Integer
floor
Number
Long Integer
rent
Currency
total_rent
Currency
advanced
Currency
image
Text
status
Yes/No
255
Room:
36
Foreign key
Field name
Datatype
Size
room_no
Number
Long Integer
room_type
Text
255
floor
Number
Long Integer
rent
Number
Long Integer
book
Yes/No
Key
Primary key
Billing:
Field name
Datatype
bill_no
Text
Size
255
customer_id
Text
255
room_no
Text
255
room_charge
Currency
Extra_charge
Currency
total_room_c
hg
Currency
CheckDate
Date/Time
rcv_amnt
Currency
Key
Primary key
Foreign key
5.2 Normalization:
Where the 1NF deals with redundancy of data across a horizontal row, second
normal form deals with redundancy of data in vertical columns. As stated earlier, the
normal forms are progressive, so to achieve 2NF, tables must already be in 1NF and
there must be a primary key in each table.
In our case database has been normalized in 2NF, since there is primary key in
every table upon which other key is dependant.
38
In 3NF we are looking for data in our tables that is not fully dependant on
primary key, but dependant on other value in the table. In other words there must not be
any transitive dependency in out tables.
39
CHAPTER
CODING
40
Chapter6
Coding
BASIC DEFINITION
The code generation step performs the translation of design into a machine
understandable form. The detail of the design is accomplished mechanistically by the
code generation.
To reduce input, control errors code designers are used. The code also
redesigned to accelerate the entire process.
EVALUATION
Following are the various types of CODES used in the proposed system
describe in details.
Functional Code: This method is used from different types of the functions to
display the call details information with regard to telephone dialler, and their refilling
41
data could be accessed with the help of dropdown list box prepared. Similarly program
details, circular details, research details and seminar details are also displayed.
Sequence Code: In this method, display of program information and whether
that particular program will be conducted in a particular month or not is generated in
sequential order.Similarly circular information, research information, and seminar
information are also generated in sequential order.
Mnemonic Code: This method is used for combination of defined numbers,
letters or numbers and letters for the generation of the code. This code is useful for the
generation of true and false in the case, whether the particular program has the same
specific facility or not. Same is with the case of computer program. So we can see the
utilization of the mnemonic code in the coding stage for the decision making purpose.
Code efficiency:
Code efficiency is one of the major tasks in the system
development life cycle. It checks whether the access tie is minimized or not, whether the
errors are eliminated or not, whether the data integrity is maintained or not etc. To
enhance the efficiency of the system, drop down list and menus are prepared so that the
user would have the options to select the options he feels suitable.
Code Optimization:
Code that is generated by optimizing run faster than code that is
not optimized. Thus the higher the level of optimization, the faster the code should
execute.
One optimization techniques is the recognition of the common
sub expressions. Optimization is also possible by examining the loop for more common
sub expression compute only once before the loop begins.
Loop unrolling is another optimization technique. By repeating
the body of the loop several times within that loop the number of iterations needed for
the loop is divided by the number of the body repetitions. It reduces the loop overhead.
One of the important tasks in Software development life cycle is
code optimization. It supplements the efficiency of the coding and is the penultimate
stage of the removal of any data redundancy and unnecessary occupation of the space.
42
CHAPTER
SYSTEM TESTING
43
Chapter7
System Testing
TESTING
In the testing process the Demo version if the software i.e. actual replica of the
existing system will be installed so that the users can use it as they like and give their
valuable suggestion and advice. There after security can be incorporated in the system.
In this phase we will be using both alpha and beta test, which will enable the system to
check the whole system thoroughly. The said demo version software can be used for a
period of 15 days to 1 month and during this period only training of the proposed
software will be imported. This phase will allow the entire user to use the system in a
much more efficient way.
44
The design tests for software and other engineered products can be as
challenging as the initial design of the product itself. The objectives of the testing are
the findings of errors with a minimum amount of time and effort.
1. Knowing the specified function that a product has been designed to perform,
tests can be conducted that demonstrate each function is fully operational while
at the same time searching for errors in each functions.
2. Knowing the internal workings of a product, tests can be conducted to ensure
that all gears mesh that is, internal operation are performed according to
specifications and all internal components have been adequately exercised.
45
assumption
and
logical
errors
are
inversely
46
The Alpha test is conducted at the developers site by a user. The software is used in a
natural setting with the developer looking over the shoulder of the user and recording
errors and usage problems. Alpha tests are conducted in a controlled environment.
The beta test is conducted at one or more user sites by the end-user of the software.
Unlike the alpha testing, the developer is generally not present. Therefore, the beta test
is alive application of the software in an environment that cannot be controlled by the
developer. As a result of problems reported during beta tests, software engineers make
modifications and then prepare for release of the software product to the entire customer
base.
Acceptance testing is running the system with live data by the actual user.
Acceptance testing is technically similar to system testing but politically it is different.
In system testing, bugs are found and corrected with no one watching. Acceptance
testing is conducted in the presence of user, audit representatives, or the entire staff.
Actually system testing is considered as the dress rehearsal of the acceptance testing. In
our project we have done both system as well as acceptance testing by entering real time
data in the human resource management system in the presence of the user and the
output reports are generated after the data entry is done in the required format. The users
are very much satisfied by the reports generated by the software. Some errors are found
during alpha & beta testing and sequentially they are rectified and finally at last during
acceptance testing the software is error free.
Security Testing
Security testing means to protect the system from improper penetration. During
security testing the tester plays the role of the individual who desire to penetrate the
system. Security testing means to protect the system from improper penetration.
The tester may attempt to acquire passwords through external means, may attack
the system with user software designed to breakdown any defences that have been
constructed, may overwhelm the system thereby designing service to others, may
purposely cause system errors.
Some of the security measures I have used in my software are as follows:
47
Validation Testing
Software validation is achieved through a series of black box tests that
demonstrates conformity with requirements. A test plan outlines the classes of tests
to be conducted and a test procedure defines specific test cases that will be used to
demonstrate conformity with requirements. The end user of the software, staff of
dark system performs the validation test. Validation test is succeeded when the
expectation of user is fulfils completely.
A list plan outlines the classes of test to be conducted and a list procedure
defines specific test cases that will be used to demonstrate conformity with
requirements.
Therefore mentioned tests are done to detect errors when the data of the
real system is input. This is very important stage for the developer as this judge
whether his project was developed to meet the requirements or not. After each
successful test, any deficiency reported to the developer is noted down for the
removal in the next stage.
This is conducted to be more important as the users are aware of the
processes inside the system. Proper validation and messages are needed to be
informed the user during each mistake they make. Also necessary help is required to
be given for each time they are confused.
Integration Testing
It is a systematic technique for construction of the program structure while at the
same time conducting test to uncover error associated with interfacing. The
objective is to take unit-tested module and built a program structure that has been
dictated by design.
Unit testing
Unit testing verifies the smallest module of the software designed. Using this
testing the entire module can be debugged very easily. The relative complexity of
48
test and the error detected as a result its limited by the constrained scrap established
for unit testing.
The unit test is always white box oriented and the step can conduct in parallel
for multiple modules.
Unit testing is considered an adjunct to the coding step. After source code has
been developed and verified for the syntax connection, unit test case designed starts.
Output Testing
No system is useful if it does not provide the required output. Asking the user
about the required format must match the output generated by the system under
consideration. This test is also done by matching the required formats with the
output formats obtained by the system and the users are very much satisfied by the
reports generated by the software.
CHAPTER
SCREEN SHOTS
49
Chapter8
Screen Shots
Login Window :
50
Main Window:
51
52
53
54
About :
Data Report:
55
CHAPTER
CONCLUSION
56
Chapter9
Conclusion
CONCLUSION
The main outlook of the software helps the laboratory for giving all necessary
information and accurately keeping the record in a computerized form.
As the existing system is manual one which is not efficient and take more time in
dealing with data, therefore the authorities intended to overcome the drawback and
hence they proposed to design an central process which would be more users friendly.
The solution obtained from the study of the existing system recommends that it is highly
beneficial to have newly computerized system.
LIMITATION
1. High risk of virus attack as the systems are connected to the internet most of the
time.
57
CHAPTER
BIBLIOGRAPHY
58
10
59
Chapter10
Bibliography
Books
60
61