PHARMACY MANAGEMENT SYSTEM

DOCUMENTATION

Submitted by
Group 5

Group Members
Asad Ejaz 22011598-026

Zohaib Suleman 22011598-011

Muhammad Yatoof 22011598-039

Hussain Muhammad 22011598-036

SUBMITTED TO
MA`AM HAFSA DAR
.
 Page 1

Contents
1. Introduction ........................................................................................................................................... 2
1.1 Existing systems ............................................................................................................................. 3
2. System Modules..................................................................................................................................... 3
2.1 Modules ......................................................................................................................................... 3
2.2 Stakeholders and Actors ................................................................................................................ 4
2.3 Roles and Responsibilities ............................................................................................................. 4
3. RE ........................................................................................................................................................... 4
3.1 Questionnaire/ Elicitation Technique ............................................................................................ 4
3.1.1 Survey ............................................................................................................................................... 4
3.2 Functional Requirements and Non-Functional Requirements ...................................................... 6
3.2.1 Functional Requirements........................................................................................................... 6
3.2.2 Non-Functional Requirements................................................................................................... 6
3.3 Use case Diagram........................................................................................................................... 7
3.4 Use case description ...................................................................................................................... 8
3.4.1 User description 1: ........................................................................................................................ 8
3.4.2 Description No.2: .......................................................................................................................... 8
3.4.3 User Description 3: ....................................................................................................................... 9
3.4.4 User Description 4: ....................................................................................................................... 9
3.4.5 User Description 5: .....................................................................................................................10
 Page 2

Project Title
Pharmacy Management System
1. Introduction
A pharmacy Management system is a software application that helps the pharmacy
shops and small medical stores to manage their medicines delivery, records of their medicines updating,
and records of sale prescription and expiry date of medicines. This system allow admin to update and
view their medicines and also view the financial record of pharmacy. And all system access will
recommended to owner.

What

This is a Pharmacy Management System that provides the facility to owner with ease to store the
important data about pharmacy. In this system, owner of the shop will manage the sales records,
supplier records, and financial records of pharmacy

Who

The main user of this management system is the Admin (known as Owner) who has the direct access
to its system functionalities and control everything in his system.

Problems

Pharmacy Management System solves many problems and challenges that are faced by owner of the
shop. These problems are as given below:

➢ It will provide secure login functionality, it will allow only registered and authorized person to access the
system. It will protect the sensitive data and information.
➢ It will provide the feature of adding medicine when there will be a new stock.
➢ It will provide the feature of deleting medicine from inventory only to authorized users.
 Page 3

➢ It will provide the features of viewing the medicines that are approaching to expire to prevent
the sale of expire medicines and to ensure the safety of customer.
➢ Transactions of sales will be access by the owner.

1.1 Existing systems

Before this, there was a system which did not prove to be good due to some limited
functions and requirements. But on the contrary, this system is quite affected due to some special
functions that this system shall provide. Earlier in the system, the owner could not update the medicines
and also see the expiry date of medicines, but this system allows the owner to update the medicines at
will, order the medicines and view the expiry date of the medicines. Earlier the system, the salesman
had fully authority that he could see the financial records of the pharmacy and he could also make
changes in the records of the pharmacy without informing the owner, but in this system, the salesman
does not have any such authority.

Existing system is fully typically registered system in which we risk to loss the
important data of pharmacy. So this system is fully secure and easily run on the pharmacy. And he had
to face difficulties in the stocking the drugs supplied by the medicine company through EMPLOYEE. Also
in existing system, the owner had full access to the system, therefore the existing system was not fully
secure. But in this system, the owner could see the sales record of the medicines and also manage the
supplied medicines delivered by Drug Company. And in this system, the owner can also stock the
supplied medicine. And in this system only owner has full access to system.

2. System Modules
2.1 Modules
User Registration:

➢ Login
➢ Logout
➢ ViewProfile

Inventory Management:

➢ AddMedicine
➢ DeleteMedicine
➢ UpdateMedicine
➢ ViewMedicine
➢ ViewExpireMedicine
➢ ViewSalesRecord
➢ ViewSupplyRecords
➢ SellMedicine
 Page 4

2.2 Stakeholders and Actors

The Admin (known as owner of the shop).

2.3 Roles and Responsibilities

In the pharmacy Management System, there are one primary roles with their
responsibilities and secondary actor is Data Base.

Primary Actor

OWNER (ADMIN)
✓ Owner can add medicine, delete medicine, and update medicine.
✓ Owner can see the sale of transactions.
✓ Owner has full access of system.

Secondary Actor

✓ Data Base

3. RE
3.1 Questionnaire/ Elicitation Technique
Survey (Questionnaire)

3.1.1 Survey

QUESTIONS AGREE NEUTRAL DISAGREE

Q.1: Should anyone else access this system other than you?

Q.2: Will only you manage this entire system and its responsibilities?

Q.3: Do you want to add medicines with their expiry date in this

system?

Q.4: Do you want the expired medicines to be removed

automatically from the system?

Q.5: Do you want this system to be updated weekly or monthly?

 Page 5

Q.6: Do want to save sell records, personal medicines of patients

and transaction records in this system?

Q.7: Do you want to show supplier records and transaction records

to someone other than you?

Q.8: Do you want to work online in this system?

Q.9: Would you like to add medicine name, delivery time and stock
time in this system?

Q.10: What ideals functions you want to include in this system?

Ans.: I want this system to add the medicines, remove the medicines when the medicines expired, and save

the sale and transaction records.

Q.11: Do you want to make this system fully secure? If yes then why?

Ans.: Yes, because in this system I want to keep the records of patient medicines which is sensitive to be not

share with others, and record of transactions. And no one can access this system.

Q.12: Are you satisfied with the features mentioned above and if so why?

Ans.: I am satisfied because this system has all features which was required for my software and further
I do not want any more features.
 Page 6

3.2 Functional Requirements and Non-Functional Requirements

3.2.1 Functional Requirements
Registration use case models
REQ-1: This system shall allow owner to login into system.
REQ-2: This system shall allow owner to view profile.
REQ-3: This system shall allow owner to logout from the system.
Inventory management use case models
REQ-4: This system shall allow owner to add medicines.
REQ-5: This system shall allow owner to delete medicines.
REQ-6: This system shall allow owner update medicines.
REQ-7: This system shall allow owner to view the expiry date of medicines.
REQ-8: This system shall allow owner to view and manage supply records.
REQ-9: This system shall allow owner to view medicines.
REQ-10: This system shall allow owner to sell the medicines.

3.2.2 Non-Functional Requirements

Reliability:

The system will have safeguards and safety, but in case of failure that will reactivate in
few minutes. This system will also provide a 24/7 availability time to owner.

Portability:

This system will be used on only owner access devices. Those devices can range from
PCs to smart devices such as smart phones.

Security:

This system will ensure the sensitive data of patients and records of medicines which is
stored in that system securely.

Performance:

This system would be responsive and provide quick response and access to medicines
information.
 Page 7

3.3 Use case Diagram.

 Page 8

3.4 Use case description

3.4.1 User description 1:

Inventory Management System

U.C Name: Login Developer: Asad Ejaz

Actor: Admin Date: June 4, 2023

Pre-Condition: Actor must be authorized.

Actor’s Action System’s Response

1) Actor request for login.
3) Actor provide User Name, Password and
click on login.
2) System display requested screen for capturing user
details.
4) System display message for Successful logged in.

Post Condition: Admin will be logged in screen will appear.

3.4.2 Description No.2:

Pharmacy Management System

U.C Name: Add.Medicine Developer: Muhammad Yatoof

Actor: Admin Date: June 4, 2023

Pre-Condition: Admin must be authorized to add medicines.

Actor’s Action System’s Response

1) Actor requested to add medicine. 2) System display window for entering medicine
detail.
4) Actor fill the detail and also expiry date to 5) System display medicine added successfully.

add medicine.
 Page 9

Post Condition: Medicine record will be added to database.

3.4.3 User Description 3:

Pharmacy Management System

U.C Name: Delete.Medicine Developer: Asad ,Yatoof,Hussain,Zohaib

Actor: Admin Date: June 4, 2023

Pre-Condition: Medicine must be added and admin must be authorized to delete medicine.

Actor’s Action System’s Response

1) Actor requested to delete the medicine. 2) System deliver window to capture the medicine
detail.
3) Actor fill detail and submit. 4) System delete the requested medicine.

Post Condition: Medicine should be deleted from database successfully.

3.4.4 User Description 4:

Pharmacy Management System

U.C Name: View.Sale.Record Developer: Hussain,Zohaib

Actor: Admin Date: June 4, 2023

Pre-Condition: Sale record must be added and admin must be authorized to view the sale records.

Actor’s Action System’s Response

1) Actor requested to view sale records.
2) Actor click on the specific sale record to
view.
1) System display the requested window to view
sale records.
2) System display requested specific records to the
the actor .
 Page 10

Post Condition: System will fetch the sale records from the database.

3.4.5 User Description 5:

Pharmacy Management System

U.C Name: Logout Developer: Zohaib Suleman

Actor: Admin Date: June 4, 2023

Pre-Condition: Actor must be logged in.

Actor’s Action System’s Response

1) Actor requested to logout. 2) System successfully logout the Actor.

Post Condition: Login window must be prompted to the user.

Page 11