PHARMACEUTICAL STORE DATABASE

MANAGEMENT SYSTEM
MUHAMMAD ZAHID EP086171

ABDUL BASIT AZIZ EP086101

INTRODUCTION:

This project is design for Pharmaceutical store. This project provides

facilities for controlling the database and its keep the record of the daily selling includes the
customer record for each selling and generates the billing receipt as well.

It manages the inventory of the store means it keep updating the database after each sell
of purchasing item.

It updates the records for example if four tablets are selling than these four tablets will go
and minus from the original quantity so that the user can see that how much quantity he has left
in the database.

It saves the record of daily sell for each and every customer individually including the
purchasing date and amount of sell.

Generates the billing receipt which contains information about the particular customer
purchasing using the “receipt no” attribute which distinguish the record of customer with the
other customer.

The database contains the five table’s i.e. MEDICINE, MEDICINE TYPE, RECIEPT,
BILL, and DAILY SELL.

Medicine table contains the attributes: MED ID, MED NAME, QUANTITY, RETAIL PRICE,
TRADE PRICE, and EXPIRY DATE.

Medicine type table contains the attributes: MED TYPE ID, DOSAGE FORM, and MED ID

Receipt table contains the attributes: RECIEPT NO, RECIEPT NO

Bill table contains the attributes: MED ID, RECIEPT NO

Daily sell table contains the attributes: MED ID, PURCHASING QUANTITY, DATE OF
SELL, RETAIL PRICE, and TOTAL PRICE FOR EACH MEDICINE.
DESCRIPTION OF APPLICATION:

The above given is the screen shot of my application. First the user has to select the dosage from
i.e. (tablets, capsules, syrup, and drops).When the user select the dosage form than all the medicines of
type dosage form will come in the select medicine combo box and when the user selects the medicine
than retail price of that medicine will show and when the user inter the quantity of medicine than total
price will show to the user. The next picture will show correct meaning of what I am saying which can be
easily understand by you.

After selecting medicine and its quantity the user has to click the select button so that the
selected data will be shown in the grid. When the user clicks on the select button the quantity which he
has inter will also subtract from the original quantity present in the database and the value which we
found after subtraction will save in the quantity attribute of that medicine in the database and. Next
picture will show you the selected medicines in the grid.
 The above picture of my application shows that the user has selected the 2 quantities of aspirin
and one quantity of amocilin. After selecting all medicines the user has to click the sell button so that
the total cost of all medicines will be shown to the user and also all selected medicines which are shown
in grid view will inserted in the daily sell table as well as a printout of the Grid view will also come as a
receipt so that the customer will easily see that how much medicine he has purchased.

Next picture will show you the total cost after pressing the sell button.

This was the application of my software similarly in the insert tab you can insert the new medicine in
the database and in the update tab you can update the quantity or expiry date etc of any medicine and
in the search tab you can search for any medicine and in the delete tab you can delete any medicine.

This was all the description of my application. This application can be easily understood by the any
person working in the pharmaceutical store and it is very helpful for him because he don’t have to make
register to make daily records and to calculate total cost of medicine and to search for a particular
medicine. This application saves the time of the user and helps to do the work for him automatically.
NORMALIZATION:

In relational database design, the process of organizing data to minimize redundancy. Normalization
usually involves dividing a database into two or more tables and defining relationships between the
tables. The objective is to isolate data so that additions, deletions, and modifications of a field can be
made in just one table and then propagated through the rest of the database via the defined
relationships.
Now I am going to normalize my database.

FIRST NORMAL FORM:

A relation is in the first normal form if and only if every attribute is single valued for each tuple.
MEDICINE TABLE:

MED ID MED NAME QUANTITY TRADE REATAIL EXPIRY

PRICE PRICE DATE
97 ASPIRIN(Ferozson) 241 41.65 49 9/28/2010
12:00:00 AM

MEDICINE TYPE TABLE:

MED TYPE ID DOSAGE FORM

01 TABLETS
02 CAPSULES

RECEIPT TABLE:

RECEIPT NO RECEIPT DATE

0012 6/18/2010 3:19:27 AM

BILL TABLE:

MED ID RECEIPT NO
97 0012

DAILY SELL:

MED ID PURCHASING DATE OF SELL RETAIL PRICE TOTAL PRICE

QUANTITY FOR EACH
MEDICINE
97 2 6/18/2010 3:19:27 49 98

Since no multi value attributes are found therefore the data is in first normal form
SECOND NORMAL FORM:

A relation is in second normal form if and only if it is in first normal form and all the nonkey attributes
are fully functionally dependent on the key.

MED ID MED NAME QUANTITY TRADE REATAIL EXPIRY

PRICE PRICE DATE
97 ASPIRIN(Ferozson) 241 41.65 49 9/28/2010
12:00:00 AM

MEDICINE TYPE TABLE:

MED TYPE ID DOSAGE FORM

01 TABLETS
02 CAPSULES

RECEIPT TABLE:

RECEIPT NO RECEIPT DATE

0012 6/18/2010 3:19:27 AM

BILL TABLE:

MED ID RECEIPT NO
97 0012

DAILY SELL:

MED ID PURCHASING DATE OF SELL RETAIL PRICE TOTAL PRICE

QUANTITY FOR EACH
MEDICINE
97 2 6/18/2010 3:19:27 49 98

Since all the non key attributes are fully functionally dependent on the primary key therefore the data is in
second normal form.
THIRD NORMAL FORM:

A relation is in third normal form if it is in second normal form and no nonkey attribute is transitively
dependent on the key.

MED ID MED NAME QUANTITY TRADE REATAIL EXPIRY

PRICE PRICE DATE
97 ASPIRIN(Ferozson) 241 41.65 49 9/28/2010
12:00:00 AM

MEDICINE TYPE TABLE:

MED TYPE ID DOSAGE FORM

01 TABLETS
02 CAPSULES

RECEIPT TABLE:

RECEIPT NO RECEIPT DATE

0012 6/18/2010 3:19:27 AM

BILL TABLE:

MED ID RECEIPT NO
97 0012

DAILY SELL:

MED ID PURCHASING DATE OF SELL RETAIL PRICE TOTAL PRICE

QUANTITY FOR EACH
MEDICINE
97 2 6/18/2010 3:19:27 49 98

Since no nonkey attribute is transitively dependent on the primary key therefore the data is in third normal
form.
Now the data is normalized and it is ready for implementation.