The document is a project report on the development of a Pharmacy Management System by students at Bangladesh University of Business and Technology. The system is designed to assist pharmacists in managing medication details efficiently, offering functionalities such as medicine entry, searching, and billing through a user-friendly interface. It is built using C# and ASP.NET with a MySQL database to improve inventory management and data security in pharmacies.

1. Bangladesh University of Business & Technology
(BUBT)
PROJECT REPORT
On
Pharmacy Management System
Submitted By
Name ID Intake
Pranta Chakraborty 16171103042 34
Dipta Roy 16171103027 34
Mrityunjoy Bhaduree 16171103009 34
Submitted To
Suman Saha
Assistant professor
Department of CSE BUBT

2. I
ACKNOWLEDGEMENT
We are extremely grateful and remain indebted to our honorable Assistant professor
Mr. Suman Saha for being a source of inspiration and for his constant support in the Design,
Implementation and Evaluation of the project. We are also thankful to him for his constant
constructive criticism and invaluable suggestions, which benefited me a lot while developing
the project on “Pharmacy Management System”. He is very co-operative throughout this
project work. Through this column, it would be my utmost pleasure to express my warm thanks
to him for his encouragement, co-operation and consent without which I wouldn’t be able to
accomplish this project.
Many people, especially our classmates and team members itself, have made valuable comment
suggestions on this proposal which gave us an inspiration to improve our project. We thank all
the people for their help directly and indirectly.
With Regards

3. II
ABSTRACT
Pharmacy Management System application to help pharmacist to manage pharmacy in the
systematic ways. Pharmacy Management System can make the work easier by giving the
details of medicine when its name is entered. A computer gives the details of the medicine like
rate of medicine, and expiry date of the medicine. It becomes very difficult in big medical
stores to handle the details of all the medicines manually, so by using this pharmacy
management system We can maintain the records of all the medicines. It is fed with the
information whenever new medicines are brought and it is provided with expire date with
search option. When we entire the name of medicine it gives the details of medicine.
The technology platform in implementing this system uses visual studio programming
environment with C# and ASP.NET using MYSQL for SQL database.

4. III
TABLE OF CONTENTS
ACKNOWLEDGEMENT ---------------------------------------------------------- I
ABSTRACT -------------------------------------------------------------------------- II
CHAPTER-1 : INTRODUCTION
1.1 Introduction to pharmacy management system -------------------------------- 1-2
1.2 Motivation -------------------------------------------------------------------------- 2
1.3 Project Objectives ----------------------------------------------------------------- 3
1.3.1 Objective of the Project --------------------------------------------------------- 3
1.4 Key benefits ------------------------------------------------------------------------ 3-4
1.5 Contributions ----------------------------------------------------------------------- 4
1.6 Organization ------------------------------------------------------------------------ 4
1.7 Summary ---------------------------------------------------------------------------- 5

5. IV
CHAPTER-2 : : LITERATURE REVIEW
2.1 Introduction ------------------------------------------------------------------------ 6
2.2 The future of Pharmacy ----------------------------------------------------------- 6
2.2.1 Categories of the Technology ------------------------------------------------- 6-7
2.3 Benefits of the Proposed System ------------------------------------------------ 7
CHAPTER-3 : PROPOSED SYSTEM ANALYSIS AND DESING
3.1 Introduction ------------------------------------------------------------------------ 8
3.2 System Analysis ------------------------------------------------------------------- 8
3.2.1 Analysis of Existing System --------------------------------------------------- 9
3.2.2 Analysis of the Proposed System --------------------------------------------- 9
3.3 Method of Information ----------------------------------------------------------- 10
3.4 System Design --------------------------------------------------------------------- 10-11
3.5 System Modeling ------------------------------------------------------------------ 12
3.6 System Flowchart ------------------------------------------------------------------ 12
3.6.1 Structure Chart ------------------------------------------------------------------- 13
3.6.2 System Flowchart --------------------------------------------------------------- 14
3.7 Functional Requirement ---------------------------------------------------------- 15
3.8 Nonfunctional Requirement ------------------------------------------------------ 16-17
3.9 Database Specification ------------------------------------------------------------ 17
3.10 Database Design ------------------------------------------------------------------ 17

6. V
3.10.1 Administrator Login table ---------------------------------------------------- 18
3.10.2 Medicine Information table --------------------------------------------------- 18
3.11 Entity Relationship Diagram (E-R Diagram) --------------------------------- 18-19
3.11.1 General Overview -------------------------------------------------------------- 19
3.11.2 E-R Diagram Symbols and Natation’s -------------------------------------- 20
3.11.3 (E-R Diagram)------------------------------------------------------------------ 21
CHAPTER -4 : USER MANUAL
4.1 Home page -------------------------------------------------------------------------- 22
4.2 Admin Control Panel -------------------------------------------------------------- 23-24
4.3 Add Medicine page ---------------------------------------------------------------- 24
4.3.1 Manage Medicine page --------------------------------------------------------- 25
4.4 Manufacture page ----------------------------------------------------------------- 25
4.5 Add account page ------------------------------------------------------------------ 26
4.5.1 Manage Account ----------------------------------------------------------------- 27
4.6 Search Customer ------------------------------------------------------------------- 28
4.7 Medicine Sells and View --------------------------------------------------------- 29
4.8 Employee Dashboard -------------------------------------------------------------- 30

7. VI
CHAPTER -5 : SYSTEM IMPLEMENTATION
5.1 Introduction ------------------------------------------------------------------------- 31
5.2 Development ----------------------------------------------------------------------- 31
5.2.1 Microsoft Visual Studio -------------------------------------------------------- 31-32
5.2.2 MYSQL Community Server --------------------------------------------------- 32
5.2.3 .NET Framework ---------------------------------------------------------------- 32-33
5.3 System Documentation ----------------------------------------------------------- 33-34
5.4 Hardware Requirement ----------------------------------------------------------- 34
5.5 Software Requirement ------------------------------------------------------------ 34
CHAPTER -6 : CONCLUTION
6.1 Conclusion -------------------------------------------------------------------------- 35
6.2 Recommendation ------------------------------------------------------------------ 35
6.3 Limitations -------------------------------------------------------------------------- 36
6.4 Future Goals ------------------------------------------------------------------------ 36
REFERENCES ------------------------------------------------------------------------------- 37

8. VII
List of Figure
Figure No. Title of Figure Page No.
Figure No.4.1 Home page 21
Figure No.4.2 Dashboard 22-33
Figure No.4.2.1 Dashboard tools 23
Figure No.4.3 Add Medicine page 23
Figure No.4.3.1 Manage Medicine page 24
Figure No.4.4 Manufacturer page 24
Figure No.4.5 Add Accounts page 25
Figure No.4.5.1 Manage accounts page 26
Figure No.4.6 Search Customer 27
Figure No.4.7 Medicine Sells and View 28
Figure No.4.8 Employee Dashboard 29

9. VIII
List of Table
Figure No. Title of Figure Page No.
Figure No.3.1 Administrator table 8
Figure No.3.2 Medicine information table 8
Figure No.3.3 Accounts table 10

10. 1
CHAPTER -1
(INTRODUCTION)
1.1 Introduction
This project entitled with Pharmacy Management System. This application developed using
C# technology as front end and backend is MYSQL.
Pharmacy management system can make the work easier by giving the details of the medicine
when its name is entered. A computer gives the details of the medicine like rate of medicine. It
becomes very difficult in big medical stores to handle the details of all the medicines
manually, so by using this pharmacy manage system we can maintain the records of all the
medicines. [1]
The Pharmacy Management System application has more benefits, Easy to find medicine
because we use strong search option and easy to add medicine, medicine type, medicine
deadline and also delete and modify option its help to both of customer and pharmacist.
we add the category of user. We use three different types of user.
Types of user are:
1. ADMIN
2. MANAGER
3. CUSTOMER
The application is reduced as much as possible to avoid errors while entering the data. It also
provides error message while entering invalid data. No formal knowledge is needed for the
users to use this system.
Thus by this all it proves it is user friendly. This System as described above can lead to error
free, secure, reliable and fast management system. It can assist user to concentrate on their
other activities to concentrate on the record keeping thus it will help organization in better
utilization of resources. These systems ultimately allow you to better manage resources.

11. 2
The system will do the following activities:
 Store medicine data's
 Search Medicine data effectively
 Update, delete, and edit medicine information
 Generate report on medicine
 prepare bill for the medicine
 Changing login password
In general, The Pharmacy management system is based on computer technology that gives
service for user, manage by the pharmacist who give implementation of function relatively in
effective time as well as will deigned for removing time wasting, saving resources, easy data
access of the medicine, secure on data input and data access by removing almost manual based
system.
1.2 Motivation
The pharmacy management system is built for the sake of ensuring effective and clear data
saving and manipulating as well as neat work on the pharmacy medical products.
This refers the pharmacy management system project highly minimize time and resource by
which, searching the medicine data you can get the data in quickest time. And almost the
resources are wise used since most actions are done on the pharmacy system. Some of the
resources minimized include paper, manpower and related things. The other thing is for storing
data’s in secure way. [2]

12. 3
1.3 Project Objectives
It is the user friendly application for Pharmacist which reduces the burden and helps to manage
all sections of Pharmacy like Medicine management and Billing etc. which improve the
processing efficiency. It deals with the automating tasks of maintaining of Bills. In Pharmacy,
Billing management is the key process. Including safe data store about medicine as well as fast
searching, delete and update of medicines. The pharmacy management system is easy for use
so the user can do pharmacy actions without ambiguities. [1]
The main Objectives of the PMS is making the pharmacy organizations computerized by
creating neat work through minimizing or eliminating wasting of time as well as removing the
resources such as papers for data saving since know a day is paper based decrease
malfunctioned works on the medical usage by giving correct information on each medicine.
1.3.1 Objective of the Project
a) To design a system that can keep and track of user.
b) To design a system that is useful to handling medicine.
c) To design system that is much better than manual data recording system.
1.4 Key benefits
In this system have some benefits those are.
I. Generate reports
BY using this system, we can easy generate report of possible a available medicine price and
details print out.
II. Time saving
In manual system it is very hard to find medicine and identify the Medicine. But in this system
easy to find and identify the medicine. So this system saves the time.

13. 4
III Security
To change or update anything an administrative id and password is need Which provides users
better security.
IV. User FriendlyDashboard
The user interface is very handy, easy to use for anybody who have just a basic knowledge of
using computer.
V. Admin Privileges
Admin can add medicine, add user t, edit user type, update and delete medicine list, medicine
details and types.
1.5 Contributions
In this topic we are discuss about
i. Physical system under this project we discuss about how to develop a system.
ii. Background structure of database.
iii. User manual under this topic we show that how the project works.
1.6 Organization of this project
i. In second chapter, we give the review on whole project.
ii. In third chapter we give information about our proposed
system and Database structure ER diagram, implementation,
experimental analysis.
iii. In fourth chapter we give user manual.
iv. The working tools has described in chapter five shortly.

14. 5
1.7 Summary
Pharmacy management system is designed to improve the accuracy, 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. Pharmacy management
system was developed to ensure the security of information and reliability of Pharmacy records
when accessing and providing services to the customers. The information gathered during the
data collection was properly analyzed and the results provided the basis for the new system.
The system was tested and found to be functional and the outputs produced by this system were
encouraging. The application will hence reduce the loss of information unlike the existing
system and also information will be processed fast. [2]

15. 6
CHAPTER-2
(LITERATURE REVIEW)
2.1 Introduction
A pharmacist is a medical professional who dispenses medicine to patients according to a
prescription ordered by a physician or other clinician. Pharmacists have an in depth knowledge
of the chemistry of various medicine 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 it 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
matter relating to medication distribution and use and disease state management. Pharmacists
play a vital role improving patient care through the medicine and information they provide. [3]
2.2 The future of pharmacy
Technological options available to pharmacies today are as numerous as they are convenient.
As the healthcare system becomes more digital, the most exciting thing is that pharmacists will
have the potential to become more connected to patients and have more time for patient-
centered activities.
2.2.1 Categories of Some of the technologies
Categories of Some of the technologies in the future are:
1. Resources for clinical decision support.
2. Error prevention and quality assurance.
3. Advances in bar-coding and even radio-frequency identification technology will help
pharmacists verify the appropriate use of medications.

16. 7
4. Telecommunications infrastructure. For example, to be able to send a patient a text
message reminder to take meds or measure blood glucose levels. This will lead to better
self-care management behavior’s.
5. Automation and robotics.
6. Collaborative practice connectivity, achieved through a combination of electronic
prescribing (e-prescribing) and the ability to connect to and exchange data with labs
and physician offices.
7. Delivery service support, using GPS-driven telecommunications systems for routing,
tracking, order status, dispatch, locating, and oversight.
8. Pharmacy surveillance and security systems, which will create a greater level of
security for pharmacies even when pharmacists are off-site.
9. software and hardware that increase the efficiency of pharmacies by managing
workflow.
2.3 Benefits of the Proposed System
The proposed system would be designed to help make the rigorous activities carried out in a
pharmacy much easier by providing the statistics of drugs in stock, monitoring drug movement
in the pharmacy and ensuring effective policing of the activities in the pharmacy.
The new system will be designed to provide the following benefits in the interest of the
pharmacy.
1. The system would enhance management services and improve productivity.
2. The system would enhance User/System interface.
3. The system would be cost effective.
4. The system would improve information quality and accessibility.

17. 8
CHAPTER -3
(PROPOSED SYSTEM ANALYSIS AND DESING)
3.1 Introduction
System is a collection of an interrelated components that works together to achieve a purpose.
System analysis is referred to the systematic examination or detailed study of a system in order
to identify problems of the system, and using the information gathered in the analysis stage to
recommend improvements or solution to the system. [3]
System design is an abstract representation of a system component and their relationship and
which describe the aggregated functionality and performance of the system. System design is
also the overall plan or blueprint for how to obtain answer to the question being asked. The
design specifies which of the various type of approach. [3]
3.2 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. [2]

18. 9
3.2.1 Analysis of existing system
Before we analyses 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.
1. 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.
2. The state of drugs in stock is manually checked.
3. Mistake of selling expired drugs to customers.
4. Too much workload on employees
5. Filing cabinet in the pharmacy with paper record
3.2.2 Analysis of proposed system
From the problems listed in the existing system, the implementation of the proposed system
shall focus on:
1. Pharmacists having access to the proposed system at any time.
2. Ensuring effective policing by providing statistics of the drugs in stock.
3. Improving the efficiency of the system by ensuring effective monitoring of services and
activities.
4. Generating report within a specified period of time.
5. Reducing the employees’ workload.

19. 10
3.3 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:
1. Collecting and analyzing existing materials on the project topic, written by different expert.
2. Studying the present system in detail and the organizational style.
3. Knowing and understanding the input and output processes of the existing system.
4. Knowing and understanding the input and output processes of the existing system.
5. 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.
6. Primary data: This source has to do with the text book contacted for the development of
this project.
3.4 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.

20. 11
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 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.
Fig. 1.1 waterfall model of system development life cycle
Project planning
Requirement
gathering
Project
development &
interface design
Implementation
and system
testing
Maintenance and
upgrading

21. 12
3.5 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]
3.6 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.

22. 13
3.6.1 Structure chart
SELECT
MENU
ADMIN
LOGIN
CUSTOMER
LOGIN
MENEGER
LOGIN
MENEGER
MENU
ADMIN
MENU
ADD
CUSTOMER
ADD
MEDICINE
ADD
CATEGORY
GOTO
STORE
VIEW
MEDICINE
MANAGE
MEDICINE
DELETE
&UPDATE
MADICINE
VIEW SALES
VIEW
CUSTOMER
ADD
CATEGORY
ADD
MEDICINE
GOTO
STORE
VIEW
MEDICINE
MANAGE
MEDICINE
MEDICINE
STATE
VIEW SALES
VIEW
CUSTOMER
CUSTOMER
MENU
VIEW
MEDICINE

23. 14
3.6.2 System Flowchart

24. 15
3.7 Functional Requirements
There are functions done by the system such as: store the necessary information of medicine,
prepare bill for the medicine, easily searching of medicine, Update, delete and save data of
medicine.
Store the necessary information of the drugs:
The PMS (pharmacy management system) stores the detail information about each medicine
including Actual name, formula of medicine and how it is importance and for which diseases
is required. Since the information for each drug were required in some cases like the use of
drugs, when use drugs and for whom is given. [2]
Searching Medicine and other Data’s:
The PS has easily searching of medicine which shows in which shelf is put and the behavior of
the medicine. These arching process is based on the name of the give data or the identification
of the item. Here when the user searches the item on search bar the related things were
displayed in the screen and can select the actual item that the user needs. [2]
Alerting pharmacy Data’s in the system:
Changing medicines to another because of medicine outdated, modifying the saved medicine
data for incorrect data, deleting of data of the pharmacy can be done on the system. [2]
3.8 Nonfunctional 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

25. 16
pharmacy and medicines without password. As result data is protected and controlled by only
the administrator. [4]
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. [4]
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. [4]
Operation: the pharmacy management system is operated and controlled by the pharmacy
manager for safe work. [4]
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.
3.9 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. [2]

26. 17
3.10 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.
3.10.1 Administrator Login Table:
Field Name Field Type Field Length Description
Admin Username Varchar (15) Admin Username
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.
3.10.2 Medicine information table:
Field Name Field Type Field Length Description
Medicine Name Varchar (15) Medicine Name
Medicine ID Varchar (7) Medicine 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

27. 18
Field Name Field Type Field Length Description
Interest Rate Int ( ) Interest Rate
Expected Sale Int ( ) Expected Sale
Table 3.2 shows the information about the medicine in the pharmacy and is being queried from
the database on the medicine registration page to show all the medicine for user to select.
3.11 Entity RelationshipDiagram (E-R Diagram)
An entity relationship diagram (EDR) shows the relationships of entity sets stored in a database.
An entity in this context is a component of data. In other words, E-R diagrams illustrate the
logical structure database. [5]
3.11.1 General Overview
An entity relationship diagram consists of several components. ERD has 3 simple components.
Entities – An entity is a thing. In business domain terms, it’s a concept or glossary-level term.
In relational database terms, it’s the table. [5]
Relationships – The real insight from this type of diagram comes when we see how entities
relate to one another, or relationships. Relationships can be thought of as verbs that link two or
more nouns. Relationships can be modeled numerically, using the multiplicity syntax from a
class diagram, or using Crows Foot Notation. [5]
Attributes – Within each entity, there can be more than one attribute. Attributes provide
detailed information about the concept. In a relational database, attributes are represented by
the fields where the information inside a record is held. [5]

28. 19
3.11.2 E-R Diagram Symbols and Notations
Entity
RelationshipAttributes
Weak RelationshipMultivalued
Attributes
Weak Entity

29. 20
CHAPTER-4
(USER MANUAL)
4.1 Home page
This is the home page when we can login as admin, manager or customer.
Figure 4.1: Home Page

30. 21
4.2 Dashboard
This is our admin control panel page. Admin control the medicine field, manufacture field,
customer field, accounts field, and sells.
Figure 4.2: Dashboard

31. 22
And each field has some option. For example, account field has three options.
Figure 4.2.1: select option
4.3 Add Medicine page
This is our add medicine page. Admin can add medicine and save in database.
Figure 4.3: Add medicine

32. 23
4.3.1 Manage Medicine page
Here admin manage medicine. For example, admin view medicine, update and delete medicine
and also go back admin control panel from home button.
Figure 4.3.1: Manage medicine
4.4 Manufacturer page
This is manufacturer page.
Figure 4.4: Manufacturer page

33. 24
4.5 Add Accounts page
Only Admin can create accounts.
Figure 4.5: Add accounts

34. 25
4.5.1 Manage accounts
Admin also delete, update and view the accounts.
Figure 4.5.1 Manage accounts

35. 26
4.6 Search Customer
Admin can search customer and view customer details.
Figure 4.6: Search Customer

36. 27
4.7 Sells and View Medicine
Figure 4.7 : Medicine sells and view

37. 28
4.8 Employee Dashboard
Figure 4.8 : Employee Dashboard

38. 29
CHAPTER-5
(SYSTEM IMPLEMENTATION)
5.1 Introduction
System implementation is a stage in system life cycle whereby a new system is developed,
installed and made ready for use. It is this stage that all details and key point in the requirement
specification are practicalised. System implementation therefore, is a very essential stage in
which its success determines to a great extent the success of the new system. At this instance,
after all is said and done the system is duly ready to be implemented (Pharmacy Management
System).
System design is concerned mainly with the coordination of activities, job procedures and
equipment utilization in order to achieve organizational objectives. It addresses data input and
output data, processing and interface.
5.2 Development Tools
5.2.1 Microsoft Visual Studio
Microsoft Visual Studio is an integrated development environment (IDE) from Microsoft. It
is used to develop computer programs, as well as websites, web apps, web services and mobile
apps. Visual Studio uses Microsoft software development platforms such as Windows
API, Windows Forms, Windows Presentation Foundation, Windows Store and Microsoft
Silverlight. It can produce both native code and managed code.
Visual Studio includes a code editor supporting intelligence (the code completion component)
as well as code refactoring. The integrated debugger works both as a source-level debugger
and a machine-level debugger. Other built-in tools include a code profiler, forms designer for
building GUI applications, web designer, class designer, and database schema designer. It
accepts plug-ins that enhance the functionality at almost every level—including adding support
for source control systems (like Subversion and Get) and adding new toolsets like editors and
visual

39. 30
designers for domain-specific languages or toolsets for other aspects of the software
development lifecycle (like the Team Foundation Server client: Team Explorer).
Visual Studio supports 36 different programming languages and allows the code editor and
debugger to support (to varying degrees) nearly any programming language, provided a
language-specific service exists. Built-in languages include C,[6] C++, C++/CLI, Visual Basic
.NET, C#, F#,[7] JavaScript, typescript, XML, XSLT, HTML, and CSS. Support for other
languages such as Python,[8] Ruby, Node.js, and M among others is available via plug-
ins. Java (and J#) were supported in the past. [7]
5.2.2 MYSQL Community Server
MySQL is an open-source relational database management system (RDBMS). Its name is a ...
The MySQL server software itself and the client libraries use dual-licensing .... Source MySQL
Community Server and the proprietary Enterprise Server. ... Data Definition Language (DDL)
when using the innodb Storage Engine. [6]
5.2.3 .NET Framework
.NET Framework (pronounced dot net) is a software framework developed by Microsoft that
runs primarily on Microsoft Windows. It includes a large class library named Framework Class
Library (FCL) and provides language interoperability (each language can use code written in
other languages) across several programming languages. Programs written for .NET
Framework execute in a software environment (in contrast to a hardware environment) named
Common Language Runtime (CLR), an application virtual machine that provides services such
as security, memory management, and exception handling. (As such, computer code written
using .NET Framework is called "managed code".) FCL and CLR together constitute .NET
Framework. FCL provides user interface, data access, database connectivity, cryptography,
web application development, numeric algorithms, and network communications. [8]

40. 31
Programmers produce software by combining their source code with .NET Framework and
other libraries. The framework is intended to be used by newest applications created for the
Windows platform. Microsoft also produces an integrated development environment largely
for .NET software called Visual Studio.NET Framework began as proprietary software,
although the firm worked to standardize the software stack almost immediately, even before
its first release. [8]
Despite the standardization efforts, developers, mainly those in the free and open-source
software communities, expressed their unease with the selected terms and the prospects of any
free and open-source implementation, especially regarding software patents. Since then,
Microsoft has changed .NET development to more closely follow a contemporary model of a
community-developed software project, including issuing an update to its patent promising to
address the concerns. [8]
.NET Framework led to a family of .NET platforms targeting mobile computing, embedded
devices, alternative operating systems, and web browser plug-ins. A reduced version of the
framework, .NET Compact Framework, is available on Windows CE platforms, including
Windows Mobile devices such as smartphones. .NET Micro Framework is targeted at very
resource-constrained embedded devices. Silverlight was available as a web browser plugin.
Mono is available for many operating systems and is customized into popular smartphone
operating systems (Android and iOS) and game engines. .NET Core targets the Universal
Windows Platform (UWP), and cross-platform and cloud computing workloads. [8]
5.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.

41. 32
5.4 Hardware requirement
1. A minimum hard disk space of 20 Gigabytes (GB)
2. RAM size of 1GB
3. Pentium 4 dual processor CPU
4. A VGA color monitor
5. Mouse
6. Keyboard
5.5 Software requirement
1. Windows operating system such as Windows 2000, windows XP, Windows Vista,
Windows 7.
2. Visual basic 6.0 software.

42. 33
CHAPTER-6
(CONCLUTION)
6.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.
6.2 Recommendation
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 availab le
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. [4]

43. 34
6.3 Limitations
There are some drawbacks and limitations in this software as it is a beta release and under
further development process.
1. Need to install first on computer before using
2. Platform is not independent, it can't run on all devices
3. Some minor bug exists
4. Limited features, need to exploit
6.4 Future Goals
After the next release some new more sophisticated feature will be added and current bugs vet
H be fixed. The plan for the next release is-

44. 35
References
1. jonny, 2018. [Online]
Available at: https://www.coursehero.com/file/24302089/PROJECT-REPORT-
PHARMACY-MANAGEMENT
[Accessed 5 january 2006].
2. Anon., 2018. www.academia.edu. [Online]
Available at:
https://www.academia.edu/11672313/Pharmacy_Management_System_introduction
[Accessed 13 oct 2018].
3. Farghally,E.M. A.,2018. slideshare. [Online]
Available at:https://www.slideshare.net/mahmoudfarghally21/pharmacy-management-
system-project-69561583
[Accessed13 oct 2018].
4. ADEWALE, I. A., 2018. slideshare. [Online]
Available at: https://www.slideshare.net/ibitoye_ahmed/pharmacy-management-
system-project-5365478
[Accessed 23 April 2013].
5. 2016. wekipidia. [Online]
Available at: https://en.wikipedia.org/wiki/Entity%E2%80%93relationship_model
[Accessed 13 Oct 18].
6. 1994. wikipedia. [Online]
Available at: https://en.wikipedia.org/wiki/MySQL
[Accessed 13 Oct 2018].

45. 36
7. wikipedia. [Online]
Available at:https://en.wikipedia.org/wiki/Microsoft_Visual_Studio
8. Rouse, M., n.d. whatIS. [Online]
Available at: https://whatis.techtarget.com/definition/framework
[Accessed 13 oct 2018].