Harambee University

HARAMBEE UNIVERSITY
FACULTY OF TECHNOLOGY
DEPARTMENT OF COMPUTER SCIENCE

FINAL YEAR PROJECT DOCUMENTATION ON: - WEB BASED
PHARMACY MANAGMENT SYSTEM IN CASE OF ADAMA HOSPITAL
MEDICAL COLLEGE PHARMACY
GROUP MEMBERS
NO NAME ID.NO
1. TSION HAILYE 8005
2. YONAS ESHETU 8011
3. GIRMA ASEFA 8027
ADVISOR: SENIOR INSTRUCTOR ABERA G/TSADIK (M.SC).

HARAMBEE UNIVERSITY
ADAMA ETHIOPIA
July, 2022 G.C

Approval letter
This is to certify that the project is original and has not submitted for partial fulfillment of Bachelor
of Science in computer science. The Name and Signature of Group members.
Name Signature
Tsion Hailye ……………………………….
Yonas Eshetu ……………………………….
Girma Asefa ……………………………….
Project title: -web based pharmacy management system.
This is to certify that I have read this project and that in my opinion it is fully adequate, in scope and
quality, as a thesis for the degree of Bachelor of computer Science.
Name of advisor Signature
------------------------------------ ----------------------
Examining committee members signature Date
Examiner 1 ____________ ____________ __________
Examiner 2 ____________ ____________ __________
Examiner 3 ____________ ____________ ___________
Examiner 4 ____________ ____________ ___________
Examiner 5 ____________ ____________ ___________
It is approved that this project has been written in compliance with the formatting rules laid down by
the college of the university.

ACKNOWLEDGMENT
First and fore most and above all our biggest thanks would be to Almighty God because nothing
could be possible without his free will and the completion of this project is supported by him.
Secondly, we would like to thank our Advisor Abera G/Tsadik(M.SC). And project coordinator Mr.
Shambel Ture for them rest less edition of our documentation, input to the quality of thisdocument,
heart full guidance, valuable advice, and providing to execute this project.Thirdly we would like to
thank Dr. Awlachew for his willingness of interview, patience in answering to our numerous
questions, giving documents and reading materials that help us to precede our project. Finally, the
last but not the least, even if it is usual the group members would like to thank each other. The main
contributors to do this document project are teamwork, friendship and the belief that to achieve our
goal. We also hope that this project and documentation may be testaments to our continued
friendship and better work. Without helps of the particular that mentioned above, we would face
many difficulties while doing this.
Thanks Again To All Who Helped Us .
Group member
i
DEFINITIONS OF TERMS
 Pharmacist: -The customer comes with the ordered prescription then the pharmacist looks
that order of drug and gives the drug accordingly.
 Pharmacy manager: -The manager gets reports from the pharmacist, store coordinator, and
cashier.
 Store coordinator: -is responsible to register the drugs that buy from the private sectors and
also control the drugs that are goes out to the stock.
 Cashier: -The cashier receives the cost of the drug from the customer ordered by the
pharmacist.
 Store: -is the place in which the new bought drug is stored.
 Stock: - is the place in which the drug that needs to be salable is stored
ii
ABBREVIATION AND ACRONYMS
 AHMCPMS:-Adama Hospital and Medical College PharmacyManagement

System.
 PHP:-Hypertext preprocessor.
 HTML:-Hypertext markup language.
 MYSQL:-Structured Query Language.
 HTTP:-Hyper Text Transfer Protocol.
 IDE:-Integrated Development Environment.
 OOD:-Object oriented design.
 ID: - Identification.
 UC: - Use case.
 CSS:-Cascading Style Sheet.
 JS:-Java script.
 UML:-Unified Modeling Language.
 HW:-Hardware.
 DB:-Stands for database.
 OPD:-Out-Patient department.
 AHMC:-Adama Hospital and Medical College
 HAD:-Health Development Armies
 HDD:- Hard Disk
iii
Table of contents
ACKNOWLEDGMENT ....................................................................................................................... i
DEFINITIONS OF TERMS .................................................................................................................ii
ABBREVIATION AND ACRONYMS ..............................................................................................iii
LIST OF TABLES ............................................................................................................................ viii
LIST FIGURES ................................................................................................................................... ix
ABSTRACT ........................................................................................................................................ xi
CHAPTER ONE: INTRODUCTION AND BACKGROUND ............................................................1
1.1 Introduction ............................................................................................................................. 1
1.2 Background of Organization ................................................................................................... 2
1.3 Statement of the problem ........................................................................................................ 3
1.4 Purpose of the proposed system .............................................................................................. 3
1.5 Team Composition .................................................................................................................. 4
1.6 Objectives of the project ..........................................................................................................4
1.6.1 General objective .......................................................................................................... 4
1.6.2 Specific objectives ........................................................................................................ 4
1.7 Feasibility study ...................................................................................................................... 5
1.7.1 Economic Feasibility (Cost Benefit Analysis) ..............................................................5
1.7.2 Technical feasibility ......................................................................................................6
1.7.3 Operational feasibility ...................................................................................................6
1.8 Scope and Limitations of the project .......................................................................................7
1.8.1 Scope .............................................................................................................................7
1.8.2 Limitation ......................................................................................................................7
1.9 Significance of the project .......................................................................................................8
iv
1.10 Methodology ......................................................................................................................... 8
1.10.1 System Development Approach ..................................................................................8
1.10.2. Software Process Model Approach ............................................................................9
1.10.3. Data Collection Methods ......................................................................................... 10
1.11 Development Tools ............................................................................................................. 11
1.11.1. Language ..................................................................................................................11
1.12 Testing process .................................................................................................................... 12
1.12.1. Unit testing ...............................................................................................................12
1.12.2. Integrate testing ........................................................................................................12
1.12.3 System testing ........................................................................................................... 12
1.13 Tasks of the Team Members in the project ......................................................................... 13
1.14 Time Schedule .....................................................................................................................14
CHAPTER TWO: DESCRIPTION OF EXITING SYSTEM ............................................................15
2.1 Major Function of Current System ........................................................................................15
2.2 Users of the current system ................................................................................................... 16
2.3 Drawback of the current system ............................................................................................17
2.4 Business rule of the current system .......................................................................................18
2.5 Paper Document in the Existing System ............................................................................... 19
CHAPTER THREE: PROPOSED SYSTEM ....................................................................................21
3.1 Overview ............................................................................................................................... 21
3.2 Functional Requirement of the New System .........................................................................22
3.3 Non-functional requirement of the new system .................................................................... 23
3.3.1. User friendly/system interface ................................................................................... 23
3.3.2. Response time ............................................................................................................ 23
3.3.3. Reliable ...................................................................................................................... 23
v
3.3.4 Compatible .................................................................................................................. 23
3.3.5 Database size ...............................................................................................................24
3.3.6 Security ....................................................................................................................... 24
3.3.7 System modification ................................................................................................... 24
3.3.8 Physical environment ..................................................................................................24
3.3.9 Quality issue ................................................................................................................25
3.3.12 Maintenance .............................................................................................................. 25
3.3.13 Manageability ............................................................................................................25
3.4 Performance Requirement .....................................................................................................26
3.5 System Model ........................................................................................................................26
3.5.1 Scenarios .................................................................................................................... 27
3.5.2 Use Case Model .......................................................................................................... 31
3.6 Object Mode .......................................................................................................................... 48
3.6.1. Data dictionary ...........................................................................................................48
3.6.2. Class diagram .............................................................................................................52
3.7 Dynamic Model .....................................................................................................................53
3.7.1Sequence diagram ........................................................................................................ 54
3.7.2Activity diagram .......................................................................................................... 63
3.7.3 State diagram ...............................................................................................................71
3.7.4 User interface .............................................................................................................. 78
CHAPTER FOUR: SYSTEM DESIGN .............................................................................................79
4.1. Overview of system design .................................................................................................. 79
4.1.1. Purpose of the system design ..................................................................................... 79
4.1.2 Design goal ................................................................................................................. 80
4.2 Proposed system architecture ................................................................................................ 82
vi
4.2.1 System process ............................................................................................................83
4.2.2 Subsystem decomposition ...........................................................................................84
4.2.3 Hardware/software mapping ....................................................................................... 85
4.2.4 Persistent Data management ....................................................................................... 86
4.2.5 Component diagram ....................................................................................................89
4.2.6 Deployment diagram ...................................................................................................90
4.2.7 Boundary condition .....................................................................................................91
4.2.8 Database design ...........................................................................................................92
4.2.9 Access control ............................................................................................................. 93
CHAPTER FIVE : SYSTEM IMPLEMENTATION AND TESTING ........................................... 95
5.1 Introduction ........................................................................................................................... 95
5.2 SystemTesting ....................................................................................................................... 95
5.3 System Implimentation ..........................................................................................................98
CHAPTER SIX :CONCLUSION AND RECOMANDATION ......................................................101
6.1 Conclusion ...........................................................................................................................101
6.2 Recommendation .................................................................................................................101
Reference .......................................................................................................................................... 102
APPENDIX ........................................................................................................................................ xii
vii
LIST OF TABLES
Table1.1 Team composition ................................................................................................................. 4

Table 1.2 software requirement ............................................................................................................ 9
Table 1.3 Task table ............................................................................................................................13
Table 1.4Time Schedule of the Project ...............................................................................................14
Table 3.1use case description for login .............................................................................................. 36
Table 3.2 use case description for Register employee ........................................................................37
Table 3.3 use case description for Create account ..............................................................................38
Table 3.4 use case description for active/inactive account .................................................................39
Table 3.5 use case description for change password .......................................................................... 40
Table 3.6 use case description for View report .................................................................................. 41
Table 3.7 use case description for Register Customer ........................................................................42
Table 3.8 use case description for Register drug ................................................................................43
Table 3.9 use case description for check expire date ..........................................................................44
Table 3.10 use case description for order drug ..................................................................................45
Table 3.11 use case description for Print receipt ................................................................................46
Table 3.12 use case description for log out ........................................................................................ 47
Table 3.13 Data Dictionary for Account ............................................................................................ 48
Table 3.14 Data Dictionary for customer ........................................................................................... 48
Table 3.15 Data Dictionary for Drug ..................................................................................................49
Table 3.16 Data Dictionary for Feedback ...........................................................................................49
Table 3.17 Data Dictionary for Iboxemployee .................................................................................. 50
Table 3.18 Data Dictionary for Message ...........................................................................................50
Table 3.19 Data Dictionary for Report ............................................................................................. 51
Table 4.1 Access Control ....................................................................................................................94
Table 5.1 System test ..........................................................................................................................97
viii
LIST FIGURES
Figure 2.1. Cash sales invoice form ....................................................................................................19
Figure 2.2. Prescription paper .............................................................................................................20
Figure 3.1 Use case diagram ...............................................................................................................35
Figure 3.2 Class Diagram ................................................................................................................... 53
Figure 3.3 sequence diagram for login ............................................................................................... 54
Figure 3.4 sequence diagram for Register Employee .........................................................................55
Figure 3.5 sequence diagram for Create Account .............................................................................. 56
Figure 3.6 sequence diagram for Delete Account .............................................................................. 57
Figure 3.7 sequence diagram for Active/inactive Account ................................................................ 58
Figure 3.8 sequence diagram for Register Drug .................................................................................59
Figure 3.9 sequence diagram for Check Expire Date ......................................................................... 60
Figure 3.10 sequence diagram for Order Drug ...................................................................................61
Figure 3.11 sequence diagram for Print Receipt ............................................................................... 62
Figure 3.12 Activity diagram for login ...............................................................................................63
Figure 3.13 Activity diagram for Register Employee ........................................................................ 64
Figure 3.14 Activity diagram for Create Account .............................................................................. 65
Figure 3.15 Activity diagram for Active/Inactive Account ................................................................66
Figure 3.16 Activity diagram for Register Drug ................................................................................ 67
Figure 3.17 Activity diagram for Order Drug .................................................................................... 68
Figure 3.18 Activity diagram for Check Expire Date .........................................................................69
Figure 3.19 Activity diagram for Print Receipt .................................................................................. 70
Figure 3.20 State diagram for Login ...................................................................................................71
Figure 3.21 State diagram for Register Employee ..............................................................................72
Figure 3.22 State diagram for Create Account ................................................................................... 73
ix
Figure 3.23 State diagram for Register Drug ......................................................................................74
Figure 3.24 State diagram for Order Drug ..........................................................................................75
Figure 3.25 State diagram for Check Expire Date ..............................................................................76
Figure 3.26 State diagram for View Report ........................................................................................77
Figure 3.27 User interface of Home page ...........................................................................................78
Figure 4.1 system architecture ............................................................................................................82
Figure 4.2 system Process ..................................................................................................................83
Figure 4.3 subsystem Decomposition .................................................................................................84
Figure 4.4 Hardware/software mapping ............................................................................................. 85
Figure 4.5 Persistent Mapping for Admin .......................................................................................... 86
Figure 4.6 Persistent Mapping for Manager ....................................................................................... 87
Figure 4.7 Persistent Mapping for Pharmacist ................................................................................... 87
Figure 4.8 Persistent Mapping for Store Coordinator ........................................................................ 88
Figure 4.9 Persistent Mapping for Cashier ......................................................................................... 88
Figure 4.10 Component Diagram ...................................................................................................... 89
Figure 4.11 Deployment Diagram ...................................................................................................... 90
Figure 4.12 Database design ...............................................................................................................92
Figure 5.1 User interface for home page ............................................................................................ 98
Figure 5.2 User interface for login form .............................................................................................98
Figure 5.3 User interface for Store coordinator page ......................................................................... 99
Figure 5.4 User interface for Register drug form ............................................................................... 99
Figure5.5 User interface for View drug ............................................................................................100
Figure 5.6 User interface for Check Expire Date ............................................................................. 100
x
ABSTRACT
Adama Hospital and Medical College Pharmacy Management System is one pharmacy in Adama
Town. This Pharmacy gives services for the ailing society by selling the drug. In the pharmacy,
there are two places in which the drug is available. Those are stock and store. The stock is the place
in which the drug that needs to be salable is stored. And the store is the place in which the new
bought drug is stored. At present manual system is being utilized in the pharmacy. It requires the
pharmacist to manually monitor each drug that is available in the pharmacy. This usually leads to
mistakes as the workload of the pharmacist increases.
This system has its own expected output for the customer as well as the employers in the pharmacy.
The functions that involve in this system are new store item registration, check availability items in
the data base, Store item expired date checking before the actual expired date reaches, purchase and
Sale drugs, manage account, authentication, retrieve data, insert, update, delete data is can be works
successfully.
In general, the project aimed to describe the general approaches to be followed to automate the
existing manual system to a computerized system. The system is developing by using PHP language.
The system use MYSQL as a back for database development and use HTML , CSS and JS as a
front end.
xi
CHAPTER ONE: INTRODUCTION AND BACKGROUND
1.1 Introduction
Technology is spreading its wing in almost every walk of human life activities. Now a day it is
better if every activity is done using new technology to fulfill the need of human being,
Organization and Enterprise etc. As today’s world, there are many organizations and each
organization needs to be preferable, computable and work on fastest way to satisfy users interest
etc. i.e. they should have facilitated their activities in computerized way.
Hence Pharmacy management system is a management system that is designed to improve accuracy
and to enhance the performance of the task in the pharmacy. It is a computer based system which
helps to the employee inside the pharmacy to facilitate the activity of the pharmacy in a manner
way.
In the pharmacy, there are two places in which the drug is available. Those are stock and store. The
stock is the place in which the drug that needs to be sold is stored. And the store is the place in
which the new bought drug is stored.
At present manual system is being utilized in the pharmacy. It requires the pharmacist to manually
monitor each drug that is available in the pharmacy. This usually leads to mistakes as the workload
of the pharmacist increases.
1
1.2 Background of Organization
Adama Hospital Medical College was previously known by the name of Haile Mariam Mamo
Memorial Hospital and Adama Referral Public Hospital at different times. It is one of the first
Medical Hospital situated in Adama town, located in Oromia Region, 100 km to southeast of Addis
Ababa, Ethiopia.The Hospital was inaugurated by missionaries from abroad in 1938 E.C and it was
among the first non-governmental Hospital in the nation with persistent commitment the pursuit to
establish as the nation’s leading healthcare provider. Then the Hospital developed its facilities,
technology, service standards and personal to become a renowned institution. It was put under
government during the dergue region in 1970 E.C.
The Hospital was upgraded to Medical College in 2003 E.C because of its location, patient load and
staff capacity. The college is led by the board and has three major wings (Academic and research,
Health service and the Development and Administration).Till now, the Hospital College has
undergone different reforms. To implement these reforms the HAD were organized at different
levels. The Hospital is serving a catchment population of more than six million; from five region
(Oromia, Amhara, Afar, Somali, and Dire-Dawa). The Hospital has 232 beds capacity and serving
on average 1000 patients per day at six medical case teams OPDs and different specialty clinics.
In general, AHMC is proving services using all available material, financial and human resources.
Because of improved services, the number of patients coming to the Hospital College is increasing
from day to day. If the number continues at this rate, the Hospital College will reach a position
where it can no longer provide efficient service for the community. The Hospital College has tried
to expand its existing facilities for the fundamental transformation, and the construction of the new
Hospital College complex was designed and started to be constructed with the cost of nearly one
billion ETB. At the completion, the new buildings will be expected to have 1200 beds capacity,
diagnostic facilities, offices, classrooms and the like. Indeed, the constructions were planned in three
phases. The first phase of ward complex, OPD, emergency, classrooms and Administration blocks
are on the way of about to be completed.
2
1.3 Statement of the problem
Managing a very large pharmacy with records on paper is tedious and difficult to keep track of
inventory with regards to the drugs in the stock inside the pharmacy. Since it is manual system
quantity of drugs available based on the categories and their functions can’t be easily known. Do to
this the patient, can’t get the drug they want. The employees of the pharmacy as well as the
customer are difficult to getting full information about drugs when needed immediately. Preparing
report for each drug takes long time for the pharmacist. It is difficult to identify which drugs are out
dated or expired. The existing system is executed in manually, do to this reason most sensitive data
is lost. During registering the drug most of the time it redundant data is occur.
1.4 Purpose of the proposed system
 To give fast response or service for customer.

 To know the drug those are finished in the pharmacy and replaces it by new drug in
computerized way.
 To know the medicine which their expired date is reached or passed.
 To Increase customer satisfaction .
 To decrease the work load of the User.
 Minimize the cost of Stationary resource to store data.
 More secured
 Easy to control and manage all activities of the system
3
1.5 Team Composition
No. Name Role
1. Yonas Eshetu Planning ,Analysis,Design,Documentation

and Coding
2. Girma Asefa Planning ,Analysis,Design,Documentation

and Coding
3. Tsion Hailye Planning ,Analysis,Design,Documentation

and Coding
Table1.1 Team composition

1.6 Objectives of the project
1.6.1 General objective
To Develop computerized Pharmacy Management System for Adama Hospital and medical college.
1.6.2 Specific objectives
 Study the existing pharmacy management method
 Identify the problem of existing pharmacy management method
 Previous system analysis.
 Identifying the Alternatives solutions.
 Selecting the best alternative solution.
 Current system design and Impalement.
 Create the database that will store the pharmacy data.
4
 Develop and implement a user-friendly interface.
 Make accountability and reliability also store and stock control.
1.7 Feasibility study
Feasibility study is essential to evaluate the cost and benefits of the new system. On the basis of the
feasibility study decision is taken on whether to proceed or to cancel the project. Need of the
feasibility study:
 It determines the potential of the existing system.
 It used to determine/finds out the problem of the existing system.
 To determine all goals of the new system.
 It finds all possible solutions of the problems of the existing system.
The feasibility study was done in five phases documented below.
1.7.1 Economic Feasibility (Cost Benefit Analysis)
This stage determines the cost or value analysis. It can be software, hardware, and the people. The
new proposed system will be economically feasible because it takes less capital as compared as the
existing system.
Generally, the system that we developed, Adama Hospital and Medical college Pharmacy
Management System brought a number of tangible and intangible benefits.
Tangible benefits:
1. Cost Reduction
2. Error Reduction
3. Increase Speed of activity
5
Intangible benefits:
1. Reduce Resource Consumption
2. Increase security
3. Increase Management flexibility
1.7.2 Technical feasibility
The proposed system doesn’t require much technical expertise. The system to be developed by using
technologically system development techniques such as PHP, Java script, CSS and MySQL database
without any problems and the group members have enough capability to develop the project. So the
system will be technically feasible.
1.7.3 Operational feasibility
The system to be developed will provide accurate, active, secured service and decreases labor of
workers and also it is not limited to particular groups or body. And also it is plat form independent
i.e. it run’s in all operating system. This system has been operationally feasible and the system has
been user friendly. The pharmacy worker and users of system uses the system to perform its regular
task without any ambiguity. The user of the system can understand the new system with little
training and instruction. Operationally, the system has capable of producing quick and qualitative
services for the pharmacy worker and the customer, so that to have immediate and satisfied services.
The systems developed are operationally more functional.
6
1.8 Scope and Limitations of the project
1.8.1 Scope
The scope of the project is listed in the following: -

 All users can login and logout except customer.
 Our proposed system Manage Employee (register, view and delete).
 Manage customer(Register, view, search)
 Manage users account (create, view, delete, active/inactive and change password).
 Allow customers to get information about drug and its price.
 The system checks expired date and warn up or give warning about those drug few day left
to expire.
 The system generates report.
 The system calculates the cost of drug and gives receipt for customer.
1.8.2 Limitation
 The customers pay the cost of drug by cash.
 The system dose not have digital attendance and dose not include or support salary.
 The system does not hold electronic prescription.
7
1.9 Significance of the project
As per the scope of the project, the outcome will include the followings: -
 Provide better data warehousing systems.
 It provides efficient, flexible and reliable drug storing, and locating .
 Minimize time consumption (speedup service) .
 Facilitate quality control.
 Decrease data damage by backup and recovery.
 Better customer satisfaction.
 To reduce resource wastage in terms of cost.
 To minimize the work load of the employees.
 Enhance best controlling method for the drug.
 Increase friendship among user of the system.
1.10 Methodology
In order to accomplish this project on time and within the cost, we followed different procedures
which are described below.
1.10.1 System Development Approach
To achieve the objective of this project we use Object Oriented Design. It is about how our objects
collaborate with each other. Here, we decide who create which objects and how they interact to
fulfill the needs of a user. After Finding and organizing the objects, we describe how the objects
interact, class name and attributes with their association identified then we moved to OOD and
during this we used to design the system include Database design (Persistence models), Deployment
modeling and User interface prototyping.
8
Software Requirement: These are software requirements to develop the system
Applications Software tools
Client Side Scripting HTML, CSS, JavaScript
Any Operating System MS Windows
Database Server MySQL
Web server Xampp
Server-Side scripting PHP
Browsers Mozilla Firefox, Internet Explorer, Chrome
Editors Notepad++,sublime text,vs code
User Interface Design HTML, CSS
Table 1.2 software requirement
Hardware Requirement: Are hardware needed to develop the system (planning up to testing the
proposed developed system)
 Personal computer or laptop
 Desktop
 Tablet
 Flash disc
1.10.2. Software Process Model Approach
Since requirements are well known, frequently changed and system are not stable, we use the Spiral
Model Linear framework type to achieve the objective of this project.
9
1.10.3. Data Collection Methods
These methods are designed in detail to ensure higher response rate and better accessibility to
respondents. Listed below are different methods of data collection used.
1.10.3.1. Site observation
We observed the problem when staffs are filling drug requisition form manually.Delay in the
response to the request and the speed with which the request is answered.
1.10.3.2. Interview
This is one of data collection method that enables to gather information from the organization
directly in the form of asking question and getting answers for those questions. So, we will use this
method to gather information by asking the manager of the pharmacy some basic questions
regarding the following issues will be asked during the interview: -
 How do you access Pharmacy?
 How do you get drug needed for your daily work?
 How do you know if the drug you need is available or not in Pharmacy?
 How do you generate a report and how much time does it take?
 What problems are you faced in this system?
1.10.3.3. Document Review
In order to crosscheck we use document review of different department like the operation and
maintenance department, sourcing and facility department, marketing department, fixed accesses
network department and other related workers.
10
1.11Development Tools
Software requirement for developing the project includes:
 MYSQL, PHP, HTML, JavaScript and CSS (version 3.0) and WAMP. MYSQL: -To
warehouse and manage users and schedule information on the database and access the
information at the time we need. It is platform independence, portable, have many objects
and compatible.
 PHP: - Is a server-side programming language that used to develop the website.
 HTML (version 5.0) - It is the predominant markup language for developing web pages.
 XAMMP: - It is open source software and it is an HTTP web server notable for playing a
key role in the initial growth of the WWW and the most popular web server to host and
handle HTTP request from client machines to the web server IDE .
 We also use Notepad++ sublime text and vs code as an editor MS word for documentation
and browsers like Mozilla, Firefox, chrome and internet explorer.
1.11.1. Language
To develop the system, we use HTML, CSS, and JAVASCRIPT for front-end development, PHP for
back-end development and MYSQL for the data storage.
11
1.12Testing process
Software testing can also provide an objective, to finding the error that is making the program
independent view of the software to allow the business to appreciate and understand the risks of
software implementation.
1.12.1. Unit testing
Verification or a set of operations that the software correctly implements particular function on the
smallest element of the program, which means the module will be tested alone in order to, discover
ever error in code of new system.
1.12.2. Integrate testing
Integration testing (sometimes called integration and testing) will be tested in the phase of software
testing in which individual software module will combined and tested as group. So the team planned
in this part combining all the module together and test for each other for the system functionality. If
error occurred in combine system the module with problem will be identified and re-combined .
1.12.3 System testing
After all of the above testing is checked we will test our system by other peoples and we will
conduct some comments how they get our system.
12
1.13 Tasks of the Team Members in the project
The project team composed of four members. We are solving the problem in group. Because of
decision on problem and approach are made by group agreement, which is much better than
individual decision. The table below show more detail about phase and activity. The following table
describes the role and responsibility of team organization.
PLANNING ACTIVITY RESPONSIBEL PERSON

Planning phase  Data gathering Yonas Eshetu
 List the problem
Girma Asefa
 Plan new system
Tsion Hailye
Analysis phase  Gathering Yonas Eshetu

requirement
Girma Asefa
Tsion Hailye
Design phase  UML Diagram Yonas Eshetu
Girma Asefa
Tsion Hailye
Documentation phase  Write full Yonas Eshetu

documentation for
Girma Asefa
the system using
the above phase. Tsion Hailye
Coding phase  Typing complete Yonas Eshetu

coding part of the
Girma Asefa
system
Tsion Hailye
Table 1.3 Task table
13
1.14 Time Schedule
Table 1.4Time Schedule of the Project
14
CHAPTER TWO: DESCRIPTION OF EXITING SYSTEM
2.1 Major Function of Current System
The current pharmacy system was manually base system which is almost all works on the pharmacy
organization is accomplished by papers. Among thus Medicine data search in order to buy audit and
other related works. And the other one is data security the data's can be accessed anyone who
entered to the pharmacy house as friends, other humans without the volunteer of the pharmacist.
The pharmacists work in tedious situation because of upper reasons. Not efficient on arrange
medicine on the shelf meaning arrangement method is difficult to take in mind. Also, there is a
difficulty on store the data which wastes resources as well as time to retrieve the necessary data
from the manually based data system. So generally, the existing system does not arrange medicine
in systematic way, dose not store the medicine appropriate data, security for the data is low, does not
indicate how much medicine is needed and sold quickly and efficiently.
The pharmacy management system gives services to the user as well as their own through different
functionalities. These functionalities are the followings: -
 Bought the drug
First of all, the pharmacist bought the drug from distributor of the drug for selling to the
customer. The way of bought the drug are the pharmacist sends the list of the drug you went to
bought for the distributor. Then the distributor checks the availability of the drug as well as expire
date and other information of the drug and then sell the drug for the pharmacist.
 Registering the drug
After bought the drug from distributor, the pharmacist stores the drug in the stock by using the
category of the drug, identification of the drug and uses other drug registration form.
 Sell the drug for the customer
The pharmacist sells the drug for the customer based on the restriction price of the drug. The
customer pays the cost of the drug for the cashier.
15
 Check the expire date of the drug
The pharmacist and store coordinator check the expire date of the drug in the store and stock
respectively.
2.2 Users of the current system
An existing system compromises different Users to carry out its job. Among those different actors
( Users), the most common are:
 Pharmacist
The customer comes with the ordered prescription then the pharmacist looks that order of drug and
gives the drug accordingly. The customer gets his/her requested service from the pharmacist.
 Pharmacy manager
The manager gets reports from the pharmacist, store coordinator, and cashier. The reports help the
manager to see how services are given to the client.
 Store coordinator
Store coordinator is responsible to register the drugs that buy from the private sectors or from the
governmental association, and also control the drug that are goes out to the stock.
 Cashier
The cashier receives the cost of the drug from the customer ordered by the pharmacist.
 Customer
The customer bought drug from pharmacist and pay the cost of drug to cashier
16
2.3 Drawback of the current system
Do to the manual document being used by pharmacy management system, in keeping information’s
of the drug, patient and general information of the pharmacy many drawback encountered which
includes: -
Cost
 It requires high cost in terms of resource like papers, pen and labor.
Service
 There is no customer satisfaction because the system is not easy to coordinate and takes
more time to give services i.e. searching drug, drug information.
 The existing system is not easy uncomfortable.
Work load
 There is high work load over the pharmacist or store coordinator.

Notification
 There is no notification whether the drug information(i.e. finished and expired date of
drug)
Response time
 Users were expected to come physically to view and check their profile and information
of the pharmacy.
 Takes a lot of time to came and access the required information of pharmacy.
 Take a lot of time to retrieve particular drug information.
Security and Controls
 Damage of documents due to fire or unwanted person.
 Illegal removal of forms by falsified employee leading to insecurity. Page 16
17
Efficiency
 Do to the manual operation most of the activities were wasting resources like medical
materials, money and time to produce the corresponding outputs.
 Delay in processing drug registration.
 This makes the previous system inefficient while utilizing resources.
2.4 Business rule of the current system
Every governmental and non-governmental organizations or institutions have their own rules and
policy, which used to govern all activities of the organization. So, our project organization also has
their own business rules to govern the activities in the pharmacy.
 The user who is not registered does not allowed to perform any activity to the system.
 The system does not register different drugs and users with the same ID.
 Pharmacist doesn’t sell the expired drugs.
 The pharmacist must treat customers in good manner and should address customer’s
request.
 The cashier should receive the price of medicine honestly from customers and he/she
should generate report for manager.
 Manager should control the entire activity in the stock and should receive clear and
appropriate report from the workers of the pharmacy.
 Manager should control the overall information from any biases properly.
 Forms should contain stock information appropriately.
 The manager or the owner of the pharmacy must pay the cost for the worker once per
month.
18
2.5 Paper Document in the Existing System
 Cash sales invoice form
In the existing system the pharmacist uses any paper for sending request to governmental as well as
in the non-governmental institution for bought the drug. Then the organization changes the request
of the pharmacist in to formal form and return to the pharmacist. This form is given below.
Figure 2.1. Cash sales invoice form
19
 Prescription paper
This paper brings by the customer from the hospital and gives the paper for the pharmacist. The
pharmacist analysis the paper and give the drug for the patient. This form seems like below.
Figure 2.2. Prescription paper
20
CHAPTER THREE: PROPOSED SYSTEM
3.1 Overview
The design of the pharmacy management system is computer based which will simplify the
maintenance of the information, accessible and efficient. The Pharmacy Management System will
provide the information about the end of the drugs in the medical so that the physician can order
those drugs before the end. The pharmacist will get more accurate information at the time sell,
about the details of the use of medicines and the dosages so that the system will become more
reliable to use than the present system. The records of each work will be secure as to access the
information the actor must have to provide the ID and password in the system.
By carefully analyzing and observing the problem of existing system we came up with a solution
that the current manual system should be changed in to computerized. The computerized system will
eliminate or reduce the problem on time, work load and complexity on storing drugs information.
The system will include a database for recording drugs that facilitate fast information
retrieval,modifying, inserting and deleting. It also includes an attractive user interface that facilitates
accessing the database and recording drugs easily.
The system allows the user to enter expiry date for a particular product or drug during opening stock
and sales transaction. It also involves arrival of new batches of drugs, getting information about the
drugs e.g. expiry date, number of drug type left, and location of a drug in the pharmacy. Players
represent external entities that interact with the system. They manage and perform the systems
functionality.
 Pharmacists having access to the proposed system at any time
 Improving the efficiency of the system by ensuring effective managing of services and
activities.
 Generating report.
 Reducing the employees’ workload in the organization.
21
3.2 Functional Requirement of the New System
The functional requirement is the services that are provided by the system. It also describes the
interactions between the system and the user, and any other external system.
 Manage Drug(Register,Delete ,Update price,Search and View ).
 Check Expire Date of Drug.
 Order Drug.
 Check Drug
 Generate Report .
 Manage Account (create,delete and view account).
 Active or inactive users account
 Change Password
 Generate Receipt
 Receive Comment or Feedback
 Manage Employee(Register,Delete and View)
 Manage Customer(Register,Search and View)
22
3.3 Non-functional requirement of the new system
Non-functional requirement describes user visible aspects of the system that are not designed to the
functional behavior of the system. Some of the non-functional requirements are:
3.3.1. User friendly/system interface
The system should be user-friendly interactive.
 The pharmacist can easily retrieve information in the stock.
 The skilled person interacts with the system properly.
 The customers easily understand and use the system. Page 24
3.3.2. Response time
The system should give the right response for the user as fast as possible.
3.3.3. Reliable
The pharmacy system is available based on the user needs can work properly. And do transaction
efficiently include 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 minimum
seconds. The pharmacy system is password protected to change thing on the system. Here the
pharmacist manager control over the system by login to the pharmacy system. Any user cannot use
the system but the employee of the pharmacy can see on the general properties of the pharmacy. As
result data is protected and controlled by only the administrator or manager of the pharmacy.
3.3.4 Compatible
The new proposed system should be compatible with any browsers, operating system or platform
independent of browsers. The system can be accessed everywhere at any time by using internet
connection.
23
3.3.5 Database size
The system is capable of storing huge amount of data with one database and will provide fast access
to the user according to their privilege. The database stores the permanent data for two years. After
completing the two year the data delete from the database. The usage of the database size is
comfortable for the system.
3.3.6 Security
The system should allow login to only authorized users. Any information system must be secure to
fulfill the three main components of system security which are :-
 Confidentiality
 Integrity
 Availability
Therefore, to make the system that we are going to develop secure, we are going to employ
authentication mechanism which is giving the user, username and password so that no one apart
from the authenticated user can get access to the system.
3.3.7 System modification
Through time there are always chances when the users’ needs add another additional functionality,
when the system administrator identifies the system needs to be modified, while the organizations
work style is changed and depending on different reasons. Some of the user interface and basic
modification can be performed by the collection developers but the system developers are the right
person to update the system.
3.3.8 Physical environment
The system is expected to run on network which contains a database server, client computers and
printers. The database server used to store the drug in the stock as well as in the store for the
pharmacy system user. The client computers are used to run the system and see the necessary
24
information’s that store in the database server. The printers are needed for the pharmacy employer
for printing necessary information from client computer.
3.3.9 Quality issue
To keep the quality of the system when it functions there are basic considerations determined as
requirements for reliability, user requirement, and system portability.
3.3.12 Maintenance
Before develop the system, routine maintenance activities must be prepared within the database.
Some of the required periodic maintenance activities include:
i. Preventive maintenance (backup)
ii. Corrective maintenance (recovery)
iii. Adaptive maintenance (enhancing performance, adding entities and attribute, and so on)
iv. Assignment of access permissions and their maintenance for new and old users
Maintenance requirement is involving when PMS (Pharmacy Management System) is used in

several times, there are the changes of the PMS is being request by the pharmacist. The changes
generate the system maintenance activities, which can be grouped into three types, corrective
maintenance in response to system errors, adaptive maintenance due to changes in the business
environment, perfect maintenance to enhance the system. For the PMS it may be include these three
maintenance activities which is, pharmacist want to add the module or delete the module of the PMS
application.
3.3.13 Manageability
The system administers or the manager will be responsible for taking care for system manageability
and the system is easily managed by responsible employees because everything is done online. The
overall activities are controlled by the system admin.
25
3.4 Performance Requirement
The system performs its task within a user acceptable time and space. This includes the following:-
 Response time: - depending on the strength of available network the system should be
response in short period of time.
 Storage space:-to do work efficiently the processor to be more than 2GB RAM
3.5 System Model
Used to construct an abstraction of a system that focuses on interesting aspects and ignores
irrelevant details. Our system includes three types of system model. Those are
1. Functional model (scenario, use case model)
2. Object model (class diagram)
3. Dynamic model (sequence, activity and state chart diagrams).
26
3.5.1 Scenarios
Scenario is real-life examples of how the system can be used. It should include scenario name,
flow of event, what can go wrong and how this is handled. Based on this the following scenarios
for our project are listed below.
1. Name of Scenario: login

Participating actor: - All users except customer
Flow event:-
a. The user opens the system.
b. System home page displayed to users.
c. The user click login link.
c. The login form is displayed to the user.
d. The user enters a valid username and password.
e. The System display user page.
Exceptional flow:-
If the user does not fill the correct username and password, the system notifies to enter
Correct username and password.
2. Name of Scenario: - Register drug
Participating actor: - Store-coordinator.
Flow event:-
a. The Store-coordinator open and login to the system.
b. Store-coordinator page displayed.
c. Store-coordinator select manage drug link.
d. The system Display Option.
e. Store-coordinator select register drug link.
f. Drug Registration form is displayed.
g. Store-coordinator fills the correct value to the form.
h. Click register button.
i. The system display successful message
27
Exceptional flow: - If the Users do not enter correct information in to the form, the system notifies
to enter the correct drug data.
3. Name of Scenario: - Check Expired date of drug
Participating actor: - Store-coordinator.
Flow event:-
a. The Store-coordinator open and login to the system.
b. Store-coordinator page displayed.
c. Store-coordinator click check expired date link.
d. The system displays expired drug.
e. Store-coordinator deletes expired drugs.
Exceptional flow: - No.
4. Name of Scenario: - Order drug
Participating actor: - Pharmacist.
Flow event:-
a. The Pharmacist open and login to the system.
b. Pharmacist page displayed.
c. The Pharmacist click order drug link.
d. Order drug form displayed.
e. Pharmacist enters customer id, select drug name and quantity.
f. Pharmacist click order button.
g. The system display you have successfully order message.
Exceptional flow: if he/she enters wrong data, the system displays a message to enter correct Data.
5. Name of Scenario: Active/Inactive Account

Participating actors: Admin.
Flow event:
a. Admin open and login to the system.
b. Admin page opened.
c. Admin select manage Account link.
d. Users Account displayed.
28
e. Admin click right symbol on user account.
f. Account active/inactive form displayed.
g. Admin selects 1 to activate account or 0 to inactivate account and click change button.
h. The system display successfully change status message.
Exceptional flow: if he/she enters wrong data, the system displays a message to enter correct Data.
6. Name of Scenario: Register Employee
Participating actors: Manager.
Flow event:
a. Manager open and login to the system.
b. Manager page opened.
c. Manager click manage employee link.
d. Manager select register employee link.
e. The system displays register employee form.
f. Manager fills user detail.
g. Manager Click register button.
h. The system displays successfully registered message.
Exceptional flow: if Manager enters wrong data, the system displays a message to enter correct
Data.
7. Name of Scenario: Create Account
Participating actors: Manager.
Flow event:
a. Manager open and login to the system.
b. Manager page displayed
c. Manager select manage Account link.
d. The system displays option.
e. Manager select create Account link.
f. The system displays Create Account form.
g. Manager fills user detail.
h. Manager Click create button.
i. The system displays successfully Account created message.
29
Exceptional flow: if manager enters wrong data, the system displays a message to enter correct
Data.
8. Name of Scenario: Give feedback.
Participating actor: Customer
Flow event:-
a. The customer click feedback link.
b. The form is displayed.
e. customer fills the field.
f. Click submit feedback button.
g. The system display successful message.
Exceptional flow: if the customer enters invalid data, the system notifies to enter valid data.
9. Name of scenario: - Print receipt
Participating actor: Cashier
Flow event:-
a. Cashier Login to the system.
b. Then the system displays cashier page.
c. The cashier click on fetch order link.
d. The system displays fetch order form.
e. Cashier enter customer Id and click on search button.
f. The system check the field is empty.
g. The system validate the enter data.
h. The system display sold drug with corresponding total price.
i. The cashier click cash button.
i. The cashier click print button.
Exceptional flow: if the actor enters invalid data, the system notifies to enter valid data.
30
3.5.2 Use Case Model
Use case components:
 Actor: is a person, or external system that plays a role in one or more interaction with the
system. And represented with:
Actor name
 Use case: describes a sequence of actions that provides something of measurable value to an
actor and is drawn as a horizontal ellipse.
 System boundary: indicates the scope of the system project. Anything within the box represent
functionalities in side in scope.
 Include Relationship: A part of use case which appears in the same identical form in other use
cases may be transferred to its own use case and re-integrated universally via an Include
relationship in order to avoid the redundant specification of these identical parts.
31
 Extend Relationship: If a part of the tasks is transferred from one circumstance to another,
this is modeled in its own use case. The arrow is given the stereotype "extend". The Extend
relationship points to the use case to be extended, and starts from that use case which describes
the extension's behavior.
a) Actor identification
 Login.
 Active /inactive Accouunt.
 View Account
 View user message.
 View user comment.
 Change password.
 Logout.
 Login.
 Register Employee.
 Delete Employee.
 Create Account.
 Delete Account.
 View Account.
 View Report.
 Logout.
32
 Login
 Register Customer
 View Customer
 Search Customer
 Order Drug
 Check Drug
 Logout
 Login.
 Register Drug.
 View Drug.
 Delete Drug.
 Update Price.
 Check Expire Date.
 View Feedback
 Logout.
33
 Login
 Fetch Order
 Print Receipt
 View Message
 View Comment
 Logout
 View drug
 Give feedback.
34
b) Use case Diagram
Figure 3.1 Use case diagram
35
c) Use case Description
Use Case ID UC01

Use Case Name Login
Use Case Description To authenticate users.
Actor Manager, Pharmacist, store coordinator, cashier and Admin.
Pre-Condition Users must have username and password to access the system.
Post-Condition Login to the actor page/leave from page.
Main Flow Step 1.The user open home page.

Step 2.The user clicks the login link.
Step 2.The system displays the login form that contains user name and password.
Step 3.The user fills the valid user name and password.
Step 4.The user click “login” button.
Step 5.The systems verify user name and password.
Step 6.The system display user page.
Step 7.Use case end.
Exceptional Flow A.1 The system display “invalid user name or password” message.
A.2 The user back to step [3] of basic course of action.
Table 3.1use case description for login
36
Use Case ID UC02
Use Case Name Register Employee
Use Case Description Register employees
Actor Manager
Pre-Condition No
Post-Condition Register employees information’s to database.
Main Flow Step1.The manager login to the system.

Step2.The system displays the manager page.
Step 3. Manager click manage employee link.
Step4.The system display option.
Step5. Manager select register employee link.
Step6.The system display employee registration form.
Step7. Manager fills the employee registration form.
Step 8.The system validates the entered data.
Step 7.The system displays “employee register successfully” message.
Step 8. Use case end.
Exceptional Flow A.1 The system displays “invalid data entries please try again” message.
The user resume at step [7].
Table 3.2 use case description for Register employee
37
Use Case ID UC03
Use Case Name Create Account
Use Case Description Manager to create Account
Actor Manager
Pre-Condition Manager Login to the system.
Post-Condition Manager creates Account for users.
Main Flow Step 1. Manager login to the system.

Step 2.The system displays the manager page.
Step 3.Manager click manage account link.
Step 4. The system display option.
Step 5. Manager click create account link.
Step 6.The system displays create account form.
Step 7. Manager fills the entire field space.
Step 8. Manager clicks “create” button.
Step9.The systems check the field space whether empty.
Step 10.The system validates the data you entered.
Step 11.The system displays “you are successfully creates Account”.
Step 12. Use case end.
Exceptional Flow A.1 The system displays “Please fulfill the entire information” message [at step 7].
A.2 The system displays “Incorrect data enter” message
Admin resumes at step [8].
Table 3.3 use case description for Create account
38
Use Case ID UC04
Use Case Name Active/Inactive Account
Use Case Description To active/inactive user account if necessary
Actor Admin
Pre-Condition User must have an Account
Post-Condition User Account activated or inactivated.
Main Flow Step1. Admin login to the system.

Step2.The system displays Admin page.
Step3.The Admin click “manage account “link.
Step4. The system displays users account.
Step5.Admin click right symbol.
Step6. The system displays active/inactive the account form.
Step7.Admin selects 1 to activate or select 0 to inactivate user account.
Step8. Admin click “change” button.
Step 8.The system displays “successfully change status” message.
Step9.Use case end.
Exceptional Flow No
Table 3.4 use case description for active/inactive account
39
Use Case ID UC05
Use Case Name Change Password
Use Case Description To change users Password
Actor Admin
Pre-Condition Admin must be login to the system.
Post-Condition Password of user changed and saved changes to database.
Main Flow Step 1. Admin login to the system.

Step2. The system displays Admin page.
Step3.Admin click change password link.
Step 4. The system display change password form.
Step5. Admin fills form.
Step6. Admin click “change password” button.
Step7. The system validates the entered data.
Step8.The system displays “user password changed successfully” message.
Step9.Use case end.
Exceptional Flow A.1 The system display “wrong old password” message.
A.2 The user back to step 5 of basic course of action.
Table 3.5 use case description for change password
40
Use Case ID UC06
Use Case Name View Report
Use Case Description To view report
Actor Manager
Pre-Condition Manager Login into the system
Post-Condition Manager View Reports
Main Flow Step1.The Manager login into system

Step2.The system displays manager page
Step3.The Manager clicks “view report link”.
Step4.The systems display report option.
step5. Manager select general report link.
Step6.The system display report.
Step7.Use case end.
Exceptional Flow
No
Table 3.6 use case description for View report
41
Use Case ID UC07
Use Case Name Register Customer
Use Case Description Register customer information to database
Actor Pharmacist
Pre-Condition Pharmacist must be login to the system.
Post-Condition Pharmacist register customer into the database.
Main Flow Step1. Pharmacist open and login into the system.
Step2.The system displays pharmacist page.
Step 3. Pharmacist click “manage customer” link.
Step4.The system displays option.
Step5. Pharmacist select register customer link.
Step6.The systems display customer registration form.
Step7.Pharmacist fills the form.
Step8. Pharmacist click “Submit” button.
Step9.The system displays “successfully register” message.
Step 10.Use case end.
Users resumes at step [7].
Table 3.7 use case description for Register Customer
42
Use Case ID UC08
Use Case Name Register Drug
Use Case Description Registering the new drug in to the data base.
Actor Store coordinator.
Pre-Condition Store coordinator must be login to the system.
Post-Condition Store coordinator register drug into database.
Main Flow Step 1. Store coordinator open and login into system.
Step 2.The system displays the Store coordinator page.
Step 3.Store coordinator clicks manage drug link.
Step 4.The displays option.
Step 5. Store coordinator select register drug link.
Step6.The system displays the register drug form.
Step 7. Store coordinator fills the form.
Step 8. Store coordinator clicks “Register” button.
Step9.The system display “Successfully Register” message
step 10.Use case end
Users resumes at step [7].
Table 3.8 use case description for Register drug
43
Use Case ID UC09
Use Case Name Check expire date
Use Case Description To check the drug out of date.
Actor Store coordinator
Pre-Condition Store coordinator must login in to the system.
Post-Condition To check the drug those are expired and remove it.
Main Flow Step1. Store coordinator open and login into the system.
Step2.The system displays the stock coordinator page.
Step3. Store coordinator click on check expire date link.
Step4.The systems displays expired drug.
Step5. Store coordinator clicks on “Delete” button.
Step6.The system display “Delete successfully” message.
Step7.Use case end.
Exceptional Flow A.1 The system display “there is no expire drug” message.
Table 3.9 use case description for check expire date
44
Use Case ID UC10
Use Case Name Order drugs.
Use Case Description The pharmacists order drugs.
Actor Pharmacist.
Pre-Condition Pharmacists login to the system and order the required drug.
Post-Condition Pharmacists ordered drug for sale.
Main Flow Step1. Pharmacists open and login into the system.
Step2.The the system displays Pharmacists page.
Step3.The Pharmacists clicks order link.
Step4.The system displays order form.
Step5. Pharmacists fill order form field.
Step6.Click on order button.
Step7.The system check empty filled.
Step8.The system validates the entered data.
Step9. The system display successfully ordered.
Step8.Use case end.
Exceptional Flow 1: Information Not Filled Message.
The system displays “Please fill the forms of the field!” message.
The Pharmacists resumes at step 5.
2: Invalid data.
System displays “Invalid data entries please try again” Counter resume at step 5.
Table 3.10 use case description for order drug
45
Use Case ID UC11
Use Case Name Print Receipt.
Use Case Description Give receipt for the customer.
Actor Cashier.
Pre-Condition 1. Cashier must have user name and password.

2. There must be list of drug that must be sold by the pharmacist.
Post-Condition Cashier print sold drug and give receipt for customer.
Main Flow Step1. Cashier open and login into the system.
Step2.Then the system displays cashier page.
Step3.The cashier click on fetch order drug link.
Step4.The system display form.
Step5.Enter customer Id and click on search button.
Step6.The system check the field is empty.
Step7.The system validate the enter data.

Step8.The system display sold drug with corresponding total price.
Step9.Cashier click print button.
Exceptional Flow 1. The system displays “Please fill the field!” message.
The cashier resumes at step 5.
2. The system displays “Incorrect data entry!” massage.
The cashier resumes at step 5.
Table 3.11 use case description for Print receipt
46
Use Case ID UC12
Use Case Name Logout
Use Case Description Used to leave from the page.
Actor Manager, Pharmacist, store coordinator, cashier and Admin.
Pre-Condition Users must be logged into the system.
Post-Condition The actor must be leave from the page.
Main Flow Step1.The users clicks the logout link

Step2.The users leaves the page.
Step3.Use case end.
Exceptional Flow No
Table 3.12 use case description for log out
47
3.6 Object Mode
3.6.1. Data dictionary
Data Dictionary for Account
Field Name Data type Description
Accountid Varchar Holds the account id of users.
username Varchar Holds the username of the users.
password Varchar Holds the password of the users.
User type Varchar Hold the users role.
Favorite Varchar Hold the Favorite for users.
Account status Int Holds users account status.
photo Varchar Store users photo
Table 3.13 Data Dictionary for Account
Data Dictionary for Customer

Customer id Int Holds the ID of customer.
First name Varchar Holds the First name of the customer.
Last name Varchar Holds the Last name of the customer.
Age Int Holds customer Age.
Sex Varchar Holds customer Sex.
zone Varchar Holds customer zone.
wereda Varchar Holds customer wereda.
kebele Varchar Holds customer kebele.
Table 3.14 Data Dictionary for customer
48
Data Dictionary for Drug
DrugID Int Holds the ID of drug.
Drug name Varchar Holds the name of the drug.
Company name Varchar Holds the company name of the drug.
Bach Number Varchar Hold the bach number for drug
Quantity Varchar Hold the quantity for drug.
Unit Price Int Holds unit price for drug
Shelf number date Holds shelf number for drug
Manufacture Date date Holds manufacture drug for drug
Expire Date date Holds expire date for drug
Description varchar Holds description for drug
Photo varchar Holds photo for drug
Table 3.15 Data Dictionary for Drug
Data Dictionary for Feedback

FeedbackID Int Holds the ID of feedback.
Account ID Varchar Holds account ID.
Name Varchar Holds the name .
User type Varchar Hold user type
Message body Varchar Hold message body of feedback.
Date Date Holds feedback date
Table 3.16 Data Dictionary for Feedback
49
Data Dictionary for Iboxemployee
IED Int Holds the ID of Iboxemployee.
AccountID Varchar Holds the ID of account.
Message Double Holds message.
Date Int Hold Date
Status Varchar Hold status of account
Table 3.17 Data Dictionary for Iboxemployee

Data Dictionary for Message
MessageID Int Holds the ID of message.
Name Varchar Holds the name of messge.
AccountID Int Holds the ID of account.
Usertype Varchar Hold the usertype
Message Varchar Hold message
Date Date Holds Date
Status Int Holds status of account
Table 3.18 Data Dictionary for Message
50
Data Dictionary SoldDrug
Sale number Int Holds the sale number
CustomerID Varchar Holds customer ID.
Bachnumber Int Holds Bach number of drug.
Quantity Varchar Holds quantity of drug
Date Date Hold the Date of sold drug
Status Varchar Hold status of account
Audited Varchar Hold audite of drug
Table 3.19 Data Dictionary for Report
51
3.6.2. Class diagram
We use class diagram to describe the structure of a system by showing the system's classes, their
attributes, operations (or methods), and the relationships among objects.
For designing of Class diagram, we have used UML. This diagram is the main building block of our
object-oriented modeling. The team applies it for both general conceptual modeling of the
systematic of the application, and for detailed modeling translating the models into programming
code. The classes in a class diagram represent both the main objects, interactions in the application
and the classes to be programmed. In the system, Classes are abstractions that specify the attributes
and behavior of a set of objects and Objects are entities that encapsulate state and behavior. Each
object has an identity: It can be referred individually and is distinguishable from other objects. In
mapping the diagram, we have used the following criteria:
One –to- One relationship:-here when both involved entities exchange primary keys where the
new exchanged primary keys become the new foreign keys of the tables.
One –to- many relationships:-here the primary key on the many side has been mapped to the one
side.
Many –to- many relationships:-here the primary key on the many side has been mapped to the
many side.
52
Class Diagram
Figure 3.2 Class Diagram
53
3.7 Dynamic Model
3.7.1Sequence diagram
As the name indicates, the system used sequence diagram to show sequence of activities or how
processes operate with one another and in what order. It is a construct of a Message Sequence
Chart. It shows object interactions arranged in time sequence. It depicts the objects and classes
involved in the scenario and the sequence of messages exchanged between the objects needed to
carry out the functionality of the scenario. Sequence diagrams are typically associated with use
case realizations in the Logical View of the system under development. With this diagram we show,
as parallel vertical lines (lifelines), different processes or objects that live simultaneously, and, as
horizontal arrows, the messages exchanged between them, in the order in which they occur. This
allows the specification of simple runtime scenarios in graphical manner. So the group member
lists some sequence diagrams for the system scenario are listed below
1. Login
Figure 3.3 sequence diagram for login
54
2. Register Employee
Figure 3.4 sequence diagram for Register Employee
55
3. Create Account
Figure 3.5 sequence diagram for Create Account
56
4. Delete Account
Figure 3.6 sequence diagram for Delete Account
57
5. Active/Inactive Account
Figure 3.7 sequence diagram for Active/inactive Account
58
6. Register Drug
Figure 3.8 sequence diagram for Register Drug
59
7. Check Expire Date
SS
Figure 3.9 sequence diagram for Check Expire Date
60
8. Order Drug
Figure 3.10 sequence diagram for Order Drug
61
9. Print Receipt
Figure 3.11 sequence diagram for Print Receipt
62
3.7.2Activity diagram
An activity diagram is used to understand the flow of work that an object or component performs. It
can also be used to visualize the interaction between different use cases. One of the strengths of
activity diagrams is the representation of concurrent activities. Some of the activity diagrams of our
system are listed below.
1. Login
Figure 3.12 Activity diagram for login
63
Figure 3.13 Activity diagram for Register Employee
64
3. Create Account
Figure 3.14 Activity diagram for Create Account
65
4. Active/Inactive Account
Figure 3.15 Activity diagram for Active/Inactive Account
66
5. Register Drug
Figure 3.16 Activity diagram for Register Drug
67
6. Order Drug
Figure 3.17 Activity diagram for Order Drug
68
Figure 3.18 Activity diagram for Check Expire Date
69
8. Print Receipt
Figure 3.19 Activity diagram for Print Receipt
70
3.7.3 State diagram
State chart diagram is used to describe the states of different objects in its life cycle. So the
emphasis is given on the state changes upon some internal or external events. These states of objects
are important to analyze and implement them accurately. State chart diagrams are very important for
describing the states. States can be identified as the condition of objects when a particular event
occurs. Before drawing a State chart diagram we must have clarified the following points:
 Identify important objects to be analyzed.

 Identify the states.
 Identify the events.
1. Login
Figure 3.20 State diagram for Login
71
Figure 3.21 State diagram for Register Employee
72
3. Create Account
Figure 3.22 State diagram for Create Account
73
4. Register Drug
Figure 3.20 State diagram for Create Account
Figure 3.23 State diagram for Register Drug
74
5. Order Drug
Figure 3.24 State diagram for Order Drug
75
Figure 3.25 State diagram for Check Expire Date
76
7. View Report
Figure 3.26 State diagram for View Report
77
3.7.4 User interface
Figure 3.27 User interface of Home page
78
CHAPTER FOUR: SYSTEM DESIGN
4.1. Overview of system design
System design part of the system is the transformation of the analysis model into a system design
model. Up to now, we were in the problem domain. System design is the first part to get into the
solution domain in a software development. This chapter focuses on transforming the analysis
model into the design model that takes into account the non-functional requirements and constraints
described in the problem statement and requirement analysis sections discussed earlier. This
document describes the design issues of the overall system, such as design goal, subsystem
decomposition, hardware/software mapping, and persistent data management. It provides the
complete architectural overview of the proposed system. It is intended to capture and express the
significant architectural decisions, which have been made, on the system.
4.1.1. Purpose of the system design
The purpose of designing is to show the direction how the system is built and to obtain clear and
enough information needed to drive the actual implementation of the system. It is based on
understanding of the model the software built on. The objectives of design are to model the system
with high quality. Implementing of high quality system depend on the nature of design created by
the designer. If one wants to change to the system after it has been put in to operation depends on
the quality of the system design. So if the system is design effetely, it will be easy to make changes
to it.
79
4.1.2 Design goal
The objectives of design are to model the system with high quality. The design goals are derived
from nonfunctional requirements that means non-functional requirement is the description of the
feature characteristics and attribute of the system as well as any constraints that may limit the
boundary of the proposed solution.
Design goals describe the qualities of the system that the developers should consider.
• Performance
• Dependability
• Maintenance
• End user
Performance
The system should respond fast with high throughput, i.e. it should perform the task quickly
possible as possible such as generating report and receiving, viewing project status and also
employee and material information etc. The system performs its task within a user acceptable
time and space. This includes the following:-
Response time: - depending on the strength of available network the system should be response
in short period of time.
Storage space:-to do work efficiently the processor to be more than 2GB RAM and HD storage
to be more than20MB
80
Dependability
Our system includes the following dependability criteria:-
• Reliability: AHMCPM system should be reliable.
• Fault Tolerance: - AHMCPM should be fault tolerant to loss of connectivity with the service.
• Security: -AHMCPM should be secured, i.e., not allow other users or unauthorized users to access
data that has no the right to access it.
• Availability: - as long as there is an internet connection and system failure the system will be
available 24 hours a day.
Maintainability
To be maintainable the system should meet the following maintenance criteria:-
• Modifiability: AHMCPM system should be modifiable for further modification and enhancement
of the system.
• Portability: - the system is developed to be viewed and retrieved from any web browser
regardless of their version and platform it resides in it.
• Extensibility: - if it is needed to add new functionality to the system, this must be achieved by
only making a separate page and integrate this page with the existing system.
• Readability: - the system code can be viewed by clicking on the current web page and choose
“view the source code” option.
End User Criteria
The system should have simple and understandable graphical user interface such as forms and
buttons, which have descriptive names. It should give reliable response for each user comment. All
the interfaces, forms and buttons are written or designed in a simple language or common language
so that the user can access it without any difficult.
81
4.2 Proposed system architecture
In this project, the team uses a three-tier architecture, which has three layers. These three layers are
the Application or Presentation layer, the business layer and the data access layer.Application or
presentation layer is the form, which provides the user interface to either programmer or end user.
The business layer is the class, which the team uses to write the function, which works as a mediator
to transfer data from application layer or presentation layer to data layer. This layer also has a
property layer which is a class where variables are declared corresponding to the fields of the
database which can be required for the application and make the properties so that the team can get
or set the data using these properties into the variables.The third tire is the data access layer which is
also a class to get or set data to the database queries back and forth. This layer only interacts with
the database. The database queries or stored procedures will be written here to access the data from
the database or to perform any operation to the database.
Figure 4.1 system architecture
82
4.2.1 System process
Over all system of the service depicted below.
Figure 4.2 system Process
83
4.2.2 Subsystem decomposition
To reduce the complexity of the solution domain, we decompose a system into simpler parts, called
subsystems. The main need of this portion is to design the external part of the system. In this project,
there are three sub system decompositions.
Figure 4.3 subsystem Decomposition
84
4.2.3 Hardware/software mapping
When we say hardware/software mapping for the system, it describes how subsystems are assigned
to hardware and off-the-shelf components. It also lists the issues introduced by multiple nodes and
software reuse.
In this system design mainly there are three hardware components. The client side, server side, and
database. When the team applies the system, necessary software will be loaded to each side
hardware components. Network should be installed between each side. Then each subsystem
software will be assigned and configured to the mapped hardware. Then the local area network will
be connected to the internet and the system will be functional. But now it is a design phase. The
hardware software mapping of the system is described below with a simple diagram.
Figure 4.4 Hardware/software mapping
85
4.2.4 Persistent Data management
The purpose of this section is to show the mapping of the objects/classes of the system, identified
during the analysis stage, in to the corresponding relational database.
Figure 4.5 Persistent Mapping for Admin
86
Figure 4.6 Persistent Mapping for Manager
Figure 4.7 Persistent Mapping for Pharmacist
87
Figure 4.8 Persistent Mapping for Store Coordinator
Figure 4.9 Persistent Mapping for Cashier
88
4.2.5 Component diagram
Figure 4.10 Component Diagram
89
4.2.6 Deployment diagram
Figure 4.11 Deployment Diagram
90
4.2.7 Boundary condition
Describe the start-up, shutdown, and error behavior of the system:

 System Start-up: At the time the user starts to use this system first home page will be
displayed and after this page the user can select one of the menus that he want to access.
 Login page: The login page contains the user name and password and users should enter the
correct username password and their privilege correctly to get the page that he wants.
 The User enter user name
 The User enter password
 Click ‘Login’
 Click ‘Back’ if he wants to exit
 Click ‘Clear’ button if he wants to clear the text box.
 System shutdown by the user need: When the user wants to leave the site user press logout
button.
 Error handling: The system will handle the error happen during data insertion in the
following way. If the user enters number in place of text message box will display to allow
user to enter correct data again.
91
4.2.8 Database design
Figure 4.12 Database design
92
4.2.9 Access control
No Actor Privilege
1 Admin  Login
 Active/Inactive Account
 View Account
 Change Password
 View Comment
 View user message
 logout
2 Manager  Login
 Register Employee
 Delete Employee
 View Employee
 Create Account
 View Account
 Delete Account
 View report
 View Comment
 Logout
3 Pharmacist  Login
 Register Customer
 Search Customer
 View Customer
 Order Drug
 Check Drug
 View Comment
 Logout
93
4 Store Coordinator  Login
 Register Drug
 View Drug
 Delate Drug
 Check expire Date
 Update Price
 View warning drug
 View Comment
 Log out
5 Cashier  Login
 Fetch Order
 Print Receipt
 Logout
6 Customer  View Drug

 Give Feedback
Table 4.1 Access Control
94
CHAPTER FIVE : SYSTEM IMPLEMENTATION AND TESTING
5.1 Introduction
The implementation phase is the most crucial phase in which it transform the design and analysis of
the system into a tangible system by writing the code to the system to be developed and make it
operational and applicable by testing and debugging the functionalities that are done. This phase
involves the construction of the actual project result .during this phase that the project becomes
visible to outsiders, to whom it may appear that the project has just begun. This makes the
implementation stage more essential step to develop the required system.
5.2 System Testing
The test plan is designed to analyze the logic used in the implementation of the Hospital Information
Dissemination System. The tests will allow us to ensure correct program flow, and to determine the
error-handling capability of the system.
Once coding has begun, the testing process can be beginning and proceed in parallel. As each
program module is produced, it can be tested individually, as a part of larger program, and then as a
part of larger system.
 Unit testing: Unit test is a way of testing each of the system functionality independently.
Accordingly, the team has tested each one of the major activities and the rest accompanying
activities independently using different user input, different login mechanisms and any technique
of fault finding so that an incorrect functioning of the activities was corrected at the right time.
95
 Integration Testing: Integration testing is testing in which a group of components are
combined to produce output. Also, the interaction between software and hardware is tested in
integration testing if software and hardware components have any relation.
96
 System testing: It is the final step of testing. In this system tested the entire system as a whole
with all forms, code, modules. In this we tested all the functionalities in the System. All errors in
the forms, functions, modules have been tested. Finally, System testing ensures that the entire
integrated software system meets the desired requirements. It tests a configuration to ensure
known and predictable results.
Tested from Test case Expected result Actual result
Login form To validate the proper To authenticate user will be authenticated

functionality of login user and if user is authorized
by inserting username enter to the system else
and password confirm invalidity
Search To validate the Search result If the requested record

functionality of search exist display the result
form else if it doesn’t exist
display the message about
the status
Report from To validate the To generate generate the requested

functionality of report report report if the request is
form valid, if request is invalid
display message that
describes the invalidity
All forms To validate the To provide the The form is presented and
functionality of each required the required function can
form function by the operated using the form
form
Table 5.1 System test
97
5.3 System Implimentation
How Store coordinator manage drug ?
1. Open Home Page
Figure 5.1 User interface for home page

2. Click Login link , fill form and click on login button
Figure 5.2 User interface for login form
98
3. Display Store Coordinator Page
Figure 5.3 User interface for Store coordinator page
4. Click Manage drug link ,select register drug link and fill form and click
register button
Figure 5.4 User interface for Register drug form
99
5. For View Drug first Click manage drug link and select view drug.
Figure5.5 User interface for View drug

6. Click Check Expire Date link and Delete Expired drug
Figure 5.6 User interface for Check Expire Date
100
CHAPTER SIX :CONCLUSION AND RECOMANDATION
6.1 Conclusion
As we have described above this system focus on the Adama Hospital Mediical Collage Pharmacy
Management System. The main reason that initiated us to develop this system is to keep the track of
information about the execution of pharmacy management and minimize time cosubtion of service.
In this system we have add some requirements that are not described on the scope before. Now we
have come to the end of the system development by correcting any type of problems that are
occurred in the system doing period. it is time to summarize the work done.
In the first chapter we have introduced the whole project process. In the second chapter we have
dealt with the existing system, current systems and the problems in the existing system. In the third
chapter we analyzed the proposed system. We modeled the new system using different object
oriented modeling techniques such as use case diagram, activity diagram, class diagram, state
diagram, and sequence diagram. In chapter four we designed the system, system Architecture and
others, design goals, proposed system and sub system decomposition using the design modeling
diagrams such as, component diagram, deployment diagram, hardware and software mapping and
database design
6.2 Recommendation
Even if we achieved to avoid some of the main problems that are appear in the current system,
there are a lot of functionalities that can be added that we couldn’t include in our system because
of time shortage and other factors. Our project couldn't be able to include :-
 Payroll system and employee attendance.

 Electronic prescription and Language translation
 Paymement performed through olin banking system and other payment ways.So we
recommended that the next developers to include these things and to develop mobile application
for this AHMCPMS.
To deploy our system there should be Applicationserver,Webserver,Internate conectivity and other.
101
Reference
1. Bernd Bruegge and Allen H. Dutoit Object-Oriented-Software Engineering.

2. [Online] 2016 http://www.pharmacy-management-system-requirement analysis-and-
elicitation-document.
3. https://www.google.co.uk/search?sclient=psyab&site=&source=hp&btnG=Search&q=deplo
yement+diagram.
4. Lethbridge, TimothyC.
Object_Oriented_Software_Engineering__Practical_Software_Development_using_UML_a
nd_Java hal 56.
5. Navathe, Elmasri Fundamentals of Database System 6th edition.
6. www.google.com
102
APPENDIX
The important code part of our system is users login because in order to use the system the users
must be login to the system and use the system.
A. Sample code for login
<?php
include("conn.php");
if(isset($_POST['btn-login']))
$username = $_POST['username'];
$password = clean($_POST['password']);
$qry="SELECT* FROM account WHERE username='$username' AND password='$password'";
$result=mysql_query($qry,$conn1);
if($result)
if(mysql_num_rows($result) > 0) {
while ($row = mysql_fetch_array($result) ) {
$un=$row['username'];
$pa=$row['password'];
$user= $row['usertype'];
$uname = $row['UserName'];
$status= $row['account_status'];
xii
$sta= $row['photo'];
$acc= $row['accountid'];
if($status!='0') {
if($user== administrator)
session_start();
$_SESSION['SESS_FIRST_photo'] =$sta; $_SESSION['SESS_MEMBER_ID'] = $un;
$_SESSION['SESS_FIRST_NAME'] = $pa; session_write_close();
echo "<script>window.location='admin/admin.php';</script>";
exit();
else if($user== manager)
session_start();
$_SESSION['SESS_FIRST_photo'] =
$sta;$_SESSION['SESS_MEMBER_ID'] = $un;
$_SESSION['SESS_FIRST_NAME'] = $pa;
session_write_close();
echo "<script>window.location='manager.php';</script>";
exit(); }
xiii
else if($user== storecoordinator){
session_start();
$_SESSION['SESS_FIRST_ACC'] =$acc; $_SESSION['SESS_FIRST_photo'] =$sta;
$_SESSION['SESS_MEMBER_ID'] = $un; $_SESSION['SESS_FIRST_NAME'] = $pa;
session_write_close();echo "<script> window.location='storecoordinatorB.php';</script>";
exit(); }
else if($user== pharmacist){
session_start();
$_SESSION['SESS_FIRST_photo'] =$sta; $_SESSION['SESS_MEMBER_ID'] = $un;
$_SESSION['SESS_FIRST_NAME']=$pa;
echo "<script>window.location='pharmacist.php';</script>";
exit();
else if($user== cashier){
session_start();
$_SESSION['SESS_FIRST_photo'] =$sta;
$_SESSION['SESS_MEMBER_ID'] = $un; $_SESSION['SESS_FIRST_NAME'] = $pa;
echo "<script>window.location='cashier.php';</script>";
exit(); }
xiv
else{ ?>
<script> alert('YOUR USER NAME AND PASSWORD IS NOT MATCH WITH YOUR
ROLE Tray again'); window.location='newlogin.php'; </script>
<?php
}}
else {
?>
<script> alert('Your account is disabled Please Contact the Administrator!!! and Tray again');
window.location='newlogin.php';
</script>
<?php
}}
else{
?>
<script>
alert('Incorrect USER NAME or PASSWORD Pls match and Try again ');
window.location='newlogin.php';
</script>
<?php
} }}?>
B. Sample code for Register drug
xv
<?php
if(isset($_POST['register']))
$dname=$_POST['dname'];
$cname=$_POST['cname'];
$bnumber=$_POST['bnumber'];
$quantity=$_POST['quantity'];
$unitprice=$_POST['price'];
$shelfno=$_POST['shelfno'];
$mndate=$_POST['mdate'];
$exdate=$_POST['edate'];
$disc_drug=$_POST['disc'];
$mda= date("Y-m-d");
$photo=$_POST['photo'];
if ($mndate>=$exdate) {
echo "<font color='red'>manufacture date is <font color='green'>$mndate </font>greter than
expirydate or equal <font color='green'>$exdate</font>!! </font>";
echo' <meta content="10;registerdru.php" http-equiv="refresh" />';
else if($mndate>=$mda)
xvi
echo "<font color='red'> The manufacture date is <font color='green'>$mndate </font> greter
than this day <font color='green'>$mda </font>!!</font>";
else if ($exdate<=$mda) {
echo "<font color='red'> This drug allredy expiered <font color='green'>$exdate </font> and
this day is<font color='green'>$mda </font>!!</font>";
else{
$res=mysql_query("INSERTvalues(INTO drug '$dname','$cname','$bnumber', '$quantity',
'$unitprice', '$shelfno', '$mndate', '$exdate','$disc_drug','$photo')",$conn1);
if(!$res)
echo"<font color='green'><p class='wrong'>The drug allredy registered !!!</p></font>";
else
echo"<font color='green'><p class='right'>You have succefully registered the drug
!!!</p></font>";
xvii
}}}
mysql_close($conn1);
?>
C. Check expired date of drug.
<form id="form1" name="submit" method="POST" action="expier_date.php">
<?php
include('conn.php');
$result="SELECT * FROM drug where drug.expirydate <= DATE(now()) AND drug.expirydate
<= DATE_ADD (DATE(now()), INTERVAL 0 WEEK)";
$res=mysql_query($result,$conn1);
$resul ="SELECT * FROM drug where drug.expirydate >= DATE(now()) AND
drug.expirydate <= DATE_ADD(DATE(now()), INTERVAL 1 WEEK)";
$re=mysql_query($resul,$conn1);
if(mysql_num_rows($res)>0)
echo "<table id='vtable' style='width:700px;border:0px solid #336699;border-radius:10px;'
align='center'><font color=white>";
echo "<tr color 'red'>";
echo "<th height='40'><font color='red'>Drug-Name</font></th>";
echo "<th height='40'><font color='red'>Company-Name</font></th>";
xviii
echo "<th height='40'><font color='red'>Bach-Number</font></th>";
echo "<th height='40'><font color='red'>Quantity</font></th>";
echo "<th height='40'><font color='red'>Shelf-No</font></th>";
echo "<th height='40'><font color='red'>Expiry_Date</font></th>";
echo "<th height='40'><font color='red'>photo</font></th>";
echo "<th height='40'><font color='red'>Delete</font></th>";
echo "</tr>";
while($row = mysql_fetch_array($res))
echo "<tr color='red'>";
echo "<td>" . $row['drugname'] . "</td>";
echo "<td>" . $row['companyname'] . "</td>";
echo "<td>" . $row['bachnumber'] . "</td>";
echo "<td>" . $row['quantity'] . "</td>";
echo "<td>" . $row['shelfnumber'] . "</td>";
echo"<td>" . $row['expirydate'] . "</td>";
echo "<td>"."<img alt='profile photo' src='images/".$row['photo']."' width='60'
height='50'"."</td>";
echo"<td> <a href=delete.php?id=".$row['bachnumber']."><font size='4px'><input
type='submit' value='Delet' name='submit' ></font></a></td>";
echo"</tr>";
xix
}
echo "</table>";
else{
echo '<center>';
echo '<font face="monotype corsiva" size="5"color="red">expired drug not found !!</font>';
echo '</center>';
mysql_close($conn1);
?>
</form>
Questioners
1. How the pharmacist Generate report of Drug and Drug related activities worked in the
pharmacy?
2. What is the hierarchy of the Drug management?
3. How the tasks included in the pharmacy is performed?
4. What are the main activities performed in pharmacy management?
5. What are main responsible personnel’s in pharmacy management?
xx

Harambee University

Uploaded by

Copyright:

Available Formats

Harambee University

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Harambee University

Uploaded by

Copyright:

Available Formats

HARAMBEE UNIVERSITY

DEPARTMENT OF COMPUTER SCIENCE

1. TSION HAILYE 8005

2. YONAS ESHETU 8011

3. GIRMA ASEFA 8027

ADVISOR: SENIOR INSTRUCTOR ABERA G/TSADIK (M.SC).

July, 2022 G.C

Tsion Hailye ……………………………….

Yonas Eshetu ……………………………….

Girma Asefa ……………………………….

Project title: -web based pharmacy management system.

Name of advisor Signature

Examining committee members signature Date

Examiner 1 ____________ ____________ __________

Examiner 2 ____________ ____________ __________

Examiner 3 ____________ ____________ ___________

Examiner 4 ____________ ____________ ___________

Examiner 5 ____________ ____________ ___________

the college of the university.

Thanks Again To All Who Helped Us .

 AHMCPMS:-Adama Hospital and Medical College PharmacyManagement

DEFINITIONS OF TERMS .................................................................................................................ii

ABBREVIATION AND ACRONYMS ..............................................................................................iii

LIST OF TABLES ............................................................................................................................ viii

LIST FIGURES ................................................................................................................................... ix

CHAPTER ONE: INTRODUCTION AND BACKGROUND ............................................................1

1.1 Introduction ............................................................................................................................. 1

1.2 Background of Organization ................................................................................................... 2

1.3 Statement of the problem ........................................................................................................ 3

1.4 Purpose of the proposed system .............................................................................................. 3

1.5 Team Composition .................................................................................................................. 4

1.6 Objectives of the project ..........................................................................................................4

1.6.1 General objective .......................................................................................................... 4

1.6.2 Specific objectives ........................................................................................................ 4

1.7 Feasibility study ...................................................................................................................... 5

1.7.1 Economic Feasibility (Cost Benefit Analysis) ..............................................................5

1.7.2 Technical feasibility ......................................................................................................6

1.7.3 Operational feasibility ...................................................................................................6

1.8 Scope and Limitations of the project .......................................................................................7

1.8.1 Scope .............................................................................................................................7

1.8.2 Limitation ......................................................................................................................7

1.9 Significance of the project .......................................................................................................8

1.10.1 System Development Approach ..................................................................................8

1.10.2. Software Process Model Approach ............................................................................9

1.10.3. Data Collection Methods ......................................................................................... 10

1.11 Development Tools ............................................................................................................. 11

1.11.1. Language ..................................................................................................................11

1.12 Testing process .................................................................................................................... 12

1.12.1. Unit testing ...............................................................................................................12

1.12.2. Integrate testing ........................................................................................................12

1.12.3 System testing ........................................................................................................... 12

1.13 Tasks of the Team Members in the project ......................................................................... 13

1.14 Time Schedule .....................................................................................................................14

CHAPTER TWO: DESCRIPTION OF EXITING SYSTEM ............................................................15

2.1 Major Function of Current System ........................................................................................15

2.2 Users of the current system ................................................................................................... 16

2.3 Drawback of the current system ............................................................................................17

2.4 Business rule of the current system .......................................................................................18

2.5 Paper Document in the Existing System ............................................................................... 19

Examiner 1 __

Examiner 2 __

Examiner 3 __ _

Examiner 4 __ _

Examiner 5 __ _