Report Edit

ACKNOWLEDGEMENT
Every new endeavor brings with its own challenges

and obstacles and we know that with a project like “Pharmacy in Hospital
System”, we would have to climb many mountains before we succeed in our
attempt. We wish to give special recognition to the people who gave precise
information and encouragement on making of this project.
First and foremost we would like to thank Mr. MAHESWARAPPA .C.K

Principal of Govt. Science College, Chitradurga for providing the best
facility, dedicated teaching faculty and talented lab guides at Govt. Science
College, Chitradurga.
We are grateful to our project guide UMM-E-SALMA .M MSC. CS.
Lecturer Dept. of Computer Science for their precious guidance and

encouragement and suggestions throughout our project work. Who is always a
source of inspiration for students.
We are also express thanking to Mr. CHANNAKESHAVA .R.N MCA,
M.Phil. Head of the Department of Computer Science for his supervision and
keen interest during our Project Study.
We are also expressing our gratefulness to all lecturers of Govt.

Science College, Chitradurga
We are expressing our deep sense of gratitude to our beloved Parents

and we thank one and all that helped us directly or indirectly during our
project study.
Project associates. …
Amulya .C
Rudrambika .J.U
Sameena Syeda .M
Vidya .C.R
ABSTRACT
Our project Pharmacy in Hospital Management System includes
registration of patients, storing their details into the system and also
computerized billing in the pharmacy, and labs. Our software has the facility
to give a unique id for every patient and stores the details of every patient
and the staff automatically. It includes a search facility to know the current
status of each room. User can search availability of a doctor and the
details of a patient using the id.
The system is very simple in design and to implement. The system

requires very low system resources and the system will work in almost all
configurations.
Security of data.
Ensure data accuracy’s.
Administrator controls the entire system.
Reduce the damages of the machines.
Minimize manual data entry.
Greater efficiency.
User friendly and interactive.
Minimum time required.

CONTENTS
CHAPTER 1 INTRODUCTION 1
1.1 PROJECT DETAILS 1
1.2 THE SCOPE OF PROJECT 1
1.3 ADVANTAGES OF PROPOSED SYSTEM 2
1.4 EXISTING SYSTEM 2
1.5 LIMITATIONS OF EXISTING SYSTEM 2
CHAPTER 2 ABOUT VISUAL BASIC 6.0 3
2.1 OPERATING ENVIRONMENT 3
2.2 INTRODUCTION TO VB 3-4
CHAPTER 3 ABOUT ORACLE 8.X 5
3.1 INTODUCTION TO ORACLE 5-7
3.2 ABOUT NORMALIZATION 8

3.3 INTRODUCTION TO DATABASE MANAGEMENT SYSTEM 9-10
CHAPTER 4 DESIGN STRATEGY 11
CHAPTER 5 SYSTEM DESIGN 12

5.1 INTRODUCTION 12
5.2 BREAK DOWN OF PROJECT 13
5.3 SOFTWARE REQUIREMENT SPECIFICATION (SRS) 14
5.4 HARDWARE & SOFTWARE SPECIFICATION 15-16
CHAPTER 6 DESIGN PHASE 17
6.1 INTRODUCTION 17-18

6.2 ER-DIAGRAM 19
6.3 DATAFLOW DIAGRAM 20-22
6.4 DATABASE TABLE DESIGN 23-25
CHAPTER 7 TESTING & VALIDATION 26

7.1 UNIT TESTING 27
7.2 INTEGRATED TESTING 27
7.3 SYSTEM TESTING 28
7.4 ACCEPTANCE TESTING 28
SCREEN SHOTS 29-33

CONCLUSION 34
BIBLIOGRAPHY 35
Pharmacy in Hospital System Bachelors of Computer Application.
CHAPTER-1
INTRODUCTION
1.1 Project Details:
Our project Pharmacy in Hospital Management System includes

registration of patients, storing their details into the system and also
computerized billing in the pharmacy, and labs. Our software has the facility
to give a unique id for every patient and stores the details of every patient
and the staff automatically. It includes a search facility to know the current
status of each room. User can search availability of a doctor and the details
of a patient using the id.
The Pharmacy in Hospital Management System can be entered using a

username and password. It is accessible either by an administrator or
receptionist. Only they can add data into the database. The data can be
retrieved easily. The interface is very user-friendly. The data are well
protected for personal use and makes the data processing very fast.
1.2 Objectives of Proposed System:
The Pharmacy in Hospital management system software is user-

friendly software. The main objectives of the system is which shows and
helps you to collect most of the information about Hospitality and Medical
Services The system Project Report Pharmacy Hospital Management System
is very simple in design and to implement. The system requires very low
system resources and the system will work in almost all configurations.
The main objectives of the proposed system can be enumerated as

follows:
• Patients are easily allocated to the doctors.

• Doctors Search is possible.
• Today’s patient list help doctors to search their patients.
Govt. Science College, Chitradurga 1 2010-2011

1.3 Advantages Of Proposed System
The system is very simple in design and to implement. The system

requires very low system resources and the system will work in almost all
configurations.
• Security of data.
• Ensure data accuracy’s.
• Administrator controls the entire system.
• Reduce the damages of the machines.
• Minimize manual data entry.
• Greater efficiency.
• User friendly and interactive.
• Minimum time required.
1.4 EXISTING SYSTEM
Existing system refers to the system that is being followed till now.
Presently all the hospital functionalities are done manually. That is if a
patient want to consult a doctor he can visit their till his chance called. This
is make the person very difficult. Out_Patient and In_Patient tickets are
distributed directly. The main disadvantage is time consuming.
1.5 LIMITATIONS OF EXISTING SYSTEM
• Lack of security of data.

• Time consuming.
• Consumes large volume of paper work.
• Manual work
• No direct role for the higher officials.
• To avoid all these limitations and make the system working more
accurately it needs to be computerized.

CHAPTER-2
ABOUT VISUAL BASIC 6.0
2.1 Operating environment
This section gives a brief description of the environment on which the

project was developed and the front end developing tool. The package was
developed using ORACLE 8 as backend and VB 6 as front-end tool; it is
compatible with any version of Windows operating system Windows 95, 98.
2.2 Introduction to VB 6
Visual Basic is a Integrated Development Environment ( IDE ) which is

a powerful Graphical User Interface (GUI) development software, which
works on Windows 95 and above. This software comes in three editions
learners, professional and enterprise edition. VB also has third-party controls
for specialized task.
What makes VB different from almost any other programming tool is

the ease with which the interface can be developed. We literally draw the
user interface, much like using a paint program. In addition, when you have
done drawing the interface, the command buttons, text boxes, and other
controls that you have placed in a blank window will automatically recognize
user actions, such as mouse movements and button clicks. VB also comes
with a menu design feature that makes creating both ordinary and pop-up
menus a snap.

Only after you design the interface does anything like traditional
programming occur. This leads to the second step in building a VB
application: writing the code to activate the interface you built in step one.
The point is, objects in VB will recognize events like mouse clicks: how the
objects respond to them depends on the code you write, you will almost
always need to write code in order to make controls respond to events. This
makes VB programming fundamentally different from conventional
programming.
Programs in conventional programming languages run from the top,

down. For older programming languages, execution starts from the first line
and moves with the flow of the program to different parts as needed. A VB
program works completely differently. The core of a VB program is a set of
independent pieces of code that are activated by, and so respond to, only
the events they have been told to recognize. This is a fundamental shift.
Now instead of designing a program to do what the programmer thinks
should happen, the user is in control.
Much of the programming code in VB that tells your program how to

respond to events such as mouse clicks occur in what VB calls event
procedures. Essentially, everything executable in VB program is either in an
event procedure or is used by an event procedure to help the procedure
carry out its job.
The third step is the inevitable process of finding and fixing the errors.
Not even god can help you debug semantic errors but VB surely helps you
debug errors by providing debugging tools like ‘Run to cursor’, ‘Break points’,
‘stepping in and stepping out’ etc. The Integrated development environment
allows debugging at run time.
After a project is completed, it may be needed to install it on machines

that will run the application. To do this VB provides Package and Deployment
Wizard that creates the setup program. Then the setup program can be run
to install the application and all of the files it requires on each of the client
machines. Or the application can be installed on the internet server so the
client can access the program from the server.

CHAPTER-3
ABOUT ORACLE 8.X
3.1 Introduction to oracle
Oracle is a relational database management system. The key to

understanding this type of database is to understand the relationship
between data and then structuring the information base to reflect those
relationships. In this way, an information base would be built that could
stand the test of time.
The goal in a relational database is to build a database in which only

the data changes and not the underlying structures themselves. The
traditional approach did change the underlying structures and thus was
inefficient.
Relational database, system designers isolates types of information

that need capturing. They then identify the relationship between those
information types and implement a database structure. Relational systems
are data driven, and care must be taken to maintain key relationships and
integrity.

Some of the SQL statements used are:
¾ CREATE TABLE:
CREATE TABLE <table name >
<Column name> <column type> <attribute constraint>,
<Column name> <column type> <attribute constraint>,
…….
<Table constraint> <table constraint>
);
¾ DROP TABLE:
DROP TABLE <table name> ;
¾ ALTER TABLE:
ALTER TABLE <table name> ADD <column name > <column type>;
ALTER TABLE <table name> MODIFY <column name > <column

type>;
ALTER TABLE <table name> DELETE <column name >;

¾ INSERT NEW ROWS:
INSERT INTO <table name> VALUES (value1, value2…);
¾ SELECTING ROWS:
SELECT column1, column2… FROM <table name>;
¾ DELETING ROWS:
DELETE FROM <table name>
WHERE <column name>=CONDITION;
¾ UPDATE ROWS:
UPDATE <table name> SET <column name> = <new value >
WHERE <column name> = < some value>
¾ CREATE VIEW:
CREATE VIEW <view name> [(<column name>{, <column name>})]

AS <select statement>

3.2 About Normalization
It is important to obtain loss less relation to maintain the goal

database design. Database designers proposed design guidelines in the form
of normal forms to relation starting from first normal form to fifth normal
form.
“The process of converting relations from one normal form to another

normal form is known as Normalization”.
There are five types of Normalization
First normal form (1NF):
“It defines a relation schema R is in first normal form (1NF) if every

attribute of R takes only a single value (atomic values)”. Hence 1NF disallows
having a set of values.
Second Normal form (2NF):
“A second normal form is defined as a relation schema R is in 2NF if

every non prime attribute in R is fully functionality dependent on primary key
or every candidate key”.
Third Normal form (3NF):
“A third- Normal form is defined as a relation schema R is in 3NF, it is

2NF and no non-prime attribute of R is transitively dependent on the primary
key”.
Fourth Normal form (4NF):
“A relation is 4 NF if and only if whenever there exists an MVD in R,

Say A->->B, then all the attributes of R is also functionally dependent on A,
that is, A->->X for all attributes X of R”.

3.3 Introduction to Database Management System
A Database Management System consists of a collection of interrelated

data and a collection of programs to access that data. The data contains
information about one particular enterprise. The primary goal of a DBMS is to
provide an environment, which is both convenient and efficient to use in
retrieving and storing information.
Database systems are designed to manage large bodies of information.

The management of data involves both the definition of structures for the
storage information and the provision of mechanism for the manipulation of
information. In addition, the database system must provide for the safety of
the information stored, despite system crashes or attempt of unauthorized
access. If data is to be shared among several users, the system must avoid
possible anomalous results.
A major purpose of a database system is to provide users with an

abstract view of the data. That is, the system hides certain details of how the
data is stored and maintained. This is accomplished by defining three
abstractions at which the database may be viewed: the physical level, the
conceptual level, and the view level.
Underlying the structure of a database, is the data model, a collection

of conceptual tools for describing data, data relationships, data semantics,
and data constraints .The various data models that have been proposed fall
into three category :object–based logical models, record based logical
models and the physical data models.
Databases change over time as information is inserted and deleted.

The collection of information stored in the database at a particular moment
in time is called an instance of the database. The overall design of the
database is called database scheme. The ability to modify a scheme
definition in one level without affecting a scheme definition in the next higher
level is called data independence. There are two level of data independence:
physical data independence and logical data independence.

A database scheme is specified by a set of definitions, which are

expressed by data definition language (DDL). DDL statements are compiled
into a set of tables, which are stored in a special file called data dictionary,
which contains metadata. Data Manipulation Language (DML) is a language
that enables users to access or manipulate such data. There are two types -
procedural DMLs, which require the user to specify what data is needed and
how to get it and nonprocedural DMLs which require the user to specify what
data is needed without specifying how to get it.

CHAPTER-4
DESIGN STRATEGY
As the information system requirements were predictable it was

decided to follow the classical System Development Life Cycle method
(Waterfall method). It is one of the oldest and most widely used paradigms
for software development. This process demands a systematic, sequential
approach to software development that begins at the system level and
progresses through analysis, design, coding, testing, and maintenance level.
The step of the classical life cycle paradigm is very similar to the generic
steps that are applicable to all software engineering paradigms. Modeled
after the conventional engineering cycle, the classical life-cycle approach
encompasses the following activities.
The classical life cycle encompasses the following activities
Initial System Design.
Software Requirement Analysis.
Design.
Coding.
Testing.
Maintenance.

CHAPTER-5
SYSTEM DESIGN
5.1 Introduction
Design is the first step in moving the problem domain to solution

domain. The goals of the design process are to produce model or a
representation of the system, which can be used later to build the system.
The produced model is called the design of the system.
The design activity is a two-level process. The first level produces the
system design, which defines the components needed for the system and
hoe the components interact with each other. The second level is a detailed
design that refines the system design, by providing more description of the
processing logic of components and data structures, so that the design can
be easily implemented.
Design is a multi step process that focuses on software architecture,

data structure, procedural details (algorithms etc) and interfaces between
the modules. The design process also translates the requirement into the
representation of the software that can be assessed for quality before coding
begins.
Software design methodology changes continually as new methods;

better analysis and border understanding evolve. Software design is at a
relatively early stage in its evolution. Therefore, software design
methodology lacks the depth, flexibility and quantitative nature that are
normally associated with more classical engineering design disciplines.
However, techniques for software design do exist, criteria for design qualities
are available and design notation can be applied.
Once software requirements have been analyzed and specified,

software design leads the three technical activities Design, Code and testing
that are required to build and verify software. Each activity transforms
information in a manner that ultimately results in validation of the computer
software.

5.2 Break down of project:

¾ Visual Basic acts as front end with which the user directly interacts.
¾ ODBC acts as the middleware that adds processing capabilities to the
front end.
¾ DATABASE acts as backend that may be Oracle8.x.
Enter Data
USER VISUAL BASIC
(Front end)
View Results
Return the process the collected

Results data
ODBC
(Middleware)
Retrieve the Store data in the

Data from Database
Database
DATABASE
(Back end)
Fig: System design of the project

5.3 SOFTWARE REQUIREMENT SPECIFICATION (SRS)
Need for SRS:
The origin of most software systems is in the need of clients, who

either want to automate the existing manual system or desires in new
software systems. The developers create the software system itself.
Finally the users use the completed software. Thus there are three major
parties interested in the new system: client, user and the developers. The
requirements for the system that will satisfy the needs of the clients and
the concerns of the users have to be communicated to the developers
often doesn’t understand software or software development process, and
the developers often doesn’t understand the client’s problem and the
application area. This causes a communication gap between the parties
involved in the development project. A basic purpose of SRS is to bridge
this communication gap. In order to produce high quality document
containing the software requirement specification, at first we must go
through problem or requirement analysis.
Software Requirement specification
This document gives a detailed description of the Software

Requirement Specification of the project.
The purpose of the project is to create database management system

for the study of requirement specification is focused specially on the
functioning of the system. It allows the developer/analyst to understand the
system, function to be carried out, performance levels to be obtained and
corresponding interfaces to be established.

5.4 HARDWARE & SOFTWARE SPECIFICATION
Feasibility Study
Feasibility study should be cheap and quick. The result should inform
the destination of whether to go ahead current software and hardware
technology.
Technical Feasibility
In technical feasibility study, an estimate is made of whether the

identified user needs may be satisfied using current software and hardware
technology.
Financial Feasibility
The common factor for many users is price. The software jdk is an
open source. This can run on any system, i.e. it is platform independent and
architectural neutral.
Operational Feasibility
This software is developed with a proper GUI. It also provides the

overview of the project. Since this is an application project there is a need of
protecting this by giving password security.

HARDWARE REQUIREMENTS:
System : Celeron 530MHz/ Pentium IV.
RAM : 256 MB.
Hard Disk Capacity : 40 GB.
Graphics : AGP/ SVGA.
SOFTWARE REQUIREMENTS
Language : Visual Basic.
Operating System : Windows XP.
Front End : Visual Basic Script.
Back End : ORACLE 8.x.
SELECTION CRITERIA:
Platform.
Setup and Maintenance.
Available Software’s.
Documentation and Support.
Security.
Image map.
Cost.

CHAPTER-6
DESIGN PHASE
6.1 Introduction:
System design is a modeling process. It is a solution, how to

approach to create a new system. It can be defined as a transition from
user’s view to programmer’s or database person’s view. The design phase
mainly depends on the detailed specification in the feasibility study. The
system design phase acts as a bridge between the required specification
and the implementation phase.
From a project management point of view software design is

conducted in two steps. Preliminary design is concerned with the
transformation of requirements into data and software architecture.
Detailed design focuses on refinement to the architectural representation
that leads to detailed data structure and algorithmic representation for
software.
The major steps in the design phase are input design, output
design, and dealing with coding issue. The very first step is design of input
and output screen to the client requirements. Next comes the various
issues that should be dealt while coding and the code should be such that
it should be compatible with the real time environment and should be
generic in nature.

Input design:
System analysis decides the following input design details:

1. What data to input?
2. What medium to be used?
3. How the data should be arranged or coded?
4. The dialogue that is used to guide the user input data.
5. Methods for performing input and error correction steps.
The input screens are designed with extreme care. If by mistake

some wrong data is input into the system, it must be able to detect the
mistakes and take effective measures to correct it, such as prompting the
user of the incorrect data, rectifying the error by itself.
Output design:
Computer output is the most and direct source of the information to

the user. In output design the emphasis is given to design to the hard
copy and a soft copy of information needed for the users. Efficient,
intelligent and friendly screens improve the relationship between client the
system for design making. System analysis decides the following input
design details:
1. Who will receive the output?

2. What is its planned use?
3. How much a detail is needed?
4. When and how often is the output?
5. By what method?

6.2 Entity Relationship Diagrams
Doctors Staff
Medicine
Diagnose
Hospital
Patient
User
Bill

6.3 DATA FLOW DIAGRAM
Data flow graphs also called as dataflow diagrams (DFDS) are

commonly used during problem analysis. Data flow diagrams are quite
general and are not limited to problem analysis for software requirement
specification. They were in use long before the software begins. DFD are
useful in understanding a system and can be effectively used during
analysis.
A DFD shows the flow of data through a system. It views a system

function that transforms the inputs into desired outputs. Any complex
system will not perform this transformation in a “Single step”, and a data will
typically undergo a series of transformations before it becomes the output.
The DFD aims to capture the transformations that take place within a system
to the input data so that eventually the output data is produced. The agent
performs the transformation of data form one state to another is called a
process (or a bubble). So, a DFD shows the movement of data through the
different transformations or processes in the system. The processes are
shown by named circles and data flow is represented by named arrows
entering or leafing bubbles. A rectangle represents a source or sinks and is a
net originator or consumer of data. A source or a sink is typically outside the
main system of study.
Some conversations used in drawing this DFD. All external files are
labeled in straight line. The multiple data flows by a process is represented
by ‘*’ between the data flows. This symbol represents the AND relationship.
The symbol ‘+’ represents the OR relationship between the data flows.

Zero- Level- DFD
PATIENT Admin
PHARMACY
IN HOSPITAL
MANAGEMENT SYSTEM
TEST MEDICINE
INFORMATION

LOGIN FAIL
USER LOGS IN TERMINATE
LOGIN SUCCESS
MAIN FORM
GET PATIENT
DATA
LOOK UP
PATIENT MEDICINE
DATABASE
ABSENT
EXISTS
VERIFY
MEDICINE
LABORATORY MAKE
DATABASE TESTING
BILL ISSUED
PATIENT PREPARE TERMINATED

DATABASE BILL
LABORATORY
DATABASE
Fig: Data Flow Diagram of the project

6.4 DATABASE TABLE DESIGNS

Table descriptions:
hsm_dct
Name Null? Type
------------------------------- -------- ----
name varchar(30) not NULL,
age int,
qualification varchar(40),
address varchar(40),
resi_phno int,
doctor_id int not NULL,
specialization varchar(40),
consult_time varchar(40),
off_phno int,
salary int,
date_of_join varchar(20),
primary key(doctor_id)
hsm_patient
Name Null? Type

------------------------------- -------- ----
age int,
a_date varchar(20) not NULL,
patient_id int not NULL,
ward_no int,
stf_id int not NULL,
doc_id int not NULL,
primary key(patient_id),
foreign key(patient_id) references hsm_bill(p_id),

foreign key(patient_id) references hsm_drep(p_id),

foreign key(stf_id) references hsm_stf(staff_id),
foreign key(doc_id) references hsm_dct(doctor_id)
hsm_stf
Name Null? Type
------------------------------- -------- ----
age int,
salary int,
staff_id int not NULL,
work varchar(40) not NULL,
work_hrs varchar(30),
date_of_join varchar(20),
primary key(staff_id)
hsm_drep
Name Null? Type
------------------------------- -------- ----
p_id int not NULL,
diseases varchar(40),
blood_grp varchar(5),
blood_pr varchar(10),
sugar_level varchar(20),
height int,
weight int,
primary key(p_id)

hsm_medicine
Name Null? Type
------------------------------- -------- ----
mname varchar(30) not NULL
mtype varchar(30) not NULL,
descrp varchar(50),
stock int,
cost float,
primary key(mname,mtype)
hsm_bill
Name Null? Type
------------------------------- -------- ----
p_id int not NULL,
paid varchar(5) not NULL,
dis_date varchar(20),
bed_charge int,
consult_fee int,
labcost int,
med_cost int,
food_charge int,
primary key(p_id)

CHAPTER-7
TESTING AND VALIDATION
Testing:
Testing goes side by side with implementation that is aimed at

ensuring the systems works accurately and effectively before the live
operation is performed. The common view of testing held by the user is to
ensure that here are no errors in a program with explicit intention of
handling errors.
Test Plans
The project User Profile Analysis by Web Usage Mining is made up of

several interrelated modules. Unit testing was performed at the initial stage
of development in the order to fix bugs at initial stages followed by system
testing. Here each test was conducted on particular set of test data. At the
end acceptance test is done to satisfy the user.
Types of Testing
Some important types of testing are as follows:
• UNIT TESTING
• INTEGRATED TESTING
• SYSTEM TESTING
• ACCEPTANCE TESTING

7.1 Unit Testing
In unit testing application developer tests the system. The whole
application is made up of different modules. Unit testing focuses on each sub
module independent of one another, to locate errors. This enables the
programmer to detect errors. While testing the module the concept of trace
and breakpoints are applied at different stages of testing. The unit testing of
this project was done in which each and every module was tested with
certain test data to ensure that the program works accurately. The unit
testing was carried out successfully.
7.2 Integrated Testing
Integrated testing is to the system as a whole. That is to test the
system when all the modules and its sub modules are integrated. This
testing is done to ensure that all the modules, which works correctly when
independent, works without any discrepancies when integrated. System
testing ensures that the related modules work together to achieve the main
objective of the application.

7.3 System Testing
System testing can be defined it many ways but simple definition is
that the validation succeeds when the system function in a manner that
reasonably expected by the user. Validation testing provides the final
assurance that the system meets all the functional, behavioral and
performance requirements.
The project was tested with all its modules and ensured that there
were no errors, it has been seen that the system is working perfectly, to the
satisfaction of the user meeting all the requirement of user.
7.4 Acceptance Testing
After performing the system testing, the next step applied to the
system is output testing of the proposed system. Since no system could be
useful, if it does not produce required output in the specific format. User
acceptance of the system is the key factor for the success of any system.
The system under consideration is tested for user acceptance, by constantly
keeping in touch with perspective user of the system at the time of
developing and the changes are made whenever required.

SCREEN SHOTS





CONCLUSION
The basic goal has been to design an efficient DBMS package for this
software package is implementing to fulfill the requirements of the Pharmacy
in Hospital management system software is user-friendly software. The main
objectives of the system is which shows and helps you to collect most of the
information about Hospitality and Medical Services The system Project
Report Pharmacy Hospital Management System is very simple in design and
to implement. The system requires very low system resources and the
system will work in almost all configurations.
The main objectives of the proposed system can be enumerated as

follows:
• Patients are easily allocated to the doctors.
• Doctors Search is possible.
• Today’s patient list help doctors to search their patients.
The scope of this project is limited to only Hospitals.

BIBLIOGRAPHY
1. ELMASRI and NAVATHE, FUNDAMENTALS OF DATA BASE SYSTEMS

ADDISON WESLEY, 3RD EDITION, 2000
2. MURRACH’S BEGINNERS TO PRO-VISUAL BASIC 6.0 MURRACH

PUBLICATION.
3. SQL and VB Course Materials from SSI, Aptech.
4 Pharmacy Agencies.
5. Hospitals.

Report Edit

Uploaded by

Document Information

Original Description:

Original Title

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

Report Edit

Uploaded by

Copyright:

Available Formats

ACKNOWLEDGEMENT

Every new endeavor brings with its own challenges

First and foremost we would like to thank Mr. MAHESWARAPPA .C.K

We are grateful to our project guide UMM-E-SALMA .M MSC. CS.

Lecturer Dept. of Computer Science for their precious guidance and

We are also express thanking to Mr. CHANNAKESHAVA .R.N MCA,

We are also expressing our gratefulness to all lecturers of Govt.

We are expressing our deep sense of gratitude to our beloved Parents

The system is very simple in design and to implement. The system

 Ensure data accuracy’s.

 Administrator controls the entire system.

 Reduce the damages of the machines.

 Minimize manual data entry.

 User friendly and interactive.

 Minimum time required.

CHAPTER 2 ABOUT VISUAL BASIC 6.0 3

2.1 OPERATING ENVIRONMENT 3

2.2 INTRODUCTION TO VB 3-4

CHAPTER 3 ABOUT ORACLE 8.X 5

3.1 INTODUCTION TO ORACLE 5-7

3.2 ABOUT NORMALIZATION 8

CHAPTER 4 DESIGN STRATEGY 11

CHAPTER 5 SYSTEM DESIGN 12

CHAPTER 6 DESIGN PHASE 17

6.1 INTRODUCTION 17-18

CHAPTER 7 TESTING & VALIDATION 26

SCREEN SHOTS 29-33

1.1 Project Details:

Our project Pharmacy in Hospital Management System includes

The Pharmacy in Hospital Management System can be entered using a

1.2 Objectives of Proposed System:

The Pharmacy in Hospital management system software is user-

The main objectives of the proposed system can be enumerated as

• Patients are easily allocated to the doctors.

Govt. Science College, Chitradurga 1 2010-2011

1.3 Advantages Of Proposed System

The system is very simple in design and to implement. The system

1.4 EXISTING SYSTEM

1.5 LIMITATIONS OF EXISTING SYSTEM

• Lack of security of data.

Govt. Science College, Chitradurga 2 2010-2011

ABOUT VISUAL BASIC 6.0

2.1 Operating environment

This section gives a brief description of the environment on which the

Visual Basic is a Integrated Development Environment ( IDE ) which is

What makes VB different from almost any other programming tool is

Govt. Science College, Chitradurga 3 2010-2011

Programs in conventional programming languages run from the top,

Much of the programming code in VB that tells your program how to

After a project is completed, it may be needed to install it on machines

Govt. Science College, Chitradurga 4 2010-2011

ABOUT ORACLE 8.X

3.1 Introduction to oracle

Oracle is a relational database management system. The key to

The goal in a relational database is to build a database in which only

Relational database, system designers isolates types of information

Govt. Science College, Chitradurga 5 2010-2011

Some of the SQL statements used are:

CREATE TABLE <table name >

<Column name> <column type> <attribute constraint>,

<Column name> <column type> <attribute constraint>,

<Table constraint> <table constraint>

Ensure data accuracy’s.

Administrator controls the entire system.

Reduce the damages of the machines.

Minimize manual data entry.

User friendly and interactive.

Minimum time required.

Initial System Design.

Software Requirement Analysis.