A

PROJECT REPORT ON

“Lodging Management System”

FOR THE FULLFILLMENT OF TY BCA Project

SUBMITTED TO
KBC NORTH MAHARASHTRA UNIVERSITY,
JALGAON
SUBMITTED BY
MR. Abhishek Sanjay Bhavar
UNDER THE GUIDANCE OF
Prof.Piyush Agrawal
SITABAI MANGILAL AGRAWAL CHARITABLE
TRUSTS INTITUTE OF MANAGEMENT
(Dist.Jalgaon)

2021-2022
 Smt. S. M. AGRAWAL CHARITABLE TRUST’S
Smt. S. M. AGRAWAL INTITUTE OF
MANAGEMENT, CHALISGAON, DIST-
JALGAON, 424101-(Maharashtra)

Date:/ /2021

This is to certify that, the Project Titled “Lodging Management

System” a bonafide documentation done by Mr.Abhishek
Sanjay Bhavar TYBCA Sem-6 for the partial fulfillment of BCA
Degree as per norms of KBC North Maharashtra University,
Jalgaon. It was carried out under our supervision. He has
satisfactorily completed his Project.

Guide I/C Director

Prof.Piyush Agrawal Prof.Piyush
Agrawal

Sign of Sign Of
External Examiner1 External Examiner2
Date: - Date:
 SUBHASH RESIDANCY
STATION ROAD, CHALISGAON

Date : / / 2022

CERTIFICATE

This is Certificate That Mr.Abhishek Sanjay Bhavar Studant of

Bachelor of Computer Application from , Smt. S. M. AGRAWAL
INTITUTE OF MANAGEMENT CHALISGAON,has successfully
completed his project work on “ Lodging Management
System” For our organization as per the requirement of the
system.
His performance during the project has been very
satisfactory.
We wish best luck for his future.

For – Subhash Residency

 Acknowledgement
I take great pleasure in submitting this project report on “Lodging
Management System” as a part of the requirements for the Bachlor of Computer
Application Degree, Semester-VI. It is always a difficult task to
acknowledgement all those who have been tremendous us help in an industrial
project of this nature . At the very outset I take this opportunity to express my
deep sense of gratitude to the Head of Department, Mr. Piyush Agrawal, for this
valuable guidance and interest throughout the period of our post-Graduation
study in every possible way.

Completing this project report would not have been possible without the
cordial help extended to me by members of our department, especially
Mr.A.S.Bhavar, I thank all faculty members of Computer Management
Department, for their experience guidance and co-operation during the project.

I have grateful acknowledgement.

Mr.Mushtaque Qureshi
 Index

Sr. No. CHAPTERS

1 Introduction

2 System Analysis

3 System Requirement

4 System Development
5 System Design

6 Database Design

7 Screenshot

8 System Testing

9 Conclusion

10 Bibilography
CHAPTER NO:-1
Introduction
 INTRODUCTION
My project title is Lodging Management System. I have tried my best to make
the complicated process of Lodging Management System as simple as possible
using Structured & Modular technique & Menu oriented interface. I have tried to
design the Project in such a way that user may not have any difficulty in using
this package & further expansion is possible without much effort. Even though I
cannot claim that this work to be entirely exhaustive, the main purpose of my
exercise is perform each Employee’s activity in computerized way rather than
manually which is time consuming
I am confident that this software package can be readily used by non-
programming personal avoiding human handled chance of error. This project is
used by two types of users

• Administrator (management of the Lodging).

Online users can see the required articles or news

Administrator can maintain daily updates in the lodging records.

Administrator is must be an authorized user. He can further change the password.
There is the facility for password recovery, logout etc.

The main aim of the entire activity is to automate the process of day to day
activities of Lodging like Room activities, Admission of a New Customer, Assign
a room according to customer’s demand, checkout of a computer and releasing
the room and finally compute the bill etc.

The limited time and resources have restricted us to incorporate, in this

project, only a main activities that are performed in a Lodging Management
System, but most care has been taken to make the system efficient and user
friendly

“Lodging Management System” has been designed to computerized the following

functions that are performed by the system:
• Room Detail Information
• Staff Information
• Customer Information
• Check-in and check-out Detail Information
• Advance Booking Information
• Check-out of customer
• Check-in customer
• Check-out customer
• Room Details
• Individual customer Report
 OBJECTIVE
During the past several decades personnel function has been transformed
from a relatively obscure record keeping staff to central and top level
management function. There are many factors that have influenced this
transformation like technological advances, professionalism, and general
recognition of human beings as most important resources.

➢ A computer based management system is designed to handle all the

primary information required to calculate monthly statements.
➢ Separate database is maintained to handle all the details required for the
correct statement calculation and generation.
➢ 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.
➢ Similarly, record maintenance and updation can also be accomplished by
using the identification of the customer with all the details being
automatically generated. These details are also being promptly
automatically updated in the master file thus keeping the record absolutely
up-to-date.
➢ The entire information has maintained in the database or Files and whoever
wants to retrieve can’t 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:

• Room activities,
• Admission of a New Customer,
• Assign a room according to customer’s demand,
• Checkout of a computer and releasing the room
• Finally compute the bill etc.
• Packages available.
• Advance online bookings.
• Online Cancellation.
• List of Regular customers.
• Email facility.
• Feedback
Chapter No.:-2
System Analysis
 System Analysis
❖ Introduction
System analysis is the process of totally understanding the current system
by gathering interpreting facts, diagnosing problems and using the facts to
improve the current system.
This phase is detail appraisal of the existing system. This appraisal includes
how the system works and what it does. It also includes finding out in more
details about what the system problems are and what user requires from new
system or any new change in the system. After this phase analyst should be
familiar with both the detail operation of the system and what is required by the
system.
The output of this phase results the details of model of the system. The
model describes the system function, data flow in the system. The phase also
contains the detail set of user required manual and these requirements are used
to set objective for new system.
❖ Fact Finding -
The methods for collecting data about requirements are called Fact Finding
Techniques. This includes –
• Interviews
• Observations
❖ Interview –
Interview with Manager of the firm gave the detail information of functioning
of the existing system.
❖ Observation –
Observation includes observing standard operating procedure that gave the
information about the activities carried out. Thus this data gave the required data
for the system as well as help to design the new system.

Following are the points to be noted –

1. The existing system was carefully studied.
2. The requirements of various procedures were noted after interviewing
the Manager.
3. While developing the system various suggestions and changing
requirements are concerned

Feasibility Study

Feasibility studies aim to objectively and rationally uncover the strengths and
weaknesses of the existing business or proposed venture, opportunities and
threats as presented by the environment, the resources required to carry through,
and ultimately the prospects for success. In its simplest term, the two criteria to
judge feasibility are cost required and value to be attained. As such, a well-
designed feasibility study should provide a historical background of the business
or project, description of the product or service, accounting statements, details of
the operations and management, marketing research and policies, financial data,
legal requirements and tax obligations. Generally, feasibility studies precede
technical development and project implementation.These tests are:

1. Economical feasibility
2. Technical feasibility
3. Behavioural feasibility
 1. Economic Feasibility

Economic analysis is the most frequently used method for evaluating the
effectiveness of a new system. More commonly known as cost/benefit analysis,
the procedure is to determine the benefits and savings that are expected from a
candidate system and compare them with costs. If benefits outweigh costs, then
the decision is made to design and implement the system. An entrepreneur must
accurately weigh the cost versus benefits before taking an action.

Cost-based study:

It is important to identify cost and benefit factors, which can be categorized

as follows:

1. Development costs and

2. Operating costs.

This is an analysis of the costs to be incurred in the system and the benefits
derivable out of the system.

Time-based study:

This is an analysis of the time required to achieve a return on investments.

The future value of a project is also a factor

2. Technical Feasibility

The assessment is based on an outline design of system requirements in

terms of Input, Processes, Output, Fields, Programs, and Procedures. This can
be quantified in terms of volumes of data, trends, frequency of updating, etc. in
order to estimate whether the new system will perform adequately or not.
Technological feasibility is carried out to determine whether the company has
 the capability, in terms of software, hardware, personnel and expertise, to handle
the completion of the project. When writing a feasibility report the following
should be taken to consideration:

• A brief description of the business to assess more possible factors which

could affect the study.

• The part of the bu siness being examined.

• The human and economic factor.

• The possible solutions to the problems.

At this level, the concern is whether the proposal is both technically and
legally feasible.

3. Behavioural Feasibility

Proposed projects are beneficiary only if they turned into information

systems that will meet organisation operating requirement. Simply stated this test
of feasibility asks if the system will works when it is developed and installed.
Which are the major barriers for implementation? Here are question that will help
test the operations feasibility of project.

Are current business methods acceptable to the user ? If they are not, user
may welcome the change that will about more operational and useful system.

• Gathering Information :-

The analysis through collection of data plays the wider role in the analysis
of the system. So the data is collected at different levels of management to keep
track of ful l information of the system.
 The collection of data is done from

Top Level Management

Middle Level Management

Low Level Management

Different methods used to collect the data:

1. Questioners :

The data is collected through questioners by filling a set of questions from

the different levels of management. The questions made by questioners are three
different types.

They are,

• Structured questioners
• Unstructured questioners
• Semi-structured questioners
2. Interviews :

Interviews were conducted to collect the information. The interviews were

conducted at two levels.

• Formal Group Interviews: The interviews conducted for formal groups

i.e., the hierarchical (official) groups in the firm.
• Informal Group Interviews: The interviews were conducted for informal
groups i.e., the groups formed outside the company.
3. Observation :

The data is also collected by observation of the firm. The data is collected
by observing on the site at different timings and at different situations like when
the firm is busy and when the firm hasn’t much work to do.
 4. Record Review :

To collect the data and to get a clear idea of the firm some of the data is
also collected from the past records of the firm. This information helps very much
to get a clear idea of the firm i.e., the different problems occurred in different
seasons and some exception conditions. This very much gives a clear idea of
exceptional conditions.

• System Study :-
➢ Existing System :

The existing system is the manual based system which needs a lot of efforts
and consume more time. It is difficult to upgrade all the record and recover
information in the existing system.

➢ Disadvantages of the Existing System :

o It requires more man power.
o More manual labor needed here.
o Low security is available.
o It has more data redundancy.
o It is difficult to update data.
o It is difficult to keep record.
➢ Proposed System :

The proposed system is having many advantages over the existing system. It
require less overhead and very efficient.

➢ Advantages of Proposed System :

o Gives high security.
o Data redundancy can be avoided in this system.
o It is easy to handle, keep and update record.
 Chapter No.:-3
System Requirements
Hardware Requirement –
Hardware of computer means all physical components of computer system.
Computer hardware consists of input devices, CPU and output devices. Input
devices are connected directly to the computer system.
The following hardware is required to operate the project –

▪ CPU - Dual Core or Higher

▪ Hard Disk - 500 GB or Higher
▪ RAM - 8 GB or Higher
▪ Monitor - 14 inch
▪ Keyboard & Mouse - 100 keys & Logitech Mouse
▪ Printer - Any ( possibly LaserJet )

Software Requirement –
The software required for this project is –
▪ Operating System - MS Windows XP or above
▪ Front End - Microsoft C#.NET
▪ Back End - MS Access 2010
▪ Visual Studio 2012
 ❖ Technology Overview

Introduction to C#.Net:-
C# is an elegant and type-safe object-oriented language that enables
developers to build a variety of secure and robust applications that run on the
.NET Framework. You can use C# to create traditional Windows client
applications, XML Web services, distributed components, client-server
applications, database applications, and much, much more. Visual C# 2010
provides an advanced code editor, convenient user interface designers, integrated
debugger, and many other tools to make it easier to develop applications based
on version 4.0 of the C# language and version 4.0 of the .NET Framework.
▪ As an object-oriented language, C# supports the concepts of encapsulation,
inheritance, and polymorphism. All variables and methods, including the
Main method, the application's entry point, are encapsulated within class
definitions.
▪ In addition to these basic object-oriented principles, C# makes it easy to
develop software components through several innovative language
constructs, including the following:
▪ Encapsulated method signatures called delegates, which enable type-safe
event notifications.
▪ Properties, which serve as assessors for private member variables.
▪ Attributes, which provide declarative metadata about types at run time.
▪ Inline XML documentation comments.
▪ Language-Integrated Query (LINQ) which provides built-in query
capabilities across a variety of data sources.
▪ C# has a rich set of predefined data types which you can use in your
programs. The following figure illustrates the hierarchy of the predefined
data types found in C#.
 Features of C# :
▪ C# supports Data Encapsulation, Inheritance, Polymorphism, Interfaces.
▪ C# has been based according to the current trend and is very powerful and
simple for building interoperable, scable, robust applications.
▪ In C# we cannot perform unsafe casts like convert double to a boolean.
▪ It supports garbage collection, automatic memory management, and a lot.
▪ C# allows the users to use pointers as unsafe code blocks to manipulate
your old code.
 Introduction to MS-ACCESS:-
Microsoft Access is a powerful program to create and manage your
databases. It has many built in features to assist you in constructing and viewing
your information. Access is much more involved and is a more genuine database
application than other programs such as Microsoft Works.
Microsoft Access and may solve some of your problems, but it is a very
good idea to use the Help Files that come with Microsoft Access, or go to
Microsoft's web site. First of all you need to understand how Microsoft Access
breaks down a database. Some keywords involved in this process are: Database
File, Table, Record, Field and Data-type. Here is the Hierarchy that Microsoft
Access uses in breaking down a database.
▪ MS-Access is well-known database management system package that can
store and classify relatively large amounts of data. Most of this data is
stored in the form of tables, list etc.
▪ MS-Access helps to design database tables as per as requirements and in
the specified format.
▪ The data stored in MS-Access table is mostly secured and can be converted
into any machine compatible format whenever required.
▪ MS-Access also keeps the track of relationships among the table, making
it possible to process data and create sophisticated reports and compute
static.
▪ Using MS-Access as back end with Visual Studio 2012 provides easy
accessibility, faster processing speed with faster data retrieval.
 Introduction to Visual Studio 2012 :-

Visual Basic Express 2012 is the version of Visual Basic.Net launched by

Microsoft in 2012. Visual Basic Express 2012 is almost similar to Visual Basic
Express 2010 and Visual Basic 2008, but it has added some new features. The
most distinct difference is that Visual Basic Express 2012 no more comes as a
standalone program; it is now bundled with other Microsoft Programming
languages C# and C++ in an Integrated Development Environment (IDE) called
Visual Studio 2012.

Although Microsoft has released the latest Visual Studio 2017, the older
versions of Visual Studio are still available for download. First of all, Visual
Basic 2012 is very much similar to Visual Basic 2010 and Visual Basic 2008.
However, it is very different from Visual Basic 6. While they are nearly similar
in terms of Interface and program structure, their underlying concepts are quite
different. The main difference is that Visual Basic 2012 is a full-fledged Object
Oriented Programming Language while Visual Basic 6 may have OOP
capabilities, it is not fully object oriented. In order to qualify as a fully object
oriented programming language, it must have three core technologies namely
encapsulation, inheritance and polymorphism.

The Controls in Visual Basic 2012 are objects that can be placed on the
form to perform various tasks. We can use them to create all kinds of Windows
applications. They are categorized into Common Controls, Containers, Menus,
Toolbars, Data, Components, Printings and Dialogs. At the moment, we will
focus on the common controls. Some of the most frequently used common
controls are Button, Label, ComboBox, ListBox, PictureBox, TextBox etc. To
insert a control into your form in Visual Basic 2012 IDE, we just need to drag the
control from the toolbox and drop it into the form. We can reposition and resize
it as we like.
 Chapter No.:-4
System Development
 ❖ Software Development Life Cycle :-
The software development life cycle (SDLC) is a framework defining tasks
performed at each step in the software development process. SDLC is a structure
followed by a development team within the software organization. It consists of
a detailed plan describing how to develop, maintain and replace specific software.
The life cycle defines a methodology for improving the quality of software and
the overall development process.

The software development life cycle is also known as the software

development process.

What is SDLC?

SDLC is a process followed for a software project, within a software

organization. It consists of a detailed plan describing how to develop, maintain,
replace and alter or enhance specific software. The life cycle defines a
methodology for improving the quality of software and the overall development
process. The following figure is a graphical representation of the various stages
of a typical SDLC.
 SDLC consists of following activities:

1. Planning: The most important parts of software development, requirement

gathering or requirement analysis are usually done by the most skilled and
experienced software engineers in the organization. After the requirements
are gathered from the client, a scope document is created in which the
scope of the project is determined and documented.
2. Implementation: The software engineers start writing the code according
to the client's requirements.
3. Testing: This is the process of finding defects or bugs in the created
software.
4. Documentation: Every step in the project is documented for future
reference and for the improvement of the software in the development
process. The design documentation may include writing the application
programming interface (API).
5. Deployment and maintenance: The software is deployed after it has been
approved for release.
6. Maintaining: Software maintenance is done for future reference. Software
improvement and new requirements (change requests) can take longer than
the time needed to create the initial development of the software.
SDLC Model :-

There are several software development models followed by various

organizations:

• Waterfall Model: This model involves finishing each phase completely

before commencing the next one. When each phase is completed
successfully, it is reviewed to see if the project is on track and whether it
is feasible to continue.
• V-Shaped Model: This model focuses on the execution of processes in a
sequential manner, similar to the waterfall model but with more importance
placed on testing. Testing procedures are written even before the
commencement of writing code. A system plan is generated before starting
the development phase.
• Incremental Model: This life cycle model involves multiple development
cycles. The cycles are divided up into smaller iterations. These iterations
can be easily managed and go through a set of phases including
requirements, design, implementation and testing. A working version of
the software is produced during the first iteration, so working software is
created early in the development process.
 • Waterfall Model :-

The Waterfall Model was first Process Model to be introduced. It is very

simple to understand and use. In a Waterfall model, each phase must be
completed before the next phase can begin and there is no overlapping in the
phases. Waterfall model is the earliest SDLC approach that was used for software
development.

In “The Waterfall” approach, the whole process of software

development is divided into separate phases. The outcome of one phase acts as
the input for the next phase sequentially. This means that any phase in the
development process begins only if the previous phase is complete. The waterfall
model is a sequential design process in which progress is seen as flowing steadily
downwards (like a waterfall) through the phases of Conception, Initiation,
Analysis, Design, Construction, Testing, Production/Implementation and
Maintenance.

As the Waterfall Model illustrates the software development process in a

linear sequential flow; hence it is also referred to as a Linear-Sequential Life
Cycle Model.
The waterfall model is a sequential software development process model
that follows the following defined phases:

1. Conception
2. Initiation
3. Analysis
4. Design
5. Construction
6. Testing
7. Production/Implementation
8. Maintenance

➢ Waterfall Model – Design:

Waterfall approach was first SDLC Model to be used widely in

Software Engineering to ensure success of the project. In "The Waterfall"
approach, the whole process of software development is divided into
separate phases. In this Waterfall model, typically, the outcome of one
phase acts as the input for the next phase sequentially. The following
illustration is a representation of the different phases of the Waterfall
Model.
Sequential Phases in Waterfall Model

• Requirements: The first phase involves understanding what need to be

design and what is its function, purpose etc. Here, the specifications of the
input and output or the final product are studied and marked.
• System Design: The requirement specifications from first phase are studied
in this phase and system design is prepared. System Design helps in specifying
hardware and system requirements and also helps in defining overall system
architecture. The software code to be written in the next stage is created
now.
• Implementation: With inputs from system design, the system is first
developed in small programs called units, which are integrated in the next
phase. Each unit is developed and tested for its functionality which is referred
to as Unit Testing.
• Integration and Testing: All the units developed in the implementation phase
are integrated into a system after testing of each unit. The software designed,
needs to go through constant software testing to find out if there are any flaw
or errors. Testing is done so that the client does not face any problem during
the installation of the software.
• Deployment of System: Once the functional and non-functional
testing is done, the product is deployed in the customer environment or
released into the market.
• Maintenance: This step occurs after installation, and involves making
modifications to the system or an individual component to alter attributes or
improve performance.These modifications arise either due to change
requests initiated by the customer, or defects uncovered during live use of
the system. Client is provided with regular maintenance and support for the
developed software.
 All these phases are cascaded to each other in which progress is seen as
flowing steadily downwards (like a waterfall) through the phases. The next phase
is started only after the defined set of goals are achieved for previous phase and
it is signed off, so the name “Waterfall Model“.
 ❖ Waterfall Model - Advantages:-
• The advantage of waterfall development is that it allows for
departmentalization and control. A schedule can be set with deadlines for
each stage of development and a product can proceed through the
development process model phases one by one.
• The waterfall model progresses through easily understandable and
explainable phases and thus it is easy to use.
• It is easy to manage due to the rigidity of the model – each phase has specific
deliverables and a review process.
• In this model, phases are processed and completed one at a time and they do
not overlap. Waterfall model works well for smaller projects where
requirements are very well understood.

❖ Waterfall Model – Disadvantages:-

• It is difficult to estimate time and cost for each phase of the development
process.
• Once an application is in the testing stage, it is very difficult to go back and
change something that was not well-thought out in the concept stage.
• Not a good model for complex and object-oriented projects.
• Not suitable for the projects where requirements are at a moderate to high
risk of changing.
Chapter No.:-5
System Design
 • Systems design is the process of defining the architecture, modules,
interfaces, and data for a system to satisfy specified requirements. Systems
design could be seen as the application of systems theory to product
development. There is some overlap with the disciplines of systems
analysis, systems architecture and systems engineering.
• Overview-

If the boarder topic of product development "blends the perspective of

marketing, design, and manufacturing into a single approach to product
development," then design is the act of taking the marketing information and
creating the design of the product to be manufactured. Systems design is therefore
the process of defining and developing systems to satisfy
specified requirements of the user.

Until the 1990s, systems design had a crucial and respected role in the data
processing industry. In the 1990s, standardization of hardware and software
resulted in the ability to build modular systems. The increasing importance of
software running on generic platforms has enhanced the discipline of software
engineering.

➢ Architectural design-

The architectural design of a system emphasizes the design of the system

architecture that describes the structure, behavior and more views of that system
and analysis.

➢ Logical design-

The logical design of a system pertains to an abstract representation of the

data flows, inputs and outputs of the system. This is often conducted via
modelling, using an over-abstract (and sometimes graphical) model of the actual
system. In the context of systems, designs are included. Logical design
includes entity-relationship diagrams (ER diagrams).

➢ Physical design-
The physical design relates to the actual input and output processes of the
system. This is explained in terms of how data is input into a system, how it is
verified/authenticated, how it is processed, and how it is displayed. In physical
design, the following requirements about the system are decided.

1. Input requirement,
2. Output requirements,
3. Storage requirements,
4. Processing requirements,
5. System control and backup or recovery.

Put another way, the physical portion of system design can generally be
broken down into three sub-tasks:

1. User Interface Design

2. Data Design
3. Process Design

User Interface Design is concerned with how users add information to the
system and with how the system presents information back to them. Data Design
is concerned with how the data is represented and stored within the system.
Finally, Process Design is concerned with how data moves through the system,
and with how and where it is validated, secured and/or transformed as it flows
into, through and out of the system. At the end of the system design phase,
documentation describing the three sub-tasks is produced and made available for
use in the next phase.
 Physical design, in this context, does not refer to the tangible physical
design of an information system. To use an analogy, a personal computer's
physical design involves input via a keyboard, processing within the CPU, and
output via a monitor, printer, etc. It would not concern the actual layout of the
tangible hardware, which for a PC would be a monitor, CPU, motherboard, hard
drive, modems, video/graphics cards, USB slots, etc. It involves a detailed design
of a user and a product database structure processor and a control processor. The
H/S personal specification is developed for the proposed system.
 ❖ Project Design

Project design first requires gathering , synthesizing , analyzing

information with enough objectively and detail to support a program decision that
makes optimum use of resources to achieve desired results. IRG helps countries
and organizations ensure that interventions are ethically sound , technically up-
to-date, relevant to the program setting and acceptable to or endorsed by the
beneficiary populations. Our technical experts help organizations clearly
articulate their goals and objectives, and the strategies and activities that will be
required to achieve them.

The design process translates requirements into representation of the

software that can be assessed for quality before coding begins. Design is multi-
step process that focuses on data structure, software architecture, interface
representations and procedural details. In this phase we started developing outline
for our modules on which our project would rest.

System Design

• The entire system is projected with a physical diagram which specifies the
actual storage parameters that are physically necessary for any database
parameters that are physically necessary for any database to be stored on
to the disk. The overall system existential idea is derived from this diagram.
• The relation upon the system is structure through a conceptual ER-
Diagram, which not only specifies the existential entities but also the
standard relations through which the system exists and the cardinalities that
are necessary for the system state to continue.
 ❖ Data Flow Diagram (DFD)

A data-flow diagram (DFD) is a way of representing a flow of a data of

a process or a system (usually an information system) The DFD also provides
information about the outputs and inputs of each entity and the process itself. A
data-flow diagram has no control flow, there are no decision rules and no loops.
Specific operations based on the data can be represented by a flowchart.

Data Flow Diagram is the core modeling activity in the structured analysis.
It is a graphical representation technique for information flow modeling and
functional modeling. It represents the movement of data from input to output.
Data flow diagram is also called as bubble chart or flow graph.

The data flow diagram represents the flow of information in the system.
Data flow diagram is partitioned in different levels. The data flow diagram is used
to represent the system at different level abstractions. The data flow diagram may
be partitioned into different levels like level 0, level 1, level 2, level 3, etc.
depending on the system requirements.

Following are some notations used for constructing data flow diagram-
• Circle:-

The circle represents the process within the data flow diagram.
 • Rectangle:-

The rectangle represents the external entity.

• Open Rectangle:-

The open rectangle represents the storage file or database.

• Arrows:-

The labeled arrows represent incoming and outgoing flow of data in the
flow diagram.

❖ DFD Components

DFD consists of processes, flows, warehouses, and terminators. There are several ways to view
these DFD components.

• Process

The process (function, transformation) is part of a system that transforms inputs

to outputs. The symbol of a process is a circle, an oval, a rectangle or a rectangle
with rounded corners (according to the type of notation). The process is named
in one word, a short sentence, or a phrase that is clearly to express its essence.
 • Data Flow

Data flow (flow, dataflow) shows the transfer of information (sometimes also
material) from one part of the system to another. The symbol of the flow is the
arrow. The flow should have a name that determines what information (or what
material) is being moved. Exceptions are flows where it is clear what information
is transferred through the entities that are linked to these flows. Material shifts
are modeled in systems that are not merely informative. Flow should only
transmit one type of information (material). The arrow shows the flow direction
(it can also be bi-directional if the information to/from the entity is logically
dependent - e.g. question and answer). Flows link processes, warehouses and
terminators.

• Warehouse

The warehouse (datastore, data store, file, database) is used to store data for later
use. The symbol of the store is two horizontal lines, the other way of view is
shown in the DFD Notation. The name of the warehouse is a plural noun (e.g.
orders) - it derives from the input and output streams of the warehouse. The
warehouse does not have to be just a data file, for example, a folder with
documents, a filing cabinet, and optical discs. Therefore, viewing the warehouse
in DFD is independent of implementation. The flow from the warehouse usually
represents the reading of the data stored in the warehouse, and the flow to the
warehouse usually expresses data entry or updating (sometimes also deleting
data). Warehouse is represented by two parallel lines between which the memory
name is located (it can be modelled as a UML buffer node).

• Terminator

The Terminator is an external entity that communicates with the system and
stands outside of the system. It can be, for example, various organizations (e.g. a
bank), groups of people (e.g. customers), authorities (e.g. a tax office) or a
department (e.g. a human-resources department) of the same organization, which
does not belong to the model system. The terminator may be another system with
which the modeled system communicates.
 0th level DFD:-

Booking Details Booking Report

CheckIn Details CheckIn Report

CheckOut Details CheckOut Report

Hotel

Customer Details Management Customer Report

System

Room Details Room Report

 First Level Data Flow Diagram:-

1)Booking Information:-

Customer Information

Room Information
Booking Booking Report
Information

2)CheckIn Information:-

Customer
Information

Room Information CheckIn CheckIn Report

Booking
Information
 3)CheckOut Information:-

CheckIn Details

CheckOut Report
Service CheckOut
Bill

Service
Consumptiion
 ❖ Entity Relationship Diagram (ERD)
An entity-relationship diagram (ERD) is a data modeling technique that graphically
illustrates an information system’s entities and the relationships between those
entities. An ERD is a conceptual and representational model of data used to represent
the entity framework infrastructure.

The elements of an ERD are:

• Entities
• Relationships
• Attributes

• Entity:-

An entity is an object in the system which we want to model and stores the
information about the database groups of same of object are called as entity type or
entity sets. Entities are represented by rectangle.

Rectangle

• Attributes:-

All the data related to an entity is stored in the attributes, each attributes can have
any value for its domain. The attributes are represented by an oval.

Oval
The attributes can be single level or multi levels. The multi value attributes can be
represented by double ellipse.

• Relationship:-

A relationship is a meaningful association between entity types. A relationship is

indicated by a diamond.

• Link:-

The relationship between multiple entities as well as link of a multiple attributes is

represented by lines.
 E R Diagram Room
Customer Type
Name

Room No Room
Customer Phone No Facility
ID

Customer CheckIn Room

has

Consume
Services Room Details

Service Description Room Room

Code Charges Capacity

Service
Type
 ❖ Use Case Diagram
A use case diagram is a dynamic or behavior diagram in UML. Use case
diagrams model the functionality of a system using actors and use cases. Use cases
are a set of actions, services, and functions that the system needs to perform. In this
context, a "system" is something being developed or operated, such as a web site.
The "actors" are people or entities operating under defined roles within the system.

❖ Basic Use Case Diagram Symbols and Notations

➢ System
Draw your system's boundaries using a rectangle that contains use cases. Place
actors outside the system's boundaries.

➢ Use Case
Draw use cases using ovals. Label the ovals with verbs that represent the
system's functions.

➢ Actors
Actors are the users of a system. When one system is the actor of another
system, label the actor system with the actor stereotype.
➢ Relationships
Illustrate relationships between an actor and a use case with a simple line. For
relationships among use cases, use arrows labeled either "uses" or "extends."
A "uses" relationship indicates that one use case is needed by another in order
to perform a task. An "extends" relationship indicates alternative options under
a certain use case.
➢ Use Case Diagram:

Room Details

Customer Details
DetailsDetails

CheckIn Details

CheckOut Details Database

Booking Details

Exit
Chapter No.:-6
Database Design
 ➢ Introduction

Database Management System (DBMS) is a collection of programs which

enables its users to access database, manipulate data, reporting / representation
of data .

It also helps to control access to the database.

Database Management Systems are not a new concept and as such had been
first implemented in 1960s.

Charles Bachmen's Integrated Data Store (IDS) is said to be the first DBMS
in history.

With time database technologies evolved a lot while usage and expected
functionalities of databases have been increased immensely.

Database is a systematic collection of data. Databases support storage

and manipulation of data. Databases make data management easy. Let's discuss few
examples.

An online telephone directory would definitely use database to store data

pertaining to people, phone numbers, other contact details, etc.

Your electricity service provider is obviously using a database to manage

billing , client related issues, to handle fault data, etc.

➢ There are 4 major types of DBMS.

• Hierarchical - this type of DBMS employs the "parent-child" relationship of

storing data. This type of DBMS is rarely used nowadays. Its structure is like
 a tree with nodes representing records and branches representing fields. The
windows registry used in Windows XP is an example of a hierarchical
database. Configuration settings are stored as tree structures with nodes.
• Network DBMS - this type of DBMS supports many-to many relations. This
usually results in complex database structures. RDM Server is an example of
a database management system that implements the network model.
• Relational DBMS - this type of DBMS defines database relationships in form
of tables, also known as relations. Unlike network DBMS, RDBMS does not
support many to many relationships. Relational DBMS usually have pre-
defined data types that they can support. This is the most popular DBMS type
in the market. Examples of relational database management systems include
MySQL, Oracle, and Microsoft SQL Server database.
• Object Oriented Relation DBMS - this type supports storage of new data
types. The data to be stored is in form of objects. The objects to be stored in
the database have attributes (i.e. gender, ager) and methods that define what
to do with the data. PostgreSQL is an example of an object oriented relational
DBMS.
 Room Information Table
Field Name Data Type Description
sRoomNo Number Primary Key
sRoomType Text
sRoom Price Number
sRoomStatus Number
sBookingDate Text

Customer Information Table

Field Name Data Type Description
CustomerID Number Primary Key
Customer Name Text
DOB Text
Address Text
City Text
State Text
Nationality Text
Customer ID Prof Text
Card Text
 Customer Booking
Field Name Data Type
Customer Id Number
Customer Name Text
Gender Text
Address Text
City Text
State Text
Nationality Text
Card No Text
Passport No Text
Booking Date Date
Staying Text
Check In Date Date
Room type Text
Room no Text
Amount Text
Total Text
 Checkin Information
Field Name Data Type
Booking type Text
Customer id Number
Customer Name Text
Gender Text
Date of birth Date
Address Text
City Text
State Text
Nationality Text
Passport No Text
Card No Text
Check In Date Date
Staying Text
Check Out Date Date
Room Type Text
Room Number Text
Amout Text
Total Text
 Checkout Information
Field Name Data type
Customer Id Number
Customer Name Text
Gender Text
Date of Birth Date
Address Text
City Text
State Text
Nationality Text
Passport No Text
Card No Text
Checkin Date Date
Staying Text
Checkout Date Date
Roomtype Text
Room No Text
Amout Text
Total Text

Salary Information Table

Field Name Data Type Description
sStaffId Number Foreign Key
sStaffName Text
Gender Number
City Text
sMobile No Number Primary Key
sDateOfJoining Date
sSalary Number

sDisignation Text

sWorkingStaff Text
 Salary Distribution Table
Field Name Data Type Description
sEntryNumber Number Foreign Key
sStaffId Number
sStaffName Text
SMobileNo Text
sDesignation Text Primary Key
sSalary Number
sSalaryDate Date/Time
sSalaryAmount Number
Chapter No.:-7
Screenshot
Chapter No.:-8
System Testing
 ➢ Introduction -
The objective of the system was to ensure that individual programs are
working as accepted, the programs link together to meet requirements and to ensure
that the system and associated system work together. Initial phase of system testing
include unit testing and debugging.
Unit testing comprises the set of tests performed by an individual programmer
prior to integration of unit into larger system. The situation can be illustrated as
below -
• Coding
• Debugging
• Unit Testing
• Integration Testing
Debugging is the process of isolating and correcting the causes known as Errors.
After debugging the program units were again tested.
• White Box Testing –
A. Transaction Path Testing -
In this phase each bad condition within a unit program was tested. As and a
loop or conditional statement occurs into a unit the loop was tested for correctness,
for boundary condition and for avoiding in finite execution cycle. The path of each
transaction path from origin to destination was tested for reliable result.
B. Module Testing –
The module testing was carried during programming stage itself. Individual
programs were tested at the time of coding and necessary changes were made to
ensure that modules in the programs are working properly.
 • Black Box Testing –
After module and string testing the system was tested as a whole. The system test
was under taken to check bundled modules for errors, and errors were corrected. The
testing on actual data followed this.
A. Output Testing –
No system can be useful if it does not produced required output. For getting
desired output the system under consideration was tested by the user about the
needed format.
• Validation Testing –
User acceptance of system is a key factor for the success. At the time of
developing required changes were made so as to satisfy the user’s need. This testing
can be achieved with the help of Black Box Testing. This testing tries to uncover the
errors but the focus is on the user requirement. Validation can be defined in many
ways. Different types of procedures can also perform by testing.
• GUI Testing –
GUI environment has helped to produced user friendly application but it
become more difficult to design and to test the application. The design data entry
can be done using some following points –
▪ Is alphanumeric data can be properly enclosed and input the system?
▪ Do graphical model of the data entry work properly?
▪ Is invalid data properly recognized?

• System Implementation –
Through a testing of different of the system as describe above are to actual use
by using live data by user and staff after sufficient training number. This indicates
considerable time saving system and comes out fast and efficient development.
 In system implementation personal checks out and put new software into use,
trains user to install new application.
There are many implementation strategies some time system developer may
choose to pilot the operation only one area of firm with one or two person.
Sometimes they run old and new system together to compare the results.
User Training – The first few days I was physically present at factory with
manager for help them to understand new computerized system
Chapter No.:-9
Conclusion
 It has been a great pleasure for me to work on this exciting and challenging
project. This project proved good for me as it provided practical knowledge of
Windows Based Application using .NET Framework.
At the end, I would like to say that the system developed by me is flexible and
can be used by any hostelling business organization which offers lodging facility.
With the help of this system other reports required to the user can be prepared
easily.
The quality and reality of the software depends upon the result of the phases
in the system development. The software quality includes the modularity, good
communication, user friendliness, maintainability, etc.
Chapter No.:-10
Bibilography
 The following are the books tht have been referred for the successful completion
Of our project work:

Complete Reference:-
5th Edition by Herbert Schildt,published by McGraw-Hill Publishing Company
Limited.
Software Engineering:-
A Practitioner’s Approach, Fifth Edition by Roger S Pressman, Published by
McGraw – Hill
International Edition.
Visual Basic 6 Programming:-
By Steven Holzner, published by dream tech press.
Database:-
By Elmasri Navathe.