PHARMACY MANAGEMENT SYSTEM

ACKNOWLEDGMENT
My profound gratitude to Almighty Allah for the knowledge, wisdom
and understanding that he bestowed on me to carry out this project.
I appreciate my supervisor Prof. Wan Fang for the supervision and
support that he gave, which helped the progression and smoothness
of the project. The co-operation is much indeed appreciated.
 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. Today management is one of
the most essential features of all form. Management provides sophistication to
perform any kind of task in a particular form. This is pharmacy management
system; it is used to manage most pharmacy related activities in the pharmacy.
CHAPTER 01
INTRODUCTION
Pharmacy management system is a management system that is designed to
improve accuracy and to enhance safety and efficiency in the pharmaceutical
store. It is a computer based system which helps the Pharmacist to improve
inventory management, cost, medical safety etc.
The system allows the user to enter a manufacturing and expiry date for a
particular product or drug during opening stock and sales transaction. The
system will also give report showing the list of products expiry after a specified
date before the product eventually expires. It also involves manual entry upon
arrival of new batches of drugs and upon drug movement out of the pharmacy
for a certain period, e.g. every month, the pharmacist may want to generate
report for the movement of drugs in and out of the pharmacy, getting
information about the drugs e.g. expiry date, date purchased, number of drug
type left, location of a drug in the pharmacy.
At present, manual system is being utilized in the pharmacy. It requires the
pharmacist to manually monitor each drug that is available in the pharmacy.
This usually leads to mistakes as the workload of the pharmacist increases.

1.1 PURPOSE
The aim of this project is to develop a software for the effective management
of a pharmaceutical store that will be able to achieve the following objectives:

- Ensuring effective policing by providing statistics of the drugs in stock.

- Maintaining correct database by providing an option to update the drugs
in stock.
- Improving the efficiency of the system by ensuring effective monitoring
of services and activities.
- To provide optimal drug inventory management by monitoring the drug
movement in the pharmacy.
- To ensure that there exists a level of restricted access based on
functionality and role.
- To ensure that the system is user friendly.
- To be able to generate report within a specified period of time.
1.2 BACKGROUND
Due to the size and quality service of the pharmacy, the pharmacy has a very
large customer base. These customers tend to visit the pharmacy for services
mostly when they close from work. At this period, the number of customers
that patronize the pharmacy is on the increase, thereby making the workload
of the pharmacists much more tedious. This case makes it difficult for the
pharmacist to attend to customers in a short period.
Meanwhile the pharmacist has to ensure satisfaction in services to keep their
customers. The factors mentioned above, results in delay of the services being
rendered to the customers, thereby slowing down sales and risk losing valuable
customers in the long run.

1.3 SCOPE
The scope of this project is limited to the activities of a pharmaceutical store
which includes will improving health outcomes, reduce hospital and long term
care admissions, enhance access and care in the Estate and surrounding
communities and ensuring best use of resources, the use of a computer based
management system for improving the efficiency of a pharmacy is needed and
it is an essential part of any modern continuously evolving society.
The system will not be able to handle drug prescription, drug to drug
interaction. The system will not be able to handle contraindication and
polypharmacy in a prescription; this implies that these services will be
manually completed by the pharmacist.

1.4 DEFINITIONS, ACRONYMS & ABBREVIATIONS

Definitions
A pharmacy was always more than just a place to get your prescription.
Patients treated pharmacists as consultants, someone to help them choose an
over-the-counter medicine or make sense of a prescription’s dosage and
instructions. Always happy to oblige, they rarely had enough information about
a person’s medical history, allergies, or treatment plans to give more complete
advice. This, however, is changing. The healthcare industry is experiencing
transformations and pharmacies are no exception.
Acronyms
System: Is the complex purposeful collection of interrelated components that
work together to take some objectives.
Drug interaction; is a situation in which a substance (usually another drug)
affects the activity of a drug when both are administered together.
Polypharmacy: is the use of multiple medications by a patient, especially when
too many forms of medication are used by a patient, i.e. when more drugs are
prescribed than is clinically warranted.
Contraindication: is the condition or factor that serves as a reason to withhold
a certain medical treatment.

Abbreviations
PMS = Pharmacy Management System
DBMS = Database Management System
GB = Giga Byte

1.5 REFERENCES
- Barbara Griggs. Green Pharmacy: The History and Evolution of Western
Herbal Medicine, Second Edition. Viking press, (1982). Pg 93-97.
- Charles E. Rosenberg, Morris J. Vogel. The Therapeutic Revolution: Essays
in the social history of American Medicine, Second Edition. University of
Pennsylvania press, (1979). Pg 174.
- Peter G Homan, Briony Hudson, Raymond C Row. Popular Medicines: An
illustrated
- Leslie G. Mathews. History of Pharmacy in Britain. Edinburgh, E&S.
Livingstone(1962). Pg 213-223.
- History, Fourth Edition. Trade paperback, Pharmaceutical press (2008).
Pg. 127.
- Stuart Anderson. Making Medicines: A Brief History of Pharmacy and
Pharmaceuticals, Sixth Edition. Jessica Kingsley publisher, (2005). Pg 214.
- Charles E. Rosenberg. History of Medicine and Allied Sciences, Seventh
Edition. University of Pennsylvania press, (2003). Pg 197.
CHAPTER 02
REQUIREMENTS & CONSTRAINS
2.1 Functional Requirements
Selecting Or Writing Requirements for a Pharmacy Management System (PMS)
presents significant challenges and requires considerable insight, particularly
for those in the midst of the initial confusion caused by a newly automated
medication-use process. To address the majority of operational transformations
driven by supporting medication management systems, the PMS must be able
to communicate and exchange data accurately, effectively, consistently, and
multi-directionally with other medication systems, as well as non-medication
systems, and, more importantly, be able to use the information that has been
exchanged.
Traditional pharmacy systems that have focused on and isolated the
transcription, preparation, and distribution phases of the medication-use
process are now being looked upon as the hub for communicating meaningful
information outside the pharmacy domain. The next-generation pharmacy
information management systems must distance themselves from previous
requirements for integration and interfacing and move towards system
interoperability, allowing for real-time sharing of information across the
medication-use cycle. They must move beyond system analysts and or
pharmacists maintaining and managing dictionary tables and medication
information, and require the real-time transmission of drug knowledge from
expert resources directly into the application with little or no manipulation.
Capturing the services, tasks, or functions a pharmacy information
management system is required to perform within the framework of today’s
complex medication-use process calls for broader insight into how information
may be shared outside the pharmacy realm. The sequence and extent of
interactions between systems and providers necessary to deliver these services
or functions have greater implications than previously performed with PMS.
This will require the pharmacy analyst to develop use cases that go beyond the
traditional acute care and hospital pharmacy settings to adequately represent
the pharmacy management system functional requirements necessary in
today’s environment.
Although the focus of this article is on functional requirements, it is important
for pharmacy leaders to articulate and develop use cases for non-functional
requirements, particularly when direct patient care becomes more dependent
on these systems. Some important non-functional requirements to consider
when evaluating a pharmacy management system include:

 System availability
 Allowance for maintainability and enhancements
 Recovery from failure
 Reliability
 Response time
 Throughput

To maintain the integrity of the medication-use cycle, the PMS must effectively
use and communicate information in real time from and to supporting
medication and patient care-related systems. This will facilitate the following
core medication-use functions:

 Order management and communication

 Order verification, confirmation, and fulfillment
 Preparation, distribution, and inventory control, storage, and security
 Administration
 Intervention and monitoring

Order Management and Communication

Pharmacy management systems must provide greater functionality than the

standalone medication order management systems used today. PMS must
permit multidirectional real-time sharing of order processing information
across the continuum of care. PMS must tightly integrate medication order
management with enterprise-wide process tracking systems, allowing
upstream or downstream providers to access information regarding the status
of their order. The system must provide customizable order views, triaging
capabilities, and the ability to communicate delivery or availability time of a
particular order to others involved in the medication-use process. The PMS
must provide a variety of mechanisms for notifying performing departments of
pending orders, including text and verbal paging.

Order Verification, Confirmation, and Fulfillment

The PMS should support multiple verifications of an order(s) by more than one
type of user or multiple users of the same type. Order verification and
confirmation would include the process by which the pharmacist confirms the
appropriateness of an ordered medication, including any alerts or patient-
specific information such as tests, procedures, and labs. Although the alerting
systems in future PMS may play a secondary role, customers must be attentive
to how the system manages these alerts to minimize needless communication.
The system must effectively use upstream alerts to avoid redundant warnings
and must be able to communicate necessary information regarding alert
reconciliations to the provider and nurse. The system must allow the user to
defer verification or modification and facilitate communication with the
physician or nurse regarding the verification status. These communications
must be reconcilable in the PMS.

The system should allow the pharmacist the ability to fulfill an order with the
necessary components to deliver an “administrate-able” dose without altering
the integrity of the order or requiring additional communication with the
ordering provider. The fulfillment process should be transparent to the
ordering process and avoid any additional transcription. The pharmacist must
have the ability to edit the provider’s medication order during verification and
fulfillment, with or without requiring the provider’s signature. Customers
should require considerable flexibility within the verification process to address
state board of pharmacy or specific institutional policies pertaining to changing
components of a medication order and required signing1.

Preparation, Distribution, and Inventory Control, Storage, and Security Once an

order has been verified, confirmed, and fulfilled with the appropriate
components for preparation, the PMS must communicate requirements to the
supporting medication preparation and dispensing systems that will preserve
medication integrity and security. Such systems include automated dispensing
cabinets, robotic IV automation devices, and automated packaging systems.
These systems must work collectively, prioritizing the daily drug preparation
and fulfillment processes and can utilize bar code technology at each step to
enhance efficiency and dispensing accuracy. They must provide the flexibility to
support a number of delivery approaches, focusing on just-in time, patient-
specific distribution and avoiding functionality that promotes unordered drugs
on the patient care units.

The PMS must support systems such as automated dispensing cabinets and
storage and retrieval systems that automate and manage inventory throughout
the receiving, storage, retrieval, and distribution process. Requirements should
include:

 Real-time, on-hand inventory information at the time of patient-specific

medication ordering and/or verification and fulfillment
 Inventory control across multiple facilities
 The ability to automate wholesale medication-ordering processes
 Automated workflow in the distribution process with sequenced orders
that guide staff through emergency, high-priority, routine, and batch
order fulfillment

Administration

Pharmacy management systems play a significant role in the drug

administration and documentation processes. These systems need to act as an
intermediary between ordering and medication administration systems by
translating what has been ordered into a bar code-enabled, “administrate-
able” dose on an electronic “to do” list. Proper documentation of and/or
scanning these doses should fulfill the electronic medication administration
record (EMAR). The EMAR needs to be a continuous document that includes
medications administered across all levels and episodes of care within all areas
of the organization. It must also be capable of linking with the organization’s
billing and financial services systems to improve compliance with billing
regulations. The PMS must provide a means to reconcile doses from
medication administration systems and the order fulfillment and preparation
processes with the pharmacy’s inventory management systems. Customers
seeking a PMS must be assured the system is able to connect ordering and
administration systems, including smart pump systems, allowing for real-time
communication between systems in multiple directions. Imagine the pharmacy
system being able to recognize when to prepare and send another continuous
medication infusion without a nurse or member of the pharmacy intervening.
The PMS must be able to send specific medication administration instructions
directly to an infusion device to deliver a particular medicine over a specified
period of time. These types of requirements reemphasize the need for future
PMS to not only communicate information, but to also use information from
other administration-related systems.

Intervention and Monitoring

Pharmacy management systems must incorporate functionality to support the

documentation and monitoring of pharmacists’ clinical interventions as well as
adverse drug reaction or event reporting. Although most customers expect
these systems to allow for data mining and extraction, many fail to recognize
the importance of allowing users or managers to develop and run queries
spontaneously without dramatically effecting system performance. The ability
for pharmacy managers and users to run ad hoc or planned detailed reports
helps identify trends in intervention acceptance, time spent on clinical
activities, and drug costs avoided. The PMS must provide pharmacy managers
with key financial data to quantify and to improve their clinical programs and
staff. Other features customers should require include:

 Electronic notification or alerting to appropriate care giver(s) of

interventions, adverse drug reactions, and/or medication errors
 Ability to electronically reconcile or share follow-up information of
ongoing monitoring of patients’ clinical events
 Real-time management reporting and trending capabilities that can be
exported and graphed
 The ability to support mobile solutions
 Integrated in-depth drug information

User interface
The user interface is friendly which is easy to use. And having attractive frame
structure which is prepared in assumption with other related systems. Also the
user can change him/her user favorite interfaces that Is available in the system.

2.2 Non-Functional Requirements

This pharmacy management system is able to operate in the following
characteristics.
Usability: Any familiar in using windows operation can operate the system
since it has user friendly user interface. Which have the instruction menu’s how
to use it which self-directive application then can be used the system without
ambiguity.
Reliability: The pharmacy system is available based on the user needs, can
work properly, and do transactions efficiently including safe data management
of the pharmacy. For invalid and malfunctioned operation, the system will
restart in order to prevent data loose as well as safe operation within 5
seconds. The pharmacy system is password protected to change things on the
system. Here the pharmacist manager control over the system by login to the
pharmacy system. Any user can’t use the system but the guest user can see on
general properties of the pharmacy and medicines without password. As result
data is protected and controlled by only the administrator.
Performance: The pharmacy management system operates its function in small
amount of time which is less than two seconds and can be accessed by one
user at a time or concurrently. To access the user must first login to the system
which must have the pharmacy system privileged and also the system can store
data up to 40 GB data. When the system may be busy due to malfunction
operation it may wait up to one minute other ways the pharmacy system
restarts.
Operation: the pharmacy management system is operated and controlled by
the pharmacy manager for safe work.
Supportability: This pharmacy management system operates in any version of
windows operating system. Such as windows xp, windows 2003, windows 7,
windows 8 and other related versions. The system can be easily maintained by
the manager of the pharmacy system by using the prepared documents of the
system for easy maintenance. Other ways it is maintained by the system
developers for corrective and other heavy problems.
Implementation: The system is implemented in Intel(R) Core(TM) i5 processor
with 4 GB RAM,64-bit computer. And it is implemented through testing on both
Black and White testing. The language we use implement the system is
NetBeans IDE, JDK, MYSQL database.
CHAPTER 03
SYSTEM ANALYSIS AND DESIGN
3.1 SYSTEM ANALYSIS
System analysis is the study of sets of interacting entities, including computer
systems analysis. This field is closely related to requirements analysis or
operations research. It is also "an explicit formal inquiry carried out to help
someone identify a better course of action and make a better decision than he
might otherwise have made. System Analysis is a methodology that involves
the application of systematic approaches to collects facts about an existing
system with the aim of improving it or replacing it with more efficient system
within the context of the available resources. In other words, System analysis
can also be viewed as the process of investigating a system, identifying
problems and using the information to recommend improvements to the
system.

3.1.1 ANALYSIS OF EXISTING SYSTEM

Before we analyze the design of the proposed system, we need to carefully
highlight the problems of the existing system so as to avoid recurrence. This
analysis serves as a pointer on how to embark on building the proposed system
that will help the Pharmacist provide optimal drug inventory management by
monitoring the drug movement and state in the pharmacy. The problems of
the current system should be outlined. Below are some of the problems
associated with the existing system;
- Significant amount of time is allocated for writing the order as the
pharmacist needs to go through the stock balance and make rough
estimate for the amount to order based on Figures.
- The state of drugs in stock is manually checked.
- Mistake of selling expired drugs to customers.
- Too much workload on employees
- Filing cabinet in the pharmacy with paper record.
3.1.2 ANALYSIS OF PROPOSED SYSTEM
From the problems listed in the existing system, the implementation of the
proposed system shall focus on;

- Pharmacists having access to the proposed system at any time.

- Ensuring effective policing by providing statistics of the drugs in stock.
- Improving the efficiency of the system by ensuring effective monitoring
of services and activities.
- Generating report within a specified period of time.
- Reducing the employees’ workload.

3.2 REQUIREMENTS DEFINITION

Preliminary investigation plays an important role in developing a satisfactory
requirement. Its’ as a result of thorough investigation of how the current or the
existing system works using the facts gathered at the preliminary investigation
that leads to focusing on the possibility of replacing the existing system or
improving upon the existing system. This task involves information gathering.

3.2.1 METHOD OF INFORMATION GATHERING

Collection of fact is the act of getting and gathering information from various
sources in order to be able to compose the project. Data used for designing of
the system were gathered through several means. Therefore the method used
in the design and collections of information from various sources are as
follows:

- Collecting and analyzing existing materials on the project topic, written

by different expert.
- Studying the present system in detail and the organizational style.

- Knowing and understanding the input and output processes of the

existing system.
- Interviews: A qualitative form of interview was conducted in the
pharmacy to know the equipment needed, and the mode of operation of
the old system.
 - Primary data: This source has to do with the text book contacted for the
development of this project.

3.3 SYSTEM DESIGN

System design is the process of defining the architecture, components,
modules, interfaces, and data for a system to satisfy specified requirements
through system modeling. One could see it as the application of systems theory
to produce development. The design of this system will be user friendly. It shall
be designed in such a way that employees will be able to navigate easily
through the information supplied on the system.
In other words, system design consists of design activities that produce system
specifications satisfying the functional requirements that were developed in
the system analysis process. System design specifies how the system will
accomplish. System design is the structural implementation of the system
analysis.

FIG. 3.3.1 WATERFALL MODEL OF SYSTEM DEVELOPMENT LIFE CYCLE

The diagram above is a system development life cycle that illustrates how the
design of the project is broken down into five different phases, which are
Project Planning, Requirement Gathering, Project Implementation and
Interface Design, Implementation and System Testing, Maintenance and System
Upgrading.
The proposed Pharmacy Management System for Boniks Pharmacy and Stores
will start with project planning by determining the users of the system, aims
and objectives of the project. After these, extensive research will be done to
determine how to design an effective system, as well as to review the current
system. Then, the design was with an initial prototype of the system, and then
refined it based on their suggestions. Phases of analysis, design and
implementation were performed iteratively until users and designers agreed on
a final system specification. At this point, the project could move to the final
implementation phase.

3.4 SYSTEM MODELLING

During the system requirements and design activity, systems may be modelled
as a set of components and relationships between these components. These
are normally illustrated graphically in a system architecture model that gives
the reader an overview of the system organization. System modelling helps to
give more detailed system specifications which are in form of graphical
representations that can describe problem to be solved or the system that is to
be developed. Because of the graphical representations used, models are often
more understandable than detailed natural language description of the system
requirements. Examples of such modelling tool is a System Flowchart.

3.5 SYSTEM FLOWCHART

System flowchart is a type of diagram that represents an algorithm or process,
showing the steps as boxes of various kinds, and their order by connecting
these with arrows. This diagrammatic representation can give a step-by-step
solution to a given problem. Process operations are represented in these boxes,
and arrows connecting them represent flow of control. Flowcharts are used in
analyzing, designing, documenting or managing a process or program in
various fields. Different symbols are used in the flowchart to represent input,
output, decision, connectors and process.
3.5.1 STRUCTURE CHART
3.5.2 SYSTEM FLOWCHART
3.5.3 ADMIN FLOWCHART
3.5.4 SUPERVISOR FLOWCHART
3.5.5 STAFF LOGIN FLOWCHART
3.5 DATABASE DESIGN
This is a shared collection of data that are related or files that are to meet the
immediate need of authorized users. These data may be in form of text,
numeric, date or encoded images.
ADMINISTRATOR LOGIN TABLE
Field Name Field Type Field Length Description
Admin_Usernam Varchar (15) Admin Username

e
Password Varchar (15) Admin password
Table 3.1 Administrator table

Table 3.1 above serves as a repository for administrator details that will be able
to have access to the entire details on the application. It is a table that stores
the administrator login details.
DRUG INFORMATION TABLE
Field Name Field Type Field Length Description
Drug_Name Varchar (15) Drug Name
Drug_ID Varchar (7) Drug Number in

stock
Manufacturer Varchar () Manufacturer
Batch_No Varchar () Batch Number
Production_Date Date/Time () Production Date
Expiry_Date Date/Time () Expiry Date
Dosage Text () Dosage
Reg_Date Date/Time () Registration Date
Quantity Int () Quantity
Cost_Price Int () Cost Price
Interest_Rate Int () Interest Rate
Expected_Sale Int () Expected Sale
Table 3.2 Drug Information Table

This table is named tblDRUG, it depicts the information of the drugs in the
pharmacy.
Table 3.2 shows the information about the drugs in the pharmacy and is being
queried from the database on the drug registration page to show all the drugs
for user to select.
SUPERVISOR LOGIN TABLE
Field Name Field Type Field Length Description
USERNAME Varchar (15) Supervisor username
PASSWORD Varchar (15) Supervisor password
Table 3.3 Supervisor Login Table

Table 3.3 above serves as a repository for supervisor details, which will be able
to have access to the required details on the application as stipulated by the
administrator. It is a table that stores the supervisor login details.
STAFF LOGIN TABLE
Field Name Field Type Field Length Description
USERNAME Varchar (15) Staff Username
PASSWORD Varchar (15) Staff Password
Table 3.4 Staff Login Table

Table 3.4 above serves as a repository for a staff details that will be able to
have access to the required details on the application as stipulated by the
administrator. It is a table that stores the staff login details.
STAFF INFORMATION TABLE
Field Name Field Type Field Length Description
STAFF_NAME Varchar () Staff Name
REGNO Int (6) Registration number
STAFF_SEX Varchar (6) Staff Sex
NATIONALITY Varchar () Nationality
STAFF_STATUS Varchar (15) Staff Status
DOB Date () Date Of Birth
PHONE_NO Int (11) Phone Number
ADDRESS Varchar () Contact Address
STATE Varchar () State
EMAIL Varchar () Email
USERNAME Varchar () Username
PASSWORD Varchar ( 15) Password
Table 3.5 Staff Information Table
Table 3.5 above consist of information of the list and information of the
employed staff in the pharmacy .The information of staff on the required field
can be seen from the table 3.5 above.

CHAPTER 04
SYSTEM IMPLEMENTATION
4.1 CHOICE OF PROGRAMMING LANGUAGE
Choosing a programming language depends on your language experience and
the scope of the application you are building. While small applications are
often created using only one language, it is not uncommon to develop large
applications using multiple languages.
The propose application to be built is not a web based application that needs
internet facilities to function but a standalone application.
The choice of programming language to use for this programm is visual basic.
The structure of the Basic programming language is very simple, particularly as
to the executable code.
Visual Basic has many new and improved features such as inheritance,
interfaces, and overloading that make it a powerful object-oriented
programming language. It is particularly easy to develop graphical user
interfaces and to connect them to handler functions provided by the
application.
Visual Basic fully integrates the .NET Framework and the common language
runtime, which together provide language interoperability, garbage collection,
enhanced security, and improved versioning support. Visual Basic supports
single inheritance and creates Microsoft intermediate language (MSIL) as input
to native code compilers.
4.2 SYSTEM TESTING AND DEBUGGING
Testing is an integral part of software development processes. This is to ensure
that the quality requirement of the application is not compromised by testing
and debugging program modules before they are integrated, testing the system
to ensure an effective inter-operability after integration.
Debugging has to do with fixing of errors encountered during program
execution. System testing deals with the real life testing of the system, to
ascertain how far it has gone in carrying out the expected task. This was carried
out in two phases.
Number one is the source code testing which examine the logic of the program.
Secondly, the specification testing which involves the examination of the
system as regard to what it should do and how it should be done given specific
conditions. This includes inputting data, collecting its output and comparing it
with the output of the old system and assessing it to see if it can replace the
old system.

4.3 SYSTEM DOCUMENTATION

System documentation is a crucial aspect of implementation process. It
describes the working of components and serves as a method of
communication between application developers and users. It also helps future
analysis of application either by the same or different system analysts and
developers.
To setup the system, there must be visual basic 6.0 software installed on the
computer before it can work.

4.4 HARDWARE REQUIREMENT

A minimum hard disk space of 20 Gigabytes (GB)

- RAM size of 1GB

- Pentium 4 dual processor CPU

 - A VGA color monitor

- Mouse

- Keyboard

4.5 SOFTWARE REQUIREMENT

- Windows operating system such as Windows 2000, windows XP,
Windows Vista, Windows 7.

- Visual basic 6.0 software.

4.6 DATABASE SPECIFICATION

A database is a single file which consists of structured data and records which
are stored in minimum or no duplication of data. It is therefore a constructed,
consistent and controlled pool of data. A good database must be common to all
users and independent of the programs which use it to generate output.
However, Microsoft Access was used as the database application tool for
designing the database management system. The database management
system is limited only to database administrator (Management). Whilst the
system designer / developer / programmer is responsible for maintaining and
upgrading of the database and the whole software.

4.7 MODULE DESCRIPTION

HOME PAGE
 Figure 4.1 showing HOME PAGE

Figure 4.1 shows the select login page. It is the first interface that appears on
the screen when the application is being loaded. This interface displays the
name of the application and some other information about the software. The
page consist of logins that exist for several other levels in the application. They
consist of administrator, supervisor and staff login.
ADMIN LOGIN MENU

Figur
e 4.2 Showing Admin login menu

Figure 4.2 above, shows the admin login area of the application. After a
successful login supplying the correct username and password, it opens into
another page where the activities of the admin module are fully stipulated. The
admin controls all the major activitis of this application. Activities such as
Addstaff, Add Drugs, Change Username and password, Manage drugs, View
sales etc can only be controlled by the admin.
Futhermore,the Admin has control over the supervisor and all other user of
the application.
SUPERVISOR LOGIN

Figure 4.3 Showing Supervisor login

Figure 4.3 above shows the supervisor login.The supervisor is an employee that
manages the activities of the pharmacy. After a successfu login, some of the
activities that can be performed by the supervisor are Manage drugs, view
sales, view drugs etc.
The supervisor has a high level of acces on the application except for addition a
new staff.

STAFF LOGIN
 Fig
ure 4.4 Showing Staff login

Figure 4.4 above shows the staff login section.The staff is resonsible for
updating the list of drugs in the store.The staff can also engage in buying and
selling of drugs.The staff is required to provide a valid username and password
in other to be able to perform its activities.
ADMIN MAIN MENU

Fig
ure 4.5 Showing Admin Menu Module
Figure 4.5 above shows the Admin module menue. It list activities that can be
performed by the administrator.the Administrator is the person responsible for
the upgrade,management on the software.the administrator is given an
unlimited access as to performing the operations in the pharmacy.
DRUG REGISTRATION FORM

Figure 4.6 Showing Drug Registration Form

Figure 4.6 above shows the drug registration form. New drugs brought to the
pharmacy are registered here. It receives the details of new batches of drug in
the pharmacy.
STAFF REGISTRATION FORM

Figure 4.7 Showing Staff Registration Form

Figure 4.7 above shows the staff registration form. Important information like
the contact details is collected with this form. A login detail that is, a username
and a password is assigned to the new staff as well.
STORE MANAGER

Figure 4.8 Showing the Store Manager

Figure 4.8 above shows the store manager. Here drugs can be sold. The user
will be required to select a category of drug to sell. Drugs in the pharmacy are
categorized based on their function. When the drug needed to be purchased is
selected, the software generates important information about the drug such as
dosage, available quantity, selling price, expiry date, location of the drug in the
pharmacy etc. Also the user can sell drugs, print bill, check all stock, low stock
or check the expired drugs in stock.
SALES WINDOW

Figure 4.9 Showing Sales

Figure 4.9 shows the list of drugs sold in the pharmacy. There is an option to
view the sales in the pharmacy within a specified date.

4.8 SYSTEM MAINTENANCE

Maintenance is a continuous process of making modifications and upgrading
the application. This usually commences after the application has gone into
use. There are two different ways by which this application can be maintained.
They include:
Additive or Enhancement maintenance: Business processes are dynamic. As
business processes change, applications that support these processes must
evolve to reflect these changes. Thus, for this application to perform optimally
and to meet changing user requirements, it must be modified continuously.
Corrective maintenance: This is required in the event that an error occurred
when the application is in use. Corrections must be made to changes
discovered that can cause malfunctioning of the system.
CHAPTER 05
CONCLUSION AND RECOMMENDATION
5.1 CONCLUSION
Effective implementation of this software will take care of the basic
requirements of the pharmacy management system because it is capable of
providing easy and effective storage of information related to activities
happening in the stipulated area. With these, the objectives of the system
design will be achieved.
In order to allow for future expansion, the system has been designed in such a
way that will allow possible modification as it may deem necessary by the
pharmacy management, whenever the idea arises.

5.2 RECCOMMENDATION
Designing this application (Pharmacy management system) is not an easy task.
It all started from the requirement gathering and passes through so many other
stages before completion.
Based on the benefits of this system and tremendous value it will add to
customer-user satisfaction, the below recommendation will be considered;
It is recommended that the new system should be used with the necessary
specifications of the system requirements and provision for an uninterrupted
power supply should be made available throughout the hours of operation of
the pharmacy to avoid power outage. There should also be basic computer
knowledge for the users of the software.
It is recommended that the software be improved especially in areas of
accounting as it will be of great impact to the development of retail pharmacy.