APPROVAL

This Project entitled “Pharmacy Management System” Prepared and submitted by

Abdullahi Ahmed Siyad , Zakariye Salad Fidow and Abdullahi Abdi nour in partial
fulfillment of the requirements For the degree of Bachelor of Science in Information
Technology has been Examined and approved by the panel on oral examination

Supervisor: Eng. Abdikani Jama Isse

Date: _______/ _______/ ____________

Signature: ________________________

Dean Faculty of Computer Science

Mr. Ismail Abdullahi Ahmed ______________________

Date: _______/ _______/ ____________________

i
 DECLARATION
We declare this thesis is our original work and not has been presented for a degree or any other
academic award in any university or institutional of learning.

Student Name: Abdullahi Ahmed Siyad

Signature: ___________________________

Date: _____/_____ /____________________

Student Name: Abdullahi Abdi nour

Signature: ___________________________

Date: _____/_____ /___________________

Student Name: Zakariye Salad Fidow

Signature: ___________________________

Date: _____/_____ /___________________

ii
 ACKNOWLEDGEMENT
First of all, we are very thankful to Almighty Allah, who has empowered us with His
guidance throughout my life to achieve our missions in the life. We are thankful to beloved
lecturer his continuous, We would like to offer our gratitude to our supervisor/lecturer Eng.
Abdikani Jama Isse for giving our valued guidelines that enabled us to work efficiently.
Without his kind supervision, we would never have had the chance to complete our research
work on time. Lastly, we would like to dedicate this project to our beloved parents who
sacrificed all their luxuries to educate us, to all the teachers and lecturers who have
contributed directly or indirectly to our education up to where we are now and to all
classmates at the Salaam University who have been supplementary support to our study
efforts.

iii
 ABSTRACT
This project is insight into the design and implementation of a Kaaliye 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.

iv
 Table of Contents
APPROVAL ............................................................................................................................................ i
DECLARATION .................................................................................................................................... ii
ACKNOWLEDGEMENT ..................................................................................................................... iii
ABSTRACT........................................................................................................................................... iv
CHAPTER ONE ..................................................................................................................................... 1
INTRODUCTION .................................................................................................................................. 1
1.0 Introduction ................................................................................................................................... 1
1.1 Background of the System ............................................................................................................ 3
1.2 Problem Statement ........................................................................................................................ 4
1.3 Purpose of the Project ................................................................................................................... 5
1.4 Project objectives .......................................................................................................................... 5
1.5 Project Scope ................................................................................................................................ 5
1.6 Significance of the project ............................................................................................................ 5
1.7 Report organization ...................................................................................................................... 6
CHAPTER TWO .................................................................................................................................... 7
LITERATURE REVIEW ....................................................................................................................... 7
2.0 INTRODUCTION ........................................................................................................................ 7
2.1 Theoretical and Conceptual Development .................................................................................... 7
2.2 Case Study Of The Research ........................................................................................................ 8
2.3 Compare Between exiting system ................................................................................................. 8
2.3.1 PrimeRx ..................................................................................................................................... 8
2.3.2 CoverMyMeds ........................................................................................................................... 9
2.3.3 Kaaliye pharmacy system .................................................................................................... 10
2.4 chapter summary ......................................................................................................................... 11
CHAPTER THREE .............................................................................................................................. 12
SOFTWARE PLANING AND ANAYLAYSING ........................................................................... 12
3.0 INTRODUCTION ...................................................................................................................... 12
3.1 OPERATIONAL FRAMEWORK .............................................................................................. 12
3.2 WORK BREAK DOW STRUCTURE (WBS) ........................................................................... 14
3.3 SYSTEM REQUIREMENT SPECIFICATION ......................................................................... 14
3.4 USER REQUIREMENTS DEFINITION ................................................................................... 15

v
 3.5 PROBLEM ANAYLAYSIS IDENTIFICATION ...................................................................... 15
3.6 REQUIREMENTS GATHERING TECHNIQUES ................................................................... 15
3.7 INTERVIEW .............................................................................................................................. 15
3.8 OBSERVESTION....................................................................................................................... 16
3.9 PROCESS MODELING ............................................................................................................. 16
3.10 Data flow Diagram (DFD) ........................................................................................................ 16
3.10.0 Data flow Diagram (DFD) ..................................................................................................... 17
3.11 Unified Modeling Language (UML)......................................................................................... 17
3.12 Use Case Diagram (UCD)......................................................................................................... 19
3.13 Data Modeling .......................................................................................................................... 20
3.14 Entity Relationship Diagram ..................................................................................................... 20
3.15 ERD SYMBOLS ...................................................................................................................... 21
3.17 ERD of the proposed system ..................................................................................................... 23
3.18 Suitable Solutions Strategies Of The Process System .............................................................. 23
4.19 System Feasibility ..................................................................................................................... 24
3.20 Technical Feasibility ................................................................................................................. 24
3.21 Operational Feasibility .............................................................................................................. 24
3.21 Economic Feasibility ................................................................................................................ 25
3.22 Schedule Feasibility .................................................................................................................. 25
3.23 Chapter Summary ..................................................................................................................... 25
CHAPTER FOUR................................................................................................................................. 26
SOFTWARE DESING ......................................................................................................................... 26
4.0 Introduction ................................................................................................................................. 26
4.1 Architectural Design ................................................................................................................... 26
4.2 User Interface Design ................................................................................................................. 27
4.3 Database Storage Design ............................................................................................................ 27
4.4 Database Design.......................................................................................................................... 28
4.5 Database Normalization .............................................................................................................. 28
4.6 First Normal Form (1NF)............................................................................................................ 28
4.7 Second Normal Form (2NF) ....................................................................................................... 29
4.8 Third Normal Form (3NF) .......................................................................................................... 29
4.9 Normalized Tables of the proposed system ................................................................................ 29
4.9 Transforming E-R Diagrams into Relations ............................................................................... 30
4.10 Data Dictionaries ...................................................................................................................... 30

vi
 4.11 Designing Forms and Reports ................................................................................................... 34
4.12 Chapter Summary ..................................................................................................................... 39
CHAPTER FIVE .................................................................................................................................. 40
SYSTEM IMPLEMENTATION .......................................................................................................... 40
5.0 Introduction ................................................................................................................................. 40
5.1 Coding Phase .............................................................................................................................. 40
5.1.0 Add Drug ................................................................................................................................. 40
5.2 Test system implementation........................................................................................................ 44
5.3 Development testing Release testing .......................................................................................... 44
5.4 Development testing ................................................................................................................... 44
5.5 Releasing Testing ........................................................................................................................ 44
5.6 User testing ................................................................................................................................. 44
5.7 Developing User manuals ........................................................................................................... 45
5.8 Chapter Summary ....................................................................................................................... 45
CHAPTER SIX ..................................................................................................................................... 46
CONCLUSION & ENHANCEMENT ................................................................................................. 46
6.0 Introduction ................................................................................................................................. 46
6.1 Objective achievement ................................................................................................................ 46
6.2 Weaknesses and problems of the system .................................................................................... 46
6.3 Future Work ................................................................................................................................ 46
6.4 Chapter Summary ....................................................................................................................... 47
APPENDICES .................................................................................................................................. 47
APPENDIX A ................................................................................................................................... 47
APPENDIX B ................................................................................................................................... 48
Time framework of the developing the proposed system ................................................................. 48
reference................................................................................................................................................ 49

vii
LIST OF TABLES
Table 2.3 Comparison between exist ...................................................................................... 11

Table 3.3 SYSTEM REQUIREMENT ................................................................................... 14

Table 3.20 Technical Feasibility ............................................................................................. 24

Table 3.21 Operational Feasibility .......................................................................................... 24

Table 3.21 Economic Feasibility ........................................................................................... 25

Table 3.22 Schedule Feasibility .............................................................................................. 25

Table 4.6 First Normal Form (1NF) ....................................................................................... 28

Table 4.7 Second Normal Form (2NF) ................................................................................... 29

Table 4.8 Third Normal Form (3NF) ...................................................................................... 29

Table 4.9 Normalized Tables .................................................................................................. 29

Table 4.10 User registration table ........................................................................................... 31

Table 4.10 Name:Drugs .......................................................................................................... 31

Table 4.10 Name:DrugEntry ................................................................................................. 31

Table 4.10 Name:DrugDetails 1 ............................................................................................. 32

Table 4.10 Name:Sales .......................................................................................................... 32

viii
LIST OF FIGURES

Figure 2.3.1 PrimeRx ................................................................................................................ 9

Figure 2.3.2 CoverMyMeds .................................................................................................... 10

Figure 2.3.3 Kaaliye pharmacy system .................................................................................. 10

Figure 3.1 OPERATIONAL FRAMEWORK ........................................................................ 13

Figure 3.2 WORK BREAK DOW STRUCTURE (WBS) ..................................................... 14

Figure 3.10 Data flow Diagram (DFD) ................................................................................... 17

Figure 3.10.1 Data flow Diagram (DFD) ................................................................................ 17

Figure 3.12 Use Case Diagram (UCD) ................................................................................... 19

Figure 3.15 ERD SYMBOLS ................................................................................................ 21

Figure 3.17 ERD of the proposed system ............................................................................... 23

Figure 4.1 Architectural Design .............................................................................................. 26

Figure 4.2 User Interface Design ............................................................................................ 27

Figure 4.9 Transforming E-R Diagrams Into Reationship...................................................... 30

Figure:4.11 Login page ......................................................................................................... 35

Figure:4.11 Add Drug .......................................................................................................... 35

Figure:4.11 Drug Entry ........................................................................................................... 36

Figure: 4.11 Drug Details ...................................................................................................... 37

ix
Figure:4.11 Sales .................................................................................................................... 37

x
 CHAPTER ONE

INTRODUCTION

1.0 Introduction
The pharmacy management system, also known as the pharmacy information system, is a
system that stores data and enables functionality that organizes and maintains the medication
use process within pharmacies. (wekipedia, 2019)

pharmacy the science and art concerned with the preparation and standardization of drugs.
Its scope includes the cultivation of plants that are used as drugs, the synthesis of
chemical compounds of medicinal value, and the analysis of medicinal agents. Pharmacists
are responsible for the preparation of the dosage forms of drugs, such as tablets, capsules, and
sterile solutions for injection. They compound physicians’, dentists’, and veterinarians’
prescriptions for drugs. The science that embraces knowledge of drugs with special reference
to the mechanism of their action in the treatment of disease is pharmacology. (john C.karantz,
2019)

The beginnings of pharmacy are ancient. When the first person expressed juice from a
succulent leaf to apply to a wound, this art was being practiced. In the Greek legend,
Asclepius, the god of the healing art, delegated to Hygieia the duty of compounding his
remedies. She was his apothecary or pharmacist. The physician-priests of Egypt were divided
into two classes: those who visited the sick and those who remained in the temple and
prepared remedies for the patients. In ancient Greece and Rome and during the Middle Ages
in Europe, the art of healing recognized a separation between the duties of the physician and
those of the herbalist, who supplied the physician with the raw materials from which to make
medicines. The Arabian influence in Europe during the 8th century AD, however, brought
about the practice of separate duties for the pharmacist and physician. The trend toward
specialization was later reinforced by a law enacted by the city council of Bruges in 1683,
forbidding physicians to prepare medications for their patients. In America, Benjamin
Franklin took a pivotal step in keeping the two professions separate when he appointed an
apothecary to the Pennsylvania Hospital The development of the pharmaceutical
industry since World War II led to the discovery and use of new and
effective drug substances. It also changed the role of the pharmacist. The scope

1
for extemporaneous compounding of medicines was much diminished and with it the need
for the manipulative skills that were previously applied by the pharmacist to the preparation
of bougies, cachets, pills, plasters, and potions. The pharmacist continues, however, to fulfill
the prescriber’s intentions by providing advice and information; by formulating, storing, and
providing correct dosage forms; and by assuring the efficacy and quality of the dispensed or
supplied medicinal product.. (john c.karanz, 2019)

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 (Altexsoft, 2021)

Kaaliye Pharmacy management system is a management system that is designing to improve

accuracy and to enhance safety and efficiency in the pharmaceutical store. It is online system
based which helps the Pharmacist to improve inventory management, cost,medical sells,and
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.

A pharmacy management system is used to manage all transactions and records related to
managing sales and inventory. It is a computer-based system that aids pharmacists in
managing inventories, costs, and other factors including medical safety The system allows the
user to enter a manufacturing and expiry date for a particular product or drug during opening
stock and sales transaction.

This paper discusses development of pharmacy management system and Kaaliye

Pharmacy(kp)is the case study of this project;. This is pharmacy management system,This
paper is categorized sections: background of the system Problem statement, purpose of the
project, Project objectives, Project Scope, Significance of the project, Report organistion

2
1.1 Background of the System
A pharmacy information system is a platform that streamlines and standardizes pharmacy
operations. Find out about its origins and evolution. The art and science of pharmacy traces
back to ancient times of the Egyptians and Greeks. Pharmacy was once a subset of medicine,
but eventually, they split. The first college of pharmacy was the Philadelphia College of
Pharmacy, founded in 1821. Louis Dufilho, Jr. was the first licensed pharmacist, opening the
first pharmacy in New Orleans. Of course, so much has changed, and technology now plays a
huge role in pharmacy operations, specifically the pharmacy information system.
(infowekers, 2021)

Pharmacy information systems began with a simple user interface and little functionality.
They were, however, a giant leap for pharmacists regarding organizing and storing patient
data. The biggest challenge most pharmacies had in the early days was switching to another
software. Over two decades ago, it was impossible to do this without it being completely
manual. InfoWerks actually changed that, completing the first pharmacy data conversion. The
current market for pharmacy software is large and broad. There are options for almost every
type of pharmacy: retail, hospital, LTC, specialty, and more. Pharmacists and technicians use
these systems to manage:Prescriptions dispensing and labeling,Patient information and
medication history, Physician monitoring, Inventory,Billing and insurance,Pricing structure
variables, Reporting, Clinical screening (i.e., allergies, drug interactions, etc.).

The newest pharmacy platforms are robust software engines that automate many practices
and ensure that you’re always compliant with regulations. It’s become the central location of
data, which can be analyzed and evaluated to make better decisions about care and business,
in general.. (infowekers, 2021)

Future iterations of these software systems will bring even more functionality. Right now,
there’s a push toward interoperability with EHRs, but that same demand applies to pharmacy
systems. New tools that are data science related to track data trends and challenges are likely
to become prevalent.

These platforms will also play a role in comprehensive medical management and medication
adherence. If pharmacists can proactively view patients at risk of not adhering to the
prescription plan, outreach could help. Support from a pharmacist and the prescriber could
curb medication no adherence, which costs the healthcare system millions every year.

3
Further, the data they collect could also enhance public health initiatives to better understand
social determinants of health (SDOH), chronic diseases, and addiction. (infowekers, 2021)

The use of the current pharmaceutical management system is essential. It involves

information technology, as stated by important from demand to supply, as well as the
importance of information about drugs itself both from the point of use and the side effect or
consequences of use. This system contains an evaluation of the patient’s opinion about
medicines and hospital pharmacy services so that services bases on user perceptions, which
can also develop through collaboration. Optimal control of pharmaceutical supplies is the
first step in the healing phase of each patient from a treatment point, but it requires the
application of information technology and computer in addition to inventory theory.
(Research on Pharmacy management, 2019)

Kaaliye pharmacy system which helps the Pharmacist to improve inventory management,
cost, medical safety etc. Pharmacy management system was developed to ensure the security
of information and reliability of Pharmacy records when accessing and providing services to
the customers.

1.2 Problem Statement

The Current pharmacy system were manually base system which all most all works on the
pharmacy organization is accomplished by paper, In Current system almost kaaliye pharmacy
do not use computerized system and use manual searching of medicine on shelf because of
manual based system and there is nothing which gives alarm for the finished or sold medicine

Pharmacy management has kept paper record, Managing a very large pharmacy with records
on papers will be difficult to keep track of inventories with the drugs in the store, expiry
date, sales medical ,quantity of drugs available based on the categories and their functions.

4
1.3 Purpose of the Project

The pharmacy management system is built for the sake of ensuring effective clear data saving
and manipulating system, the pharmacy management system project highly minimize time
and resource by which, searching the medicine data you can get the data in quickly time.

The primary aim of is to improve accuracy and enhance safety and efficiency in the
pharmaceutical store

1.4 Project objectives

The objectives of the project:

1. To design easily accessibility of the users

2. To design easily accessibility of sales report

3. To design accessibility of stock report

4. To develop maintaining correct database by providing an option to update the drug in

stock.

1.5 Project Scope

This System was developed for kaaliye pharmacy, This project covered the following areas:
Sales management, Stock management, expired date management and report management.

This proposed system will be developed frontend htmlY&css, backend php and mysql ,

It was implemented between Oct, 2022 to JUL2023. This project is for kaaliye pharmacy
Mogadishu-Somalia.

1.6 Significance of the project

Pharmacy management system is actually a software which handle the essential data and save

the data and actually about the database of pharmacy and its management

Benefits Of Pharmacy Management System

 Drug – KPMS The user of the system can create new drug and update.

5
  Accessibility – Improved control over pharmacy operations.

 Reduced paperwork – Eliminates paper-based workflow and simplifies data storage

and retrieval.

 Expression – The system can Tell Drug the expiration date is less than 6 month

1.7 Report organization

APPROVAL DECLARATION ACKNOWLEDGEMENT ABSTRACT TABLE OF

CONTENTS LIST OF TABLES LIST OF FIGURES

The first part of this chapter is background: Introduction Background of the system Problem
statement Purpose of the project, Project objectives Project Scope Significance of the project
Report organization. Chapters 2: LITERATURE REVIEW Introduction Theoretical and
Conceptual Development Case study of the research Compare Between exiting system
Chapter Summary. Chapter 3: SOFTWARE PLANNING AND ANALYZING Introduction
Operational Framework Work Break down structure (WBS) System Requirement Software
Requirement Specification User Requirements Definition Problem Analysis Identification
Requirements Gathering Techniques Interview Observation Process Modeling Data flow
Diagram (DFD) Unified Modeling Language (UML) Use Case Diagram (UCD) Data
Modeling Entity Relationship Diagram ERD SYMBOLS TYPES OF RELATIONSHIP ERD
of the proposed system Suitable solution Strategies of the proposed system, System
Feasibility Technical Feasibility Operational Feasibility Economic Feasibility Schedule
Feasibility Chapter Summary. Chapter 4: SOFTWARE DESIGN Introduction Architectural
Design User Interface Design Database Storage Design Database Design Database
Normalization First Normal Form (1NF) Second Normal Form (2NF) Third Normal Form
(3NF) Normalized Tables of the proposed system Transforming E-R Diagrams into Relations
Data Dictionaries Designing Forms and Reports Chapter Summary. Chapter5: SYSTEM
IMPLEMENTATION Introduction Coding Phase Test system implementation Development
testing Release testing User testing Developing User manuals Chapter Summary. Chapter 6
CONCLUSION & ENHANCEMENT Introduction Objective achievement Weaknesses and
problems of the system Future Work Chapter Summary
6
 CHAPTER TWO

LITERATURE REVIEW
2.0 INTRODUCTION
A pharmacist is a medical professional who dispenses drugs to patients according to a
prescription ordered by a physician or other clinician. Pharmacists have an in-depth
knowledge of the chemistry of various drugs and how they react in humans, and also how
drugs interact with each other (Charles E. Rosenberg, 1980). Pharmacists must accurately
measure and package medicine, ensuring its dosage and safety to be administered properly to
a patient. While the pharmacist does not typically select or prescribe the medication, the
pharmacist educates the patient on how to take the medication and what reactions or
problems to be avoided.

As medication experts, pharmacists are concerned with safeguarding the public's health in
matters relating to medication distribution and use and disease state management.
Pharmacists play a vital role in improving patient care through the medicine and information
they provide. (IBTOYE AHMED, 2013)

PHARMACY PRACTICE IN THE PAST: This gives an overview of events that have
occurred in pharmacy practice through several ages both in the past and present, and also
indicates possible events of the future. (IBTOYE AHMED, 2013)

2.1 Theoretical and Conceptual Development

THIS SECTION DICUSSES THE CONCEPTS OF PHARMACY, MANAGEMENT,

SYSTEM

-PHARMACY: is the science and practice of discovering, producing, preparing, dispensing,

reviewing and monitoring medications, aiming to ensure the safe, effective, and affordable
use of medicines. It is a miscellaneous science as it links health sciences with pharmaceutical
sciences and natural sciences. The professional practice is becoming more clinically oriented
as most of the drugs are now manufactured by pharmaceutical industries. Based on the
setting, pharmacy practice is either classified as community or institutional pharmacy.
Providing direct patient care in the community of institutional pharmacies is
considered clinical pharmacy. (WIKIPEDIA, 2017)

7
-MANAGEMENT: (or managing) is the administration of an organization, whether it is
a businesS, a non-profit organization, or a government body. It is the art and science of
managing resources of the business.

Management includes the activities of setting the strategy of an organization and coordinating
the efforts of its employees (or of volunteers) to accomplish its objectives through the
application of available resources, such as financial, natural, technological, and human
resources. "Run the business"[1] and "Change the business" are two concepts that are used in
management to differentiate between the continued delivery of goods or services and
adapting of goods or services to meet the changing needs of customers - see trend. The term
"management" may also refer to those people who manage an organization—managers.
(WIKIPEDIA, 2016)

-SYSTEM: A system is a collection of elements or components that are organized for a

common purpose. The word sometimes describes the organization or plan itself (and is
similar in meaning to method, as in "I have my own little system") and sometimes describes
the parts in the system (as in "computer system").

A computer system consists of hardware components that have been carefully chosen so that
they work well together and software components or programs that run in the computer.

The main software component is itself an operating system that manages and provides
services to other programs that can be run in the computer. (TECHTARGET, 2014)

2.2 Case Study Of The Research

Kaaliye Pharmacy Case Study Of The Research kaaliye Pharmacy Is A Pharmacy That
Sells Whole Sell Drugs, Pharmacy has Need A system Simplifies The Works.

2.3 Compare Between exiting system

There are many systems used before for this research we have choosing some of web bases
Pharmacy system includes:

2.3.1 PrimeRx is a total pharmacy dispensing software that enhances overall pharmacy
productivity and customer relationship management.

8
Figure 2.3.1 PrimeRx

2.3.2 CoverMyMeds is a cloud-based platform that provides healthcare providers and

pharmacies with tools to manage and streamline patients' journeys across the entire
medical process. Using the built-in online portal, providers can facilitate PA & hub
enrollment through point of medication selection.

9
Figure 2.3.2 CoverMyMeds 1

2.3.3 Kaaliye pharmacy system: This is Online system that Use Kaaliye pharmacy The system have
many factions The system can register new drug and and update also have.

Figure 2.3.3 Kaaliye pharmacy system 1

10
Feature PrimeRx CoverMyMeds Proposed System
Sign up ✓ × ✓
Login ✓ ✓ ✓
drugs ✓ ✓ ✓
Customer ✓ ✓ ×
Sales ✓ ✓ ✓
Expiration ✓ ✓ ✓
Table 2.3 Comparison between exist 1

2.4 chapter summary

This section delves into the fascinating world of pharmacy, management, and systems.
Pharmacy, the art and science of ensuring safe and effective medication use, blends health
sciences, pharmaceutical sciences, and natural sciences. With a growing focus on clinical
practice, pharmacy professionals play a crucial role in patient care within community or
institutional settings. Management, on the other hand, is the art of resource administration in
organizations, be it businesses, non-profit entities, or government bodies. It involves setting
strategies, coordinating employee efforts, and adapting to evolving customer needs. Finally,
systems are collections of elements united by a common purpose. From computer systems
with hardware and software components to well-organized plans, systems are the backbone
of efficiency and functionality.

Embarking on a captivating case study, we explore Kaaliye Pharmacy—a wholesale drug

provider in need of a streamlined system. By investigating their unique requirements, we aim
to develop an innovative solution that simplifies their operations and enhances overall
productivity.

In this captivating chapter, we conduct a comprehensive comparison of web-based pharmacy

systems. Our chosen contenders are PrimeRx, a robust pharmacy dispensing software
renowned for enhancing productivity and customer relationship management.

11
 CHAPTER THREE
SOFTWARE PLANING AND ANAYLAYSING

3.0 INTRODUCTION
Software is a set of instructions, data or programs used to operate computers and execute
specific tasks. It is the opposite of hardware, which describes the physical aspects of
computer. The word software was first used by John Turkey in 1958. The theory of software
was first proposed by Alan Turing in 1935. (Linda Rosencranc, 2021)

Software is often divided into three categories:

1.System software serves as a base for application software. System software includes
devicedrivers, operating systems (OSs), compilers, disk formatters, text editors and utilities
helping thecomputer to operate more efficiently

2.Programming software is a set of tools to aid the developers to write programs. The various
toolsavailable are compilers, linkers, debuggers, interpreters and text editors.

3.Application software is intended to perform certain tasks. Examples of application

softwareinclude office suites, gaming applications, database systems and educational
software.

Planning:A basic management function involving formulation of one or more detailed plans
toachieve optimum balance of needs or demands with the available resources.Software
Analyses is Software analysis patterns or analysis patterns in software engineering
areconceptual models, which capture an abstraction of a situation that can often be
encountered inmodelling.[

3.1 OPERATIONAL FRAMEWORK

The Operational Framework starts planning, proposal, chapter one introduction, chapter two
literature review, chapter three software planning & analyzing chapter four software design,
chapter five system implementation and finally chapter six conclusions & enhancement

12
 Initialization
Phase one
Literature review

Data
Phase two

Interview Observation

Analyzing

Designing

Phase tree System

acceptanc No
e

Yes

Test the System

Report writing

Figure
3.1 OPERATIONAL
3.1 1 FRAMEWORK 1

13
3.2 WORK BREAK DOW STRUCTURE (WBS)
A work-breakdown structure (WBS) in project management and systems engineering is
a deliverable-oriented breakdown of a project into smaller components. A work breakdown
structure is a key project deliverable that organizes the team's work into manageable sections.
(WIKIPEDIA, 2010)

The initial phase in delivering a Project Plan is the production of the Work Breakdown
Structure (WBS), listing all the phases, activities and tasks that make up the project. The
WBS product of this system is shown below

Rregistration of users

Sign in & sign out process

SALES MANAGEMENT

STOCK MANAGEMENT

DRUG MANGAEMENT

Reports

Figure3.2 WORK BREAK DOW STRUCTURE (WBS)

3.3 SYSTEM REQUIREMENT SPECIFICATION

A SRS is a total meaning of the expected reason and condition for programming under
development

Software :
Versions

Operating System Windows 7,10,11

Front End HTML,CSS

:

Back End PHP

: And MySQL
Server

Server APACHE
:

Browser Google
: Chrome,
Internet Explorer and
etc.

Table 3.3 SYSTEM REQUIREMENT 1

14
3.4 USER REQUIREMENTS DEFINITION
the user of the this system is required simplifying the hard work in manual base example
when costumer went whole sale medicine and you don’t know how much medicine are
available the employee must be search the stock and then tell the customer did not get the
medicine

3.5 PROBLEM ANAYLAYSIS IDENTIFICATION

Pharmacy management system of kaaliye pharmacy will be used in the pharmacy this system
is able to oversee all essential pharmacy tasks the user enabled to visit the system and manage
the database in every time and Everywhere and the project will also be useful for medical
store for getting Easily

3.6 REQUIREMENTS GATHERING TECHNIQUES

Requirements gathering techniques are a process of collecting information from various
sources, There are two fundamental kinds of collecting data and they are: Interview and
Observation. The researchers has taken observation because it enables researchers to
specifically observe what individuals do practically rather than relying on what individuals
say they did and researchers document program activity takes time and cost gathering
providing documentation, rather than relying on recollections of the events.

3.7 INTERVIEW
An interview is a qualitative research method that relies on asking questions in order
to collect data Interviews involve two or more people, one of whom is the interviewer asking
the questions. (tegan george, 2022)

There are several types of interviews, often differentiated by their level of structure.

 Structured interviews have predetermined questions asked in a predetermined order.

15
  Unstructured interviews are more free-flowing.

 Semi-structured interviews fall in between.

3.8 OBSERVESTION
Observational research is a research technique where you observe participants and
phenomena in their most natural settings. This enables researchers to see their subjects make
choices and react to situations in their natural setting, as opposed to structured settings like
research labs or focus groups. (delvetool, 2019)

3.9 PROCESS MODELING

Systems may be represented as a set of components with interactions between them
throughout the system requirements and design activity. In a system architectural model,
which provides the reader with an overview of the system organization, these are typically
shown graphically. System modeling aids in providing more precise system requirements,
which take the form of graphical depictions of the issues that need to be resolved or the
systems that need to be created. Models are frequently easier to understand than in-depth
English language descriptions of the system requirements because they use graphical
representations.

3.10 Data flow Diagram (DFD)

The abbreviation for a data flow diagram is DFD. DFD describes the data flow of a system or
process. It also provides information on each entity's inputs, outputs, and the process itself.
There are no loops, decision rules, or control flows in DFD. A flowchart can describe specific
operations depending on the type of data.

It is a graphic tool that can be used to communicate with users, supervisors, and other staff
members. It can be used to analyze existing as well as proposed system

It provides an overview of :

-What data is system processes.

-What transformation are performed.

-What data are stored.

-What results are produced , etc.

16
Figure 3.10 Data flow Diagram (DFD)

3.10.0 Data flow Diagram (DFD)

Registration of Sign in & sign out

process Sales management
users

pharmacy Drugs management

Stock management management system

Reports

Figure 3.10.0 Data flow Diagram (DFD)

3.11 Unified Modeling Language (UML)

Unified Modeling Language (UML) is a general purpose modelling language.

The primary goal of UML is to establish a uniform method for visualizing a system's design process.
It resembles blueprints used in other engineering disciplines quite a bit.

UML is a visual language rather than a programming language. To depict the behavior and structure
of a system, we use UML diagrams. Software engineers, businesspeople, and system architects can
benefit from UML's modeling, design, and analysis tools.

17
Structural UML Diagrams –

Class Diagram – The most widely use UML diagram is the class diagram. It is the building
block of all object oriented software systems. We use class diagrams to depict the static
structure of a system by showing system’s classes,their methods and attributes. Class
diagrams also help us identify relationship between different classes or objects.

Composite Structure Diagram – We use composite structure diagrams to represent the

internal structure of a class and its interaction points with other parts of the system. A
composite structure diagram represents relationship between parts and their configuration
which determine how the classifier (class, a component, or a deployment node) behaves.

Object Diagram – An Object Diagram can be referred to as a screenshot of the instances in a

system and the relationship that exists between them. Since object diagrams depict behaviour
when objects have been instantiated, we are able to study the behaviour of the system at a
particular instant. An object diagram is similar to a class diagram except it shows the
instances of classes in the system. We depict actual classifiers and their relationships making
the use of class diagrams.

Component Diagram – Component diagrams are used to represent how the physical
components in a system have been organized. We use them for modelling implementation
details. Component Diagrams depict the structural relationship between software system
elements and help us in understanding if functional requirements have been covered by
planned development. Component Diagrams become essential to use when we design and
build complex systems. Interfaces are used by components of the system to communicate
with each other.

Deployment Diagram – Deployment Diagrams are used to represent system hardware and its
software.It tells us what hardware components exist and what software components run on
them.We illustrate system architecture as distribution of software artifacts over distributed
targets. An artifact is the information that is generated by system software. They are primarily
used when a software is being used, distributed or deployed over multiple machines with
different configurations.

18
Package Diagram – We use Package Diagrams to depict how packages and their elements
have been organized. A package diagram simply shows us the dependencies between
different packages and internal composition of packages. Packages help us to organise UML
diagrams into meaningful groups and make the diagram easy to understand. They are
primarily used to organise class and use case diagrams.

3.12 Use Case Diagram (UCD)

Drug

Drug Entry

Sales

Users
Admin User
n
Drug Details

Figure 3.12 Use Case Diagram (UCD)

19
3.13 Data Modeling

Data modeling is the process of creating a conceptual representation of data and its
relationships to support understanding, analysis, and organization of information within a
specific domain or system. It involves identifying and defining the structure, constraints, and
rules that govern the data and how it is organized.

Data modeling aims to capture the essential aspects of the real-world entities, their attributes,
and the relationships between them. By creating a data model, we can effectively
communicate and visualize how data should be structured and organized, enabling better
decision-making, system design, and data management.

3.14 Entity Relationship Diagram

An Entity-Relationship Diagram (ERD) is a graphical representation of the entities (objects),

attributes, and relationships within a system or domain. It is a popular modeling tool used in
data modeling to visually depict the structure and associations of data.

When creating an ERD, you typically start by identifying the entities and their attributes.
Then, you determine the relationships between entities and specify the cardinality and
participation constraints. The resulting diagram provides a visual representation of the data
structure, helping stakeholders understand the system's data requirements and relationships.

ERDs are widely used in database design, software engineering, and systems analysis. They
serve as a communication tool between stakeholders, including developers, designers, and
business analysts, to ensure a common understanding of the data model. ERDs can be created
using specialized software tools, drawing tools, or even by hand.

20
3.15 ERD SYMBOLS

Figure 3.15 ERD SYMBOLS

21
3.16 Types of Relationship
Three types of relationships can exist between two entities, which are given below and also
discussed in this article with examples.

 One-to-One relationship.

 One-to-Many relationship or Many-to-One relationship.

 Many-to-Many relationship.

22
3.17 ERD of the proposed system
The following figure 3.5 shows us the ERD diagram

Username Password

Phone
Login

Email
ID

Pass User Has Drug.ID

Qty
Name
D.ID
ID Drug Entry Price

D.Name
Detail.ID
Manage Drug Type
Drug.ID

Drug Detail
Qty

Sales
Price

Expire date S.ID D.Name Qty Price Sales Date

Figure 3.17 ERD of the proposed system

3.18 Suitable Solutions Strategies Of The Process System

The current pharmacy system is a manually operated system that mostly relies on paper for pharmacy
organization. Almost all pharmacies in the current system still search for medications manually. Now
it comes to the development of a new system that manage all the system.

23
4.19 System Feasibility
A feasibility study for an information system program is covering many or all important
points of the project so as to declare whether or not an organization should proceed with its
execution.

Feasibility study is divided into four types:

1. Technical feasibility.

2. Operational feasibility.

3. Economic feasibility.

4. Schedule feasibility.

3.20 Technical Feasibility

Hardware Price

Computer 250

Printer 50

Scanner 40

Total 340

Table 3.20 Technical Feasibility

3.21 Operational Feasibility

Operational Feasibility Price

ONJOB TRAINING 50

DEVELOPERS 100

DOCUMENTATION 10

Total 160

Table 3.21 Operational Feasibility

24
3.21 Economic Feasibility
ECONOMIC Price

TECHNICAL 340

OPERATIONAL 160

Total 500

Table 3.21 Economic Feasibility

3.22 Schedule Feasibility

Phase Duration

Specification 4 weeks

Development 9 weeks

Implementation 8 weeks

Validation 3 weeks

Total 24 weeks

Table 3.22 Schedule Feasibility

3.23 Chapter Summary

This chapter we learn software planning and analyzing, Introduction Operational Framework
Work Break down structure (WBS) System Requirement Software Requirement
Specification User Requirements Definition Problem Analysis Identification Requirements
Gathering Techniques Interview Observation Process Modeling Data flow Diagram (DFD)
Unified Modeling Language (UML) Use Case Diagram (UCD) Data Modeling Entity
Relationship Diagram ERD SYMBOLS TYPES OF RELATIONSHIP ERD of the proposed
system Suitable solution Strategies of the proposed system, System Feasibility Technical
Feasibility Operational Feasibility Economic Feasibility Schedule Feasibility

25
 CHAPTER FOUR

SOFTWARE DESING
4.0 Introduction
In this chapter, we will discuss the software design of the pharmacy management system
(PMS) that we are building using HTML, CSS, PHP, and MySQL. Software design is a
crucial step in the development of any software system, as it helps define the structure and
behavior of the application. In this chapter, we will focus on the architecture, design, and
implementation of the PMS, which is a complex system that includes several modules and
interfaces, the objective of this chapter is to present a detailed software design of the PMS,
which will be based on the client-server architecture style. The client application will be
designed using HTML, CSS, and JavaScript, and the server-side will be built using PHP and
MySQL for data storage. We will define the software architecture and design.

4.1 Architectural Design

Architectural design, also known as system architecture or software architecture, refers to the
process of defining the overall structure, components, and interactions of a system or
software application. It involves making high-level design decisions that determine how the
system will be organized, how its components will interact, and how the system will achieve
its desired functionality

Figure 4.1 Architectural Design

26
4.2 User Interface Design
User interface design (UI design) is the process of creating the visual and interactive elements of a
digital product or system that facilitate user interaction and enhance user experience. It involves
designing the layout, look, and feel of graphical user interfaces (GUIs) in software applications,
websites, and other digital platforms.

Figure 4.2 User Interface Design

4.3 Database Storage Design

Database storage design refers to the process of structuring and organizing the storage of data
within a database system. It involves making decisions on how to store and manage data
efficiently to ensure optimal performance, reliability, and scalability. The design
encompasses various aspects, including the physical organization of data files, disk layout,
partitioning, indexing, compression, and backup strategies.

Designing a database hierarchy for use with a relational database management system and
SQL server minimum search times are given while locating particular documents. That will
offer the best storage for data to prevent the database from getting too big, the easiest data
changes imaginable, and more flexibility to include new program functions as they become
necessary.

27
4.4 Database Design

Database design refers to the process of creating a well-structured and efficient database system that
accurately represents the data requirements of an organization or application. It involves determining
the entities, attributes, relationships, and constraints of the data, and organizing them into tables and
other database objects.

This section discusses about the database created for this project. The database is created using MQL
Server.

4.5 Database Normalization

Database normalization is a process used in database design to eliminate data redundancy and
improve data integrity. It involves organizing the data into tables and applying a set of rules called
normal forms to ensure that each piece of data is stored in the most efficient and logical manner.

Most popular Normalization 3 stages include:

• First Normal Form (1st NF)

• Second Normal Form (2nd NF)

• Third Normal Form (3rd NF)

4.6 First Normal Form (1NF)

First Normal Form (1NF) is a fundamental concept in database normalization. It requires that a
database table must have a primary key and that every column in the table must be atomic, meaning it
should not contain multiple values or repeating groups. Each attribute (column) in a table should hold
only a single value, and there should be no duplicated rows..

Drug ID Drug Name Drug Type

101 PANADOL Tablet
102 capsule injection
103 Ampicilin Drops
Table 4.6 First Normal Form (1NF)

28
4.7 Second Normal Form (2NF)
Second Normal Form (2NF) is a further step in the normalization process. To satisfy 2NF, a
table must already be in 1NF, and all non-key attributes (columns) must depend on the entire
primary key. In other words, no partial dependencies should exist in the table. If a table has a
composite primary key, each non-key attribute should be dependent on the entire composite
key, not just a subset of it.

DrugID Drugame Type Qty Price ExpireDate

101 Panadol Tablet 20 1 12/06/025
102 Capsul injection 10 1.2 14/08/2026
103 Ampicilin Drop 5 0.5 13/05/2027
Table 4.7 Second Normal Form (2NF)

4.8 Third Normal Form (3NF)

Third Normal Form (3NF) is another level of database normalization. For a table to be in
3NF, it must satisfy the requirements of 2NF, and it should have no transitive dependencies.
A transitive dependency occurs when a non-key attribute depends on another non-key
attribute, rather than directly depending on the primary key. In 3NF, all non-key attributes
should depend only on the primary key, and not on other non-key attributes.

S.ID DrugID Drug Name Type qty price Total S.Date

1 102 Capsul Injection 5 3 15 25/06/2023
2 101 Panadol Tablet 10 2.5 25 28/06/2023
103 103 Ampicilin Drop 2 1.5 3 01/07/2023
Table 4.8 Third Normal Form (3NF)

4.9 Normalized Tables of the proposed system

Users

Add Drug

Drug Entry

DrugDetail

Sales

User
Table 4.9 Normalized Tables

29
4.9 Transforming E-R Diagrams into Relations
Transforming an Entity-Relationship (E-R) diagram into relations involves mapping the
entities, relationships, attributes, and cardinalities from the diagram to tables in a relational
database. This process is also known as schema normalization or database schema design.

Figure 4.9 Transforming E-R Diagrams into Relationship

4.10 Data Dictionaries

A data dictionary, also known as a metadata repository, is a centralized resource that provides
detailed information about the structure, organization, and meaning of data within a database
or information system. It serves as a reference guide for understanding and managing the data
elements, attributes, relationships, and constraints in a database.

30
Table 4.10 User registration table

Table 4.10 Name:Drugs

Table 4.10 Name:DrugEntry

31
Table 4.10 Name:DrugDetails

Table 4.10 Name:Sales

Design Table:

User registration table

32
Drugs

DrugEntry

Drug Details

Sales

33
4.11 Designing Forms and Reports
Designing forms and reports involves creating user-friendly and visually appealing layouts to present
information effectively.

The design of data entry screens consists of the following Table:

• Login page

• Add Drug

• Drug Entry

• Drug Details

• Sales

• Stock Report

• Sales Report

• Expire soon

• Users

34
• Login Page

When user try to enter the system User most be enter username and password if user or
password is incorrect user can see message box said “Incorrect username or password”

Figure:4.11 Login page

• Add Drug

This form is Drug Registration Form firs you need to register new drag you went insert drug
name, Select Drug type and then you click the save button.

Figure:4.11 Add Drug

35
• Drug Entry

Figure:4.11 Drug Entry

36
• Drug Details

Figure: 4.11 Drug Details 1

• Sales

Figure:4.11 Sales

37
• Stock Report

• Sales Report

• Expire soon

38
• Users

4.12 Chapter Summary

This chapter discusses about the design and the implementation of the project. Software and database
design were the following steps of this chapter which was the conversion of the requirement analysis,
to show the interior design of the system. After that we discussed the database Design, ERD, Data
Dictionary, Table Design, Form design and etc, although we have covered majority of the project still
we are going to the coding step of the project

39
 CHAPTER FIVE
SYSTEM IMPLEMENTATION

5.0 Introduction
The system implementation phase marks the transition from the development stage to the
operational stage of the pharmacy management system. This chapter focuses on the activities
involved in implementing the system, ensuring its functionality, and preparing it for use by
end-users. The implementation phase includes various stages such as coding, testing, user
feedback, and the development of user manuals.

5.1 Coding Phase

During the coding phase, the development team translates the system design specifications
into actual code. The chosen programming languages, frameworks, and tools are used to
write the necessary code that implements the functionalities of the pharmacy store system.
Coding standards and best practices are followed to ensure code readability, maintainability,
and adherence to industry standards. The code is designed in a modular and reusable manner,
promoting efficient development and future enhancements.

5.1.0 Add Drug

<html>
<head>
<title>Drug Registration Page </title>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
</head>
<style>
body {
background-color: #F5F5F5;
font-family: Arial, sans-serif;
}
form {
max-width: 500px;
margin: 20px auto;
padding: 20px;
background-color: #FFFFFF;
border-radius: 5px;
box-shadow: 0px 0px 5px 1px #CCCCCC;
}
input[type="text"], input[type="Text"], input[type="name"] {
display: block;

40
 width: 100%;
padding: 10px;
margin-bottom: 10px;
border: 1px solid #CCCCCC;
border-radius: 3px;
font-size: 16px;
color: #444444;
}
input[type="radio"] {
margin-right: 10px;
}
input[type="submit"] {
display: block;
width: 100%;
padding: 10px;
background-color: #4CAF50;
color: #FFFFFF;
border: none;
border-radius: 3px;
font-size: 16px;
cursor: pointer;
}
input[type="submit"]:hover {
background-color: #3E8E41;
}
.bold {
font-weight: bold;
}
.tbl{
width:100%;
border-collapse:collapse;

}
.tbl td,th{
border:1px solid black;
padding:10px;

}
.tbl th{
background:lightgray;
text-align:left;
}
.tbl tr:hover{
background:#88d040;
}
.tbl a{
text-decoration:none;

41
 font-weight:bold;
font-size:20px;

}
</head>
</style>
<?php
session_start();
?>
<?php
include("dbcon.php");
?>
<form action="Add_DRUG.PHP"method="POST">
<b class="bold">Drug Registration Form</b>
<br />
<br />
<b>Enter Drug Name:</b>
<input type="text" name="txtDrugName" class="txt" placeholder="Enter drug Name">
<b>Select Drug Type:</b><Select name="ddlDrugType" class="txt">
<option>---Select Drug Type---</option>
<option>tablet</option>
<option>injection </option>
<option>Drops</option>
<option>Syrup</option>
</Select>
<br />
<input type="submit" name="btnSave" value="Save" class="btn">

</form>
<?php
if(isset($_POST["btnSave"]))
{
$DrugName=$_POST['txtDrugName'];
$type=$_POST['ddlDrugType'];
if($DrugName=="")
{
echo "<script>";
echo "alert('Enter drug Name')";
echo "</script>";
return;

}
if($type=="---Select Item Type---")
{
echo "<script>";
echo "alert('Select drug Type')";
echo "</script>";

42
 return;

}
$check="Select DrugName from drugs where DrugName='$DrugName'";
$r=mysqli_query($Con,$check);
if(mysqli_num_rows($r)>0)
{
echo "<script>";
echo "alert('This drug Name Already Exists')";
echo "</script>";
return;

}
$GetID="select IFNULL(MAX(DrugID),100)+1 as DrugID from drugs";
$r=mysqli_query($Con,$GetID);
$data=mysqli_fetch_array($r);
$drug_id=$data['DrugID'];
//Insertion
$qry="Insert Into drugs(DrugID,DrugName,type)value($drug_id,'$DrugName','$type')";
$result=mysqli_query($Con,$qry);
if(mysqli_affected_rows($Con)>0)
{

echo "Drug Data is Saved Successful";

}
else
{
echo '<div style="color:red;"> Failed To Save Drug Data </div>';
}

}
?>
<table class="tbl">
<tr>
<th>Action</th>
<th>Drug ID</th>
<th>Drug Name</th>
<th>Drug Type</th>
</tr>

<?php
$qry="Select * from drugs";
$result=mysqli_query($Con,$qry);
while($data=mysqli_fetch_array($result))
{
?>
<tr>

43
<td><a href="DrugUpdate.php?DrugID=<?php echo $data ['DrugID'];?>"> Update</a></td>
<td><?php echo $data ['DrugID'];?></td>
<td><?php echo $data ['DrugName'];?></td>
<td><?php echo $data ['type'];?></td></tr>
<?php
}
?>
</table>
</body>
</html>
5.2 Test system implementation
Before proceeding further, the implemented system undergoes a series of tests to validate its
functionality and identify any issues or bugs. The testing phase consists of three main stages:
development testing, release testing, and user testing.

5.3 Development testing Release testing

Development testing is conducted by the development team to identify and resolve any
coding or logical errors within the system. Unit tests are performed on individual modules to
ensure their correctness and integration tests are carried out to validate the interactions
between different system components.

5.4 Development testing

Development testing is conducted by the development team to identify and resolve any
coding or logical errors within the system. Unit tests are performed on individual modules to
ensure their correctness and integration tests are carried out to validate the interactions
between different system components.

5.5 Releasing Testing

Once the development testing is completed, the system moves to the release testing phase.
This phase focuses on testing the system in a controlled environment that closely resembles
the production environment. The system is tested for its overall functionality, performance,
security, and compatibility with existing infrastructure. Any identified issues or defects are
addressed and resolved before proceeding to the next stage.

5.6 User testing

User testing involves engaging actual end-users to evaluate the system's usability,
effectiveness, and user experience. Feedback from users is collected to identify any usability
issues or areas for improvement. User acceptance testing (UAT) is conducted to ensure that
the system meets the users' requirements and expectations. The feedback gathered during this
phase is valuable in refining the system and making necessary adjustments.

44
5.7 Developing User manuals
In parallel with the testing activities, user manuals are developed to provide detailed
instructions and guidance on how to use the pharmacy store system. The manuals include
information on system functionalities, workflows, data entry procedures, and troubleshooting
tips. User manuals aim to assist users in understanding and effectively utilizing the system,
reducing the learning curve and enhancing user satisfaction.

5.8 Chapter Summary

This chapter covered the system implementation phase of the pharmacy store system. It
discussed the coding phase, where the system design specifications were transformed into
actual code. The testing phase, including development testing, release testing, and user
testing, was highlighted to ensure the system's functionality, performance, and user
acceptance. Additionally, the development of user manuals was emphasized to support end-
users in utilizing the system effectively. The next chapter will delve into the deployment and
maintenance aspects of the pharmacy store system.

45
 CHAPTER SIX
CONCLUSION & ENHANCEMENT
6.0 Introduction
This Chapter discusses the tasks, which have been done during the previous documentations
of this system, furthermore, this unit will cover how this project meats the project’s
objectives. Moreover, it will explain the experiences that have been gained during this project
and it includes the future recommendation, which capture how to extend this Kaaliye
pharmacy management system.

6.1 Objective achievement

After our system completed, we achieved to designed and implemented an Kaaliye Pharmacy
management system, management system which removed manual process into an Online
system, now the User of the system can use through online whenever and wherever and that
is the main achievement of the new system and all the objectives of the system have been
achieved and the requirements of the users have been met through the project.

6.2 Weaknesses and problems of the system

1. Security of the system is one of the limitations of our system

2. Every User of the system can create new user and update

6.3 Future Work

It has been achieved the final phase development of Kaaliye pharmacy management system
and it is like any other system. It needs improvements and maintenance Future.

46
6.4 Chapter Summary
A lot of experience has been gained during this project such that the literature review

Provided knowledge of existing system of Pharmacy Management systems and also it helps

Us identifying the weaknesses and the strengths of the developing system by comparing

The features of the system that is going to be developed with three existing systems which

Are related to it. During the methodology study, it identifies the software engineering

Methodology for any software engineering system.

APPENDICES

APPENDIX A
Interview questions of Kaaliye Pharmacy

1. Which Method To Manage The Drugs?

2. How Does The Pharmacy Store The Drugs?

3. How does Customer feel When the Drug Searching Takes a time?

4. How do you want to Solve These Problems?

47
APPENDIX B

Time framework of the developing the proposed system

NO ACTIVITIES Jan Feb March April May Jun July

1 Proposal
writing
2 Reading and
correction by
Supervisor
3 Proposal
Submission
4 Data
Collection
5 Analyzing
Project
6 Designing
project and
conclusion
7 Implementation
and
conclusion

8 Thesis
Submission`

48
reference
AHEMD, I. (2013). INTODUCTION. PHARAMACY , 7.

AHMED, E. I. (2013). INTRODUCTON. PHARMACY , 8.

Altexsoft. (2021, july 13). Pharmacy Management System: Benefits, Features, and Providers of
Pharmacy Software. Retrieved nov wed, 2022, from Altexsoft:
https://www.altexsoft.com/blog/pharmacy-management-system/

delvetool. (2019, sep 3). observational. Retrieved oct 27, 2022, from develtool:
https://delvetool.com/blog/observation

ENG IBTOYE AHEMD. (2013, MAR 2). HISTORY. PHARMACY , p. 7.

ENG IBTOYE. (2013). HISTORY. PHARMACY , 9.

George A. Bender. (1967). HISTORY OF PHARMACY. NEW YORK.

IBTOYE AHMED. (2013). INTODUCTION. PHARMACY , 6.

IBTOYE AHMED. (2013). INTODUCTION. PHARAMCAY MANAGEMENT , 7.

IBTOYE AHMED. (2013). INTRODUCTION. PHARMACY , 6.

IBTOYE AHMED. (2013). INTRODUCTION. PHARMACY , 9.

infowekers. (2021, jan 12). Pharmacy Information System Origins and Evolution. Retrieved nov wed,
2022, from inforwekers: https://infowerks.com/pharmacy-information-system/

infowekers. (2021, jan 13). Pharmacy Information System Origins and Evolution. Retrieved nov wed,
2022, from infowekers: https://infowerks.com/pharmacy-information-system/

infowekers. (2021, jan 12). Pharmacy Information System Origins and Evolution. Retrieved nov wed,
2022, from infowekers: https://infowerks.com/pharmacy-information-system/

Isak, A. A. (2020). Introduction to Chemistry. Mogadishu: Beder.

isak, m. a. (2016, April). Hospital information system. Retrieved December 11, 2022, from
WIKIPEDIA: https://en.wikipedia.org/wiki/Hospital_information_system

john C.karantz. (2019, feb 19). pharmacy. Retrieved nov wed, 2022, from Brintannica:
https://www.britannica.com/science/pharmacy/Research

john c.karanz. (2019, feb 19). pharmacy. Retrieved nov wed, 2022, from Britannica:
https://www.britannica.com/science/pharmacy/Research

Linda Rosencranc. (2021, mar 1). software. Retrieved 12 26, 2022, from .techtarget:
https://www.techtarget.com/searchapparchitecture/definition/software#

Research on Pharmacy management. (2019). Research on Pharmacy management , 4.

TECHTARGET. (2014, FEB 12). SYSTEM. Retrieved NOV 3, 2022, from TECHTARGET:
https://www.techtarget.com/searchwindowsserver/definition/system

49
tegan george. (2022, mar 10). types of interview. Retrieved 12 27, 2022, from scribbr:
https://www.scribbr.com/methodology/interviews-
research/#:~:text=An%20interview%20is%20a%20qualitative,by%20their%20level%20of%20structu
re.

wekipedia. (2019, nov 29). Pharmacy management system. Retrieved nov wed, 2022, from wikipedia:
https://en.wikipedia.org/wiki/Pharmacy_management_system

WIKIPEDIA. (2016, OCT 12). MANAGEMENT. Retrieved NOV 23, 2022, from WIKIPEDIA:
https://en.wikipedia.org/wiki/Management

WIKIPEDIA. (2017, NOV 7). PHRAMACY. Retrieved NOV 23, 2022, from WKIPEDIA:
https://en.wikipedia.org/wiki/Pharmacy

WIKIPEDIA. (2010, MAR 12). WORK BREAK DOWN STURUCTURE. Retrieved DEC 27, 2022,
from WIKIPEDIA: https://en.wikipedia.org/wiki/Work_breakdown_structure

50