2. INTRODUCTION:
1.The main aim of the project is the management of the database of the pharmaceutical shop.
2.This project is insight into the design and implementation of a Pharmacy Management System.
3.This is done by creating a database of the available medicines in the shop. The primary aim of pharmacy
management system is to improve accuracy and enhance safety and efficiency in the pharmaceutical store.
4. The aim of this project is to develop software for the effective management of a pharmaceutical store.
5. We have developed this software for ensuring effective policing by providing statistics of the drugs in
stock.
3. Description on the topic:
► This program can be used in any pharmaceutical shops having a database to
maintain.
► The software used can generate reports, as per the user’s requirements.
► The software can print invoices, bills, receipts etc. It can also maintain the
record of supplies sent in by the supplier. Here, the admin who are handling
the organization will be responsible to manage the record of the employee.
► Each employee will be given with a separate username and password.
4. Problem Definition:
► The aim of the project is to create an effective software to help the
pharmacist to maintain the records of the medicines, handle user details,
generate invoice, check and renew validity and provide a scope of
communication between users by using inbuilt messaging system.
► Pharmacy management system deals with the maintenance of drugs and
consumables in the pharmacy unit.
► This pharmacy management system is user friendly.
5. Objectives :
-> Primary objective
•To gain practical experience by modeling a software based on real world problem.
•To understand how to work on Front-end (Java) and Back-end (MySQL) by using server(wamp).
-> Secondary objective
•To develop an application that deals with the day to day requirement of any pharmacy.
•To develop the easy management of the medicines (drugs).
•To handle the inventory details like sales details, purchase details and stock expiry and quantity.
•To provide competitive advantage to the pharmacy.
•To provide details information about the stock on details necessary and help locate it in shop
easily.
•To make the stock manageable and simplify the use of inventory in the pharmacy.
6. Hardware and software tools:
► The system services and goals are established by consultation with system
user.
► They are then defined in details and serve as a system specification. System
requirement are those on which the system runs.
7. ⚙ Hardware Requirements:
o Computer with either Intel Pentium processor or AMD processor.
o 1GB+ DDR RAM
o 40GB hard disk drive
8. 💻 Software Requirements:
o Windows/ MacOS/ Linux operating system.
o JRE and JDK.
o MySQL server (WAMP or XAMPP or any)
9. DESIGN :
Database Design is a collection of processes that facilitate the designing, development, implementation and
maintenance of enterprise data management systems.
It helps produce database systems:
o That meet the requirements of the users
o Have high performance.
Architecture Description;
The design of a DBMS depends on its architecture.
It can be centralized or decentralized or hierarchical.
The architecture of a DBMS can be seen as either single tier or multi-tier.
10. ENTITIES AND ATTRIBUTES
COMPANY DRUG HISTORY_SALE LOGIN
NAME
ADDRES
S
PHONE
NAME
TYPE
BARCODE
DOSE
CODE
COST-PRICE
SELL-PRICE
EXPIRY
COMPANY-NAM
E
PRODUCTION
DT
EXPIRATION DT
PLACE
COUNTRY
USER-NAME
BARCODE
DOSE
TYPE
PRICE
AMOUNT
DATE
TIME
NAME
QUANTITY
NAME
TYPE
DATE
TIME
ID
12. ER Diagram:
An entity–relationship model describes interrelated things of interest in a specific domain of
knowledge.
It is composed of entity types and specifies relationships that can exist between instances of those
entity types.
13. Relational Schema Diagram:
Relational schema is a collection of meta-data. Database schema describes the structure and
constraints of data representing in a particular domain
14. NORMALIZATION
► NORMALIZATION
► N O R M A L I Z A T I O N F O R PA T I E N T T A B L E
► Patient (PT_ID, PT_NAME, CONTACT, ADDRESS, CITY, PROVINCE, POSTAL-CODE, HEALTH_PLAN_ID, COMPANY_NAME,
ISSUE_DATE, EXPIRE_DATE)
► The PATIENT table is in 1NF because it has no repeating groups. ¬ It is also in 2NF because there is only one single primary key (no
composite primary key) and thus no partial dependencies.
► The record design is not in 3NF and thus, it has transitive dependencies exist i.e nonkey field depends on other field.
► 3NF: Converting from 2NF to Third Normal Form (3NF) RULE: Remove all transitive dependencies (nonkey field depending on other
nonkey)
► HENCE, THE PATIENT TABLE IS NOT IN 3NF BECAUSE OF THE FOLLOWING NONKEY DEPENDENCIES: HEALTH_PLAN_ID
HEALTH_PLAN_ID, COMPANY_NAME, ISSUE_DATE ◊ , EXPIRE_DATE
► Therefore, the normalization yields to three tables: ♣ Patient (PT_ID, PT_NAME, CONTACT, ADDRESS, CITY, PROVINCE,
POSTALCODE) ♣ Health Plan (HEALTH_PLAN_ID, COMPANY_NAME, ISSUE_DATE, EXPIRE_DATE)
15. NORMALIZATION FOR PRESCRIPTION
TABLE
Prescription (PRESC_ID, PRESC_DATE, PRESC_TOTAL, PT_ID, DOCTOR_ID,
DOCTOR_F_NAME, DOCTOR_L_NAME, DOCTOR_CONTACT, REFILL_DATE,
REFILL_USED)
The record design is not in 1NF and thus, it has repeating records.
1NF: Converting from UNF to First Normal Form (1NF) RULE: Remove all the repeating
groups in the table and separate them from the main table.
HENCE, THE PATIENT TABLE IS NOT IN 1NF BECAUSE OF THE FOLLOWING
REPEATING VALUE ATTRIBUTES: REFILL PRESC_ID, REFILL_DATE,
PRESC_REFILL_USED ◊
16. ► The record design is not in 2NF and thus, it has repeating records.
► 2NF: Converting from 1NF to Second Normal Form (2NF) RULE: All the nonkey attributes should directly
be dependent on the primary key(could be composite primary key) of that table.
► HENCE, THE PATIENT TABLE IS NOT IN 2NF BECAUSE OF THE FOLLOWING NON DEPENDING
ATTRIBUTES ON PRIMARY KEY: DOCTOR DOCTOR_ID, DOCTOR_F_NAME, DOCTOR_L_NAME,
◊ DOCTOR_CONTACT .
► The Prescription table is in 3NF because it has no transitional dependencies.
►
► Therefore, the normalization yields to three tables: ♣ Prescription (PRESC_ID, PRESC_DATE,
PRESC_TOTAL, PT_ID, DOCTOR_ID) ♣ Doctor (DOCTOR_ID, DOCTOR_F_NAME,
DOCTOR_L_NAME, DOCTOR_CONTACT) ♣ Refill (PRESC_ID, REFILL_DATE, REFILL_USED)
17. IMPLEMENTATION :
► Description on Implementation
The goal of this application is to manage the medicines and various function of the pharmacy.
List of modules:
o Login page
o Home page
o Company
o Purchase
o Drugs
o Sales
o User/Settings
o Messaging
18. Result and Discussion
► By using MySQL commands and its database this website Pharmacy management tends to store
all the data received from the users including drugs sales details and the profit made by the
owners are all in this data base.
► This website allows the user to generate invoices for sales, check expiry and quantity remaining
of the drugs.
► It also provides user with options to renew validity and add more drugs into the store and
update the database accordingly.
► By using xampp server these database commands are easily initiated into the database and the
ER diagram with relational schema diagrams helps us to make the structure of the database
faster and it was easier to make them understand the needs of the website.
19. CONCLUSIONS AND FUTURE SCOPE:
o Detailed information gathering has to be done. Without that the purpose for using the software won’t be
satisfied properly.
o However, it can give good profits in the long run.
o Implementing the software requires change in the business practices.
o Efficient organization of all knowledge is the analysis company and easy analysis access and retrieval of
information is possible.
o In this project we can also include BAR CODE facility using the bar code reader, which will detect the
expiry date and the other information about the related medicines.
o Company using this software will always be able to plan in future and always be aware of their financial
position in the market.
o It leads to ease in functioning of business processes.
o The project can be made more robust by including biometric verification.
o There is also a scope to expand by implementing newer technologies like cloud etcetera.
