SUNYANI TECHNCAL UNIVERSITY

DEPARTMENT OF APPLIED SCIENCE

HND COMPUTER SCIENCE
PHAMACY MANAGEMENT SYSTEM
FOR
VANDYKE PHAMACY
 GROUP MEMEBERS
MENSAH ENOCK -06170339
ALI DAABU -06170
SALIFU WATAARA-06170342
OWUSU MICHEAL-06170
MENSAH SAMUEL-06170
 ABSTRACT
This project is insight into the design and
implementation of a Pharmacy Management System.
The primary aim of is to improve accuracy and
enhance safety and efficiency in the pharmaceutical
store. This is pharmacy management system; it is
used to manage most pharmacy related activities in
the pharmacy.
 Introduction

• The purpose of this Systems Requirements Specifications document

(SRS) is to provide the guidelines necessary to design and
implement software that
fulfills all the requirements given.
• In case of Pharmacy Management System (simply referred to as
PMS), this document will contain enough information so that in the
event, that the current is not able to complete the software, a future
team can use this document and only this document to create another
version of the software that still fulfills all the requirements.
• Furthermore, this document can be used by clients and stakeholders
as a representation of their requirements for the software. Fulfilling
all the requirements of the Software Requirement Specification
(SRS) will be in essence fulfillment with the client.
 Document Purpose

• A PMS (Pharmacy Management System) is a computer

system typically used to manage the sales in the
pharmacy shop. It includes hardware components such
as a computer, a bar code scanner, a printer and final
names of drugs, also software to manage the operation
of the shop.
• The most basic function of a PMS is to handle sales. A
user must login to use the PMS. The users of a PMS are
the employees of the shop include
cashiers and administrator. Administrator can access the
system management functions of the PMS including
user management and security configuration that
cashiers can’t do.
 Product Scope

PMS will help the shop's owners to store the

following information with every purchase made
by customers: a unique transaction number
assigned to every transaction, the items
purchased and their prices, the date and time of
the transaction, discounts applied to the
transaction (if any), and the total price of all the
items bought.
 Product Scope cont..

In generating reports on sales, the system can show

detailed reports on the sales made on a daily,
weekly, monthly, or cumulative basis. The user can
view this report any time he wishes. To do so, he or
she must input a specific day (for daily), a starting
day for a week (for weekly), or a month (for
monthly). All transactions are stored by the system
for future reference. Each transaction has the
products purchased, the discounts applied, and the
prices.
Definitions, Acronyms and Abbreviati
ons
• Administrator: System administrator who is given specific
permission for managing and controlling the system.
• Pharmacy shop owner: Someone who has a supermarket
and wants his supermarket to be a part the application.
• Stakeholder: Any person who has interaction with
the system who is not a developer.
• Sale: commercial transaction between customer and
retailer, where customer buys a number of products from
the retailer.
• Sale transaction: commercial transaction between
customer and retailer.
• Product Record: descriptor of physical products with same
bar code.
 Acronyms

PMS: Pharmacy Management System

GUI: Graphical user interface
SRS: Software Requirements Specification
document
UCD: Use Case Diagram
 Overall description
Product Functionality
• Transactions Module
• Administration Module
• Reports Module

• End Users and Characteristics:

• There are two types of user that interact
with the system: Administrators and Cashier.
Describe the characteristics of each user
 Administrator

• The administrator is one of the two users of the

system. In this case, the administrator is the operations
manager of the shop. However, there can be more than
one administrator. Other users can also become
administrators provided that they are qualified and
authorized.
• Cashier:
• cashier is the second user of the system. The cashiers
are responsible for the transactions made with the
customers. They can view, add, edit and cancel orders.
They use the system for every transaction created.
 System Stakeholders

The stakeholders in this system are;

• Administrators

• Shop's owners.

• Customers

• Cashier.
 Functional requirements

Retrieve name and price of good

Name retrieve name and price of
product
Description
Input Barcode scanner
Output Name and product
Action Access backend catalogue
system and given barcode find and
retrieve product
description
 Handle payment cash

Name Handle payment cash

Description
Input Amount to be paid, cash received
Output Change to be given
Action If result ok, add amount to be paid
to total amount of cash
Pre – condition Cash received and amount to be
paid
Post condition Amount of cash (after
payment) or
amount of cash (before payment)
and amount to be paid
 Deduce stock amount

Name Deduce stock amount

Description
Input Barcode
Output Stock amount after this sale
Action Deduce one from
stock amount of product
Pre-condition Valid code, at least
one product in stock
Post-condition Product. Stock Amount
after = Product. Stock Amount before
 Handle coupon

Name Handle coupon

Description
Input Coupon (id of coupon, id of
promotion, id of product)
Output Discounted price for
product
Action Read bar code on coupon, find
id of coupon, retrieve name of promotion and
product, verify that promotion is still valid, verify
that product is available, retrieve discount rate
 USE CASE DIAGRAM
Add new item

Administrator
Login Manage
Delete item
item

User
Edit item
View report

V.cashier report
V. sales report

Log out Manage

order

Add order Cashier Cancel order

 Non-functional Requirements
Software Quality Attributes
Reliability : The Operational Interface shall
have a Mean Time between Failures of no less
than 7 days
Availability: The following requirements
indicate the expected availability of the
Operational Interface.
The system shall be available 99.5% of the time
Security : The software system needs a robust
security mechanism in place so that unauthorized
users are not allowed access to parts of the
system.
 Maintainability
The following requirements increase the maintainability
of the Operational Interface software.
All source code and development related documents shall
be controlled under a version control system
Portability:
Operating Systems,
Since the software must run on several popular hardware
platforms and the goal is to achieve a reasonable level of
platform independence.
The system shall be compatible with the Microsoft
Windows Operating System such as (windows 10, 8,
8.1,7, XP or greater).
 Usability

The system user interface intuitive, easy to

use and provide an overall positive user
experience.
Training : The system will facilitate training of
new operators with the system by having a
feature that simulates the Operational Interface.
Database : Has been the use of a database in
order to save the information and data shop it
(Sql database)
 Appendix -
First day: the project have been identified
Second Day: The project was to understand and define requirements
Third day: we defined the Functional Requirements and non-functional
requirements.
Fourth day: Completed Project

References
ANSI/IEEE Std 830-1998, IEEE Recommended Practice for Software
Requirements Specifications
ANSI/IEEE Std 1233-1996, IEEE Guide for Developing System
Requirements Specifications
http://www.softwareengineering-9.com/
SRS_example_2010_group2
END OF PRESENTATION

THANK YOU