CONTENT:

CHAPTER 1: INTRODUCTION
Project Introduction
Problem Description
Tools and Technology Used

CHAPTER 2: INITIAL SYSTEM STUDY

Existing System With Limitation
Proposed System With Objectives

CHAPTER 3: FEASIBILITY STUDY

Economic Feasibility
Technical Feasibility
Durability Feasibility

CHAPTER 4: SYSTEM ANALYSIS

System Flowcharts
Entity Relationship Diagram
Data flow-diagram
Context-diagram

CHAPTER 5: SYSTEM DESIGN

Introduction
File /Database design
Normalization

CHAPTER 6: CODING
Entire System Coding

CHAPTER 7: SYSTEM TESTING

Introduction
Preparation of Test Data-White Box Test & Black Box Test.
Unit Testing, Class Testing.
Testing with dummy/live data

CHAPTER 8: SCREEN SHOTS

CHAPTER 9: CONCLUSIONS

CHAPTER10: BIBLIOGRAPHY

CHAPTER

Introduction

PROJECT INTRODUCTION

Chapter1

Introduction

1.1 Project Introduction:

The Paramount success of information technology in the last few decades

has made irrelevant the role of time and space separating human experience through
integration of information system. This integration of system with the use of IT has
another myth of industrial societies that any business organization for establishment
with IT if it is to survive into the next century. The day to day prominence of economic
liberalization and the bilateral trade among various countries in the world have made it
imperative for every business organization to harness and apply the benefits of IT.
The software programs have simplified the process of complex
mathematical and analytical computation. The redundancy of calculations has been
reduced to minimum with the help of software program which result in saving a lot of
time and manpower. This can be easily understood simply by comparing any banking
system before and after computerization of the system.
Thus it is obvious that to keep the pace with the rapidly and continuously
changing complexity of modern business entails better application of IT for prospective
niche in the global market.
1.2 Problem Definition:

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.

1.3 Tools and Technology Used

The following tools and technology are used to develop the system

HARDWARE REQUIREMENTS:
Processor

: Pentium III and above

Memory

: 512 MB RAM

Hard Disk

: 160 GB Hard Disk

Printer

: Laser, Dot Matrix Printer

Mouse

:Optical Mouse

CD/RW

: DVD-RW

Keyboard

: Multimedia

SOFTWARE REQUIREMENTS:
5

Component

Software Name and Version

Operating System

Windows

Back-end-tool

Microsoft Access 2003

Front End Tool

Microsoft Visual Basic 6.0

About Microsoft Visual basic 6.0:

Microsoft Visual basic 6.0 the product of

Microsoft Visual Studio and is developed by Microsoft Corporation.
Microsoft Visual basic 6.0 is a GUI programming Language. It is a 4GL
tool.

Advantage of using Microsoft Visual Basic 6.0:

End users point of view:

A Graphical User Interface (GUI) programming
language provides a good interface to the user. Applications developed
using this programming language have simple graphical interfaces such
as text boxes, command buttons, list boxes, windows, menus, pictures
etc. These components work on point and click method that means any
end user having a very little knowledge of operating the computer can
work in the application developed using it.

Programmers point of View:

There are many advantages to choose VB6 for

developing Applications , some of them are:
Microsoft visual basic 6.0 provides plenty of Reusable
Components that reduces a great deal of work for the programmer. Now
programmer does not have to bother about developing codes for
components such as text boxes, command buttons, menus etc. instead of
the concentrate to develop codes for the main objective of the application.
Another great advantage of using VB 6.0 is that it has a very
powerful and efficient Editor that help programmer to develop code as
soon as possible and as far as error free. The editor provides a great deal
of help to the programmer to write code by popping up the attributes and
methods of typed component, programmer only has to select those
attributes and methods to write code. With using of VB6 a programmer
having a little knowledge of programming can develop a well working
Application.
VB6s Debugging tool is also very powerful and efficient.
VB6 supports almost all database packages like Oracle, Ms Access,
Dbase, FoxPro etc. It has very efficient control to connect the databases
to the front end. VB 6 has a control named Data Report, which enables us
to create complex Reports. Programmers do not have to purchase third
party product to develop Reports. It has another many advantages, which
are not described here.

About Microsoft Access 2003:

Microsoft Access 2003 is the product of
Microsoft Office 2003, which is developed by Microsoft Corporation. It is a
database Package that enables developer to create, update and delete
relational databases. It supports SQL (Structured Query Language).
Hotel Management System maintains its database using SQL
statements. Back end of Hotel Management System is totally
maintained by Microsoft Access 2003. It is very easy to create relations
among tables in this database package.

About Microsoft Visual Studio Package and Deployment Wizard:

Package and Deployment wizard is a product of

Microsoft Visual Studio, which is developed by Microsoft Corporation.
It enables developer to package his or her Application. Developer only
has to follow the instructions of package and deployment wizard and
his or her Application is packaged for distribution.

CHAPTER

SYSTEM STUDY

Chapter2

System Study

2.1 The Existing System

The study of the existing system is always an important step in any

computerization process. A solid understanding of the previous system is necessary in
order to have an idea about flow of various operations in terms of data.
In this case there is no computerized system. The organization does the work
manually. The agency will not have the daily updated details of information status. The
existing system has been doing everything manually and it is time consuming and error
prone. Nowadays people live a busy schedule life, so people have less time to enquire or
gather the information. There is no guarantee of secure data transaction. Data
inconsistency can occur due to duplication of information.
The whole process of assigning room and billing was done manually till date.
Registration of customer and the process of check out used to take time when the
software was not installed.
The existing system consists of many modules use by different set of peoples in
various ways. It needs the authorization of each module separately and lack of
integration and hence it lack to manage properly.
Limitation of Existing System
1. It is a very time consuming process.
2. Huge amount of paper work is required.
3. Sometime data may be loss due to lack proper management.
4. It is not always error free.
5. Low in security.
6. Result processing takes more time as it is done manually.
7. Possibility of data duplication as there is no repetition check.
8. Difficulty of searching and retrieving records.
9. Low in security.

2.2 The Proposed System

To overcome the anomalies of the existing system, the proposed system is a
humble approach to structuring all the activities of the system. It is designed not only
10

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.

OBJECTIVE OF THE PROPOSED SYSTEM:

The purpose of hotel management system is to manage in an efficient manner
and no time wasting for checking information. The main objective of the project Hotel
Management System is used for maintaining the information for each and every
customer through a fully automated system that not only saves lot of time but also gives
fast results.
The objectives of the proposed system are to overcome the difficulties
encountered with the existing manual system as well as to keep the objectives and
features of the traditional manual system. The objective of the project is summarized as:

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

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 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

3. Introduction to System Development Life Cycle

System Development, a process consisting of two major steps of System
Analysis and design, starts when Management or sometimes systems development
personnel realize that a particular business system needs improvement.
The Systems Development Life Cycle (SDLC) method is thought of as the set of
activities that analysts, designers and users carry out to develop and implement an
information system. The Systems Development Life Cycle method consists of the
following activities: -

1. Preliminary investigation, which comprises of Feasibility Study.

2. Determination of System Requirements.
3. System Design.
4. System Testing.
5. Implementation.

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

3.1 Economic Feasibility:

Economic analyses are used for evaluating the effectiveness of the proposed
system. More commonly known as cost/benefit analyses; the procedure is to determine
the benefits and saving that are expected from a proposed system and compare them
with costs. If benefits outweigh costs, a decision is taken to design and implement the
system. Otherwise, further justification or alternative in the proposed system will have
to be made if it is to have a chance of being approved. This is an ongoing effort that
improves in accuracy at each phase of system lifecycle. As it is the first phase of the
project, the cost is estimated.

3.2 Technical Feasibility

In examining technical feasibility, configuration of the system is given more
importance than the actual make of hardware. The configuration should give the
complete picture about the systems requirements: This can be used as a basis for the
tender document against which dealers and manufacturers can later make their
equipment bids. Specific hardware and software products can then be evaluated keeping
in view with the logical needs.
The technical issues usually raised during the feasibility stage of the
investigation include the following:

Does the necessary technology exist to do what is suggested?

Does the proposed equipments have the technical capacity to hold

the data required to use the new system?

Will the proposed system provide adequate responses to inquires,

regardless of the number or location of users?

Can the system be upgraded if developed?

Are there technical guarantees of accuracy, reliability, ease of

access and data security?

15

3.3 Operational Feasibility:

Proposed projects are beneficial only if they can be turned out into information
systems. That will meet the organizations operating requirements. An operational
feasibility aspect of the project is to be taken as an important part of the project
implementation. Some of the important issues raised to test the operational feasibility of
a project include the following:

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

System analysis is a detailed study of the various operation performed by a

system and their relationship within and outside the system. It is a systematic technique
that refines goals and objectives. The goal of system development is to deliver the
system in line user requirement
And analysis is the heart of this process. One of the best approaches to system analysis
is the structured analysis.

Structure analysis is a set of technique and graphical tools that allow us to

develop new kind of specifications that is easily understandable to the developer. It is
the detailed step by step
Investigation of the related procedure to see what must be done and to determine the
best way of doing it. The objective is to build a system specification that provides the basis for
design and implementation.

Tools used in System Analysis and Design

E-R Diagram

Data Flow 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

There are three basic elements in ER models:

Entities are the "things" about which we seek information.
Attributes are the data we collect about the entities.
Relationships provide the structure needed to draw
information from multiple entities.

Entity-Relationship diagram of HOTEL MANAGEMENT SYSTEM can be

depicted as follows-

21

Entity Relationship Diagram

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

4.2 DATA FLOW DIAGRAM

As the information moves through the system, it is modified by a series of

transformations. A Data Flow Diagram is a graphical technique that depicts information
flow and the transformation that are applied as the data Moves from input to output. A
DFD may be used to represent a System at any level of abstraction. DFDs may be
partitioned into levels that represent increasing information flow and functional detail. A
Level- 0 DFD, also called Context Diagram, represent the entire system as a single
24

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

Basic notation used to create the DFD:

The basic notation used to create the DFD of the SMS is illustrated below:
1. External Entity:The producer or the consumer of information that resides outside the
bounds of the system to be modeled. It is denoted by the following rectangular shape.

2. Process:Transformation of the information residing within the bounds of the

system to be modified. The following shape denotes it.

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. Context Diagram(0 level

DFD)

Request for login

USER

1.0
User Login Process

27

Login
details

login_tabl

Check for room

availability

2.0
Availability Check
process

Accept Customer

Print Out Receipt

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 Flows and Data Stores

Sl.No Field Name

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

implementation plan, and prepare logical design walk through.

The physical design maps out the details of the physical system; plans the
system implementation plan and specifies hardware and software. System design
translates the system requirement into the ways of the system as recommended in the
feasibility study.
Thus the system design is the translation from user-oriented document a
document oriented to a programmer or a database personal. System design is a highly
creative process that can be greatly facilitated by the followingStrong Problem Definition
Pictorial description of the Existing System

33

Set of Requirements of the new system

5.1.1 Database Design:

The general purpose of database is to handle information as an integrated form.

A database is a collection of interrelated data, stored with minimum redundancy. In
database design, several objectives are considered.
1) Controlled redundancys unique aspect of database design is starting data only
once, which redundancy and improves performance.
2) Easy to learn and use
3) Data independence
4) Accuracy and integrity
5) Privacy and security
6) Performance improvement
A Database can be thought of as a set of logically related files
organized to facilitate access by one or more applications programs and to
minimize the data redundancy. Intact, a Database is defined as a stored
collection of data, organized on the basis of relationships in the data rather
than the convenience of storage structures. It is not a replacement of files.

The database tables that are used in Hotel Management System are
shown below:

34

5.1.2 TABLE DESCRIPTION:

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:

Basically database normalization is the process of efficiently organizing data in a

database. There are two goals of the normalization process: eliminate redundant data
and ensure data dependencies make sense. Both of these are worthy goals as they reduce
the amount of space a database consumes and ensure that data is logically stored.
37

5.2.1 First Normal Form:

The normalization process involves getting our data to conform to three

progressive normal forms, and a higher level of normalization cannot be achieved until
the previous levels have been achieved (there are actually five normal forms, but the last
two are mainly
In our case database has been normalized in 1NF, since there is not any
non-atomic field.

5.2.2 Second Normal Form:

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.

5.2.3 Third Normal Form:

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

In the proposed system we optimized different types of the codes

such as conditional and looping etc.
Un optimized Code:
Eg.
If (condition1>condition2)
{
If (condition1>condition3)
{
Statement;
}
}
Optimized Code:
Example:
If (condition1>condition2 && condition1>condition3)
{
Statement;
}
Necessary check constraints have been declared to restrict unauthorized
accessing and retrieving of data. The system has been designed to prompt the user and
request for valid data. The access time and delay in the conversion is taken on priority
for the efficiency of the system.

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.

Any engineered product can be tested in one of two ways:

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.

Black Box Testing

The first test approach is called black box testing and it alludes to tests that are
conducted at the software interface. It is used to demonstrate that software functions are
operational, that is the input is correctly accepted and the output is correctly produced,
and the integrity of the external information (e. g. a database) is maintained. A blackbox test examines some fundamental aspect of a system with little regard for the internal
logical structure of the software. During the black-box tests, those errors, which came to
the light, were removed and validation were put through to allow correct input of data
and accordingly the correct output is displayed. To prevent occurrence of wrong input of
data, a check constraint is added to prompt the user.

45

White Box Testing

White box testing also known as Glass box testing is next approach of testing
where the control structure of the procedural design is derived to test case. With the help
of this test we can derive test cases that1. Guarantee that all independent paths within a module have been
exercised at the least once.
2. Exercised all logical decision on their true or false sides,
3. Execute all loops at their boundaries and within their operational bonds
and
4. Exercised internal data structures to ensure their validity.
The white box test is useful to determine the following types of errors:
Incorrect

assumption

and

logical

errors

are

inversely

proportional to the probability that a program path will be

executed.
We often believe that a logical path is not likely to be executed
when in fact; it may be executed on a regular basis.
During the translation of program into programming language source code it
misspell,errors will occurs randomly. These errors are corrected by syntax checking
mechanism.

Alpha, Beta & Acceptance Testing

It is virtually impossible for us to foresee as to how the customer will really use
a program. Instruction for use may be misinterpreted, strange combination of data may
be regularly used, and output that seemed clear to us could be unintelligible to a user in
the field. If software is developed as a product to be used by many customers, it is
impractical to perform formal acceptance tests with each one. To uncover the errors that
the end-user may face, we have carried out the alpha and the beta test.

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

Room Booking Form :

Check Out Form :

52

New Room Creation Form :

Set New Rate Form :

53

Room Information Form :

Room Search Form :

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

2. If there is a virus attack as the stored information might get corrupt.

3. Administrator needs to keep the password and his login name secret.
4. This project is not tested in certain situations such as power failure during
transactions and then what will happen to the data store.
Though we have tried our best to fulfill all the necessities of the system while
developing the software, there is every possibility of some draw back in the system. So
this drawback can overcome by further modification.

CHAPTER

BIBLIOGRAPHY

58

10

59

Chapter10

Bibliography

Books

1. Software Analysis and Design- Elias M. Awad

2. Software Engineering- Rajib Mall
3. Fundamental of Database Systems- Elmasri, Navathe, Somayajulu,Gupta
4. Database Management System-Alexis Leon and Mathews Leon

60

5. Learn To Program Visual Basic-John Smiley

61