Pharmacy Final Destination
Pharmacy Final Destination
A PROJECT REPORT
SUBMITTED BY
                           THIRUNAVUKARASU.R
                                 (2113141040064)
                              Under the guidance of
                     R.Samundeeswari MCA.,MBA.,M.PHIL.,
                          ASSISTANT PROFESSOR
                                 MARCH – 2024
                GURU NANAK COLLEGE
                               (AUTONOMOUS)
BONAFIDE CERTIFICATE
Submitted for the Project Viva Voce Examination held on ________________ at GURU
NANAK COLLEGE (Autonomous), Guru Nanak Salai, Velachery, Chennai - 600 042.
(Computer Application) at Guru Nanak College (Autonomous), Chennai hereby declare that
record of the original work carried out by me under the Guidance and Supervision of
Application). I further declare that this has not been submitted anywhere for the award of
DATE:                                                             (2113141040064)
                                ACKNOWLEDGEMENT
I would like to thank the Principal Dr. T. K. Avvai Kothai M.Com., Mphil., Ph.D. and Vice
Principal Dr. Anitha Malisetty MBA., NET., Ph.D. for providing the necessary resources
I extend my deepest thanks to The Head of Department, Dr. D.Leelavathi M.Com., M.Phil.,
B.Ed., MBA., Ph.D. whose guidance, support, and encouragement were invaluable throughout
this endeavour. Her expertise and insights have been instrumental in shaping this project and
gratitude for his/her invaluable guidance, patience, and encouragement. His/Her mentorship
has been a beacon of light, steering me through the complexities of this project and helping me
realize my potential.
I also like to extend my thanks to the Faculty Members, for their valuable suggestion during
the course of the study of my project. Last but not least, I thank my family and friends for
1.3 BENEFITS 3
2. SYSTEM ANALYSIS 4
3. SYSTEM DESIGN 10
4                                               19
       SYSTEM DEVELOPMENT
                                                19
           4.1 LANGUAGE / TOOLS
                                                21
           4.2 CODING
                                                50
           4.3 SAMPLE SCREENSHOT & OUTPUT
6 CONCLUSION 58
7 FUTURE ENHANCEMENT 59
8      BIBLIOGRAPHY                             60
                                       CHAPTER 1
                                   INTRODUCTION
The main aim of the Pharmacy Management System is the pharmaceutical shop. This project
is insight into the design and implementation of a Pharmacy Management System. This is done
by creating a database of the available medicines in the shop. The primary aim of pharmacy
management system is to improve accuracy and enhance safety and efficiency in the
pharmaceutical store. The Pharmacy Management System Project in Python is a computer
based program for managing, monitoring, and recording medical store activities. Through
automated features, it helps to increase the efficiency of medical stores. It also aids in the
resolution of challenges with manual pharmacy management. The pharmacy management
system, often known as the pharmacy information system, is a system that organizes and
manages the drug usage process within pharmacies by storing data and enabling functionality.
A Pharmacy Management System in Python with Graphical User Interface (GUI) with a
SQLite3 database connectivity in python using Tkinter. A user can add, update, delete, search
medicine details.
                                              1
1.1 ABSTRACT
                                              2
1.2 OBJECTIVE
The Pharmacy Management System’s major goal is to keep track of Medicines, Stocks,
Inventory, Pharmacy, and Sales. It keeps track of all information pertaining to Medicines,
Companies, Sales, and Medicines. Because the project is entirely constructed at the
administrative level, only the administrator has access.
1.3 BENEFITS
The pharmacy information system (PIS) is a multi-functional system that helps pharmacists
keep track of drug supplies and organize them. The technology helps to reduce prescription
errors, improve patient safety, track costs, and report drug usage.
                                                3
                                        CHAPTER 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.
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.
    •   Significant amount of time is allocated for writing the order as the pharmacist needs to
        go through the stock balance and make rough estimate for the amount to order based on
        Figures.
    •   The state of drugs in stock is manually checked.
    •   Mistake of selling expired drugs to customers.
    •   Too much workload on employees.
    •   Filing cabinet in the pharmacy with paper record.
                                                4
2.2 PROPOSED SYSTEM
From the problems listed in the existing system, the implementation of the proposed system
shall focus on
                                               5
2.3 HARDWARE/ SOFTWARE REQUIREMENT
                                Processor          CORE i3
     Minimum Hardware
        Requirement
                               Main Memory        4 GB RAM
HDD 80 GB
Server Python
                                    6
•   Client Side Requirement
                                               Pentium IV
Minimum Hardware
                              Processor
   Requirement
                                               1GB RAM
                         Main Memory
HDD 4GB
                                  7
2.4 FEASIBILITY STUDY
After doing the project Pharmacy Shop Management System, study and analyzing all the
existing or required functionalities of the system, the next task is to do the feasibility study for
the project. All projects are feasible – given unlimited resources and infinite time. During
system analysis the feasibility study of the proposed system is to be carried out. This is to
ensure that the proposed system is not a burden to the company. For feasibility analysis, some
understanding of the major requirements for the system is essential.
• ECONOMICAL FEASIBILITY
• TECHNICAL FEASIBILITY
• OPERATIONAL FEASIBILITY
A. Economical Feasibility
This is a very important aspect to be considered while developing a project. We decided the
technology based on minimum possible cost factor.
                                                 8
B. Technical Feasibility
This study is carried out to check the technical feasibility, that is, the technical requirements of
the system. Any system developed must not have a high demand on the available technical
resources. This will lead to high demands on the available technical resources. This will lead
to high demands being placed on the client. The developed system must have a modest
requirement, as only minimal or null changes are required for implementing this system
C. Operational Feasibility
No doubt the proposed system is fully GUI based that is very user friendly and all inputs to be
taken all self-explanatory even to a layman. Besides, a proper training has been conducted to
let know the essence of the system to the users so that they feel comfortable with new system.
As far our study is concerned the clients are comfortable and happy as the system has cut down
their loads and doing.
                                                 9
                                      CHAPTER 3
SYSTEM DESIGN
• Primary Design Phase: In this phase, the system is designed at block level. The blocks are
created on the basis of analysis done in the problem identification phase. Different blocks are
created for different functions emphasis is put on minimizing the information flow between
blocks. Thus, all activities which require more interaction are kept in one block.
• Secondary Design Phase: In the secondary phase the detailed design of every block is
performed.
The general tasks involved in the design process are the following:
• System reviews.
                                               10
User Interface Design is concerned with the dialogue between a user and the computer. It is
concerned with everything from starting the system or logging into the system to the eventually
presentation of desired inputs and outputs. The overall flow of screens and messages is called a
dialogue. The following steps are various guidelines for User Interface Design:
• The screen should be formatted so that various types of information, 8 instructions and
messages always appear in the same general display area.
• Message, instructions or information should be displayed long enough to allow the system
user to read them.
• Use display attributes sparingly. Default values for fields and answers to be entered by the
user should be specified.
• The system user should never get an operating system message or fatal error.
                                              11
3.1 DATABASE DESIGN
The most important aspect of building software systems is database design. The highest level
in the hierarchy is the database. It is a set of inter-related files for realtime processing. It contains
the necessary data for problem solving and can be used by several users accessing data
concurrently. The general objective of database design is to make the data access easy, in
expensive and flexible to the user. Database design is used to define and then specify the
structure of business used in the client/server system. In this project, here used Microsoft SQL
Server as the database to implement the data store part.The most important part in the database
design is the identification of tables to beused.
                                                  12
3.2 TABLE DESIGN
PHARMACY RECORDS TABLE
Uses NCHAR(100) -
Dosage NCHAR(10) -
                           13
3.3 DATA FLOW DIAGRAM
A data flow diagram (DFD) is a graphical view of how data is processed in a system in terms
of input and output. It contains some symbol for drawing the data flow diagram. A data flow
diagram is a way of representing a flow of a data of a process or a system. The DFD also
provides information about the inputs and outputs of each entity and the process itself. A data
flow diagram has no control flow, no decision rules and no loops. For each data flow, at least
one of the endpoints must exist in a process. The refined representation of a process can be done
in another data flow diagram, which subdivides this process into sub processes.
SYMBOL DESCRIPTION
DATA FLOW
PROCESS
ENTITY
DATA STORE
                                              14
CONTEXT ANALYSIS DIAGRAM
MEDICINE DETAILS
                      PHARMACY        INVENTORY
   MEDICINE
                     MANAGEMENT        MEDICINE
 INFORMATION
                       SYSYTEM          DETAILS
                           15
FIRST DFD DIAGRAM
                     COMPANY      DRUGS
   PHARMACY           DETAILS    DETAILS
  MANAGEMENT
    SYSTEM
                       1.0         2.0
                       16
SECOND DFD DIAGRAM
                        17
FLOWCHART
Client
                        Request
                         drugs
Pharmacist
                  NO      Drug         YES
                       availability?
Purchase Sales
     Purchase                                Sales
      reports                                reports
End
                        18
                                      CHAPTER 4
                              SYSTEM DEVELOPMENT
4.1 LANGUAGE/TOOLS
PYTHON
The Python installers for the Windows platform usually include the entire standard library and
often also include many additional components. For Unix-like operating systems Python is
normally provided as a collection of packages, so it may be necessary to use the packaging
tools provided with the operating system to obtain some or all of the optional components.
Guido van Rossum began working on Python in the late 1980s as a successor to the ABC
programming language and first released it in 1991 as Python 0.9.0. Python 2.0 was released
in 2000 and introduced new features such as list comprehension, cycle- detecting garbage
collection, reference counting, and Unicode support. Python 3.0, released in 2008, was a major
revision that is not completely backward-compatible with earlier versions. Python 2 was
discontinued with version 2.7.18 in 2020. Python consistently ranks as one of the most popular
programming languages.
                                              19
SQLITE3
SQLite is a C library that provides a lightweight disk- based database that doesn't require a
separate server process and allows accessing the database using a nonstandard variant of the
SQL query language. Some applications can use SQLite for internal data storage. It's also
possible to prototype an application using SQLite and then port the code to a larger database
such as PostgreSQL or Oracle.
The sqlite3 module was written by Gerhard Häring. It provides an SQL interface compliant
with the DB-API 2.0 specification described by PEP 249, and requires SQLite 3.7.15 or newer.
                                             20
4.2 SAMPLE CODING
class Pharmacy:
Management System")
self.root.geometry("1350x800+0+0")
self.root.resizable(False, False)
self.root.iconbitmap(r"F:\PharmacyManagementSystem
Project\doc.ico")
= StringVar()
                                           21
self.issuedt_var = StringVar() self.expdt_var = StringVar() self.uses_var =
StringVar()
= StringVar()
self.count = 0 self.text
= "" self.color =
["green"] self.heading
= Label(self.root,
text=self.txt, font=(
#        ,bg='#7FFFD4',fg='#0020C2',font=('times   new
roman',35,'bold'),padx=2,pady=4)
                                           22
# lbltitle.pack(side=TOP,fill=X)
b1.place(x=15, y=8)
column=0)
                                      23
update_button    =       Button(down_buttonframe,          command=self.update_new,
text="UPDATE", font=(
activebackground="black", activeforeground="white")
delete_button.grid(row=0, column=2)
                                          24
search_by = Label(down_buttonframe, text="Search By", font=( "arial",
entry_button.grid(row=0, column=7)
activebackground="white", activeforeground="white",
column=9)
                                              25
######## left small frame #######
left_smallframe = LabelFrame(topframe, bg='white', bd=10, relief=RIDGE,
height=350)
#1
column=0, sticky=W)
conn = sqlite3.connect(database=r'E:\Pharmacy_management-
my_cursor.fetchall()
                                        26
self.ref_combo["values"]             =              ('Select',row_01)
#2
column=0)
self.company_entry                       =                   Entry(left_smallframe,
textvariable=self.companyname_var, width=24, font=( "times
self.company_entry.grid(row=1, column=1)
pady=4, font=(
column=0, sticky=W)
self.type_combo=ttk.Combobox(left_smallframe,
                                         27
" Select ", "Tablet", "Capsule", "Injection", "Ayurvedic", "Drops", "Inhales")
#4
column=0, sticky=W)
conn = sqlite3.connect(database=r'E:\Pharmacy_management-
my_cursor.fetchall()
self.medname_combo                 =                   ttk.Combobox(left_smallframe,
textvariable=self.medicine_var, width=22, font=( "times
self.medname_combo["values"] = ('Select',row_02)
self.medname_combo.grid(row=3, column=1)
self.medname_combo.current(0)
#5
                                            28
lot_label = Label(left_smallframe, text=" Lot No. :", padx=2, pady=4, font=(
column=0)
self.lot_entry.grid(row=4, column=1)
#6
column=0)
self.issue_entry   =     Entry(left_smallframe,
textvariable=self.issuedt_var, width=24, font=(
self.issue_entry.grid(row=5, column=1)
#7
                                       29
exp_label = Label(left_smallframe, text=" Expiry Date :", padx=2, pady=4,
font=(
column=0)
self.exp_entry.grid(row=6, column=1)
#8
font=(
self.use_entry.grid(row=7, column=1)
#9
                                       30
sideeffect_label = Label(left_smallframe, text=" Side Effect :", padx=2, pady=4,
font=(
column=0)
self.sideeffect_entry.grid(row=8, column=1)
# 10
column=0)
self.warn_entry    =     Entry(left_smallframe,
textvariable=self.warning_var, width=24, font=(
self.warn_entry.grid(row=9, column=1)
# 11
                                       31
dosage_label = Label(left_smallframe, text=" Dosage :", padx=2, pady=4, font=(
column=2)
self.dosage_entry =      Entry(left_smallframe,
textvariable=self.dosage_var, width=23, font=(
self.dosage_entry.grid(row=0, column=3)
# 12
column=2)
self.price_entry.grid(row=1, column=3)
# 13
                                       32
qt_label = Label(left_smallframe, text=" Tablet Quantity :", padx=2, pady=4,
font=(
column=2)
self.qt_entry.grid(row=2, column=3)
Management System
width=170, height=150)
System
width=160, height=150)
                                       33
# save life label save_bgg = Label(left_smallframe, text="----------- Stay Home
width=400)
width=452, height=350)
System
Project\virus.jpeg") lbl_bg1 =
Label(right_frame, image=self.bg1)
                                           34
#### label & entry in right frame ####
font=(
y=105)
y=105)
font=(
y=130)
self.med_entry=Entry(right_frame,    textvariable=self.addmed_variable,
width=16, font=(
y=130)
                                         35
newframe     =   Frame(right_frame,   bg='darkgreen',   bd=5,   relief=RIDGE)
updatenew_button.grid(row=1, column=0)
                                      36
##### scrollbar frame in right frame ####
side_frame = Frame(right_frame, bd=4, relief=RIDGE, bg="dark green")
= ttk.Scrollbar(side_frame, orient=VERTICAL)
sc_x.config(command=self.medicine_table.xview)
sc_y.config(command=self.medicine_table.yview)
self.medicine_table.heading("ref", text="Ref")
self.medicine_table.column("medname", width=100)
                                        37
self.medicine_table.bind("<ButtonRelease-1>",                      self.medget_cursor)
self.fetch_datamed()
width=1350, height=212)
no", "comp name", "type", "medi name", "lot no", "issue", "exp",
scroll_x.config(command=self.info_table.xview)
scroll_y.config(command=self.info_table.yview)
self.info_table.column("type", width=100)
self.info_table.column("issue", width=100)
self.info_table.column("exp", width=100)
                                         39
effect", width=100) self.info_table.column("warning", width=100)
self.info_table.column("dosage", width=100)
self.info_table.column("price", width=100)
self.info_table.column("product", width=100)
self.info_table.bind("<ButtonRelease-1>", self.get_cursor)
self.fetch_new()
else:
conn = sqlite3.connect(database=r'E:\Pharmacy_management-
self.fetch_datamed() conn.close()
def fetch_datamed(self):
                                        40
conn =       sqlite3.connect(database=r'E:\Pharmacy_management-
systemmaster\pharmacy.db')
my_cursor                =           conn.cursor()
= my_cursor.fetchall()
if len(rows) != 0:
self.medicine_table.delete(*self.medicine_table.get_children())
for i in rows:
conn.commit() conn.close()
= self.medicine_table.item(cursor_row) row =
content["values"] self.ref_variable.set(row[0])
self.addmed_variable.set(row[1])
                                        41
def Update_med(self):
else: try:
= conn.cursor()
self.addmed_variable.get(),
self.ref_variable.get() ))
def Delete_med(self): if
self.ref_variable.get()=="":
try:
                                        42
conn=sqlite3.connect(database=r'E:\Pharmacy_management-
systemmaster\pharmacy.db') my_cursor=conn.cursor()
messagebox.showinfo("Delete","Successfully Deleted",parent=self.root)
self.addmed_variable.set("") ########
MEDICINE DEPARTMENT
FUNCTIONALITY #######
def addmedicine(self):
conn=sqlite3.connect(database=r'E:\Pharmacy_management-
systemmaster\pharmacy.db') new_cursor=conn.cursor()
new_cursor.execute("Insert
intoInformation(REF_NO,COMPANY_NAME,TYPE_OF_MED,MED_NAMe,
LOT_NO,ISSUE_DT,EXP_DT,USES,SIDE_EFFECT,PRECAUTION,DOSAG
E,PRICE,QUANTITY) values(?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)",(
                                          43
self.refno_var.get(),
self.companyname_var.get(),
self.typemed_var.get(),
self.medicine_var.get(),
self.lotno_var.get(),
self.issuedt_var.get(),
self.expdt_var.get(), self.uses_var.get(),
self.sideeffect_var.get(),
self.warning_var.get(),
self.dosage_var.get(),
self.price_var.get(),
self.quantity_var.get(),
))
conn.commit() self.fetch_new()
messagebox.showinfo("Success","Successfully added")
def fetch_new(self):
conn=sqlite3.connect(database=r'E:\Pharmacy_management-
systemmaster\pharmacy.db') new_cursor=conn.cursor()
row=new_cursor.fetchall()
                                         44
if len(row)!=0:
self.info_table.delete(*self.info_table.get_children())
for i in row:
self.info_table.insert("",END,values=i)
conn.commit()
def get_cursor(self,event=""):
cursor_row=self.info_table.focus()
content=self.info_table.item(cursor_row)
row=content["values"] self.refno_var.set(row[0])
self.companyname_var.set(row[1])
self.typemed_var.set(row[2])
self.medicine_var.set(row[3])
self.lotno_var.set(row[4])
self.issuedt_var.set(row[5])
self.expdt_var.set(row[6])
self.uses_var.set(row[7])
self.sideeffect_var.set(row[8])
self.warning_var.set(row[9])
self.dosage_var.set(row[10])
self.price_var.set(row[11])
self.quantity_var.set(row[12])
                                          45
def update_new(self)
conn=sqlite3.connect(database=r'E:\Pharmacy_management-
systemmaster\pharmacy.db') new_cursor=conn.cursor()
self.companyname_var.get(),
self.typemed_var.get(),
self.medicine_var.get(),
self.lotno_var.get(), self.issuedt_var.get(),
self.expdt_var.get(), self.uses_var.get(),
self.sideeffect_var.get(),
self.warning_var.get(),
self.dosage_var.get(), self.price_var.get(),
self.quantity_var.get(),
self.refno_var.get(),
))
conn.commit() self.fetch_new()
                                            46
self.clear_new() messagebox.showinfo("Success","Successfully
updated")
self.companyname_var.set("")
self.typemed_var.set("")
self.medicine_var.set("")
self.lotno_var.set("")
self.issuedt_var.set("")
self.expdt_var.set("")
self.uses_var.set("")
self.sideeffect_var.set("")
self.warning_var.set("")
self.dosage_var.set("")
self.price_var.set("")
self.quantity_var.set("")
def search_data(self):
conn=sqlite3.connect(database=r'E:\Pharmacy_management-
if len(row)!=0:
self.info_table.delete(*self.info_table.get_children())
conn.commit()
def slider(self): if
self.count>=len(self.txt):
self.count=-1 self.text=""
self.heading.config(text=self.text)
else:
self.text=self.text+self.txt[self.count]
self.heading.config(text=self.text)
self.count+=1
self.heading.after(200,self.slider) def
heading_color(self):
fg=random.choice(self.color)
self.heading.config(fg=fg)
                                            48
self.heading.after(100,self.heading_c
olor)
if _name_ == '_main_':
root=Tk() obj=Pharmacy(root)
root.mainloop()
                                        49
4.3 SAMPLE SCREENSHOT & OUTPUT
                         50
ADD MEDICINE FORM
                    51
ADD MEDICINE FORM
                    52
SQL LITE3 EDITOR
                   53
OUTPUT
         54
                                       CHAPTERR 5
                       SYSTEM TESTING AND VALIDATIONS:
It essential provides several diagramming tools that can express different aspects/
characteristics of program such as Use cases: Elicit requirement from users in meaningful
chunks. Construction planning is built around delivering some use cases n each interaction
basis for system testing. Class diagrams: shows static structure of concepts, types and class.
Concepts how users think about the world; type shows interfaces of software components;
classes shows implementation of software components. Interaction diagrams: shows how
several objects collaborate in single use case. Package diagram: show group of classes and
dependencies among them. State diagram: show how single object behaves across many use
cases. Activity diagram: shows behavior with control structure. Can show many objects over
many uses, many object in single use case, or implementations methods encourage parallel
behavior, etc.
                                               55
•   TESTING THE WHOLE SYSTEM
System testing is performed on the entire system in the context of a Functional Requirement
Specification(s) (FRS) and/or a System Requirement Specification (SRS). System testing tests
not only the design, but also the behavior and even the believed expectations of the customer.
It is also intended to test up to and beyond the bounds defined in the software/hardware
requirements specification(s).
The term implementation has different meanings ranging from the conversation of a basic
application to a complete replacement of a computer system. The procedures however, are
virtually the same. Implementation includes all those activities that take place to convert from
old system to new. The new system may be totally new replacing an existing manual or
automated system or it may be major modification to an existing system. The method of
implementation and time scale to be adopted is found out initially. Proper implementation is
essential to provide a reliable system to meet organization requirement.
• UNIT TESTING
In computer programming, unit testing is a software testing method by which individual units
of source code, sets of one or more computer program modules together with associated control
data, usage procedures, and operating procedures, are tested to determine whether they are fit
for use. Intuitively, one can view a unit as the smallest testable part of an application. In
procedural programming, a unit could be an entire module, but it is more commonly an
individual function or procedure. In object-oriented programming, a unit is often an entire
interface, such as a class, but could be an individual method. Unit tests are short code fragment
created by programmers or occasionally by white box testers during the development process.
It forms the basis for component testing. Ideally, each test case is independent from the others.
Substitutes such as method stubs, mock objects, fakes, and test harnesses can be used to assist
testing a module in isolation. Unit tests are typically written and run by software developers to
ensure that code meets its design and behaves as intended.
                                               56
•   BLACK BOX
• WHITE BOX
                                            57
                                       CHAPTER 6
CONCLUSION
The conclusion is an understanding of how the system functions. This system is called the
existing system. Now the existing system is subjected to close study and problem areas are
identified. The designer now functions as a problem solver and tries to sort out the difficulties
that the enterprise faces. The solutions are given as proposals. The proposal is then weighed
with the existing system analytically and the best one is selected. The proposal is presented to
the user for an endorsement by the user. The proposal is reviewed on user request and suitable
changes are made. This is loop that ends as soon as the user is satisfied with proposal.
Preliminary study is the process of gathering and interpreting facts, using the information for
further studies on the system. Preliminary study is problem solving activity that requires
intensive communication between the system users and system developers. It does various
feasibility studies. The "Pharmacy Management System" has been developed to override the
problems prevailing in the practicing manual system. This software is supported to eliminate
and in some cases reduce the hardships faced by this existing system. The application is reduced
as much as possible to avoid errors while entering the data.
                                               58
                                        CHAPTER 7
FUTURE ENHANCEMENT
The "Pharmacy Management System" has been developed to override the problems prevailing
in the practicing manual system. This software is supported to eliminate and in some cases
reduce the hardships faced by this existing system. The application is reduced as much as
possible to avoid errors while entering the data. It is recommended that the new system should
be used with the necessary specifications of the system requirements and provision for an
uninterrupted power supply should be made available throughout the hours of operation of the
pharmacy to avoid power outage. There should also be basic computer knowledge for the users
of the software. It is recommended that the software be improved especially in areas of
accounting as it will be of great impact to the development of retail pharmacy. Also, for those
busy executive who are always on the go, our systems come with remote access features, which
will allow you to manage your workforce anytime, at all times. These systems will ultimately
allow you to better manage resources.
                                              59
                                     CHAPTER 8
BIBILIOGRAPHY
REFERENCES
LANGUAGES                        -     www.w3schools.com
                                     www.geeksforgeeks.com
                                     Python.org
IDEAS & IMPLEMENTATIONS - www.google.co.in
www.w3schools.com
www.DocFoc.com
www.SlideShare.com
www.codeproject.com
60