mwu

School of informatics
Industrial project one
Pharmacy management system

Contents
chapter one introduction ............................................................................................................... 7
1.1 Introduction.....................................................................................................................................7
1.2 Background......................................................................................................................................8
1.3 Statement of problem and justification of the system.....................................................................9
1.4 Description of the existing system.................................................................................................10
1.4.1 Introduction of existing system..............................................................................................10
1.4.2 Main function of existing system...........................................................................................10
1.4.3 Actors of existing system............................................................................................................11
1.4.4 Limitation of existing system..................................................................................................11
1.5 Objective........................................................................................................................................12
1.5.1 General objective...................................................................................................................12
1.5.2 Specific objectives......................................................................................................................12
1.6 Scope of the project.......................................................................................................................12
1.6.1 Limitation...............................................................................................................................13
1.7 Methodology and Tools.................................................................................................................13
1.7.1 Methodology.........................................................................................................................13
1.7.1.1 Data source and data collection method...............................................................................13
1.7.1.2 System analysis and design methods (SADM)........................................................................14
1.7.1.3 Implementation method............................................................................................................14
1.7.2 Tools.......................................................................................................................................15
1.8 Budget...........................................................................................................................................15
1.9 Time line........................................................................................................................................16

chapter two Requirement Analysis.............................................................................................17

2 Requirement Analysis........................................................................................................................17
2.1 Requirement..................................................................................................................................17
2.1.1 Functional requirement.................................................................................................................17
2.1.2 Non functional requirement...........................................................................................................17
2.2 Use case ............................................................................................................................................17
2.2.1 Actor description.......................................................................................................................19
2.2.2 Use case description..................................................................................................................20
2.3 Sequence Diagrams.......................................................................................................................25
2.4 Activity diagram.............................................................................................................................29
2.5 State chart diagrams......................................................................................................................32
2.6 Class diagram.................................................................................................................................35

chapter three Design analysis.......................................................................................................37

3 Design analysis...................................................................................................................................37
3.1 Introduction...................................................................................................................................37
3.2 Purpose..........................................................................................................................................37
3.3 Software architecture....................................................................................................................38
3.4 Subsystem......................................................................................................................................39
3.5 Database design.............................................................................................................................40
3.5.1 Database table...........................................................................................................................40
3.5.2 Database schema.......................................................................................................................43
3.5.3 ER Representation.....................................................................................................................44
3.6 User interface................................................................................................................................45
3.6.1 interface ....................................................................................................................................45
3.6.2 sample user interface................................................................................................................46
Reference..................................................................................................................................................50

2
List of tables

Table 1.1:- drug Requisition format...........................................................................................................10

Table 1.2:- Dispensary stock balance format.............................................................................................11

Table 1.3 budget estimation......................................................................................................................15

Table 1.4 time schedule table....................................................................................................................16

Table 2.1 :- Actor description.....................................................................................................................19

Table 2.2 :- use case description for record drug.......................................................................................20

Table 2.3 :- use case description for update data......................................................................................20

Table 2.4 :- use case description for assign cost.........................................................................................21

Table 2.5 :- use case description for drug arrangement.............................................................................21

Table 2.6 :- use case description for Check requisition..............................................................................22

Table 2.7 :- use case description for Check expired date...........................................................................22

Table 2.8 :- use case description for Check expired date by pharmacist....................................................23

Table 2.9 :- use case description for Check presence of drug....................................................................23

Table 2.10 :- use case description for Requisition of drug.........................................................................24

Table 2.11 :- use case description for Prescription.....................................................................................24

3
Table 2.12 :- use case description for Receive cost....................................................................................25

Table 3.1 drug table...................................................................................................................................40

Table 3.2 Employee table...........................................................................................................................40

Table 3.3 Pharmacist table.........................................................................................................................41

Table 3.4 manager table............................................................................................................................41

Table 3.5 casher table................................................................................................................................41

Table 3.6 patient table...............................................................................................................................41

Table 3.7 Requisition table.........................................................................................................................42

Table 3.8 category table.............................................................................................................................42

Table 3.9 supplier table..............................................................................................................................42

Table 3.10 Pharmacist table.......................................................................................................................42

Table 3.11 glossary....................................................................................................................................49

List of figure
Fig 1.1 gun chart representation of time line.............................................................................................16

Fig 2.1 use case diagram............................................................................................................................19

Fig 2.2 Sequence diagram of patient interaction.......................................................................................26

Fig. 2.3 Sequence diagram of store manager.............................................................................................27

Fig. 2.4 Sequence diagram of pharmacist..................................................................................................28

Fig 2.5 activity diagram of pharmacy and casher.......................................................................................30

Fig 2.6 activity diagram of pharmacist to store manager...........................................................................31

Fig 2.7 state chart of patient registration...................................................................................................33

Fig 2.9 state chart of pharmacist...............................................................................................................34

Fig 3.1 software architecture.....................................................................................................................38

Fig 3.1 subsystem of the system................................................................................................................39

Fig 3.2 database schema............................................................................................................................43

4
Fig 3.3 ER representation...........................................................................................................................44

Fig 3.4 interface diagram...........................................................................................................................45

Fig 3.5 Login form......................................................................................................................................46

Fig 3.6 External interface for sore manager...............................................................................................46

Fig 3.7 External interface for recording drug.............................................................................................47

Fig 3.8 External interface for pharmacist...................................................................................................48

Fig 3.9 External interface for record patient information..........................................................................48

5
 Acknowledgment

I would like to express my gratitude to my advisor Elias .J for his guidance,

support and his continuous enthusiasm and encouragement throughout the
project. We are also thanks for all workers and managers of Red Cross society
pharmacy hawassa branch.

Finally many thanks to friends, who have helped and give suggestions,
supports and correction throughout project.

6
Chapter one introduction
1.1 Introduction

Most of the pharmacies nowadays, like to use file system because it is a traditional way. But
today, the technology has changes a lot and because of that almost all the application in the
world use computer as their stored information place. More recently, the pharmacy
management system is focused on storing stock information such as types of medicines,
price, medication review and drug information. Most pharmacy now day use Manual
recording system. This system has many disadvantages because the pharmacist always
busy with the sales transaction rather than managing the patient who comes to the
pharmacy.

Modern healthcare establishments demand speed and accuracy pharmacy management

system provides the advantage in the form of improved and efficient workflow for the
pharmacy department. The deployment of the system results in an efficient workflow with
quick patient turnaround.

This project “pharmacy management system” is a solution to problems on pharmacy

management specially focused on Red Cross society pharmacy hawassa branch. This
system is aimed to; simplify the interaction of management and workers of the pharmacy,
proper drug store management, give active services to the patient, create attractive working
environment. The system also registers drug and their product and expire date in their
category. And identify drugs which are expired.

The key benefit of pharmacy management system automating processes To improve the
appearance or efficiency of; modernize work flow and enhancing customer base are
attractive enough to draw retail pharmacy chains competing in world of growing challenge.

This project is a widow-based project that is implemented by C# and DBMS.

7
 1.2 Background

The Ethiopian Red Cross Society (ERCS) was established by government decree on 8 July
1935, in the aftermath of the second Ethio-Italian war (1935-1941). Within a few months of
its establishment, the ERCS began its involvement in humanitarian services by training and
deploying 300 first aiders and 6 ambulances to various war fronts to care for the wounded.

There were serious concerns among friendly European countries that due to poor medical
preparation by Ethiopia and the superiority of the Italian’s warfare equipment. There was
concern about the large number of wounded Ethiopian soldiers in need of medical assistance
and the lack of basic first aid services. The only country that eventually volunteered to
provide emergency field medical assistance was Russia. Due to local initiatives and foreign
concerns, the Ethiopian Red Cross Society was established on 8 July 1935 in Addis Ababa.
The first President of the Ethiopian Red Cross Society was Blattengeta Herouy Wolde Selassie
and Dr. Lambie was elected as the first Secretary-General. The Vice-Presidents were Dr.
Hanner from Sweden and Mr. Abel from Austria. The Ethiopian Red Cross Society was
officially recognized as a member of the League of Red Cross Societies, now known as the
International Federation of Red Cross and Red Crescent Societies, on 25 September 1935.

In early 1988 the ERCS and the Danish Refugee Council (DRC) initiated a project with the
technical assistance from the MOH of Ethiopia and the WHO for provision of essential drugs
and presented it to Danish International Development Agency (DANIDA). In June 1989 the
ERCS and the DRC agreed to launch the Essential Drugs Project/Program over 5-year period
in two phases .The aim was to establish 20 pharmacies and 20 satellite pharmacies at project
cost of Birr 13,700,000. The ERCS was made responsible for the physical implementation of
the project and the DRC was committed for the financial contributions and technical
supports.

Hawassa Red Cross society pharmacy is one of the branches of Ethiopian Red Cross Society
(ERCS) pharmacy Established in 1991E.C. aim of the pharmacy is providing drugs to the
society in low cost and supply drug in nearest area to the society.

8
 1.3 Statement of problem and justification of the system

In the existing system, there are different types of problems like absence of integrated data
i.e. the data related to the drug and the pharmacy management is not integrated. Lack of
proper asset management i.e. it is hard to know what type, where and how the drugs are
stored. This usually led to mistakes and under-order, also searching and retrieval of
information is time consuming and over load on pharmacist is increased in the pharmacy,
less interaction between store management and other employs, lack of human power, Loss of
great effort , resource, cost and lack of flexibility are some of the problems that are exist in
the pharmacy now.
Generally existing problems are:-
 The task was performed manually.
 There is no well arrangement of drugs.
 It’s difficult to know the expired date of drugs.
 It is difficult to manage the exact place of the drug on the shelf.
 absence of centralized drug management system

Because of these problems we initiated to develop pharmacy management system software

for the pharmacy. The new system we are trying to solve the problems by retrieving the
needed information from the pharmacy management system; this reduced unnecessary cost,
create attractive working environment, reduce work load of the pharmacist, reject drug
arrangement or order problem.

1.4 Description of the existing system

1.4.1 Introduction of existing system

The existing system of Red Cross society pharmacy of hawassa branch is use the manual
system to control pharmacy activity, satisfy patient need and make easy drug management

9
and arrangement with their limitation. The system is applicable in different process of
pharmacy; such as store management, selling processes, drug management and
arrangement.

1.4.2 Main function of existing system

 Store management:-in the store drugs are recorded and check expired date and
store until transfers to dispensary. When drug is transfer to dispensary register
amount of drugs and types of drug. And also costs of each drug are calculated.
 Drug arrangement:-drug is arranged based on their types like; antibiotic, fungi,
gastric etc…
This support easy to find out the needed drugs and easy to identify types. This
facilitates communication or interaction with user.
 Selling process:-pharmacist read patient prescription paper and identify drug then
check presence of drug. If drug is not present pharmacist locate the patient to other
pharmacy. Else, calculate the cost of the drug. Patient pay cost to casher and cashers
register in cash register machine. Patient receive recite and back to the pharmacist
and show recite then get drugs.
 With the service of the system in dispensaries if drug is finished pharmacist full the
store requisition form and send to store manager. Store manager receive requisition
form and check presence of drug and send drug to dispensaries.
Store requisition format
Date: ________/__________/____
To: ____________________________
From: _________________________
Please supply as with the following item
No Item Stock No unit
1
2
3

Requested By: _______________________

Authorized By: ______________________
Approved By: _______________________
Table 1.1:- drug Requisition format

The store management also calculates the cost of each drug send to dispensaries with the
following format:

Dispensary stock balance for the months

Code descript Expire date Unit tab Unit cost per Retail prices

10
 1
2
3

Table 1.2:- Dispensary stock balance format

1.4.3 Actors of existing system

The main actors of the existing system are:-

 Pharmacist: - who sell and consult the patient with more license than druggist.
 Druggist: - the same action and work with pharmacist
 Manager:-manage the all activity of pharmacy
 Cashier: - who receive drug price from the patient
 Patient:-as a user patient is one of actors of the system.

1.4.4 Limitation of existing system

There are different failures or weakness in existing system from them these are as
follows:-
 Unable to give fast service for customers of the Pharmacy.
 absence of centralized drug management system
 They have no computerized Pharmacy system.
 It’s difficult to know the expired date of drugs.
 It’s difficult to know the left quantity of drug.
 It is time taking to process Drug information
 It is difficult to manage and getting quick information about exact place of the drug
on the shelf.
 They use manual system for handling of Drug information.

1.5 Objective

1.5.1 General objective

A general objective of the project is developing good pharmacy management system for Red
Cross society pharmacy hawassa branch. In order to create:-

 Organized and centralized store management, drug management and arrangement.

 Makes pharmacy computerized and competitive to other pharmacy.

11
 1.5.2 Specific objectives

 To minimize time and efforts needed to perform the tasks in the pharmacy.
 Make tasks simple and efficient in every aspect as much as possible.
 To give sufficient drug delivery system for the patient
 To know easily the expired drug.
 To arrange the type of drug based on pharmacological action on the shelf.
 To provide quick information on the drug and its description and easy access on
search.
 To minimize human errors in medication safety.
 To facilitate accessibility of drug information and information management among
pharmacy employees.
 To provide optimal drugs inventory management by monitoring the drugs’
movement in the pharmacy.

1.6 Scope of the project

 Microsoft office
 It enables the operation of database such as insertion, deletion, updating and
searching.
 Enables to identify expired drug.
 Allows authorized user /personnel to update the database.
 Enables to identify less quantity drug.
 Enables to identify the position of the drug on the shelf.
 Will have access to see the drug cost.
 The system is functional in English language for their operation.

Generally we come up with this project to implement a new pharmacy management system
which can perform the entire specified task to the pharmacy with minimum time, effort and
resources. In addition great efficiency, accuracy and security of the data is approved.

1.6.1 Limitation
The proposed system is limited on the following aspects:-

 System is not support other language rather than English language.

 Users must have some skill about the system.
 Only focused on pharmacy management.

12
 1.7 Methodology and Tools

1.7.1 Methodology

1.7.1.1 Data source and data collection method

There are many different methods and techniques were used to gather data this related to
Pharmacy Management System (PMS) For Red Cross society pharmacy hawassa branch. For
this system, there we are used various techniques which used to collect data and information
such as Interview, Observation and Document review.

 Interviewing users and employee of the pharmacy:-

We interview Pharmacist, druggist and manager of pharmacy in order to get reliable
information about the pharmacy. We are also review the documents
 Observation: - we get some information about the process of pharmacy such as
arrangement of the drug, some work flow of the pharmacy, activity of the
pharmacist and casher.
 Document review: - we review some documents used by pharmacy to collect data
and to get a better Understanding about the existing system.

1.7.1.2 System analysis and design methods (SADM)

For this pharmacy management system, SADM is chosen as object oriented approach. We
used waterfall model for SADM in this system development life-cycle. Such as:-

 planning
 Requirements:-in requirement phase we use flowchart and use case.
 Flowchart-use flow chart to show the work flow of requirement.
 use case- A use case models an interaction between the Information
system itself and the users of that Information system (actors)
 Analysis:-use class diagram, Use Case and Scenario, state chart and sequence
diagram.
 Design:-we use UML class diagram.
 Implementation

13
  Testing
 Maintenance

For analysis and getting the needed information to develop this project we have planned to
use an object oriented approach. We choose this approach because of the following
advantages:

 Increased reusability: object oriented support reusability of system.

 Increased extensibility: to add and change the existing module without affecting the
rest of the program
 Improved quality: introduces user participation which improves quality of the
project
 Improved chance of project success: since object oriented approach has good
documentation
 It reduce maintenance cost

1.7.1.3 Implementation method

The purpose of this method is to convert the human understanding form to computer
understanding form. That means code the document by using appropriate programming
language. In order to our project we use c# and SQL as programming language documents.
These activities include: - Coding, testing and installation.

We prepare user interface, so that it will be implemented through that interface .The system
will be implemented by using Window operating system.

1.7.2 Tools
Development tools for our project are use hard ware and soft ware requirement.

We use hard ware requirement like:-

 Printer
 Personal Computer,
 CD(RW),
 Flash.

We use the software requirements like:-

 Microsoft office
 SQL database.
 C#.
 Internet.

14
  Edraw Max

1.8 Budget
The budget we use to develop this is system is only depending on the requirement needed
for the project even though difficult to determine the budget. To complete the project we
are going to utilize the following resource.

Budget estimation table

No Material Unit price(birr) Quantity Total cost(birr)

1 Flash(8GB) 200 2 400
2 CD(RW) 25 4 100
3 Photo copy 0.50 50page 25
4 Printing 1 60page 60
5 Transportation 10 10 times 100
6 Internet 300
7 Paper 90 1 90
TOTAL COST 1075.00

Table 1.3 budget estimation

1.9 Time line

Time line is the time that we schedule to complete project from initial to final.

No Task Name Duration Starting date Finishing Date

1 Project planning 1W Tue 12/25/12 Mon 12/31/12
2 Requirements analysis 1W Tue 1/1/13 Mon 1/7/13
3 Design 2W Tue 1/8/13 Mon 1/21/13
4 Implementation 8W Tue 1/22/13 Mon 3/18/13
5 Testing 10W Tue 1/29/13 Mon 4/8/13

Table 1.4 time schedule table

W1 W2 W3 W4 W W W W W W W W W W
5 7 9 10 14
6 8 11 12 13

15
1 Project planning

2 Requirements analysis

3 Design
4 Implementation

5 Test

Fig 1.1 gun chart representation of time line

Chapter two Requirement Analysis

2 Requirement Analysis

2.1 Requirement

2.1.1 Functional requirement

Functional requirement is describes what a system does or is expected to do .it is referred
to as functionality.

The main functional requirement for our RCS pharmacy management system is as follow:-

 Record drug with their product date, expired date, amount and cost.
 Update, delete and insert drug.
 Check expired date and presence of drug.
 Register patient with their information.
 Generate requisition.

16
 2.1.2 Non functional requirement
Non functional requirement are that describes aspects of the system that are concerned
with how well it provides the functional requirements.

Our system includes the following aspects as non functional requirement.

 Performance:-our system has good performance in response time for updating and
retrieving drug information.
 Security: - system is secured because all users are has their own privilege to access
the system.
 Throughput:- is the volume of data that system handled. our system is handle large
volume of data.
 Reliability: - system is reliable in all process.

2.2 Use case

17
18
2.2.1 Actor description

Actor Description

Store manager The manager works on store and responsible for record
drug with their information, such as name of drug, expired
date, product date, amount, cost of drug. And also send drug
to the dispensary according to requisition form received
from pharmacist. The manager has responsibility to update
drug database.

Pharmacist Pharmacist Who works on dispensary. Who read patient

prescription and identify drug name then check presence of
drug, expired date, cost of drug and identify the position of
drug. Pharmacist also sends drug requisition form to store
manager.

Casher Receive cost from patient that is calculated by pharmacist

and print receipt.

Patient
Patient Who use pharmacy.

19
 Table 2.1 :- Actor description

2.2.2 Use case description

Use case Record drug

Actor Store manager

Description Record drug with their information, such as name of

drug, expired date, product date, amount of drug.

Precondition Manager must have privilege to record data that

means manager must use username and password.

Post condition Drugs are recorded with their full information in

database.

Main path 1. Login to the manager user interface.

2. Select insert button.
3. Insert drugs with their information.

Table 2.2 :- use case description for record drug

Use case Updating data

Actor Store manager
Description Update or modify the existing data in the
database.
Precondition Managers have to use username and

20
 password.

Post condition Modified existing data information.

Main path 1. Login to the manager user interface.
2. Select update button
3. Update.

Table 2.3 :- use case description for update data

21
Use case Assign cost
Actor Store manager
Description Assign cost to the drug.
Precondition Managers have to use username and
password.

Post condition Costs of the each drug are included in

database.
Main path 1. Calculate cost of the drug.
2. Login to the manager user interface.
3. Select insert button.
4. Assign cost of the drug.

Table 2.4 :- use case description for assign cost

Use case Drug arrangement

Actor Store manager

Description Assign drug position.

Precondition Managers have to use username and

password.

Post condition
Position of drug is assigned.
1. Login to the manager user interface.
Main path 2. Select insert button.
3. Insert shelf position.

Table 2.5 :- use case description for drug arrangement

22
Use case Check requisition
Actor Store manager
Description Read requisition form send from pharmacist.
Precondition Managers have to use username and
password.

Post condition Requisition is checked.

Main path 1. Login to the manager user interface.
2. Select check button.
3. Read form.

Table 2.6 :- use case description for Check requisition

Use case Check expired date

Actor Store manager
Description Identify expired drug.
 Managers have to use username and
Precondition password.
 Drugs is must be recorded.

Post condition Expired drug is identified.

1. Login to the manager user interface.
2. Select exp. button.
Main path

Table 2.7 :- use case description for Check expired date

Use case Check expired date

Actor pharmacist
Description Identify expired drug.

23
Precondition  Pharmacist has to use username and
password.
 Drugs is must be recorded.

Post condition Expired drug is identified.

Main path 1. Login to the pharmacist user interface.
2. Insert drug name.
3. Select ok button.

Table 2.8 :- use case description for Check expired date by pharmacist

Use case Check presence of drug.

Actor pharmacist
Description Check presence of drug.

 Pharmacist has to use username and

Precondition password.
 Drugs is must be recorded.

Post condition Seen the drug is whether present or not.

Main path 1. Login to the pharmacist user interface.
2. Insert drug name.
3. Select ok button.

Table 2.9 :- use case description for Check presence of drug.

Use case Requisition of drug

Actor pharmacist

24
Description Send drug requisition form to store manager
by listing absence drug in dispensary.
Precondition Pharmacist has to use username and
password.

Post condition Requisition form reach Store database.

Main path 1. Login to the pharmacist user interface.
2. Select requisition button.
3. Insert absence drug.
4. Select send button.

Table 2.10 :- use case description for Requisition of drug

Use case Prescription

Actor pharmacist
Description Read patient prescription and identify drug type.
Precondition Pharmacist must be workers of the pharmacy.
Post condition Identified drug name.
Main path 1. Receive prescription and read.
2. Login to the pharmacist user interface.
3. Insert drug name.
4. System display drug information.
5. Tell the cost to the patient and allocate to
the casher.
Alternative path 4.1. Drug is not present
4.2. Allocate patient other pharmacy.

Table 2.11 :- use case description for Prescription

25
Use case Receive cost
Actor Casher
Description Receive cost from the patient and print recite.
Precondition cashers has to be workers on pharmacy

Post condition Received cost printed recite.

Main path 1. Check cost on prescription.
2. Receive cost.
3. Register on cash machine.
4. Print recites.
5. Give recite to the patient.
Table 2.12 :- use case description for Receive cost

2.3 Sequence Diagrams

A Sequence diagram in UML is a kind of interaction diagram that shows how process
operates with one another and in what order. It is a construct of message sequence chart. A
sequence diagram shows object interactions arranged in time sequence. It depicts the
objects and class involved in scenario and the sequence message exchange between the
objects ended to carry out the functionality of the scenario.

The following sequence diagram describes as follow.

Fig 3.2 shows the interaction between the patient and object of the system, such as
pharmacist, pharmacist user interface, dispensary DB and casher.

Fig 3.3 shows the interaction between store manager, store manager interface and store
database.

Fig 3.4 shows the interaction between pharmacist, pharmacist UI, dispensary DB and
manager UI.

26
Fig 2.2 Sequence diagram of patient interaction

27
Fig. 2.3 Sequence diagram of store manager
28
Fig 2.4 Sequence diagram of pharmacist

29
2.4 Activity diagram

Activity diagram are graphical representation of workflow of stepwise activities and

action with support for choice, iteration and concurrency. In unified modeling
language, activity diagrams can be used to describe the business and operational
step by step workflows of components in a system. An activity diagram shows the
overall flow of control.

The activity diagram in fig 3.5 is graphical representation of relation between

patient, pharmacist and casher and how activities are proceeding between them.

Activity diagram in fig 3.6 is activity diagram that show activity between pharmacist
and store manager.

Prescription

30
Fig 2.5 activity diagram of pharmacy and casher

31
Fig 2.6 activity diagram of pharmacist to store manager

32
2.5 State chart diagrams
State chart diagrams described all of the possible states that a particular object can get into
and how the objects state changes as a result of events that reach the object .To understand

complex classes better particularly those that act in different manners depending on their
state you should develop one or more UML state chart diagram state chart modeling are a
familiar technique to describe the behavior of the system it is evolved from system use case
model and has an initial state (creation state is the one that an object is in) when it is the
first time created, where as a final state is one in which no transition exit a transition is a
progression from one state to another and will be triggered by an event that is either
internal of external to the object.

33
Fig 2.7 state chart of patient registration

34
Fig 2.8 state chart for store manager

Fig 2.9 state chart of pharmacist

35
2.6 Class diagram
A class diagram describes the type of objects in the system and the various kinds of
static relationships that exist among them. Class models are created by using many
of the modeling concepts and notations. They show the class of the system. Their
interrelation ships (including inheritance, aggregation and association) and the
operations and attributes of the class and constraints those apply to the way objects
are operations and attributes of the class and constraints that apply to the way
objects are connected.

36
Fig 2.10 class diagram

37
Chapter three design analysis
3 Design analysis

3.1 Introduction

System design is focused on making high level decision concerning the overall structure of
the Red Cross society pharmacy management system. The main activity in system design of
Red Cross society pharmacy management system is including:-

 Software architecture
 Sub systems
 Database design
 User Interface

3.2 Purpose

Purpose of the design document is to define software architecture of Red Cross pharmacy
management system and describe database and their relationship between the entities.
This document provides overview of the user interface of the system. Simply this document
will highlight the system components, user interface, database relation, communication
and overall responsibility of each component.

38
 3.3 Software architecture
Software architecture is a description of the sub system and components of a software
system and the relationship between them. Subsystem and components are typically
specified in different views to show the relevant functional and non functional properties of
software system.

dispensary process component

User interface

39
 Database

System database

Fig 3.1 software architecture

3.4 Subsystem

Subsystem is typically group together elements of the system that share some common
properties. Sub division of information system in to subsystem has the following
advantages:-

 Produce smaller units of development.

 It helps reuse at the component level.
 Improves maintenance.
 Improve portability.

40
 Fig 3.1 software architecture

Fig 3.1 subsystem of the system

Filed name Data type Purpose Filed size 1.1 Da

Drug _id Char Primary key 10
Drug _name Char Not null 20 tab
Quantity Integer Not null 5 ase
Cost Numeric Not null 5,2
Expire _ date Date time Not null
Product _date Date time Not null
Supplier _ id Char Foreign key 15
Shelf_ no Integer Not null 3
Date Date time Not null
Cat _ id char Foreign key 10
design

1.1.1 Database table

Drug table

41
 Table 3.1 drug table
Employee table

Filed name Data type Purpose Filed size

Emp _id char Primary key 10
Phar _ id char Foreign key 5
F _ name Char Not null 20
L _ name Char Not null 20
Sex char Not null 5
Age Integer Not null 3

Table 3.2 Employee table

Pharmacist table

Filed name Data type Purpose Filed size

Emp _ id char Foreign key 10

Table 3.3 Pharmacist table

Manager table

Filed name Data type Purpose Filed size

Emp _ id char Foreign key 10

Table 3.4 manager table

Casher table

Filed name Data type Purpose Filed size

Emp _ id char Foreign key 10

Table 3.5 casher table

Patient table

Filed name Data type Purpose Filed size

Patient _id Char Primary key 10
Drug _ id char Foreign key 10
F _name Char Not null 20
L _name Char Not null 20
Sex char Not null 5
Age Integer Not null 3
Hospital name Char 20
Date Date time Not null

42
 Table 3.6 patient table

Requisition table

Filed name Data type Purpose Filed size

Drug _id Char Foreign key 10
Date Date time Not null
Cat _ id char Foreign key 10
Phar _ id char Foreign key 5
Amount Integer Not null 5

Table 3.7 Requisition table

Category table

Field name Data type Purpose Field size

Cat _ id char Primary key 10

Drug _ id char Foreign key 10

Cat _ name char Not null 20

Description text Not null

Table 3.8 category table

Supplier table

Field name Data type Purpose Field size

Sup _id char Primary key 15

Sup _ name char Not null 20

Address char Not null 20

43
 Table 3.9 supplier table
Pharmacy table

Field name Data type Purpose Field size

Phar _ id Char Primary key 5

Name Char Not null 20

Address Char Not null 20

Table 3.10 Pharmacist table

3.5.2 Database schema

44
 Fig 3.2 database schema

3.5.3 ER Diagram Representation

45
 Fig 3.3 ER representation

3.6 User interface

3.6.1 interface diagram

46
 Fig 3.5 interface diagram

Fig 3.4 interface diagram

3.6.2 sample user interface

47
 Fig 3.5 Login form

Fig 3.6 External interface for sore manager

48
Fig 3.7 External interface for recording drug

49
 Fig 3.8 External interface for pharmacist

Fig 3.9 External interface for record patient information

50
 3.7 Glossary

Term Definition
RCS Red Cross society
RCSP Red Cross society pharmacy
DBMS Database management system
ERCS Ethiopian red cross society
DRC Danish Refugee Council
MOH Minster of health
PMS Pharmacy Management System
SADM System analysis and design methods
UML Unified modeling language
SQL Search quarry language
UI User interface
DB Database

Table 3.11 glossary

51
Reference

1. http://www.redcrosseth.org/
2. http://www.tutorialspoint.com/uml/index.html
3. http://www.tutorialspoint.com/uml/uml useful resources.htm
4. Designing object oriented software
5. Object-Oriented Systems Analysis and Design

52