Pharmacy Management (M.

Tech Software Systems / 2023MT12044)

Version
Date Author/Owner Description of Change
Number
1 30th July 2023 Amitanjan Banerjee New Creation
(2023MT12044)

1.1 Problem Statement and Requirement Definition

The intent of this project is to create a Pharmacy Management system. Such a system will be
beneficial for pharmacy shops to keep a track of their drug inventory. This will enable them to easily
identify the depleting stocks and get notification about medicines which are expired or about to
expire. By using such a system, pharmacy shops can identify and track the suppliers/dealers for
various brands of medicine they sell. Such a system can also help them track various drugs sold to the
patients. This can help them identify subsequent sales opportunity as well notify them in case of drug
recalls or other notifications regarding medication (these two features are not in current scope of the
project).
The Pharmacy Management System is expected to meet following key business requirements:
1. Enter information related to Drugs, Suppliers and Patients:
a. The system is expected to have a user interface to enter information related to
Drugs/Medicines sold by the pharmacy. User should be able to key in various important
information related to the medicine: Name, Drug ID, Batch No., Brand, Supplier, Expiry
Date, Quantity in stock, Used For, Unit Price, Prescription/Non-Prescription. Each drug
should be uniquely identifiable by the Durg ID.
b. The system is expected to have a user interface to enter the following information
regarding the Dealers supplying the medicines: Supplier ID, Supplier Name,
Location/Address, Contact No., Supplied Drug ID, Supplier Drug Batch No. Each supplier
should be uniquely identified by the Supplier ID and Every Drug should have a
corresponding Supplier information.
c. The system is expected to have a user interface to enter following patient information:
Patient Name, Location, eMail address, Contact Number, Drug Bought, Drug batch and
Quantity Bought. System should not allow entering drug from a batch that is nearing
expiry or already expired.

2. Show Low Inventory (or Out of Stock) and Expired (or about to expire) Drugs: System should
show on the home page following key information:
a. Count and list of medicines which are out of stock, or the stock is less than 10 items
b. Count and list of medicines which have already expired or where the expiry date is less
than 30 days.

3. Fetch information related to Medicines: System should have the capability to fetch and display
following information from the database using a user interface:
a. Current inventory status of all medicines, all suppliers and all patients.
b. Medicines supplied by a particular supplier and which suppliers supply a particular
medicine.
c. Medicines purchased by a particular patient and which patients bought a particular
medicine.

4. Update/Delete information in the database: Database will provide a user interface to Update
and Delete patient, supplier, and medicine information. Before deleting a supplier system should
ensure that there is an alternative supplier for the medicine supplied by the deleted supplier.
1.2 Project Features

Feature Feature Name Description

ID
F01 Medicine Details Entry UI Screen, Backend DB and related constraints and checks to allow
users to enter medicine details for inventory.
F02 Supplier Details Entry UI Screen, Backend DB and related constraints and checks to allow
users to enter Supplier details.
F03 Patient Details Entry UI Screen, Backend DB and related constraints and checks to allow
users to enter Patient details.
F04 Medicine Details Update UI Screen, Backend DB and related constraints and checks to allow
users to update medicine details for inventory.
F05 Supplier Details Update UI Screen, Backend DB and related constraints and checks to allow
users to update Supplier details.
F06 Patient Details Update UI Screen, Backend DB and related constraints and checks to allow
users to update Patient details.
F07 Medicine Details Delete UI Screen, Backend DB and related constraints and checks to allow
users to delete medicine details for inventory.
F08 Supplier Details Delete UI Screen, Backend DB and related constraints and checks to allow
users to delete Supplier details.
F09 Patient Details Delete UI Screen, Backend DB and related constraints and checks to allow
users to delete Patient details.
F10 Out of Stock View Dashboard view on the home page to show medicines with low
stock i.e. less that 10 items or medicines which are out of stock
F11 Expired Medicine View Dashboard view on the home page to show medicines which have
expired or about to expire in 30 days
F12 View Medicine Inventory Table view to display all the medicine inventory.
F13 View Supplier List Table view to display all the suppliers and medicine inventory.
F14 View Patient List Table view to display all the patients.
F15 Supplier – Medicine Entry UI and back-end DB to Enter list of medicines supplied by a
supplier (5 per screen) with applicable constraints

F16 Patient – Medicine Entry UI and back-end DB to Enter list of medicines purchased by a
patient (5 per screen) with applicable constraints.

F17 View/Query Supplier – Table view listing supplier medicine information:

Medicine Details  Input : Supplier Name/Supplier ID
 Output : List of Medicines supplied by the given supplier
 Input: Drug ID / Drug Name
 Output: All Suppliers supplying this drug
F18 View/Query Patient – Table view listing patient-medicine information:
Medicine Details  Input : Patient Name/Patient ID
 Output : List of Medicines bought by the given Patient
 Input: Drug ID / Drug Name
 Output: All patients that bought this drug
1.3 Software and Hardware Details
The application will be developed on a 2 tier architecture.
Platform Windows
Frontend / Console Tkinter based GUI
Backend Server SQLite3, SQLiteDB Browser
Database SQLite3
Programming Language – Front end Tkinter Python GUI
Backend Server – Programming Language Python, SQL

1.4 Project Plan