INTRODUCTION

The hospital management system contains computerized patient registration,

sorting of their information into the system, and patient registration. The software
can automatically provide a search facility for each patient and the employees. It
has a search feature that lets you see each availability's status. The availability of a
doctor and patient information can be searched for by the user. With the use of a
username and password, one can access the hospital management system. A
receptionist or an administrator can access it. They alone can add data to the
database. The information is simple to retrieve.
The user interface is quite simple.
Data processing is quick and very well for personal usage. For
multispecialty hospitals, the Health Board System is created to cover a variety of
hospital administrative procedures. The management of hospital analysis and
activity-based pricing can be increased using hospital management systems[03,05].
The hospital management system enables you to grow your business and enhance
productivity and work quality[02]. The goal of the hospital management system
project is to simplify all management processes, including patient registration,
doctor appointments, and prescription writing.

The user must go through a few registers. Time is lost because of this.
Therefore, using this system will make it simple to manage everything process.
Therefore, the development team are designing this system that can help both
patients and hospital workers using the motivation of this scenario, which was
frequently performed in hospitals[01,05]. So, the stakeholders would like to have
this system that makes hospitals work quickly and efficiently.
 II. LITRATURE REVIEW

Initially, a collection of results was gathered from the databases that were
searched using various keywords. Only studies that used maturity models were
examined from the results. The studies that did not make use of maturity models
were dropped. Operational efficiency and wait times across various procedures,
departments, and people are two of the biggest problems current hospital
management systems are facing[4]. The solution includes visual simulation and
gives users the power to examine current processes and make necessary corrections
to boost service levels and process efficiency. A final sample of 41 surveys was
created because of this method. 82.93% of them are spread among a variety of
pieces, with doctorate dissertations making up 7.32% and expert's dissertations
9.76% of the total.[3,7]

A. Existing Systems
B.
Organization's storage on a daily basis. All of these details are currently kept
in the file system. There will accumulate several files because of this daily basis.
The hospitals manage and handle every single task by hand. Therefore, it could
require a lot of time and effort to complete each activity. A lot of labor is required.
At the moment, manual processes are used only in Zone Hospital to manage daily
operations. Patients will schedule appointments with doctors and lab tests with the
receptionist. Only at hospitals may patients purchase pharmacy items; there is no
option for patient delivery. Only at the hospital are the healthcare options offered
to patients. All the patient details, doctor details, lab test results are manually taken
on papers and feuded on computer latterly. And the reports will be generated by
hands with the help o experts.

C. Existing System Problem

D.
The existing system requires a lot of time. Absence of security components Every
task needs to be completed by hand. The majority of tasks and activities depend on
specialists and human resources. No direct communication with the senior officers.
The accuracy level is subjective. High expense is required for manual system
management. Difficulty in getting backup data and transfer data. Difficulty in
inserting IoT technology and robotic intelligent. Manual system in lack in user
friendliness and it not that much reliable with current technological world.

Problem Introduction:

Lack of immediate retrievals:- The information is very difficult to retrieve and to

find particular information like E.g. To find out about the patient's history, the user
has to go through various registers. This

results in in convenience and wastage of time. Lack of immediate information

storage :

The information generated by various transactions takes time and efforts to be

stored at

right place. Lack of prompt updating: -

Various changes to information like patient details or immunization details of child

are difficult to make as paper work is involved

Error prone manual calculation:- Manual calculations are error prone and take a lot
of time this may result in incorrect information. For example calculation of
patient's bill based on various treatments.

Preparation of accurate and prompt reports:-

This becomes a difficult task as information is difficult to collect from various

register.

Goals

1-User friendly 2-Simple fast

3-Low cost and effective 4-It deals with the collection of patient's information

5- Diagnosis

1.5 Objective:-

1) Define hospital

2) Recording information about the Patients that come.

3) Generating bills.

4) Recording information related to diagnosis given to Patients.

5) Keeping record of the Immunization provided to children patients.

6) Keeping information about various diseases and medicines available to cure

them

These are the various jobs that need to be done in a Hospital by the operational
staff and Doctors. All these works are done on papers

Scope of the Project:-

1) Information about Patients is done by just writing the Patients name, age and
gender. Whenever the Patient comes up his information is stored freshly. 2)
Bills are generated by recording price for each facility provided to Patient on
a

1. Separate sheet and at last they all are summed up. 3) Diagnosis information
to patients is generally recorded on the document, which contains Patient
information. It is destroyed after some time period to decrease
 2. The paper load in the office. 4) Immunization records of children are
maintained in pre-formatted sheets, which

3. Are kept in a file. 5) Information about various diseases is not kept as any
document. Doctors

4. Themselves do this job by remembering various medicines. All this work is

done manually by the receptionist and other operational staff and lot of

5. Papers are needed to be handled and taken care of Doctors have to remember
various

6. Medicines available for diagnosis and sometimes miss better alternatives as

they can't remember them at that time.

1.7 MODULES:

The entire project mainly consists of 7 modules, which are Admin module

 User module (patient)

 Doctor module

 Nurse module

 Pharmacist module

 Laboratories module

 Accountant module

Admin module:-
Manage department of hospitals, user, doctor, nurse, pharmacist, laboratories
accounts.

 watch appointment of doctors

 watch transaction reports of patient payment Bed ward, cabin status

 watch blood bank report watch medicine status of hospital stock

 watch operation report watch birth report

 watch diagnosis report

 watch death report

User module(patient):

 View appointment list and status with doctors

 View prescription details View medication from doctor

 View doctor list View blood bank status

 View operation history

 View admit history: like bed, ward

Accountant module:

 Create invoice for payment

 Order invoice to patient

 Take cash payment Watch payment history of patients

 Manage own profile

 SCOPE OF THE PROJECT

It may help collecting perfect management in details. In a very short time, the
collection will be obvious, simple and sensible. It will help a person to know
the management of passed year perfectly and vividly. It also helps in current all
works relative to Inventory. It will be also reduced the cost of collecting the
management & collection procedure will go on smoothly.

The present project has been developed to meet the aspirations indicated in the
modern age. An attempt has been made through this project to do all work ease
& fast. It provide current add, Update, Move Next, Move Previous , Move
Last, Find & Delete all facilities to accomplish the desired objectives. The
facility Include in this project and the suggested activities have been organized
to impart knowledge & develop skill & attitude in the Service official works.

(i) System Design (Introduction):

The systems objectives outlined during the feasibility study serve as

the basic from which the work of system design is initiated. Much of the
activities involved at this stage is of technical nature requiring a certain degree
of experience in designing systems, sound knowledge of computer related
technology and through understanding of computers available in the market and
the various facilities provided by the vendors. Nevertheless, a system cannot be
designed in isolation without the active involvement of the user. The user has a
vital role to play at this stage too. As we know that data collected during
feasibility study wills we utilized systematically during the system design. It
should, however be kept in mind that detailed study of the existing system is
not necessarily over with the completion of the feasibility study. Depending on
the plan of feasibility study, the level of detailed study will vary and the system
design stage will also vary in the amount of investigation that still needs to be
done. This investigation is generally an urgent activity during the system.
Sometimes, but rarely, this investigation may form a separate stage between
feasibility study and computer system design. Designing a new system is a
creative process, which calls for logical as well as lateral thinking. The logical
approach involves systematic moves towards the end product keeping in mind
the capabilities of the personnel and the equipment at each decision making
step. Lateral thought implies encompassing of ideas

Beyond the usual functions and equipment. This is to ensure that no efforts are
being made to fit previous solutions into new situations.

ii) Considerations: System Design

The system design process is not a step-by-step adherence of clear procedures

and guidelines. Though, certain clear procedures and guidelines have emerged
in recent days , But still much of design work depends on knowledge and
experience of the designer. When designer starts working on system design, he
will face different type of problems. Many of these will be due to constraints
imposed by the user or limitations of the hardware and software available in the
market. Sometimes, it is difficult to enumerate the complexity of the problems
and solutions thereof since the variety of likely problems is so great and no
solutions are exactly similar.
iii)Design Objectives:

The primary objective of the design of course, is to deliver the requirements as

specified in the feasibility reports. In general the following design objectives
should be kept in mind.

Practicality

The system must be stable and can be operated by people with average.

Efficiency

This involves accuracy, timeliness and comprehensiveness to the system

output.

Cost

It is desirable to aim for a system with a minimum cost subject to the condition
that it must satisfy all the requirements.
Flexibility

The system should be modifiable depending on the changing needs of the user.
Such modifications should not entail extensive reconstructing or recreation of
software. It should also be portable to different computer systems.

Security

This is very important aspect of the design and should cover areas of hardware
reliability, fall back procedures, physical security of data and provision for
detection of fraud and abuse.
System design involves first logical design and then physical construction of
the system. The logical design describes the structure and characteristics of
features, like the outputs, inputs, files, database and procedures. The physical
construction, which follows the logical design, produces actual program
software, files and a working system.
 SYSTEM CONFIGURATION

i) HARDWARE CONFIGURATION:
CPU TYPE : Dual Core
CPU CLOCK MEMORY : 2.66 GHz Extend
RAM DDR II : 2 GB
Disk drive : DVD Writer
Keyboard : Any
Display type : LCD monitor
Printer type : laser print
Speed : 1.1 GHz
Hard Disk : 500 GB
Mouse : optical

ii) SOFTWARE CONFIGURATION:

Operating System : Windows 7

Front End : .net
Back End : Ms Access
UML Approach

UML Diagram

A diagram is the graphical presentation of a set of elements, most often

rendered as a connected graph of vertices and arcs . you draw diagram to
visualize a system from different perspective, so a diagram is a
projection into a system. For all but most trivial systems, a diagram
represents an elided view of the elements that make up a system. The
same element may appear in all diagrams, only a few diagrams , or in no
diagrams at all. In theory, a diagram may contain any combination of
things and relationships. In practice, however, a small number of
common combinations arise, which are consistent with the five most
useful views that comprise the architecture of a software-intensive
system. For this reason, the UML includes nine such diagrams:

1. Class diagram

2. Object diagram

3. Use case diagram

4. Sequence diagram

5. Collaboration diagram

6. State chart diagram

7. Activity diagram

8. Component diagram

9. Deployment diagram
USE CASE DIAGRAM:

A usecase diagram in the Unified Modeling Language(UML) is atype of

behavioral diagram defined by and created from a use-case analysis.its purpose is
to present a graphical overview of the functionality provided by a system in terms
of actors, their goals(represented as use cases),and any dependencies between
those use cases.

Use case diagrams are formally included in two modeling languages

defined by the OMG:theunfied modeling language(UML) and the systems
modeling language(sysML)

Use case diagram of our project:

Registration

Reception

Goto doctor

Take recept

doctor patient

pharmacist

laboratorist

Discharge summary
Sequence diagram:

A Sequence Diagram is an interaction diagram that emphasis the time ordering of

messages; a collaboration diagram is an interaction diagram that emphasizes the
structural organization of the objects that send and receive messages. Sequence
diagrams and collaboration diagrams are isomorphic, meaning that you can take
one and transform it into the other.

Doctor Registration Reception Patient Laboratory Pharmacy ischarge summary

1 : login()

2 : view appointment()

3 : registration()

4 : send request()

5 : done any surgeries()

6 : go to laboratory()

7 : take medicins()

8 : paitent ok()

9 : send discharge summmary()

10 : discharge paitent()
Collaboration diagram:

A Collaboration Diagram also called a communication diagram or interaction

diagram, is an illustration of the relationships and interactions among software
objects. The concept is more than a decade old although it has been refined as
modeling paradigms have evolved.

1:Takes Appointment
10:Takes Appointment from doctor

P1 : Patient R1 : Receptionist

4:confirms appointment
9:Ask for payment

7:Take medicins

3:Doctor available
5:Consult doctor

8:paitent ok

2:takes Appointment from doctor

D1 : Doctor N1 : Nurse

6:Assist doctor
 SOFTWARE SELECTION

OPERATING SYSTEM

Operating system software is a class of program which manages the

resources of the computer processing command and control program execution
as the translation of all computer operations. It is most complex program
executed on the complex yet must also be the most reliable. An operating
system irrespective of whether it is being used on a microcomputer,
minicomputer or mainframe computer. An operating system plays three basic
roles as a manager, as a command processor and as a controller. An operating
system can be a single user, a multiuser, a multitasking in this project we have
used Window 7 and MS Dos as operating system.

M.S.WORD
Microsoft word was first released in 1983 under the name multi-tool
word for system versions were later written for several other platforms. It
became part of the suite, in which it is referred to as Microsoft office word,
although it is still also sold as a standalone product or bundled with a full
featured word processing program for windows and the Macintosh from
Microsoft, it is sophisticated program with rudimentary desktop publishing
capabilities that has become the most widely used word processing applications
on the market the first various of word come out under dos and provided both
graphics-based and text-based interfaces for working with a document.

WINDOW 7

The difference being that the server Versions are designed to be dedicated
servers. The clients versions of windows may also share data over the network
and can be configured to grant access to all are specific files only. Windows
PC’s are used to access a verify of servers on the networks, including windows
servers, UNIX, Linux and network servers and mainframes. The most widely
used operating system for desktop and Laptop computer developed by the
Microsoft window primarily runs on the x 86-based CPU windows provide a
graphical user interface and desktop environment in application displayed in
resizable movable windows on screen. Window comes in both client and server
various, all of which support networking Windows 95 was the first 32-bit
windows operating system and a major upgrade from windows 3.1 it used an
entirely different user interface that incorporated the now common start menu
and taskbar. It was also the first time the computer booted directly into
windows, rather than being loaded after booting up in dos. Windows 98 was an
upgrade to Windows 95 that tightly integrated the internet explorer, web
browser with the O/S. In 1999 windows 98 second edition fixed numerous bugs
and upgraded its applications.

MS-DOS

Ms-dos (for micro soft disk operating system) is a commercialized by

Microsoft. It was the most widely used member of the family of operating
system and was the dominant .The operating system for during the 1980’s it has
gradually been replaced on customer desktop computers with various
generation of the operating system.dos commonly refers to the family of
closely related a single user operating system from Microsoft for the PC. It was
the first O/S for windows 3.1, 95, 98 , Window NT 2000, XP and 7 emulate dos
in order to support existing dos application.
VB.Net2010
Visual Basic.NET is the next generation of Microsoft's popular Visual Basic
programming languages. Some programmers refer to the new incarnation as
VB.net, but this is incorrect. VB.net is actually not backwards-compatible with
VB6, meaning that code written in the old version will not compile under
VB.net. In fact, the languages are sufficiently different that many programmers
consider them independent. As a language, VB.net has the following traits:

Object-Oriented:-

VB.NET included limited support for object-oriented design.

Encapsulation was supported with Public and Private Data types in Classes, as
well as special accessory /matador Pairs called Properties (a feature unique to
Visual Basic). Polymorphism received crude Support through the Implements
keyword, which would require that one class implement all of the methods in
another, skeleton class. Inheritance was neglected completely. As of VB.NET,
all of this has changed. As with all 2013 languages, concepts, VB.NET includes
full-Blown support for object-oriented

Including simple inheritance. Unlike most other OOP languages, everything in

VB.net is an object, including all of the primitives (Short, Integer, Long, String,
Boolean, etc.) as well as types, events, and even assemblies. Everything inherits
from the Object base class.

Event-Driven:-

All previous versions of Visual Basic.net were event-driven, but this feature is
heavily enhanced under the vb.net framework. Events are no longer recognized
because they use certain naming convention (Object Name Event Name), but
now are declared with a Handles Object Name. Event Name clause. Event
handlers can also be declared at runtime using the Add Handler command.
 SYSTEM ANALYSIS

The system analysis part is done by the following six steps

I. Preliminary Investigation
II. Feasibility Study
III. Fact Finding Techniques
IV. Cost Benefit Analysis
V. Entity Relationship Model
VI. Data Flow Diagram
VII. Normalization

i) Preliminary Investigation

   Here in the project Hotel Management System, a detailed study of existing

system is carried along with all the steps in system analysis. An idea for
creating a better project was carried and the next steps were followed. A
detailed study of the process must be made by various techniques like
interviews, questionnaires etc. The data collected by these sources must be
scrutinized to arrive to a conclusion. The conclusion is an understanding of
how the system functions. This system is called the existing system. Now the
existing system is subjected to close study and problem areas are identified.
The designer now functions as a problem solver and tries to sort out the
difficulties that the enterprise faces. The solutions are given as proposals. The
proposal is then weighed with the existing system analytically and the best one
is selected. The proposal is presented to the user for an endorsement by the
user. The proposal is reviewed on user request and suitable changes are made.
This is loop that ends as soon as the user is satisfied with proposal.  Preliminary
study is the process of gathering and interpreting facts, using the information
for further studies on the system. Preliminary study is problem solving activity
that requires intensive communication between the system users and system
developers. It does various feasibility studies. In these studies a rough figure of
the system activities can be obtained, from which the decision about the
strategies to be followed for effective system study and analysis .

ii) Feasibility Study

An important outcome of the preliminary investigation is the
determination the at the system requested is feasible. Feasibility study is carried
out to select the best system that meets the performance requirements.

Feasibility study is both necessary and prudent to evaluate the feasibility of the
project at the earliest possible time. It involves preliminary investigation of the
project and examines whether the designed system will be useful to the
organization. Months or years of effort, thousand for millions of money and
untold professional embarrassment can be averted if an in-conceived system is
recognized early in the definition phase.

The different types of feasibility are: Technical feasibility, Operational

feasibility, Economical feasibility.

Technical Feasibility
Technical Feasibility deals with the hardware as well as software requirements.
Technology is not a constraint to type system development. We have to find out
whether the necessary technology, the proposed equipments have the capacity
to hold the data, which is used in the project, should be checked to carry out
this technical feasibility.
The technical feasibility issues usually raised during the feasibility stage
of investigation includes these
 This software is running in windows 2000 Operating
System, which can be easily installed.
 The hardware required is Pentium based server.
 The system can be expanded.

Behavioral Feasibility
This feasibility test asks if the system will work when it is developed and
installed Operational feasibility in this project:

 The proposed system offers greater level of user-

The proposed system produces best results and gives
high performance. It can be implemented easily .So this
project is operationally feasible.

Economical feasibility
Economical Feasibility deals about the economical impact faced by the
organization to implement a new system. Financial benefits must equal or
exceed the costs. The cost of conducting a full system, including software and
hardware cost for the class of application being considered should be evaluated.
Economic Feasibility in this project:

The cost to conduct a full system investigation is possible.

iii) Fact Finding Techniques

The various document of the office was studied and after a short interview the
fact finding was finished and certain
questions were arising that:

1. Whether there is any problem of retrieval.

2. Whether there is any extra Guide needed.
3. Whether you want the proposed system of Hardware detailing.
4. Whether the office member is benefited or not.
5. Whether they are ready to accept the changes or not.
And afterwards it was found that:

1. No problem of retrieval.
2. There is no extra Guide is needed.
3. Yes they want the proposed system of Hardware Detailing.
4. Yes office member is benefited.
5. Yes they are ready to accept the changes.

iv) Cost Benefit Analysis

A system is also expected to provide benefits. The first task is to identify and
then assign a monetary value to it for cost / benefit analysis.
The two major benefits are improving performance and minimizing the
cost of processing. The performance category emphasize in the accuracy of the
result or access to information and easier access to the system by authorized
users.
Our software has fulfilled all the benefits very well. Our software are
improving and minimizing the cost of processing. Our software has controlled
error and caused reduction of staff.
Tangible or Intangible cost and benefits:-

An outlay of case for a special file item or activity is referred to as a

tangible cost. The purchase of hardware or software, personal training and
employees salaries are examples of tangible cost in our software we have
included training and employee salaries approx 300 /- to be paid for
training and we have saved the salary of 3 employees but training cost is
one time cost and hence we have saved 3 x 5000 = 15000 /- per month.
V) Data Flow Diagram
Data flow oriented techniques advocate that the major data items
handled by a system must be first identified and then the processing required on
these data items to produce the desired outputs should be determined. The DFD
(also called as bubble chart) is a simple graphical formalism that can be used to
represent a system in terms of input data to the system, various processing
carried out on these data, and the output generated by the system. It was
introduced by De Macro (1978) , Gane and Sarson (1979).The primitive
symbols used for constructing DFD’s are:
Symbols used in DFD :
 A circle represents a process.

A rectangle represents external entity

A square defines a source or destination of the system data.

An arrow identifies dataflow.

Double line with one end closed indicates data store

vi) Normalization

Normalization is a data analysis technique that organizes the data such

that they are grouped to form non-redundant, stable, flexible and adaptive
entities. Normalization is a three stem technique that places the data moved in
3N forms.

We can easily change the database without rewriting many or the entire
program that used those databases.

We can make our data model as application independent as possible to

encourage the Database structure that can be extended to modify without
impact to current program.
 I. Simply stated entity in 1NF if there are no attributes that can have more than
one value for single instance of the entity any attribute that can have multiple
values actually describe a separate entity possibly an entity and relationship.

II. An entity is in 2NF if it is already in 1NF and if the value of all non primary
key attributes that are dependent on only part of primary key should be moved
to any entity where that partial key is actually the full key. That may require
creating a new entity and relationship of model.

III. An entity is in 3NF if it is already in 2NF and if the value of it non primary
key attributes that are not dependent on another non primary key attributes.
Any non primary key attributes that are dependent on other non primary key
attributes must be moved or deleted. Again new entities and relationship may
have to be added to the data model. For our convenience we have not taken the
concept of Normalization in consideration in our project.
 IMPLEMENTATION

Implementation is the stage of the project when the theoretical design is turned
out into a working system. Thus it can be considered to be the most critical
stage in achieving a successful new system and in giving the user, confidence
that the new system will work and be effective.
The implementation stage involves careful planning, investigation of the
existing system and it’s constraints on implementation, designing of methods to
achieve changeover and evaluation of changeover methods.
Implementation Review:
After the system is implemented and conversion is complete, user usually
conducts a review of the system. User usually conducts a review of the system.
 In this system all Requirements are fulfills.
 The user can easily insert, update and delete the
record in Efficient way.
 This system is user-friendly and easily understands.
 User can view the Purchase Report and Sales Report So,
user can speedily work in this system .
 The performance level of users has improved.
 Data record can be easily stored.
 DATA DICTIONARY

Field type Appropriate Uses Storage Space

Text Data containing text, a Based on what’s

combination of text and actually stored in
numbers, or numbers that the field; ranges
don’t need to be included from 0 to 255
in calculations. Examples bytes
are name, addresses,
department codes, and
phone numbers.

Memo Long text and numeric Ranges from 0 to

strings Example are notes 65,536 bytes.
and description
Number Data that’s included in 1, 2, 4 or 8
calculation (excluding bytes,depending
money). on the field size
Examples are ages, codes selected (or 16
(such as employee Bytes for
IDs),and payment Replication ID).
methods
Date/Time Dates and times ex. Are 8 bytes
Date ordered ,birth date

Auto number Unique sequential or 4 bytes (16 bytes

random numbers ex. for replication
invoice number and ID).
project number
 DATABASE –DESIGN
A database is an organized mechanism that has the capability of storing
information through which a user can retrieve stored information in an effective
and efficient manner. The data is the purpose of any database and must be
protected.
The database design is a two level process. In the first step, user requirements
are gathered together and a database is designed which will meet these
requirements as clearly as possible. This step is called Information Level
Design and it is taken independent of any individual Database Management
System (DBMS).

Organization of the data in the database is aimed to achieve. In the second

step, this Information level design is transferred into a design for the specific
DBMS that will be used to implement the system in question. This step is
called Physical Level Design, concerned with the characteristics of the specific
DBMS that will be used. A database design runs parallel with the system
design. The following two major objectives.
 Data Integrity
 Data independence
 SYSTEM TESTING

The purpose of testing is to discover errors. Testing is the process of trying

to discover every conceivable fault or weakness in a work product. It provides a
way to check the functionality of components, sub-assemblies, assemblies and/or a
finished product It is the process of exercising software with the intent of ensuring
that the
Software system meets its requirements and user expectations and does not fail in
an unacceptable manner. There are various types of test. Each test type addresses a
specific testing requirement.

TYPES OF TESTING:

Unit testing:

Unit testing involves the design of test cases that validate that the internal
program logic is functioning properly, and that program inputs produce valid
outputs. All decision branches and internal code flow should be validated. It is the
testing of individual software units of the application .it is done after the
completion of an individual unit before integration. This is a structural testing, that
relies on knowledge of its construction and is invasive. Unit tests perform basic
tests at component level and test a specific business process, application, and/or
system configuration. Unit tests ensure that each unique path of a business process
performs accurately to the documented specifications and contains clearly defined
inputs and expected results.

Integration testing:

Integration tests are designed to test integrated software components to

determine if they actually run as one program. Testing is event driven and is more
concerned with the basic outcome of screens or fields. Integration tests
demonstrate that although the components were individually satisfaction, as shown
by successfully unit testing, the combination of components is correct and
consistent. Integration testing is specifically aimed at exposing the problems that
arise from the combination of components.

Functional test:

Functional tests provide systematic demonstrations that functions tested are

available as specified by the business and technical requirements, system
documentation, and user manuals.
Functional testing is centered on the following items:
Valid Input : identified classes of valid input must be accepted.
Invalid Input : identified classes of invalid input must be rejected.
Functions : identified functions must be exercised.
Output : identified classes of application outputs must be exercised.
Systems/Procedures: interfacing systems or procedures must be invoked.

Organization and preparation of functional tests is focused on requirements, key

functions, or special test cases. In addition, systematic coverage pertaining to
identify Business process flows; data fields, predefined processes, and successive
processes must be considered for testing. Before functional testing is complete,
additional tests are identified and the effective value of current tests is determined.

System Test:

System testing ensures that the entire integrated software system meets
requirements. It tests a configuration to ensure known and predictable results. An
example of system testing is the configuration oriented system integration test.
System testing is based on process descriptions and flows, emphasizing pre-driven
process links and integration points.

White Box Testing:

White Box Testing is a testing in which in which the software tester has
knowledge of the inner workings, structure and language of the software, or at
least its purpose. It is purpose. It is used to test areas that cannot be reached from a
black box level.

Black Box Testing:

Black Box Testing is testing the software without any knowledge of the inner
workings, structure or language of the module being tested. Black box tests, as
most other kinds of tests, must be written from a definitive source document, such
as specification or requirements document, such as specification or requirements
document. It is a testing in which the software under test is treated, as a black
box .you cannot “see” into it. The test provides inputs and responds to outputs
without considering how the software works.

Unit Testing:

Unit testing is usually conducted as part of a combined code and unit test
phase of the software lifecycle, although it is not uncommon for coding and unit
testing to be conducted as two distinct phases.

Test strategy and approach

Field testing will be performed manually and functional tests will be written in
detail.

Test objectives

 All field entries must work properly.

 Pages must be activated from the identified link.
 The entry screen, messages and responses must not be delayed.
Features to be tested

 Verify that the entries are of the correct format

 No duplicate entries should be allowed
 All links should take the user to the correct page.

Integration Testing:

Software integration testing is the incremental integration testing of two or more

integrated software components on a single platform to produce failures caused by
interface defects.
The task of the integration test is to check that components or software
applications, e.g. components in a software system or – one step up – software
applications at the company level – interact without error.

Test Results:

All the test cases mentioned above passed successfully. No defects

encountered.

Acceptance Testing:

User Acceptance Testing is a critical phase of any project and requires significant
participation by the end user. It also ensures that the system meets the functional
requirements.

Test Results:
 All the test cases mentioned above passed successfully. No defects
encountered.
 CONCLUSION

The aim of this project was to save the time, make the processing faster
and accurate and to automate the Hotel management system. Maintaining the
activities of managerial area, which would not only help the employees
related to the services but also the members.

Thus all the objectives that were determined in the beginning were mate.
This system makes the management activities of service faster and accurate.
It increases the efficiency of the management system and changes a
complicated system to a simpler system. Though it has some limitations still
then it works efficiently.