Hospital Management

Hospital Management System
CHAPTER
NO.
1.
2.
PAGE NO.
CONTENT
Hospital Management
Main report
Introduction to HOSPITAL MANAGEMENT SYSTEM
Objective and scope
Theoretical Background
Definition Of Problem
New Computerized System
Project Description
System Analysis and Design vis--vis User Requirement
Project Model
System analysis
Data And Fact Gathering Technique
System design
System Planning
Methodology Adopted
System Implementation
Detail of Hardware & software used.
System Maintenance
System Evaluation
Feasibility study & Cost Benefit analysis
Detailed life cycle of the project
o ERD
o DFD
Context level
First level
Second level
o Methodology used for testing
Test Report
Screen Snapshot
Input screen
Output screen
Coding
3.
User Manual
Installation Guideline
Operational Guideline
Security
System Failure & Recovery
Back Up
Conclusion
Limitation
Future scope
4.
97
Annexure
Data Dictionary
References
Bibliography
Web-sites
101
2
5
7
12
13
14
14
15
15
16
17
18
System
INTRODUCTION TO HOSPITAL MANAGEMENT SYSTEM
The project that I am about to discuss here is the computerized Hospital

Management System. It is agreeable that there are a plethora of topics to choose from and
any large project would have been appealing but with the current infrastructure and time
available to me currently this project was one of few options left to me. Moreover I will be
able to check the existing conditions of already successfully running projects. This is a
database oriented project. Moreover if this project is completed fully and operated under
real life conditions with the incorporation of some advance features, it would be a very
serious stuff. My project is only the prototype of the original one. As a whole I can estimate
that with the completion of this project will enhance my analysis power and improve and
enrich my ability to solve problems systematically. In future it will obviously help me in
works related to both personal and professional life.
This project when completed can be compared to any existing system. This way I can
flaws in my project and rectify. As this project is an educational one and not a commercial
project. I the developer have the authority to rectify any flaws or to add any new features.
While working on this project I have been helped by many people with their positive
advise and encouragement. I am thankful to all of them.
INTRODUCTION
The topic has to be selected is the Hospital Management System.

The Hospital Management System is Graphical User Interface (GUI) based
package. The various activities of a hospital have been tried to represent in tabular form
using Oracle 8 as the back-end tool and the coding has been in Microsoft Visual Basic 6.0 as
the front-end tool.
The total system also have been tried to depict in the form of Context
Diagram, Data Flow Diagram and Entity-Relation Diagram. The system specification,
different methods employed such as ADO and advantage and use of database have also been
described. The project tried to provide all aspect of functions of a hospital. It has also been
provide with a menu driven utility for users so that they can easily run it according to their
concern.
OBJECTIVE AND SCOPE

OBJECTIVE :Computers are used widely nowadays in each and every sphere of life.
Computer makes work easier and less erroneous . Hence the computers , thus setting the
trend of fast automation , are now replacing most of the manual systems involving
heavy calculations and accuracy.
The main objective of the project is to develop a software named
HOSPITAL MANAGEMENT SYSTEM to computerize the works of a power
distribution company which would organize their works properly and keep their records in
proper order. The software is developed to take care :
1 > Maintaining the records of different doctors, patients and their corresponding
information .
2 > Maintaining the details of each and every department .
3 > Maintaining patients payment process.
4 > Maintaining patients invoices.
5 > Handling various type of quarries.
6 > Providing report for management.
The main objective is to design and develop a computer database so that it will be
easy to retrieve, Update and manipulate the records of different patient, doctor as well as
nurse. The purpose of the project is to create a user friendly hospital information system to
facilitate decision making. If the information user wants do not exist in database, he/she can
easily make entry in the database. To allow user to extends the project as much as he/she
wants. The system should have flexibility to the future needs like introduction of new records
of patient, doctor etc. The basic need for the Hospital Management System project is to
increase working efficiency, eradicating errors and saving time.
SCOPE :The project HOSPITAL MANAGEMENT SYSTEM aims at providing

different Nursing Homes a universal software for maintaining their various database like
patients, Doctors, invoice , payment etc and corresponding information and includes patients
details, Doctors details, patients payment process, different query handling associated with
the system. It will greatly increase the performance of the concerned personnel and
render the uphill task of maintaining the consistency in its various databases very
easily. Manual work would be reduced to a great extent , though not fully eradicated ,
and several reports would be auto generated so as to help the management in their
decision making regarding the various aspects of the market.
The computerized Hospital Management System has a vast scope. The
NURSINGHOME MANAGEMENT SYSTEM to be developed may be used in different
Hospital, Nursing Home and other Health Centre. This is possible for any
person to operate this software.

The goal of this project is to manage the huge doctor, patient etc. database as well as
to make the optimum use of the available resources.
The project can be extended to provide limited access to various persons so that some
person can only view the database while others, who are authorized persons can make
modifications to it.
However , I admit that I have merely unraveled the tip of what is an iceberg in
its scope . The major aspects have been covered and the intricate detailing could have
been handled with more viability, but owing to the platform and time requirement
some of the desired work could be complete.
THEORETICAL BACKGROUND
DATABASE DESIGN
Record-based logical models are used in describing data at the logical and view
levels. In contrast to object-based data models, they are used both to specify the overall
logical structure of the database and to provide a higher-level description of the
implementation. Record-based models are so named because the database structure is fixedformat of several types. The use of fixed length record simplifies the physical-level
implementation of database.
The relational model uses a collection of tables to represent both data and relationship
among those data. Each table has multiple columns and each column has a unique name. A
row in a table represent a relationship among a set of values.
WHAT IS DATABASE?
A database may be defined as a mechanized, centrally controlled collection of all
operational data about related entities of an organization where the data are physically
organized and stored in such a way that the features- shareability, availability, resolvability,
integrity, security and data independence are achieved.
In order to achieve the goals of a database it is obvious that in an enterprise with a
database system there should be some identifiable person who will bear the main
responsibility for the operational data, the person is called a Database Administrator (DBA).
WHY DATABASE?
To some extent the answer to these questions depends on whether the system in
question is single or multi-user? Here the database is so small and so simple that the
advantages might not be very obvious. The primary goal of a DBMS is to provide as
environment that is both convenient to use in retrieving and storing database information.
Database systems are designed to manage large bodies of information. The
management of data involves both the definition of structures for the storage of information
and the provision of mechanisms for the manipulation of information. In addition, the
database records are stored in various files and different application programs are written to
extract records from and to add records from and to add records to the files.
ADVANTAGES OF USING DATABASE

There are many advantages of using database. The main advantages are mentioned
below:Redundancy can be reduced In non-database system each application has its own private
files. This fact can often lead considerable redundancy in stored data, with resultant waste in
storage space. Sometimes for various business or technical reasons for maintaining several
distinct copies of the same stored data. Any such redundancy should be carefully controlled.
Inconsistency can be avoided Inconsistency can occur when the same subject is
represented by two distinct entries in the stored database. Supposing that the database
manager is not aware of the duplication and the two entries have not been regularly updated.
At such time the database is said to be inconsistent. An inconsistent database can supply
incorrect information to its users. If the said factor such as the duplicate or redundant entry is
removed then such inconsistency can be avoided. Alternatively, if the redundancy is not
removed but is controlled, then the database management system can guarantee the
consistency of the database. This can be achieved by updating both the entries
simultaneously.
Sharing of data - Sharing means not only the existing applications can share the data in the
database, but also that new applications can be developed to operate against the same stored
data. It also might be possible to satisfy the data requirement of the new application without
having to create any additional stored data.

Maintaining standards The centralization of data in their stored procedures under a Data
Base Administrator can ensure that all applicable standards are maintained in data
representation. Applicable standards can include all from corporate, industry departmental,
installation to national, international standards. Maintaining standards can help in data
interchange between different systems.
Maintaining data integrity The problem of data integrity is to ensure that the stored data is
accurate. The difference of information as a matter of fact regarding two entries that are
believed to be of the same subject is inconsistency and this leads to lack of integrity. The
particular problem can arise only if redundancy exists in the stored data. Even without the
presence of redundancy, the database can still contain incorrect information. The Data Base
Administrator can avoid this problem by defining integrity rules, which has to be checked or
maintained when update operation is to be carried out. Data integrity is even more important
in the multi-user database system because of the sharing of data.
Maintaining data security The Data Base Administrator having full authority over the data
of an organization can ensure that the means of accessing data by any authority of the
concerned organization has to be through the proper procedures and credentials. It can
formulate rules and regulations to check access of data regarding sensitive matters and also
restricting the same against unauthorized personals. It has also the authority of channeling
data to those only concerned with it.
Maintaining balance between requirement The Data Base Administrator having the
overall knowledge of requirement of the organization can define his own system or
restructure the existing system in such a manner that it can provide the best service to the
organization. With this service he can avoid conflict regarding data demand and also maintain
data independence.
Keeping organizational information in a final processing system has a number of major
disadvantages :
Data redundancy and inconsistency Since different programmers create the files and
application programs over a long period, the files are likely to have different formats and the
programs may be written in several programming languages. Moreover the same information
may be duplicated in many files. This redundancy leads to higher storage and access cost.
Also it may lead to data inconsistency.
Integrity problem The data values stored in database must satisfy certain types of
consistency constraints. Developers enforce these constraints in the system by adding
appropriate code in various Application programs. However when new constraints are added,
it is difficult to change the programs to enhance them. A DBMS should provide capabilities
for defining and enforcing these constraints.
Atomicity problem A computer system, like any other mechanical or electrical device, is
subject failure. In application, it is crucial to ensure that once a failure has occurred and has
been detected the data are restored to the consistent state that existed prior to the failure. It is
difficult to ensure this property in a conventional file processing system.
10

Concurrent access anomalies For the sake of overall performance of the system is
improved and a faster response time is possible, many systems allow multiple users to update
the data simultaneously. In such case, interaction of concurrent updates may result in
inconsistent data.
Security problem Not every user of the database system should be able to access all data.
For example, in HOSPITAL MANAGEMENT SYSTEM, the hospital authority need to see
only the part of the database that has information about the patient payment structure. They
do not to need to access to information about patient details. Since application programs are
added to the system in ad hoc manner, it is difficult to enforce such security constraints.
These are why we can use VISUAL BASIC also. Again Visual Basic is one of the popular
programming language.
11
Why we use SQL Server 2005?

ORACLE corporation offers a true relational DBMS. The Oracle database
gives many Advantages as follows :
1. A database structure is easy to visualize and understand.
2. The ability to create any number of temporary relationship between tables.
3. Freedom from concerns about how to query the database, through the use
of SQL.
4. Relational joins that provide temporary sets of data from tables in the model.
WHAT IS ODBC ?
Open Database Connectivity(ODBC) Provides a standard interface that allows
one application to access many different data sources. The source code does not have to be
recompiled for each data source. A database driver links the application to a specific source
code. Database driver is a dynamic link library that an application can invoke on demand to
gain access to a particular data source. A library of ODBC function calls that allows an
application to connect to a data source, execute SQL statement and retrieve results.
Microsofts ODBC industry standard data access interface continues to provide a way to
access relational data as part of the OLEDB specification. OLEDB includes a bridge to
ODBC to enable continued support for the broad range of ODBC relational database drivers.
The MS OLEDB provider for ODBC leverages existing ODBC drivers, ensuring fast access
to database for which an ODBC driver exists. OOLEDB is a strategic system level
programming interface to access data through out the organization. It encapsulates various
DBMS functions that enables the creation of software components implementing such
services. OLEDB components contains data provider, data consumer, service components.
WHAT IS ActiveX Data Objects (ADO) ?

Microsoft ActiveX Data Objects (ADO) is the strategic application programming
interface (API) to data and information. ADO provides consistent, high-performance access
to data and supports a variety of development needs, including the creation of front-end
database clients and middle-tier business objects that use applications, tools, languages, or
Internet browsers. ADO is designed to be the one data interface needed for single and multi
client/server and Web-based data-driven solution development. The primary benefits of ADO
are ease of use, high speed, low memory overhead, and a small disk footprint. ADO provides
an easy-to-use interface to OLE DB, which provides the underlying access to data. ADO is
implemented minimal network traffic in key scenarios, and a minimal number of layers
between the front end and data sourceall to provide a lightweight, high-performance
interface. ADO is easy to use because it uses a familiar metaphorthe COM automation
interface, available from all leading Rapid Application Development (RAD) tools, database
tools, and languages on the market today.
12
WHAT IS OLEDB ?
WHAT IS ACTIVEX CONTROLS ?
An ActiveX control is essentially a simple OLE object that supports the IUnknown
interface. It usually supports many more interfaces in order to offer functionality, but all
additional interfaces can be viewed as optional and, as such, a container should not rely on
any additional interfaces being supported. By not specifying additional interfaces that a
control must support, a control can efficiently target a particular area of functionality without
having to support particular interfaces to qualify as a control. As always with OLE, whether
in a control or a container, it should never be assumed that an interface is available, and
standard return-checking conventions should always be followed. It is important for a control
or container to degrade gracefully and offer alternative functionality if a required interface is
not available. It is important for controls that require optional features, or features specific to
a certain container, to be clearly packaged and marketed with those requirements. Similarly,
containers that offer certain features or component categories must be marketed and packaged
as offering those levels of support when hosting ActiveX Controls. It is recommended that
controls target and test with as many containers as possible, and degrade gracefully to offer
less or alternative functionality if interfaces or methods are not available. In a situation where
a control cannot perform its designated job function without the support of a component
category, that category should be entered as a requirement in the registry to prevent the
control being inserted in an inappropriate container.
These guidelines define those interfaces and methods that a control can expect a
container to support, although as always a control should check there turn values when using
QueryInterface or other methods to obtain pointers to these interfaces. A container should not
expect a control to support anything more than the IUnknown interface. These guidelines
identify what interfaces a control can support and what the presence of a particular interface
means.
13
DEFINITION OF PROBLEM
Here I am going to discuss the problem of manual HOSPITAL
MANAGEMENT SYSTEM. The problems are as follows :
1. Room Availability Problem

In this system when queries are asked about room availability, the persons working in
the enquiry has to negotiate registers to provide the information needed and it can be
quite time consuming. This problem can also be faced in relation to advanced booking or
emergency booking etc.
2. Billing Problem
In this system when billing procedures are to be maintained, it has often been observed
that problem arises while keeping track of patient expenses and also during updating
billing records. This problem is related with patient admission, charge, test etc and other
related thing which are required to maintain hospitals expenses.
3. Difficulty In Hospital Activity Record

If the management want some information about improving the functioning of different
departments and make amendments in their functioning, it become quite a problem to
provide all those information to the management without wasting a lot of time of those
working in the concerned departments and the management as well.
4. Problem In Making Reports Against Management Query

For manual system it is difficult and tiresome work to find proper answer of all the
queries of Management. Suppose Management wants to know the current status of all the
patients of the hospital, it will be then a laborious job to do.
PROPOSED SOLUTION
To find out solution to the raised problem during the current HOSPITAL
MANAGEMENT SYSTEM, different software is developed to eliminate the drawbacks of
the current system.
14
1. Solution Of Room Availability

In computerized Hospital Management System, different tables are maintained which
provides all the information about vacant room, room code, from bed number to bed
number in a room etc. These table help in quick update of room details and providing
proper information to search the any patients details and saves a lot of time.
2. Solution To Billing Provision

In computerized Hospital Management System, the bill formats are developed in software
which greatly reduces the work load of the billing personals. The format bills contain all
the options or services provided by the hospital to its patient and its also calculate the
total charge that the patient has to pay to the hospital. Thus the software used for billing
can provide fast services to patients thus saving a lot of time and also make the task less
complicated.
3. Solution To Hospital Activity

In computerized Hospital Management System, queries asked by the management about
information to improve the functioning of the hospital can be easily provided to the
management in a short notice by the concerned authorities. The informations are stored in
such a manner that they can be easily retrieved without accessing any other information.
4. Solution To Report Making To Management

In computerized system reporting making such as those can be done in quick time. It has
become possible only because of financial packages associated with the software and
occupying a separate domain in the system and can be accessed only by authorized
personals.
SYSTEM ANALYSIS VIS A VIS USER REQUIREMENT

System analysis is a detailed study of the various performed by this system
and their relationship within and outside of this system. Now one aspects of this analysis is
defining the boundaries of the system and determining whether and how this system is
interacting with the other related system. During this analysis stage, data are collected on the
available files and decisions points, transactions involve in the current system are noted. Now
analyzing the minutes of discussion with the clients and summarizing the problem. I am
going to analyze the following user requirement as they face a lot of problem to operating
THE HOSPITAL MANAGEMENT SYSTEM.
15

In modern world computerized systems are used almost everywhere. The last
couple of years have witnessed an upsurge of interest in computer system. Clear evidence of
this is to be found in an unprecedented growth in the software. Now lots of software are
found for various works like graphics software, banking software, voice recognition software
etc.
Software has its own strength depending on the power of the programmer. The
presented software is concerned with HOSPITAL MANAGEMENT SYSTEM, which can
be used in any hospital
In modern times faster lifestyles requires the job to be done quickly and it is hard
enough to do that job without the aid of the computer. So much of the software are now
found in the market to solve the problem. In fact, high-speed digital computer is one of the
reasons for the recent growth in software.
The level of presentation is appropriate for HOSPITAL MANAGEMENT
SYSTEM in this project. The software is made so that it serves all the necessary
requirements by THE HOSPITAL MANAGEMENT to the hospital. They will not face any
complication working on this software. The interface is very user-friendly and soothing to
their eyes. They have to know only the details about the patients and putting them in the
appropriate place is enough to store their information. The rest of the computations will be
handled by the software itself. They need not worry about the complicacy transactions. So in
a limited time span the output is very high. This is the target of this project.
PROJECT MODEL:
The linear or WATERFALL CYCLE :The development of this project is done on the basis of waterfall cycle .
A brief description of the model are as follows :The linear or waterfall cycle is a development process that centers around
planned work and is best suited for projects where the requirements can be clearly
defined . The linear cycle groups development activities into a sequence of consecutive
phase as shown in the figure which depicts the major phases concepts formation
system requirements definition system design and development. It also includes
installation and post-installation activities that usually follow the completion of
development . Each phase itself is made up of more detailed activities . Testing
proceeds is parallel with the major phases . a broad test strategy is defined at the
time of system requirements are identified Detailed test design takes place during
system design and testing is apart of the development phase . Each phase is sequence
can only commence after the previous phase has been completed. Each phase
produces one or more models or product in later phases . The models become part of
a phase report which describes what has been achieved in this phase and outlines a
plan for the next phase . The report also I include any models new or expanded
user requirements design decisions and problems encountered. This information is
used at the next phase . Phase reports are also used to keep management informed of
project progress so that management can use the reports to change project direction
16

and also allocated resources to the project . The models produced in the different
phases serve as important communication tools with communication progressing from
the usage to the implementation worlds. Thus as describe concept formation produces
a statement of requirements predominantly in user world terms. The system
specification definition produces a system specification that is usually made up of
three models : a requirement models in user terms a subject world model of the
system and abroad system level specification. Design produces a design specification
in system world terms whereas development produces the implemented system
modules .
Linear cycle phases are chosen to encouragement top down
problem solving . Designers must first define the problem to be solved and then use
an ordered set of steps to reach the solution. The linear cycle gives the project
direction and provides guidance on what should be done as the project proceeds . It is
integrated with the management process through reports on the project status and
keeping track of resource needs.
SYSTEM ANALYSIS :System Analysis focuses on the functions performed in the problem domain
and the data consumed and produced by these functions. A Data Flow Diagram
(DFD) is one of the tools for System Analysis and shows the flow of data through a
system (through procedural information is not shown ). A system basically involves a
series of input to derive a series of outputs vide some varied transformation , depicted
diagrammatically in DFDs . The process (or bubbles) in the DFDs are shown by
named Circles and Arrows entering or leaving the bubbles represented data flows . A
rectangle represents a source or sink and is a net originator or consumer of data .
DFDs are usually hierarchically organizes , which helps in progressively portioning and
analyzing large systems.
DFDs not only shown the data flow fromm the process to another in the
system but also depicts the binding of the various sub modules within the system
with due weights to the inherent checks which serve as the validation stages in
between the processes of the system . Based on the above theories , the DFDs of the
Supermarket Management System are drawn .
DATA AND FACT GATHERING TECHNIQUE :The specific method that is used for collecting data requirements is called factfinding techniques. These include interviewing , questionnaire and examining the present
report to trace its data source . More than one of these techniques is employed to
ensure an accurate and comprehensive investigation. The various tools used in the
Systems Analysis Stage to gather data: -
INTERVIEWING :-
17

This is the most common method of gathering information from current and
potential user of this system . Interviewing is a continuous process that is used by the
analyst to gradually build a model of the system and gain understanding of any
problems . Based on the current organizational structure an interview plan is prepared
as follows :
The user to be interviewed ,
The sequence in which the users to be interviewed and,
Interview plan for each user.
GROUP COMMUNICATION :This is obtained by communicating with the group through a set of
questions with probable answers.
RECORD REVIEW :Examining the present records and reports provide me with valuable
information about organization and operations. In record reviews, information that has
been recorded about the system and users is examined. Record inspection can be
performed at the beginning of the study , as an introduction, or later in the study as a
basis for comparing actual operations with what the records indicate should be
happening . The records can help analysts understand the existing system by
familiarizing them with what operations must be supported and with formal relations
within the organization.
SITE VISITS :Sometimes existing documents and facts collected through interview and
questionnaires do the provide information regarding some aspects of the system
which the system analyst must know for effective analysis and design be visiting the
place where the system is to be installed. The maxim Seeing is believing also
suggests this point ; because many exaggerate some facts or do not elaborate the
requisite facts , with a physical inspection of the site may reveal
SYSTEM DESIGN: The most creative and challenging phase of the system life cycle is the System
Design. The term design describes a final system and the process by which it is developed. It
refers to the technical specifications (analogous to the Engineers blue print) that will be
applied in the implementing the proposed system.
The steps involved in Systems Design phase are:
To determine how the output is to be produced and in what format.
18

Input data and Master files (database) have to be designed to meet the
requirements of the proposed system.
The operational (processing) phases are handled through program construction
and testing including a list of the programs needed to meet the systems
objectives and complete documentation.
Details related to justification of the system and an estimate of the impact of the
proposed system on the user and the organization are documented and
evaluated by management as a step toward implementation (approval of
steering committee is a must).
The final report compresses of : Procedural flowcharts

Record layouts
Report layouts
Hardware facilities needed and their estimated cost
Program specifications
Operating procedures and documentation
Security and auditing procedures
User Requirements: Once our analysis is complete, it is necessary to prepare a proposal. The proposal
itself may be long and detailed or relatively short, depending on the size and importance of
the project. The proposal will include various kind of information, but it must be presented in
a form of that clearly specifies the advantages of the project to the organization and its users.
It must be clear and precise and specify the goals. It must stress the advantages it will bring to
the organization and the improvements that will be made once the new system is in place.
So in my project after considering the problem of the user that they are facing a lot
in the introspective interests in the system I am going to find out the requirements of them.
Proper maintenance of the entire database.
Proper admission system.
Accurate updating.
Proper reports printing.
All sorts of proper information can be provided.
Authoritys requirements can be fulfilled.
SYSTEM PLANNING
19

The system is planned using the program Evaluation and review
technique. The following table shows the estimated time of the different phases of
the Project Development Process .
Activity
Phase
to
tm
(Hours) (Hours)
tp
(Hours)
te
(Hours)
Preceding
Activity
System Analysis
20
26
34
26.33
System Design
30
38
44
37.33
C1
Detailed Design
95
110
140
112.5
C2
Coding
130
150
165
149.11
C1
Debugging
90
100
130
103.33
C2
10
14
18
13.67
10
12
16
12.67
Unit and Integration

Testing
Validation and System
Testing
Fine Tuning
10
11
12
11.33
Implementation
10
11
12
11.33
Total Time
405
482
571
477.66
Where
- to is the smallest possible duration to complete the activity if everything goes well ,
- tm is the normal duration required to complete the activity.
- tp is the longest duration required to complete the activity if everything goes
wrong.
- te
is the estimated duration of the time needed calculated from the above time
estimates using the formula :
te = (to + 4tm + tp )/6
20

From the above estimation the project development will need approximately
478 hours . Working five hours a day it will take around 95 Days to develop the
project . The Program evaluation and review Technique or PERT is the most widely
used in project management. The objective of the project management can be
described in terms of a successful project , which has been finished on time , within
the budgeted cost and technical specifications, which satisfy the end users . Scheduling
requires the detail of starting and completion dates for each activity. A fundamental
ingredient in PERT is the use of network systems as a meaning of graphically
depicting the current problems or proposed project . When a network is being
constructed, certain conventions are followed to represent a project graphically , for it
is essential that the relationship between activities and events be correctly depicted.
Before illustrating the network representation , it is necessary to define some of the
key concept.
NETWORK DIAGRAM (PERT CHART)

( CORRESPONDING TO THE ABOVE TIME ESTIMATION)
D
C1
C2
6
E
10
H
8
G
7
F
From the above network diagram it is clear that all the activities comes under critical
path. This is because there are no parallel activities expect coding and debugging .The
delay in any one of the activities will cause delay of the entire project development .
The shortest path in the network is called the critical path . Identifying the critical path
is of great importance as it determines the duration of the entire project . Every
network has a critical path . It is possible to have multiple critical paths , if there are
ties among the shortest path .
So the critical path is:START ->1->2->3->4->5->6->7->8->9->10-> END
DURATION (DAYS): 5+7+22+30+21+3+3+2+2 = 95 DAYS.
DEVELOPMENT SCHEDULE DATES DERIVED BY THE ABOVE PERT CHART:-
21

Development Activity
Start Date
End Date
1st Nov , 2006
4th Nov , 2006
5th Nov , 2006
10th Nov , 2006
12th Nov , 2006

5th Dec , 2006
4th Jan , 2007
1st Feb , 2007
4th Feb , 2007
30th Nov , 2006

30th Dec , 2006
21st Jan , 2007
2nd Feb , 2007
5th Feb , 2007
7th Feb , 2007

9th Feb , 2007
8th Feb , 2007

10th Feb ,2007
1.
2.
3.
4.
5.
6.
7.
8.
9.
System Analysis
System
Design
Detailed Design
Coding
Debugging
Unit & Integration Testing
Validation & System
Testing
Fine Tuning
Implementation
SYSTEM IMPLEMENTATION
The implementation phase is less creative than system design . It is primarily
concerned with use training , site preparation and file conversion. During the final
testing , user acceptance is tested .
After the installation of the new system has been done , the users were given
a detailed demonstrations of the system and were trained how to handle the system
efficiently . Every screen was shown to user and was described to them .
The user also participated in a detail discussion of the project , their liking and
disliking. There were also a detail discussion about the different input types that are
to be entered and how to handle various controls.
After the completion of the training period , the users were requested to handle
the system and test the system using some data, or the data that were handled using
the previous system.
This type of system testing checks the readiness and accuracy of the system to
access , update and retrieve data from new files using old data. After successful
running the new system executes parallel with the old system.
For my project it is needed to implement a front end and a back end front
end with which a user can interact with the system and a back end i.e.
22

Where the database can be stored . Database of the market details , payment collection
files details . So in my project I have used the operating system Windows 98 . So
for storing data , which is entered from the front end , I have used a centralized
database system in Oracle 8i (Personal Edition) server . This database can be accessed
and manipulated by the system user through the front end. I have designed the front
end , by Visual Basic 6.0 so that user can easily interact with the system. To connect
the front end with the back end i.e. Visual Basic with Oracle 8iserver, to store the data I have
used the ADO Data control, known as ADODB For producing reports Data Environment is
also used to connect the front with the back end .
DETAIL OF HARDWARE AND SOFTWARE IS USED

In order to make this software up and running there is some bare minimum
necessities desired in the target computer. The necessities are listed below accordingly :
HARDWARE USES: 1. Intel Pentium IV processor 2.4GHz or above configuration

2. 128 MB of main memory
3. 60 MB of free hard disk space or above for installation
4. 52X CD-ROM drive for installation
5. 15 or bigger color monitor
6. mouse
7. standard 105 keys keyboard
SOFTWARE USES: 1. operating system Microsoft Windows 98/ME/2000/XP
2. Microsoft Visual Studio 2005
DATABASE REQUIREMENTS: -
1. SQL Server 2005
Software Used -
WINDOWS XP(Service Pack 2) : -
This is undoubtedly worlds most popular

and easy to use Operating system for
desktop computers and I have no
exception.
VISUAL STUDIO 2005 : -
I always wanted to build 32 bit windows

application and I think Visual Basic is the
easiest way to build it. From the day of its
inception, VB has turned from a tiny and
23

limited programming tool to a robust
Windows
application
development
environment. The most exciting feature of
it is the easy of use with point and click
operation. The GUI features of VB can be
used in many ways. There are also other
goodies like very short SDLC, yielding to
better productivity with less effort.
SQL Server 2005 : -
While deciding on database

platform, I was looking for a RDBMS
system, which can be used with ease and
can be maintained without much effort.
The RDBMS should also widely available.
But the main criterion was that the created
database should be portable enough. I
selected over many available RDBMS
software, but at last I found Personal
Oracle 8. And lately I decided on Oracle
due to its database security. Through my
project was not network enabled and is
developed as Personal edition and the
security is not as strictly maintained as in
network edition. But in future, I can
extend my project in network using
network version of Oracle. Then I can get
the benefit of it.
WHY USING THIS SOFTWARES?

Why Windows XP?
Microsoft Word 2000 is a program that helps to create neat and attractive documents
easily and quickly. Features like spell and grammar check, easy insertion of new sentences
and paragraphs in the already entered text, page numbering, etc., make the functioning of a
word processor easier, faster and more accurate.
Microsoft Word also allows changing the appearance of the text and organizing the
information in the document in a systematic manner. Changing the font sizes, styles and
colors, can change the appearance of the texts. A document looks more organized if we add
page numbers, page borders, headers and footers at the top and bottom of a page to display
useful information. Word also allows presenting the information in the document in a tabular
form, i.e. within tables.
After finishing the formatting of the document, we can take its printout. Word also
allows previewing the document before printing . Along with these features, Word also
supports different kinds of shapes to be drawn on the documents. It also supports hyperlinks,
24

which makes it suitable to be used in creating help files. That is why I have decided to
prepare my documentation and the help file in Microsoft Word 2000.
Why database programming: Databases and database systems have become an essential component of
everyday life in modern society . In a course of a day , most of us encounter several
activities that involve some interaction with the database. For example, if we access a
computerized library catalogue to search for a bibliographic term ; if we go to the
bank to deposit or withdraw funds ; if we make a hotel or airline reservation ; or if
we order a magazine subscription from a publisher , chances are that our activities
will involve someone accessing a database .
A database is a collection of related data that can be recorded and that have implicit
meaning . A database has the following implicit properties :
A database represents some aspects of real world are reflected in the database.
A database is a logically coherent collection of data with some inherit meaning
A random assortment of data cannot be referred to as a database.
A database is designed , built and populated with data for a specific purpose . It has
an intended group of user and some preconceived applications in which these users
are interested.
A database may be generated and maintained manually or it may be computerized .
A computerized database may be created and maintained either by a group of
application programs written specifically for that task or by a database management
system.
A database management system (DBMS) is a collection of programs that
enables a user to create and maintain a database . The DBMS is hence a generalpurpose software system that facilities the process of defining , constructing and
manipulating database for various applications. Defining a database involves specifying
the data types , structures and constrains for the data to be stored in the database is
the process of sorting the data itself on some storage medium that is controlled by
the DBMS. Manipulating a database involves such functions as queering the database
to retrieve the specific data , updating the database to reflect changes in the real
world , and generating the reports from the data . It is not necessary to use generalpurpose software. We could write our own set of programs to create and maintain the
database, in effect our own general purpose DBMS software.
Objective of Database management :-
25

The main motivation for designing a system to manage a database is the
ability to share data. Data is considered as an important resource of an organization
to be shared by a number of applications. Data is collected , validated , protected,
logically organized and stored with controlled redundancy . It should be always kept in
mind that the data is not only to be used for a number of current applications but it
has to serve also future applications. The flexibility of accommodating new
requirements enables one to meet the cardinal principle of information system design :
The system should be built to accommodate changing needs. Data independence is an
essential requirement to enable the design of application programs independent of the
physical format , storage and access of data . If an application program needs
information on where data is stores and how it is accessed , then any changes in
data location and access method will require changes in the application program too.
The application program must be recompiled and maintained. As the need of an
organization is bound to change, the format of data and storage systems will also
change to accommodate new data there by affecting all application programs.
An integrated Database management system has the following advantages :-
Controlling redundancies and inconsistency:

In non-database approach each applications has its own private files. This
fact can also lead to redundancy in stored data because each user group maintains its
own file for handling its data processing applications. The redundancy in storing data
in multiple times lead to several problems. First, there is a need to perform a single logical
update , i.e , for one add/ modify/ delete it has to be recorded for different users group
files. Second , storage space is wasted when same data is stored repeatedly and this
problem may serious for large database. Third , files that represent the same data may
become inconsistent. This inconsistency is an outcome of redundancy. In the database
approach , this inconsistency can be avoided . For consistency ,we should have a
database design that stores each logical data item . However , in some cases ,
controlled redundancy may be useful for improving the performance of queries. By
placing data all the data together, we do not have searched multiple files to collect
this data . DBMS should have the capacity to control the redundancy so as to
prohibit inconsistencies among the files.
Restricting unauthorized access:

When multiple user share a database, it is likely that some users will do not
be authorized to access all information in the database . For example , financial data is
often considered confidential, and hence only authorized person are allowed to access
such data. In addition, some users may be permitted only to retrieve data , whereas
others are allowed both to retrieve and update . Hence, the type of access operation
retrieval or update must also be controlled. Having complete jurisdiction over the
database, the DBA assure that the only means of accessed to the database is through
the proper channels and hence can be define can be security rules to be checked
whenever access is attempted. Different rules can be established for each type of
access to each piece of information in the database.
26
Data independence :
In no database approach the data in files and the applications, which
use the data , are interdependent . Thus any changes in data structure or storage
structure and access strategy will necessitate a changes in the applications even when
the purpose of the application remains unchanged. Thus programmers are to be
involved in modifications activities whenever record structures in file are expanded .
Changes in record structures, or storage structures or access strategy are inevitable
because requirements in business organization changed frequently for making
corresponding changes in applications. So it is desirable that applications should
remain immune to change in data structures, storage structures, or access strategy. In
database approach separating data from the programs that use it and thus making the
data sharable by different applications can achieved data independence.
Enforcing integrity constrains :

The data values stored in a database must satisfy certain types of consistency
constraints . For example , the balance of a bank account may never fall below a
prescribed amount. Developers enforce these constrains in the system by adding
appropriate code in various applications programs to enforce them . A DBMS should
provide capabilities for defining and enforcing these constrains.
Atomicity problems :
A computer system , like any other mechanical or electrical device , is subject
to failure . In many applications, it is critical that, if a failure occurs, the data be
restored to consistent state that existent state that existent prior to the failure.
Consider a program to transfer $50 from account A to account B. If system failure
occurs during execution of the program , it is possible that at the $50 was removed
from account A but was not credited to account B resulting an inconsistent database
state . Clearly , it is essential to database consistency that either both the credit and
the debit occur , or that neither occur. That is, the funds transfers must be atomic in
nature . It is difficult to ensure atomicity in a non-database system but it can be well
implemented through a DBMS .
Representing complex relationship among data :

A database may include numerous varieties of data that are interrelated in
many ways . A DBMS must have the capacity to represent a verity of complex
relationships among the data as well as to retrieve and update related data easily and
efficiently.
EXTERNAL LEVEL
EXTERNAL
VIEW
27
EXTERNAL VIEW

External / Conceptual mapping
CONCEPTUAL LEVEL
CONCEPTUAL SCHEME
Conceptual / internal mapping
INTERNAL SCHEME
INTERNAL LEVEL
STORED DATABASE
THREE LEVEL ARCHITECTURE

Why SQL Server 2005?
SQL Server 2005 is an object relational database management system. It has full
capabilities and functionality of a relational database , plus the features of an object
database. It includes several features for improved performance and functionality of
online transaction processing application , such as better sharing of run-time data
structure , larger buffer caches, and deferrable constrains . Data warehouse applications
will benefit from enhancements such as parallel execution of insert , update, delete
operations ; portioning and parallel-aware query optimization .Operating within the
Network Computing Architecture (NCA) framework . SQL Server 2005 supports clientserver applications that are distributed . SQL Server 2005 can scale tens of thousands
of concurrent users, support up to 512 petabytes of data , and can handle any type any
type of data, including text, spatial , sound and time series as well as traditional
structured data .
How Oracle Works?

The DBA initiates the database start-up procedure that
Reads the parameter initialization file.

Allocates memory for SGA.
Starts up the required processes.
Opens and reads the control file.
Opens the database data file for general access.
28
The DBA starts up a listener process to wait for user connection

requests.
A visual basic user makes a connection to the database through the
network using ODBC or SQL Objects for ADO.
The Listener process dispatches a Server process to handle the users
SQL requests.
The Visual Basic application passes a SQL statement to the database.
An area of shared pool is allocated for the SQL statement .
The required data is pulled into the Database Buffer Cache if it is not
already there.
Any data changes are made in memory and stored as Redo Log Entries
in the Redo Log Buffer .
Controls returns to the Visual Basic application with a result set if
appropriate.
The database writer process writes data changes back to disk
certain criteria are met .
when
The Log Writer writes changes to the Redo Log files when the changes
are committed .
System Global Area
Database
Buffer
Redo Buffer
Shared
Buffer Pool
Cache
Server
Process
29
Visual Basic
Application
Fig : Connecting to Oracle through a Server Process
Why Visual Studio 2005 ?

One of the primary reasons for the immense popularity of computers is the
speed with which they can accomplish specified tasks. However , computer
applications are not always easy to use .
Any applications has two parts:

i) User interface : This is the screen displayed by the application. We interact with
an application via the interface. Every paper has a user interface in one form of the
other. The application asks for and we provide necessary instruction using the interface.
ii) Program : Computers need clear-cut instructions to tell them what to do and when
to do . A set of instructions to carryout a specified task is called a program . This is
what goes on in the background. All interactions between the user and the application
are via the user interface. Thus , for any application to be successful it needs to have
a good user interface . The user interface makes a program is easy to use .
A good interface will be :

Easy to learn
Easy to use
Attractive
CHARACTER BASED SYSTEM
```````````````````````````````````````````````````
In a character-based system , text was the medium of information exchange .
The application displayed text , which prompted the user for the required information .
It also specifies the valid option , if any . The user then responded to this prompts by
specifying the required information using text . For example , a character based
application may generate a bill in a store here the user has to remember all the
products that are sold by the shop . There is no list from which he can select a
product from those available. The disadvantage with character based system was that
30

with each new application the user has to spend time and effort getting used to the
way it worked.
GRAPHICAL USER INTERFACE
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Interfaces that use graphics came to be known as graphical user interface
(GUI). These become very popular because the users could identify with the graphics
displayed on the screen .In every day life too , we associate more with images than
words. The primary requirement for an interface is that it is easy to use . We must be
able to react intuitively to an interface presented is such that it emulates real life .For
example consider a calculator . On a physical calculator , there are buttons for each of
the numbers and operations possible and we click on the necessary buttons to
perform the operations . With the use of GUI we can design a calculator that looks
very much like any real calculator.
THE NEED FOR VISUAL PROGRAMMING
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
There are several programming tools that allow us to build such visual
appealing and intuitive interfaces . These tools allow us to design interfaces that
employ user-friendly features such as menus , buttons , windows etc. However , the
disadvantages of such tools is that the interface is designed using code. The next step
is to code the functionality of the interface. Therefore , a programmer spends a lot of
time writing code for the user interface . Moreover, a large percentage of time is
wasted for designing the interface, determining which events occurred and then
writing the appropriate code. The functionality of each application is different, but the
user interface components that are used remain the same. This means that if the
process of building the user interfaces simplified then the time and
effort required in developing an application can be reduced. Thus was born the art of
visual programming . Moreover , visual programming enables the developers to create
the prototype of a large application easily . Such a prototype helps a user to
understand the look and feel of the application. The disadvantage of visual
programming is that it can be used only with GUI operating system such as
WINDOWS. Moreover, it requires computers of a higher configuration in comparison
to the conventional programming tools , such as
Larger capacity hard disk.
More RAM .
Faster processor .
Visual basic is one of the popular visual programming languages. Thats why I use
visual basic in my project development .
Visual Studio tools and their advantages
31

Data access features allows you to create databases, front- end applications , and
scalable server- side components for most popular database formats , including Microsoft
SQL Server and other enterprise level databases.
ActiveX TM technologies allow you to use the functionality provided by other
applications , such as Microsoft Word Processor , Microsoft Excel spreadsheet, and other
Windows applications. You can even automate applications and objects created using the
professional or Enterprise editions of Visual Basic .
Internet capabilities make it easy to provide access to documents And
applications across the internet or intranet from within your application , or to create
Internet server applications your finished application is a true .exe file that uses a
Visual Basic Virtual Machine that you can freely distribute .
Visual Studio in SQL Server World

~~~~~~~~~~~~~~~~~~~~~~~~~~~~
There are some important reasons to use Visual Basic rather than any other front-end
tool :
Capability : VB is capable of producing software as sophisticated as any of the
other data-access techniques available. There is little can be done with say Developer
2000 that cannot be implemented equally well with ADO or OO4O.
Flexibility : Not only database access VB can be used to write text Processor , an
e-mail listener , or 10,001 other tasks.
Familiarity : Being the most popular programming language in the world means
there is a steady of talented staff to add to development teams .
Popularity : Due to the popularity more magazine articles and books and Thirdparty product are available.
Open Database Connectivity :Each DBMS stores data in a particular format. For example , MICROSOFT
access stores data in .MDB file while Foxpro uses the .DBF format. The means ,
traditionally , a database application is developed keeping in mind a particular type of
database. Changing from one DBMS to another means rewriting the application to
handle data in a new format. This means a lot of time and effort is spend in
recreating the application each time we want to change databases.
In the early days of computing , organizations typically used just a single
DBMS. The databases was manipulated using applications written specifically used
just a single DBMS . The database was manipulated using applications written
specifically for this type of database or the DBMSs facilities itself. For example , if
the data is stored in ORACLE then we can use these to access in ORACLE database
PL/SQL
SQL *PLUS
32

However , over the years with the wide spread use of computing technology ,
it is found that , typically a medium to large size organization started to use different
types of DBMS. For example , in finance company , a department that deals with
deals with fixed deposit might use ACCESS as the local DBMS while the
organization level MICROSOFT SQL server / ORACLE is used to maintain data .
It is possible to build applications that are able to communicate with different
databases if we separate actual communication with the database from the application.
This is achieved if the application always gives a command in a particular manner .
This command is then translated such that it is understood by DBMS.
By using different translator between the application and the DBMS , we can
talk with databases created by different DBMS as shown in the figure below :
Application
Translator
Database
Fig: Communication with a database

So , we need a method of accessing database such that the application remains
unchanged even when the database is changed. This is referred to as Open Database
Connectivity (ODBC). ODBC defines a standard method for communication between
the application and the DBMS. This is accomplish by defining an applicationprogramming interface (API). An API in programming terms means a set of functions
that perform a particular task.
The application will call an API function to specify a particular task . The
API call is passed on the translator is referred to as the ODBC driver. It is the driver
that implements the various API such that they are under stood by DBMS. Thus ,
there is a driver for each DBMS and passes it back to the application.
While ODBC defines API that could be used to access any data , It did
not support the OO approach that was gaining popularity . OLEDB is a database
architecture that enables applications to have uniform access to data stored in drivers
information sources , regardless of location or type . OLEDB defines a set of COM
(Component object model) interfaces that enable a uniform access to data stored in
diverse DBMS. An interface is a class with all functions abstract (an abstract class in
OO is a class that has no implementation and must be implemented in the derived
class). The user derives class from these interfaces and implements them in their
application . The objects created from the classes are used for different database
actions like connecting, binding the records etc. Science ADO DATABASE defines
interfaces, it is said to be low-level and implemented directly only in OO language
like c++ , so it is not possible to directly implement OLEDB interfaces in a 4GL like
33

Visual Basic. Microsoft has solved this problem by providing ActiveX data object
(ADO) . These are Microsoft defined objects that allow data access through OLEDB.
COST BENEFIT ANALYSIS

Software development is a highly labor intensive activity. A project of large
dimension can easily turn into chaos if proper management controls are not imposed.
Therefore the project cost/expenditure and the profit gain after implementing the project has
to be taken into account. That is we have to consider the benefit analysis report.
This cost/benefit may be tangible, direct or indirect, fixed or variable. To build up
a large software all the elements required are estimated to get the development cost of the
considering project. When we consider all these requirements we can develop a cost
estimated model to find the proposed cost of the developing project. And from that model we
can track down the expenditure during the course of development. Now after implementing
the project we have to consider gain from it in terms of benefits that how much person month
has saved from this project. Therefore we have to consider the total expenditure and the
benefit gain from the project once it has been implemented. Here we express the benefit in
terms of person month that is the monthly salary of the person concerned for the system
which has to be replaced. Therefore this cost/benefit analysis report gives us the total picture
of how a company gets benefit from a candidate system once that has replaced an older one.
The project developing components like hardware, personnel, facility and supply
cost are also taken into consideration during the cost estimation. Then we identify the cost
and benefit of a given system and categories them for analysis. In addition, from that
estimated cost we track the expenditure and then calculate the benefits. For our project, let us
assume a virtual airport where this software has been installed. The cost/expenditure values
and the benefit gain to the company described here are taken as example.
Cost/Expenditure Report For Computerizing HOSPITAL MANAGEMENT SYSTEM

Sl.No.
01
02
03
04
Item
Hardware Cost
Software Cost
User Training
Supply Cost
TOTAL COST
Value In Rs.
20000.00
5000.00
5000.00
1000.00
31000.00
Now we identify each benefit and then assign a monetary value to it for cost-benefit.
These benefits may be tangible or intangible, direct or indirect. The major benefits are
improving performance and minimizing the cost of processing. Minimizing costs through an
efficient system by means of error control or reduction of staff is a measure of benefits and we
consider these into the following benefit chart.
34
Sl.No. Process
Time Taken In
Manual Operation
Time Taken In
Automated Operation
01 Patient & other

Entry form
25 min
10 min
02 Patient transaction
Entry form
90 min
15 min
03
Bill generation
45 min
5 min
04
Report list generation
40 min
5 min
Now we consider the time and effort saved after implementing this system. Therefore
we measure the time saved per transaction and from there calculate the person month saved
and finally print the same in terms of rupees.
SYSTEM ANALYSIS AND DESIGN
ENTITY RELATIONSHIP DIAGRAM

An entity relationship (ER) model is an illustration of various entities in the
system and relationship between them. An ER model is derived from business
specifications or narratives and built during analysis phase of the system development
life cycle .
Benefits of ER modeling :
Documents information for the organization in a clear , precise format.

Provides a clear picture of the scope of the information requirement .
Provides an easily understood pictorial map for the database design.
35
Offers an effective framework for integrating multiple applications.

Key components :
Entity Relationship (E-R) Analysis uses three major abstractions to
describe the system. These are :
Entity : A thing of significance about which information needs to be known.
Examples are customer , item etc.
Relationship : A named association between entities showing optionality and
degree . Examples are Tour and customer.
Attributes : Something that describes or qualifies an entity. For the employee
entity , the attributes would be employee Id , name , job, title , date of joining and
so on . Each of the attribute is either required or optional.
Symbols used in ER modeling :

An E-R diagram consists of the following
NAME
SHAPE
components :-
Rectangle
PURPOSE
Used for representing
entity types.
Ellipses

attributes.
Diamonds

relationship types.
36
Lines of Arcs
Used for linking attributes

to entity types and entity
types to relationship types.
Double Ellipses

Multi-valued attributes .
Dashed Ellipses
Used for denoting derived

attributes.
Used for indicating total
Double lines
participation of an entity
of an entity in relationship
type.
Double line rectangle

weak entity .
Double line diamonds

weak relationship.
37
E-R Diagram
Bed
No.
Fathers
Name
Phon
e No.
Doctor
s
Name
Date Of
Admission
Patien
t
ID
Patient
Patient
Name
Fees
Deposited
Floor
No.
Allo
tted
From
Bed No.
To
To Bed
No.
Patient
ID
T
e
s
t
Under
Doctor
Test
Description
Rooms
Roo
m
e
Address
t
e
d
Beds
Phone
No.
Keeps
Recor
ds
of
Statu
s
Name
System User
(Admin)
D
e
li
v
e
Reports
r
s
A
tt
e
n
e
d Address
d
Passwor
d
38
T
r
e
a
t
Doctor
s
s
Nurse
ID
Name
Specialization
ID
Phon
e
No.
Name
DATA FLOW DIAGRAM

At this stage , the existing information processing procedures are documented
in detail and studied minutely to determine what user expect a new system to do and
how it can be done in a better way . We first study the current system and how
documents flow in the system . Using this model we derive a logical equivalent of a
system and represent it by a logical data flow diagram. This is refined after finding
out from the user his information requirements and a new logical data flow diagram
is obtained . Along with this the processing rules, the data dictionary and information
provide by a system are obtained.
DFD refers to DATA FLOW DIAGRAM. System requirements in a graphical
form, which leads to modular design. A DFD (also known as bubble chart) has purpose of
clarifying system requirements and identifying major transformation that will become
part of system design. So it is a starting point of the design phase that functionally
decomposes the requirement specifications don to the lowest level of detail. A DFD
consists of series of bubbles joined by lines. The bubbles represent data
transformations and lines represent data flow in the system.
TECHNIQUE OF DATAFLOW DIAGRAM :

Dataflow diagramming is a menace of representing a system at any level of
detail with a graphic network of symbol showing data flows , data sources , data
process and data sources / destinations .
The purpose of Dataflow diagramming is to provide a semantic bridge between
users and system developers , the diagram are as follows :
Graphical , elimination thousands of words ;
Logical representation , modeling what a system does , rather than
physical model showing how it does it ;
Hierarchical representation , modeling what a system does , rather than
Physical model showing how it does it ;
Hierarchical showing systems at any level of details ; and Jargon less ,
allowing user understanding and retrieving.
39
Dataflow diagrams have the objectives of avoiding the cost of :User/developer misunderstanding of a system , resulting in a need to redo
system or in not using system .
Having to start documentation from the scratch when the physical system
changes science the logical system , what gets done often remains the same
when technology changes.
System inefficiency because a system gets computerized before It gets
systematized.
Being unable to evaluate system project boundaries or degree of Automation
resulting in a project in appropriate scope.
Tabular Representation of Symbols used in DFD: SYMBOL
MEANING
Source or Destination
of DATA
Or
COMMENTS
May be one customer or

number of customers .
External Entity.
Or
DATA flow
May be customer
Connected to purchase order
Process that transforms

the DATA
May be a clerk calculating

Payment amount.
Data Store
Can be a payment file, a

filing Cabinet or Disk
Data report
Can be some bill.
EXTERNAL ENTITIES :
1.
2.
Are named with appropriate name .

Can be duplicated , one or more times, on the diagram to avoid line
crossing.
40
3.
Determine the system boundary . They are external to the system being
studied . They are often be beyond the area of influence of the developer .
4.
Can represent another system or subsystem .
5.
Go on margins / edge or data flow diagram.
DATA FLOWS :
1.
Are represented with a line with an arrowhead on the head on the end.
A fork in a data flows means that the same data goes to two separate
destination. The same data coming from several locations can also be
jointed .
2.
Should only represent data not control .
3.
Are always named . Name is not include the word data.
4.
Are referenced by a combination of the identities of the constructs that the

data flow connects.
DATA STORE :
1.
Are generic for physical files (index cards , desk drawers, magnetic disk,
magnetic tapes , shirt pocket , human etc .
2. Are named with an appropriate name , not to include the word file
and numbered with a number proceed with a capital letter D.
3. Can be duplicated , one or more times , to avoid line crossing .
4. Can so to or more systems that share a data store ? Adding a solid strip on
the left boundary does this . This can occur in the case of some system
updating data store , while the other system access the data. For example , the
data store could be a fright rate builds and maintains , but is represented
system.
5. Are detailed in the data dictionary or with the data description
diagram.
PROCESS :
1. So data transformation or changed . Data coming into a process must be
worked on or transformed in some way . Thus, all process must
have inputs and outputs . In some case, data inputs and outputs will
only be shown at more detailed levels of the diagram . Each process is
always running and ready to accept the data.
41

2. Are represented by a circle .
3. Are named with one carefully chosen verb and object of the verb. Process is
one function or action . If there is an and in the name , you likely have
more than one function (process) .
4. Have physical location shown only for existing physical system or a
physical design being represented .
5. Should generally move from top to bottom and left to right.
CONTEXT DIAGRAM :
The Context Diagram represents the entire software element as a single bubble
with input and output data indicated by incoming and outgoing arrows , respectively .
Additional process (bubbles) and information flows paths are represented as the level
0 DFD is portioned to reveal more detail . Here , the emphasis is on the relationship
between the system and its environment. The system as a whole is represented as a
bubble , and the external entities are shown as squares from which input flows and to
which input is directed.
1St Level DFD
42
43
2nd Level DFD
PROPOSED TABLE STRUCTURE :
44
DOCTOR TABLE(primary key dcode)

FIELD NAME
TYPE
SIZE
DESCRIPTION
Doctor_ID
Varchar
Code of doctor
Doctor_name
Varchar
20
Name of doctor
Address
Varchar
45
Address of doctor
Phone_no
varchar
15
Doctors phone number
Specialization
Varchar
18
Doctors specialization
in particular field
PATIENT TABLE(primary key pcode)

FIELD NAME
TYPE
SIZE
DESCRIPTION
Patient_ID
Varchar
Code of patient
Patient_name
Varchar
20
Name of patient
address
Varchar
25
Address of patient
Father-name
Varchar
20
Phone_no
Varchar
15
Admission_date
Varchar
10
Guardian name of
patient
Patients phone
number
Date of admission
Diseases
Varchar
15
Disease of patient
Under_doctor
Varchar
15
Fees
Varchar
18
Patients treatment
under doctor
Patient deposits for
admission
NURSE TABLE(primary key ncode)

FIELD NAME
TYPE
SIZE
DESCRIPTION
Nurse_ID
Varchar
Code of nurse
Nurse_name
Varchar
20
Name of nurse
address
Varchar
25
Address of nurse
Phone_no
Varchar
15
Nurses phone
number
P_FINANCE TABLE(primary key pcode)

FIELD NAME
TYPE
SIZE
45
DESCRIPTION

pcode
Varchar
Code of patient
gbcha
Varchar
20
recha
Varchar
25
focha
Varchar
20
iIcuch
Varchar
15
medcn
Varchar
10
opcha
Varchar
10
General bed charge

of patient
Report charge of
patient
Food charge of
patient
Icu charge of
patient
Medicine charge of
patient
Operation charge
of patient
P_TRANSACTION TABLE(primary key pcode)

FIELD NAME
TYPE
SIZE
DESCRIPTION
pcode
Varchar
Code of the patient
vdoct
Varchar
20
pdate
Varchar
10
docre
Varchar
30
btest
Varchar
30
utest
Varchar
30
ecgre
Varchar
30
press
Varchar
20
missl
Varchar
40
Visiting doctor name

to the patient
Date of patients
test
Doctor remarks to
the patient
Blood test of the
patient
Urine test of the
patient
Ecg report of the
patient
Pressure of the
patient
Miscellaneous charge
of the patient
P_PATHOLOGICAL_TEST TABLE(primary key pcode)

FIELD NAME
TYPE
SIZE
DESCRIPTION
pcode
Varchar
Code of the patient
ptest
Varchar
40
Test of the patient
46

ptedt
Varchar
10
prepo
Varchar
45
undoc
Varchar
25
Test date of the

Patient
Test report of the
Patient
Patient under
Doctor
ROOM TABLE (primary key rcode)

FIELD NAME
TYPE
SIZE
DESCRIPTION
Room_ID
varchar
10
Code of the room
Floor_no
varchar
20
Tbnum
varchar
20
Flnum
varchar
20
Typat
varchar
45
From bed number

of the room
To bed number
of the room
Floor number of the
Room
Type of patient
in the room
ADMIN TABLE(primary key uname)

FIELD NAME
TYPE
SIZE
DESCRIPTION
Uname
Varchar
11
Name of the user
Passwd
Varchar
11
Password of the user
Status
Varchar
Status of the user
Coding :
frmLogin
47
Imports System.Data.SqlClient
Public Class frmLogin
Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles
Button2.Click
Dim i As Integer
i = MsgBox("really exit?", MsgBoxStyle.YesNoCancel)
If i = 6 Then
Application.Exit()
Else
End If
End Sub
Button1.Click
Dim login As String = "select *from login where User_Name='" & TextBox1.Text & "'and Password='" &
TextBox2.Text & "'"
Dim constr As String = "server=.;database=hospital_management;user id=;pwd=;Integrated
Security=SSPI"
Dim con As New SqlConnection(constr)
Dim dataadapt As New SqlDataAdapter(login, con)
Dim dset As New DataSet
dataadapt.Fill(dset, "Ajij")
Dim i As Integer
i = dset.Tables("Ajij").Rows.Count
If i > 0 Then
Timer1.Start()
Else
MsgBox("Invalid User Name or Password.", MsgBoxStyle.Information)
End If
End Sub
Private Sub Timer1_Tick(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles
Timer1.Tick
Timer1.Start()
ProgressBar1.Minimum = 0
ProgressBar1.Maximum = 100
Timer1.Interval = 100
ProgressBar1.Step = 5
ProgressBar1.PerformStep()
If ProgressBar1.Value = 100 Then
frmMenu.Show()
Me.Hide()
Timer1.Stop()
End If
End Sub
End Class
frmChngPwd
48

Public Class frmChngPWd
Button1.Click
Dim cmstr As String
cmstr = "update login set user_name = '" & TextBox1.Text & "',password='" & TextBox3.Text & "' where
password=" & TextBox2.Text & ""
Dim constr As String
constr = "Server=.;database=Hospital_Management;User id=;pwd=;integrated security=SSPI"
Dim cmd As New SqlCommand(cmstr, con)
con.Open()
cmd.Connection = con
cmd.ExecuteNonQuery()
MsgBox("User name and password updated successfully.")
End Sub
Button2.Click
Dim i As Integer
i = MsgBox("Really want to exit?", MsgBoxStyle.YesNoCancel)
If i = 6 Then
Me.Close()
frmMenu.Show()
End If
End Sub
End Class
frmAddUser
Public Class frmAddUser
Button1.Click
Dim cmstr As String = "insert into login values('" & TextBox1.Text & "','" & TextBox2.Text & "')"
Dim constr As String= "Server=.;database=Hospital_Management;User id=;pwd=;integrated
security=SSPI"
con.Open()
MsgBox("1 user name and password created successfilly.")
End Sub
Button2.Click
Dim i As Integer
i = MsgBox("Really want to exit?", MsgBoxStyle.YesNoCancel)
If i = 6 Then
Me.Close()
frmMenu.Show()
End If
End Sub
End Class
49
frmPatientAdmission
Public Class frmAdmission
Private Sub GroupBox1_Enter(ByVal sender As System.Object, ByVal e As System.EventArgs)
End Sub
Private Sub cmdAdd_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles
cmdAdd.Click
Dim cmstr As String = "insert into Patient_admission values('" & txtid.Text & "','" & cmbname.Text & "','"
& txtadd.Text & "'," & txtroomno.Text & ", '" & txtbedno.Text & "', '" & cmbroomtype.Text & "'," &
txtproomno.Text & ", '" & cmbdassigned.Text & "', '" & txtpcond.Text & "', '" & DateTimePicker1.Text & "')"
con.Open()
MsgBox("Data inserted Successfully.")
txtid.Text = ""
cmbname.Text = ""
txtadd.Text = ""
txtroomno.Text = ""
txtbedno.Text = ""
cmbroomtype.Text = ""
txtproomno.Text = ""
cmbdassigned.Text = ""
txtpcond.Text = ""
DateTimePicker1.Text = ""
End Sub
Private Sub cmdEdit_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles
cmdEdit.Click
If txtid.Text <> "" Then
Dim str As String
str = "select*from Patient_admission where Patient_admission_id='" & Trim(txtid.Text) & "'"
Dim da As New SqlDataAdapter(str, constr)
Dim ds As New DataSet
da.Fill(ds, "Ajij")
Dim dr As DataRow
For Each dr In ds.Tables("Ajij").Rows
txtid.Text = dr("Patient_admission_id")
cmbname.Text = dr("Patient_name")
txtadd.Text = dr("address")
txtroomno.Text = dr("room_no")
txtbedno.Text = dr("bed_no")
cmbroomtype.Text = dr("room_type")
txtproomno.Text = dr("previous_room_no")
cmbdassigned.Text = dr("Doctor_assigned")
txtpcond.Text = dr("Patient_condition")
DateTimePicker1.Text = dr("Admission_date")
Next
50

DataGrid1.DataSource = ds.Tables("Ajij")
Else
MsgBox("Enter Patient_admission_id", MsgBoxStyle.Information)
End If
End Sub
Private Sub cmdUpdate_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles
cmdUpdate.Click
Dim cmstr As String
cmstr = "Update Patient_admission set Admission_date='" & DateTimePicker1.Text &
"',Patient_condition='" & txtpcond.Text & "',Doctor_assigned='" & cmbdassigned.Text &
"',Previous_room_no='" & txtproomno.Text & " ',room_type='" & cmbroomtype.Text & "', bed_no='" &
txtbedno.Text & "', Room_no=" & txtroomno.Text & ", address='" & txtadd.Text & "', Patient_name = '" &
cmbname.Text & "' where Patient_admission_id='" & txtid.Text & "'"
If con.State = ConnectionState.Closed Then con.Open()
MsgBox("Data updated")
Else
MsgBox("Make edit first", MsgBoxStyle.Information)
End If
txtid.Text = ""
cmbname.Text = ""
txtadd.Text = ""
txtroomno.Text = ""
txtbedno.Text = ""
txtpcond.Text = ""
End Sub
Private Sub cmdDelete_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles
cmdDelete.Click
Dim i As Integer
i = MsgBox(" Sure to delete??", MsgBoxStyle.YesNoCancel)
If i = 6 Then
Dim cmstr As String
cmstr = "delete from Patient_admission where Patient_admission_id='" & txtid.Text & "'"
con.Open()
MsgBox("data deleted")
End If
End If
End Sub
51

Private Sub cmdClear_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles
cmdClear.Click
txtid.Text = ""
cmbname.Text = ""
txtadd.Text = ""
txtroomno.Text = ""
txtbedno.Text = ""
txtpcond.Text = ""
End Sub
Private Sub cmdClose_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles
cmdClose.Click
Dim i As Integer
i = MsgBox("Do you really want to exit?", MsgBoxStyle.YesNoCancel)
If i = 6 Then
Me.Close()
frmMenu.Show()
Else
End If
End Sub
End Class
frmpatientDischarge
Imports System.Data.Sqlclient
Public Class frmDischarge
cmdEdit.Click
Dim str As String
str = "select*from Patient_discharge where Patient_discharge_id='" & Trim(txtid.Text) & "'"
da.Fill(ds, "Ajij")
Dim dr As DataRow
txtid.Text = dr("Patient_discharge_id")
DateTimePicker1.Text = dr("discharged_date")
txtfees.Text = dr("fees")
cmbdoc.Text = dr("approval_doctor")
Next
Else
MsgBox("enter Patient_discharge_id", MsgBoxStyle.Information)
End If
End Sub
52

cmdUpdate.Click
Dim cmstr As String
cmstr = "update Patient_discharge set Approval_doctor='" & cmbdoc.Text & "',Fees='" & txtfees.Text &
"',Discharged_date=" & DateTimePicker1.Value & ",Patient_name='" & cmbname.Text & "' where
Patient_discharge_id='" & txtid.Text & "'"
MsgBox("data updated")
Else
MsgBox("make edit first", MsgBoxStyle.Information)
End If
txtid.Text = ""
cmbname.Text = ""
txtfees.Text = ""
cmbdoc.Text = ""
End Sub
cmdDelete.Click
Dim i As Integer
If i = 6 Then
Dim cmstr As String
cmstr = "delete from Patient_discharge where Patient_discharge_id='" & txtid.Text & "'"
End If
End If
End Sub
cmdClose.Click
Dim i As Integer
If i = 6 Then
Me.Close()
frmMenu.Show()
Else
End If
End Sub
cmdClear.Click
txtid.Text = ""
53

cmbname.Text = ""
txtfees.Text = ""
cmbdoc.Text = ""
End Sub
Private Sub frmDischarge_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles
MyBase.Load
Dim str As String
Str = "select * from Patient "
da.Fill(ds, "Ajij")
With cmbname
.DataSource = ds.Tables("Ajij")
.DisplayMember = "Patient_name"
.ValueMember = "Patient_id"
End With
End Sub
cmdAdd.Click
Dim cmstr As String
cmstr = "insert into Patient_discharge values('" & txtid.Text & "', '" & Trim(cmbname.Text) & "','" &
DateTimePicker1.Text & "' ,'" & txtfees.Text & "', '" & Trim(cmbdoc.Text) & "')"
MsgBox("data inserted")
End Sub
End Class
frmpatientMaster
Public Class frmPatient
cmdEdit.Click
Dim str As String
str = "select*from Patient where Patient_id='" & Trim(txtid.Text) & "'"
54

da.Fill(ds, "Ajij")
Dim dr As DataRow
txtid.Text = dr("Patient_id")
txtdescription.Text = dr("Description")
txtadd.Text = dr("Patient_address")
cmbfname.Text = dr("Father_name")
txtregdate.Text = dr("Reg_date")
txtphone.Text = dr("Patient_phone_no")
txtage.Text = dr("age")
txtsex.Text = dr("sex")
txtcity.Text = dr("city")
txtstate.Text = dr("state")
Next
Else
MsgBox("enter Patient_id", MsgBoxStyle.Information)
End If
End Sub
cmdAdd.Click
Dim cmstr As String
cmstr = "insert into Patient values('" & txtid.Text & "', '" & Trim(cmbname.Text) & "','" &
txtdescription.Text & "' ,'" & txtadd.Text & "', '" & Trim(cmbfname.Text) & "','" & txtregdate.Text & "','" &
txtphone.Text & "','" & txtage.Text & "','" & txtsex.Text & "','" & txtcity.Text & "','" & txtstate.Text & "')"
constr = "Server=.;database=Hospital_Management;User id=;pwd=;integrated security=SSPI;"
Dim cmd As New Sqlcommand(cmstr, con)
MsgBox("data inserted.")
End Sub
Private Sub frmPatient_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles
MyBase.Load
Dim str As String
str = "select * from Patient "
constr = "Server=.;database=Hospital_Management;User id=;pwd=;integrated security=SSPI;"
da.Fill(ds, "Ajij")
With cmbname
.DisplayMember = "Patient_name"
.ValueMember = "Patient_id"
End With
End Sub
cmdClear.Click
55

txtid.Text = ""
cmbname.Text = ""
txtdescription.Text = ""
txtadd.Text = ""
cmbfname.Text = ""
txtregdate.Text = ""
txtphone.Text = ""
txtage.Text = ""
txtsex.Text = ""
txtcity.Text = ""
txtstate.Text = ""
End Sub
cmdDelete.Click
Dim i As Integer
If i = 6 Then
Dim cmstr As String
cmstr = "delete from Patient where Patient_id='" & txtid.Text & "'"
End If
End If
End Sub
cmdUpdate.Click
Dim cmstr As String
cmstr = "update Patient set state='" & txtstate.Text & "', city='" & txtcity.Text & "',sex='" & txtsex.Text
& "', age='" & txtage.Text & "', Patient_phone_no='" & txtphone.Text & "', reg_date='" & txtregdate.Text &
"',Father_name='" & cmbfname.Text & "', Patient_address = '" & txtadd.Text & "', Patient_name='" &
cmbname.Text & "', Description='" & txtdescription.Text & "' where Patient_id='" & txtid.Text & "'"
End If
End Sub
cmdClose.Click
frmMenu.Show()
End Sub
End Class
56
frmDoctor
Public Class frmDoctor
cmdAdd.Click
Dim cmstr As String
cmstr = "insert into Doctor values(" & txtid.Text & ", '" & Trim(cmbname.Text) & "','" &
txtdescription.Text & "' ,'" & txtadd.Text & "', '" & txtquali.Text & "', " & txtphone.Text & ",'" & txtspeci.Text &
"')"
txtid.Text = ""
cmbname.Text = ""
txtadd.Text = ""
txtphone.Text = ""
txtspeci.Text = ""
txtquali.Text = ""
End Sub
Private Sub frmDoctor_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles
MyBase.Load
Dim str As String
str = "select * from Doctor "
da.Fill(ds, "Ajij")
With cmbname
.DisplayMember = "doctor_name"
.ValueMember = "Doctor_id"
End With
con.Close()
End Sub
cmdEdit.Click
Dim str As String
str = "select*from Doctor where Doctor_id=" & Trim(txtid.Text) & ""
57

da.Fill(ds, "Ajij")
Dim dr As DataRow
txtid.Text = dr("Doctor_id")
cmbname.Text = dr("Doctor_name")
txtadd.Text = dr("Doctor_address")
txtquali.Text = dr("Doctor_qualification")
txtphone.Text = dr("Doctor_phone_no")
txtspeci.Text = dr("Doctor_speciality")
Next
Else
MsgBox("enter Doctor_id", MsgBoxStyle.Information)
End If
End Sub
cmdUpdate.Click
Dim cmstr As String
cmstr = "update Doctor set Doctor_speciality='" & txtspeci.Text & "', Doctor_phone_no='" &
txtphone.Text & "', Doctor_qualification='" & txtquali.Text & "', Doctor_address='" & txtadd.Text & "',
Doctor_name = '" & cmbname.Text & "', Description='" & txtdescription.Text & "' where Doctor_id=" &
txtid.Text & ""
Else
End If
End Sub
cmdDelete.Click
Dim i As Integer
If i = 6 Then
Dim cmstr As String
cmstr = "delete from Doctor where Doctor_id=" & txtid.Text & ""
End If
End If
End Sub
58

cmdClose.Click
Dim i As Integer
i = MsgBox("Really exit?", MsgBoxStyle.YesNoCancel)
If i = 6 Then
Me.Close()
frmMenu.Show()
End If
End Sub
cmdClear.Click
txtid.Text = ""
cmbname.Text = ""
txtadd.Text = ""
txtquali.Text = ""
txtphone.Text = ""
txtspeci.Text = ""
End Sub
End Class
frmNurse
Public Class frmNurse
cmdEdit.Click
Dim str As String
str = "select*from Nurse where Nurse_id=" & Trim(txtid.Text) & ""
da.Fill(ds, "Ajij")
Dim dr As DataRow
txtid.Text = dr("Nurse_id")
cmbname.Text = dr("Nurse_name")
txtadd.Text = dr("Nurse_address")
txtphone.Text = dr("Nurse_phone_no")
Next
Else
MsgBox("Enter Nurse id.", MsgBoxStyle.Information)
End If
End Sub
Private Sub frmNurse_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles
MyBase.Load
59

Dim str As String
str = "select*from Nurse"
da.Fill(ds, "Ajij")
With cmbname
.DisplayMember = "Nurse_name"
.ValueMember = "Nurse_id"
End With
End Sub
cmdAdd.Click
Dim cmstr As String
cmstr = "insert into Nurse values(" & txtid.Text & ", '" & Trim(cmbname.Text) & "','" & txtdescription.Text
& "','" & txtadd.Text & "', '" & txtphone.Text & "')"
txtid.Text = ""
cmbname.Text = ""
txtadd.Text = ""
txtphone.Text = ""
End Sub
cmdClear.Click
txtid.Text = ""
cmbname.Text = ""
txtadd.Text = ""
txtphone.Text = ""
End Sub
cmdClose.Click
Dim i As Integer
If i = 6 Then
Me.Close()
frmMenu.Show()
End If
End Sub
cmdDelete.Click
Dim i As Integer
60

If i = 6 Then
Dim cmstr As String
cmstr = "delete from Nurse where Nurse_id=" & txtid.Text & ""
End If
End If
End Sub
cmdUpdate.Click
Dim cmstr As String
cmstr = "update Nurse set Nurse_phone_no='" & txtphone.Text & "', Nurse_address='" & txtadd.Text &
"', Nurse_name = '" & cmbname.Text & "', Description='" & txtdescription.Text & "' where Nurse_id=" &
txtid.Text & ""
Else
End If
End Sub
End Class
frmOPD
Public Class frmOPD
cmdAdd.Click
Dim cmstr As String
cmstr = "insert into OPD values('" & txtid.Text & "', '" & cmbname.Text & "','" & cmbtype.Text & "', '" &
txtdescription.Text & "','" & cmbsname.Text & "')"
61

End Sub
cmdEdit.Click
Dim str As String
str = "select*from OPD where OPD_id='" & txtid.Text & "'"
da.Fill(ds, "Ajij")
Dim dr As DataRow
txtid.Text = dr("OPD_id")
cmbname.Text = dr("OPD_name")
cmbtype.Text = dr("OPD_type")
txtdescription.Text = dr("OPD_description")
cmbsname.Text = dr("OPD_surgeon_name")
Next
Else
MsgBox("enter OPD id", MsgBoxStyle.Information)
End If
End Sub
cmdUpdate.Click
Dim cmstr As String
cmstr = "update OPD set OPD_surgeon_name='" & cmbsname.Text & "', OPD_description='" &
txtdescription.Text & "', OPD_type='" & cmbtype.Text & "', OPD_name = '" & cmbname.Text & "' where
OPD_id='" & txtid.Text & "'"
Else
End If
End Sub
cmdDelete.Click
Dim i As Integer
If i = 6 Then
Dim cmstr As String
cmstr = "delete from OPD where OPD_id='" & txtid.Text & "'"
62

End If
End If
End Sub
cmdClear.Click
txtid.Text = ""
cmbname.Text = ""
cmbtype.Text = ""
cmbsname.Text = ""
End Sub
cmdClose.Click
Dim i As Integer
If i = 6 Then
Me.Close()
frmMenu.Show()
End If
End Sub
Private Sub frmOPD_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles
MyBase.Load
Dim str As String
str = "select*from OPD"
da.Fill(ds, "Ajij")
With cmbname
.DisplayMember = "OPD_name"
.ValueMember = "OPD_id"
End With
End Sub
End Class
frmDiscipline
Public Class frmDiscipline
cmdEdit.Click
If TextBox1.Text <> "" Then
63

Dim str As String
str = "select*from NewDiscipline where Discipline_id=" & TextBox1.Text & ""
da.Fill(ds, "Ajij")
Dim dr As DataRow
TextBox2.Text = dr("Description")
ComboBox1.Text = dr("Discipline_name")
Next
Else
MsgBox("enter Discipline_id", MsgBoxStyle.Information)
End If
End Sub
cmdAdd.Click
Dim cmstr As String
cmstr = "insert into NewDiscipline values(" & TextBox1.Text & ", '" & ComboBox1.Text & "','" &
TextBox2.Text & "')"
con.Open()
MsgBox("Record inserted successfilly.")
TextBox1.Text = ""
ComboBox1.Text = ""
TextBox2.Text = ""
End Sub
Private Sub frmDiscipline_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles
MyBase.Load
Dim str As String
str = "select*from NewDiscipline"
constr = "Server=.';database=Hospital_Management;User id=;pwd=;integrated security=SSPI"
da.Fill(ds, "Ajij")
With ComboBox1
.DisplayMember = "Discipline_name"
.ValueMember = "Discipline_id"
End With
ComboBox1.Text = ""
End Sub
cmdClear.Click
TextBox1.Text = ""
64

ComboBox1.Text = ""
TextBox2.Text = ""
End Sub
cmdClose.Click
Dim i As Integer
i = MsgBox("Really exit?", MsgBoxStyle.YesNoCancel)
If i = 6 Then
Me.Close()
frmMenu.Show()
End If
End Sub
cmdDelete.Click
Dim i As Integer
If i = 6 Then
Dim cmstr As String
cmstr = "delete from NewDiscipline where Discipline_id=" & TextBox1.Text & ""
MsgBox("Data deleted")
Else
End If
Else
MsgBox("Enter id ")
End If
TextBox1.Text = ""
End Sub
cmdUpdate.Click
Dim cmstr As String
cmstr = "update NewDiscipline set Discipline_name = '" & ComboBox1.Text & "', Description='" &
TextBox2.Text & "' where Discipline_id=" & TextBox1.Text & ""
con.Open()
MsgBox("Data updated")
Else
MsgBox("Make edit first", MsgBoxStyle.Information)
End If
TextBox1.Text = ""
ComboBox1.Text = ""
TextBox2.Text = ""
End Sub
65

End Class
SYSTEM TESTING
System testing is an expensive but critical process that can takes as much as 50% of
the budget for program development. The common view of testing held by users is
that it is performed to proof that there are no errors in a program with the explicit
intention of finding errors that is, making the program fail . The tester, who may be
analyst , programmer or specialist trained in software testing , is actually trying to
make the program fail . A successful test , then , is one of the finds an error.
Analyst knows that an affective program testing does not guarantee system reliability
or quantity assurance must be design into the system .
Quality assurance is the review of software products are related documentation for
completeness , correctness , reliability and maintainability . Analyst used for four levels
of quality assurance as follows
Testing.
Verification
Validation
Certification
TESTING:These are two general strategies for testing software, such as , code testing and
specification testing.
CODE TESTING :Code testing strategy examines the logic of program . For this testing method, the
analyst develops test cases that result in executing every instruction in the programmer
module , that is every path through the program is tested .
SPECIFICATION TESTING :To perform specification testing , the analyst can determine the program specification
where in states what the program should do and how it should perform under various
66

conditions. Then , test cases are developed for each condition or combination of
condition and submitted for processing.
By examining the result , the analyst can determine whether the program performs
according to it specified requirements . This testing does not looks into the program
to study the code or path, it looks at the program as a whole.
Types of Test Data:
1. Live
2. Artificial
1. USING LIVE TEST DATA :Live test data are those that are actually extracted from organizational files . This
shows that how system will perform on typical data . Although the combinations and
conditions of the system are not tested with this data .
2. USING ARTIFICIAL DATA :Artificial test data are solely for test purposes . They are to be generated to test all
combinations of formats and values . They are generated using the utility programs of
the information system . Using this type of data all logic and control parts through the
program can be tested .
SPECIAL SYSTEM TEST :These are other tests that are image special category , as they dont focus on the
normal running of the system . These are as follows :PEAK LOAD TEST :This is used to determine whether the system will handle the volume of activities
that occur when the system is at peak of its processing demands. For instance when
all terminals when activated same time. This test applies mainly for online system.
STORAGE TESTING :This test is to be carried out to determine the capacity of the system to store
translation data on a disk or in other files . Capacities here are measured in terms of
the number of records that a disk will handle or a file can contain . If this test is not
carried out then there are possibilities that during installation one may of discover
that there is not enough storage capacity for transaction and master file records.
PERFORMANCE TIME TESTING :-
67

This test refers to the response time of this system being installed . Performances time
testing is conducted prior to implementation to determine how long it takes to receive
a response to an enquiry , makes a backup copy of file , or sends a transaction and
receive a response .
RECOVERY TESTING :Analyst must never be sure of anything . He must always be prepare for the worst .
One should assume that the system will fail and data will be damaged or lost . Even
though plans and procedures are written to cover these situation they also must be
tested.
PROCEDURE TESTING :Documentation and run manuals telling the users how to perform certain functions are
tested quite easily by asking the users to follow them exactly through a series of
events .
HUMAN FACTORS :In case during processing , the screen goes blank , the operator may star to wonder as
to what is happening can be just about to do anything such as press the enter key a
number of times , or switch of the system and so on , but if a message displayed
saying that the processing is in progressing is in progress and asking the operator to
wait , these types of problems can be avoided.
VERIFICATION :
Verification testing runs the system in a simulated environment using simulated data .
This simulated test is primarily looking for errors and omissions regarding and end
users and design specification that were specified in the earlier phase but not fulfilled
during constructions.
VALIDATION :
Validation refers to the process of using software in a live environment in order to
find errors . The feedback from the validation phase generally products change in the
software to deal with errors and failure that are uncovered . Then a set of users sites
is selected that puts the system into use on a life basis . They are called Beta test
sites .
CERTIFICATION:-
68
Software certification is an endorsement of the correctness of the program , an issue

that is rising in importance for information system applications . There is an
increasing dependences on the purchase or lease of commercial rather than on its inhouse development . However before analyst are willing are willing to approve the
acquisition of a package , they often require certification of the software by the
developer or an unbiased third party.
69
SCREEN SHOT
Exit from this system
To enter the system
70
71
To add record in
the database
To search record
From the database
To save record
in the database
To modify record
from the database
To delete record
from the database
to generate bill
72
To exit from
this form
73
USERS MANUAL : The first screen shows the splash screen and thereafter open frmLogin form of
the project and along with password security. In this project password is kaberi & user
name is kaberi. After passing the security all the menus are activated. There are twenty four
submenus under the NURSINGHOME MANAGEMENT SYSTEM, where there are eight
entry form, eight query form, eight report form. And along with every entry form there are
eight bill form.
1.
DOCTOR INFORMATION SYSTEM : Double clicking this submenu open

form called DOCTOR INFORMATION SYSTEM. Through this form, doctors
personal records can be entered. In this form doctor code, name, address, phone
no. etc. are entered.
2. PATIENT INFORMATION SYSTEM : Through this form, patients records

can be entered. In this form, patient code, name, guardian name etc. can be
entered.
3. NURSE INFORMATION SYSTEM : Through this form, nurses records can be
entered. In this form, nurse code, address, name etc. can be entered.
4. P_FINANCE INFORMATION SYSTEM : Through this form, patients finance
records can be entered. In this form, patient code, general bed charge, medicine
charge, icu charge etc. can be entered.
5. P_TRANSACTION INFORMATION SYSTEM : This submenu open a patient
transaction form. In this form, visiting doctor, doctor remarks, blood test etc. are
recorded.
6. P_PATHOLOGICAL_TEST INFORMATION SYSTEM : In this form, patient
test, patient test date, patient report etc. can be recorded.
7. N_ROUTINE INFORMATION SYSTEM : In this form, nurses routine
information can be entered. With this form, nurse code, nurse attend floor and
room, duty hour etc. are displayed.
8. ROOM INFORMATION SYSTEM : This submenu open a room information
system form. In this form, room code, floor number, type of patient etc. are
entered.
9. NOTEPAD_BILL FORM : This button is used for display of eight separated bill
form. After searching the records the user can click the note-pad bill button to
generate the separate bill form from separate entry form .
10. QUERY FORMS : Eight query forms are created in this project. The query
forms are doctor query form, nurse query form, n_routine query form, patient
74

query form etc. When user clicks any one of the query button, then a query form
appears on the desktop with complete records.
11. REPORT FORMS : Menu form has also eight report button such as d_report,
n_report,n_routine report, p_finance report etc. Pressing any of these report button
will display the separated report form for each entry form.
SECURITY :
Security is critical in system development . The amount of protection depends on the
sensitivity of the data , the reliability of the user , and the complexity of the system .
The motive behind security are to keep the organization running , protect data as an
asset , and seek management support for more installation. Here I provide a password
system for security. Only the person will be able to enter the system who is wellknown about password.
SYSTEM FAILURES AND RECOVERY :

System security in a data base environment closely linked with the system failure and
recovery. Possible failures and recovery mechanism are incorporate within this system
which are mentioned as follows:
1. Catastrophic failures are restored using the roll forward method of recovery.
2. Logical failures : The system developed is an interactive system and it provides
automatic recovery i.e rollback when the system is restarted which removes the human
function from the process.
3. Structural Failure : If this fault occurs then the system will automatically inform
user that they provides wrong data.
4. Consistency error : The system includes routines that check the consistency of data
entered in database.
Briefly the system developed is durable and reliable and can survive in its full glory
despite threats like machine crash program bugs and user errors.
BACK UP :
Back up is taken regularly after the end of day transaction . An back up procedure is
ran by the system user at the end of the day and the back up is taken in Compact
Disk Rom .After the end of fortnight tape archive back is taken and end annual
examination is transferred to disk drum.
75
CONCLUSION
The software HOSPITAL MANAGEMENT SYSTEM has been developed by
me as to the best of my knowledge and capabilities . I have been amply assisted and
guided by my seniors as and when I required help. Though I have tried my level
best to make this software full proof and exhaustive . There might have been some
shortcoming and there need much to be included in this software . I have designed
this software as per availability of data , which I have collected from different
sources and I have abided by the norms and regulations as set up by the organization
. In future , I will try to make this or any type of software much enriched with
sophistication and improved in all aspects.
LIMITATION
To write down the limitations of ones developed system is one of , may be
the most embarrassing part . The said developer has to find the sort coming of the
system that he/she has developed . To begin with , likewise , any other given system, the
system that I have developed has also its share of merits and demerits. Here I am
going to elaborate some of the demerits this system suffers from . Some of them may
be lack of infrastructure , while others due to the lack of my technical ability . As
already mentioned , a system of such software volume and developing it single ability
, it is bound so suffer from some limitation .
It is not possible for any developer to point out or demarcate all limitations the
system has . But I sill try to my level best to point out limitations as I can .
There are as follows :1. The software do not support network environment . It will run only on
standalones.
2. We cannot provide the details regarding various departments, their financial
status .
3. The project is for a particular hospital and implementation for any other health
center will require some change.
4. The data type is predefined and the user will not be able to change them.
FUTURE SCOPE
76
The software that I have developed and discussing viz, HOSPITAL

MANAGEMENT SYSTEM may have some limitations and seems to be incomplete through
others view point. But as already I have mentioned it has got enough potential for future
development. In my mind, I have some important points and facts that in my part I have not
been able to implement due to some unavoidable reasons. I also think it to be very useful to
point out some of this, which can be implemented in the near future.
Those are as follows :

1. The software can be used in network environment so that the stand
alones can be connected with others forming independent terminals
and operate upon a central database managed by server. This task will
be a real tough job, easy to say then done.
2. The number of users of the system can be increased many fold thus
making it network dependent in the real sense.
3. Due the increase in users, the security of the database and the system
as whole need to be reviewed and various validations and authorization
passwords need to be implemented for different level of users.
4. Details and records relating to every aspect and services provided in a
hospital or as a part of the hospitality industry can be maintained or
incorporated.
5. Lastly, but not the less important is the fact that it can be made more
user friendly, easy to operate and less time consuming or efficient is
the term to be used. The systems susceptibility to errors have to be
minimized to as low as zero percent.
77
DATA DICTIONARY
Data dictionary may be defined as a repository holding information
that specifies and describes that characteristic of the elements used in a system
including definitive description of process within the system .
The data dictionary is developed during the data flow analysis and
assists the analysts in determining systems requirements without ambiguity and
confusion . A DD is important to analysts for the following reason:
The details in a large system can be managed easily with the help of
DD .
A common meaning for all system elements can be communicated and
standards for naming can be enforced across application through a DD.
The features of a system become documented in a DD and
can be consulted when required .
hence it
A DD facilitates analysis of details in order to evaluate characteristics

And determine whether system change should be made.
Errors and Omissions in the system can be located with the help of a
DD .
A DD generally contains two types of descriptions for the data flowing through the
system , namely data elements and data structures.
FOUR RULES :Four rules govern the construction of data dictionary entries:1. Word should be defined to stand for what they mean and not the variable
names by which they may be described in the program .
2.
Each word must be unique ; we cannot have two definitions of the same client
name.
3. Aliases , or synonyms , are allowed when two or more entries show the same
meaning ; a vendor number may also be called a customer number . However ,
aliases should be used only when absolutely necessary.
4. Self-defining words should not be decomposed.
78
DATA DICTIONARY TYPE :There are two kinds of data dictionaries:

(i)
Integrated
(ii)
Stand-alone .
The Integrated dictionary is related to one database management system. To the extent
the organization data is under the DBMS it is global or organization wide. However ,
very few enterprise have all their eggs in one basket , so the dictionary documentation
(metadata) can be considered as local and fragmented .
The Stand-alone dictionary is not tied to any one DBMS , although it may have
special advantages for one DBMS , such as the IBM DB-PC Data-Dictionary , which
has special features related to the IBM IMS DBMS but is still a stand-alone variety
of dictionary.
DATA DICTIONARY FUNCTION :Both these type of dictionaries can be identified by functions as either PASSIVE ,
ACTIVE or IN-LINE. Viewed either way , by type or function , the difference are
striking . Passive , active, and in-line dictionaries differ functionally as follows:Passive Data Dictionaries
The functionally passive dictionary performs documentation only. This variety of
dictionary could be maintained as a manual rather than an automated database. For
more than limited documentation use , the automated passive dictionary has clear
advantages . Form the organization view the documentation function is the most
important dictionary service with the most potential benefits , so the passive dictionary
should not be thought of negatively . It has most limited functionality but may perform
its critical function of global documentation best of all.
Active Data Dictionaries
Besides supporting documentation to one degree or another , the active data dictionary
supports program and operations development by exporting database definitions and
program data storage definitions for languages such as COBOL and Job Control
Language (JCL) for execution-time performance . The IBM DB/DC Data Dictionary
already mentioned is such a stand-alone , active data dictionary . A dictionary such as
this is not an in-line data dictionary as delivered , which is not to say that it could
not be put in-line by a determined effort of major proportion .
In-Line Data Dictionaries
79
An in-line data dictionary is active during program execution , performing such feats as
transaction validation and editing . such a dictionary would always have some
documentation value , but documentation across the organization functions and activities
and all the organization information data stores is not likely. In-Line dictionaries are
associated with DBMS products such as Cullinet Software Corporations IDMS R or
Cincom Systems TOTAL , to name just two .
BIBLIOGRAPHY
During the development of the software HOSPITAL MANAGEMENT
SYSTEM, I have used many resource sand for that I am grateful to all the people concerned.
Mastering Visual Basic 6 by Evangelos Pstroutsos from Sybex/BPB .

Visual Basic 6 programming Black Book by - Steven Holzner
Complete reference SQL by James Croft.
System Analysis And Design by Award.
Fundamentals of database system by Navathe from Pearson education.
I also benefited from these web sites :

www.vbwrite.com
www.freevb.com
www.freevbcode.com
80
81

Hospital Management

Uploaded by

Copyright:

Available Formats

Hospital Management

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Hospital Management

Uploaded by

Copyright:

Available Formats

Hospital Management System