Contents

1.1. Introduction ........................................................................................................................................... 3

1.2. Architectural Design ............................................................................................................................... 4
1.3 Component Diagram ............................................................................................................................... 4
1.4 Design Class Diagram .............................................................................................................................. 6
1.4.1. Design Class Diagram Description................................................................................................... 8
1.5 Use Case Diagram ................................................................................................................................. 11
1.5.1 Use case description ...................................................................................................................... 13
1.6. Sequence Diagram ............................................................................................................................... 20

List of Tables

Table 1 Class Description of Admin ............................................................................................................ 8

Table 2 Class description of manager ........................................................................................................... 8
Table 3 Class Description of Cashier ............................................................................................................ 9
Table 4 Class Description of Pharmacist ...................................................................................................... 9
Table 5 Description of Store Coordinator .................................................................................................. 10
Table 6 Class Description of Request Order .............................................................................................. 10
Table 7 Class Description of Bill Preparation............................................................................................ 11
Table 8 Class Description of Sold drugs ..................................................................................................... 11
Table 9 use case description for login ......................................................................................................... 14
Table 10 use case description for create user account ............................................................................... 14
Table 11 use case description for register new drugs information.............................................................. 15
Table 12 use case description for prepare bill............................................................................................. 16
Table 13 use case description for update drugs information...................................................................... 17
Table 14 use case description for view available drugs in the store .......................................................... 18
Table 15 use case description for delete expired drugs information ........................................................... 19

1|Page
 List of figures

Figure 1 Architectural Design ....................................................................................................................... 4

Figure 2 component Diagram ...................................................................................................................... 5
Figure 3 Analysis Class Model .................................................................................................................... 7
Figure 4 use case diagram .......................................................................................................................... 12
Figure 5 sequence diagram for login........................................................................................................... 20
Figure 6 sequence for create account .......................................................................................................... 21
Figure 7 sequence diagram for register drugs ............................................................................................ 22
Figure 8 sequence diagram for view available drugs ................................................................................. 23
Figure 9 sequence diagram for prepare bill ................................................................................................ 24
Figure 10 sequence diagram for delete expired drugs .............................................................................. 25
Figure 11 sequence diagram for update drugs information ....................................................................... 26

2|Page
 1.1. Introduction

Technology is spreading its wing in almost every walks of human life activities. Now a day it is
better if every activity is done using new technology in order to fulfil the need of human being,
Organization and Enterprise. As today’s world there are all organizations needs to be preferable,
computable and work on fastest way in order to satisfy user’s interest i.e. they should have
facilitate their activities in computerized way. Hence Pharmacy management system is a system
that is designed to improve accuracy and to enhance the performance of the task in the pharmacy
like, registration of drugs, searching drugs information, checking expired date of drugs, report
and other tasks. It is a computer and web based system which helps employee’s to facilitate the
activity of the pharmacy in appropriate manner. The pharmacy has two places which the drugs
are available. These 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. Currently all
activities in the pharmacy performed manually. It requires the pharmacist monitor manually each
drug that is available in the pharmacy or not. This usually leads to mistakes as the workload of
the pharmacist increases.

3|Page
 1.2. Architectural Design

A software system is a set of communicating entities that collaborates to perform task. The
architecture used for the system is a three tier Client/Server Architecture. The client tier is the
applications user interface containing data entry forms and client side applications. It displays
data to the user. Users interact directly with the application through user interface. A web server
is a program that runs on a network server (computer) to respond to HTTP requests. The most
commonly used web servers is Apache. The web server used in this system is Apache. HTTP is
used to transfer data across the Internet. The third tier, called the data tier, maintains the
applications data. It stores these data in a database management system (DBMS).

Figure 1 Architectural Design

1.3 Component Diagram

Component diagrams are often used to model high-level software components and how they
interact. The interfaces between these components become clear as the model grows, which
provides a much clear delineation of duties of each component. So from that point component
diagrams are used to visualize the physical components in a system. Component diagrams can 70
also be described as a static implementation view of a system. Static implementation represents
the organization of the components at a particular moment. It does not describe the functionality
of the system but it describes the components used to make those functionalities.

4|Page
Figure 2 component Diagram

5|Page
 1.4 Design Class Diagram

Class diagram is a static diagram. It represents the static view of software. Class diagram is not
only used for visualizing, describing, and documenting different aspects of a system but also for
constructing executable code of the software. Class diagram describes the attributes and
operations of a class and also the constraints imposed on the system. The class diagrams are
widely used in the modeling of object-oriented systems because they are the only UML
diagrams, which can be mapped directly with object-oriented languages. Class diagram shows a
collection of classes, interfaces, associations, collaborations, and constraints. It is also known as
a structural diagram. The purpose of the class diagram can be summarized as:

 Analysis and design of the static view of an application.

 Describe responsibilities of a system.

 Base for component and deployment diagrams.

 Forward and reverse engineering.

6|Page
 Class model Analysis

User
userId
firstName
lastName
sex
address
phoneNo
Login()
Logout()

Figure 3 Analysis Class Model

7|Page
1.4.1. Design Class Diagram Description

Class name Attribute/operation Description

Admin Username Giving the name of the admin
Password To authenticates the users of the
system
Create Account() add accounts to the users
Update Account () Update account details of the
customers
Deactivate Account() Deactivate accounts of users
Table 1 Class Description of Admin

Class name Attribute/operation Description

Manager Username Giving the name of the manager
Password To authenticates the users of the
system
Send order() Send order to supplier
View comment() View comment that added by supplier
Search drug info() Search drug information
View available View drugs that is available to use
drugs()
Generate report() Generate reports
Table 2 Class description of manager

8|Page
 Class name Attribute/operation Description
Cashier Username Giving the name of the cashier
Password To authenticates the users of the
system
Generate report() Generate reports
Prepare Bill() Prepare Bills to request payment
Print Bill() Print Bill
Table 3 Class Description of Cashier

Class name Attribute/operation Description

Pharmacist Username Giving the name of the pharmacist
Password To authenticates the users of the
system
Search Drugs Info() Search drugs information’s online
Check Expired Date() Check expire date of drugs
Generate Report () Generate report
Register Sold Drug Registers the sold drugs information
Info()
View Available Drugs View available drugs in the stock
In stock()
Table 4 Class Description of Pharmacist

9|Page
 Class name Attribute/operation Description
Store User Name Giving the name of the Store
Coordinator coordinator
Password To authenticates the users of the
system
Check Expire Date() Check expired date of drugs in the
store
View Available View available drugs in the store
Drugs()
Generate Report () Generate report to the manager
Delete Expired Delete expired drugs in the store
Drugs()
Register New Drugs() Register new drugs
Update Drugs() Updates drugs in the store

Search Drugs Info() Searches drugs information’s in the

store
Table 5 Description of Store Coordinator

Class name Attribute/operation Description

Order Id Giving
Date To show the date the order
Drug type Indicate the drug types
Drug name To show the drug name
Table 6 Class Description of Request Order

10 | P a g e
 Class name Attribute/operation Description
Bill Bill no Indicate the bill no
Customer name To show customers name
Drug name To show drugs name
Quantity Show quantity
Total price Indicate total price
Table 7 Class Description of Bill Preparation

Class name Attribute/operation Description

Sold drugs Drug code Show drug code
Drug name Shows drugs name
Quantity Indicate drugs quantity
Table 8 Class Description of Sold drugs

1.5 Use Case Diagram

A use case diagram is a representation of a user's interaction with the system that shows the
relationship between users and the different use cases in the system.

 Use Case: A use case describes a sequence of actions that provide a measurable value to
an actor
 Actor: An actor represents a person, organization or any external system that interacts
with the system

11 | P a g e
 pharmacy management system usecase diagram

Add comment
Accept order
View order <<Extend>>
<<Extend>>
Supplier
Reject order
Send order

<<Include>>
<<Include>>
Update
View comment account

Create
Search drug info <<Include>>
account Admin
Deactivate
account
customer
<<Include>>
check expired <<Include>>
date
<<Include>> <<Include>>
view available drug <<Include>>
in the stock <<Include>>

Register sold drugs <<Include>>

info

manager generate report <<Include>>

<<Include>>
prepare bill
<<Include>>
<<Include>
Login
process payments <<Include>>

print receipt <<Include>>

pharmacis
<<Include>>
t <<Include>>
view available drugs
in the store

delete expired
<<Include>>
drugs info <<Extend>>

Register new drugs

info
cashier Logout

update drags info

store cordinator

Figure 4 use case diagram

12 | P a g e
 1.5.1 Use case description

The following consecutive tables show the use case description for each of the use cases that has
identified in the above use case diagram. Each table contains the use case name, short
description, pre-condition, post condition, Basic subjects of action and alternative subject of
action the actor initiates and interacts with the use case, description of the use case and typical
subject of events that show the interaction between the actor and the use case which enable the
team to easily depict the functions of the proposed system

Use case number UC 01

Use case name Login

Priority High
Actor Manager, Cashier, Pharmacist, supplier, Store coordinator
,customer and admin
Description: The user enters authorized username and password in order
to access the system.
Precondition The user should create account and have user name and
password.
Post condition The users successfully pass the login page and perform their
task on the system.
1. Open home page. 3. Display the login page
2. click the Login link with login form.
4. Enter the authorized 6. Check the authorized
username and password in the username and password.
login form. 7. If the username and
5. Click on LOGIN button password is correct users
8. End use case. can access the system
based on their privilege.

13 | P a g e
Alternative course of action 9. If the username and password The system displays”
is incorrect please enter correct
username and password t”
message. and returns to
basic course of action 3

Table 9 use case description for login

Use case number UC 02

Use case name Create user account
Actor Admin
Description The admin creates account for user in order to control activities on
system.
Pre-condition The admin must login to the system by using his/her username and
password, and fill users information
Post-condition The user can get username and password to access the system.
Basic course of action User action System response
1. The admin select create 2.The system display create account
account link. page with form
3. The administrator fills 4. The system validates user inputs.
the required information 5.The system registers the users into
and click on submit button. the database
7. Use case end. 6. Display user account successfully
created.

Alternative course of If the information is invalid, The system display error message and
action go to step 2
Table 10 use case description for create user account

14 | P a g e
Use case number UC 03

Use case Name Register new drugs information

Priority High

Actor Store coordinator

Description The store coordinator register drugs information when new drugs come in to the
store

Precondition The store coordinator must login with his/her own username and password.

Post condition The drugs information registered.

Basic course of User Action System Response

action
1. click the Register new drugs link 2. The system displays the form.
3. Fill the drugs information on the form.
5. The system verifies validation
4. Click on Register button
of inputs.

6. The system displays

“registered successfully”
message.

7. Use case end.

Alternative If the inputs are invalid The system displays” please

Course of action enter correct input” message.

and returns to basic course of

action 3

Table 11 use case description for register new drugs information

15 | P a g e
Use case number UC 04
Use case name prepare bill
Actor Cashier
Description The Cashier calculate bill for customer during the customer buy
drugs
Pre-condition The Cashier must login to the system by using his/her username
and password
Post-condition The Cashier can calculate the bill for the customer
Basic course of action User action System response
1.click prepare bill link 2.The system display the form
3. The cashier fills the 4. The system calculates the bill and
required information and display.
click on calculate button. 6. the system print the receipt
5.the cashier generate 7. Use case end.
receipt and click print
button

Table 12 use case description for prepare bill

16 | P a g e
Use case number UC 05

Use case name Update drugs information

Priority High
Actor Store coordinator

Description: If there is any mistake during registration the store coordinator

can update/modify drugs information
Precondition The Store coordinator should create account and have user
name and password.

Post condition The drugs information updated successfully.

Basic course of action User action System response

1. The Store coordinator click 2. The system displays the
the Update link combo box.
3.select the drug he/she wants to 4. The system display drugs
update and click update button information
5. The Store coordinator modify 6. The system displays
the drugs information and click “Updated successfully”
on save button message.
7. End use case.

Alternative course of action 7. If the modified information is The system displays” please
invalid enter correct input”
message. and returns to
basic course of action 4
Table 13 use case description for update drugs information

17 | P a g e
Use case number
UC 06
Use case name View Available Drugs in the store
Priority High
Actor Store coordinator and Manager

Description: Store coordinator and Manager can view available drugs in the
store
Precondition The Store coordinator and manager should create account and
have user name and password.

Post condition Store coordinator and Manager view available drugs

information.
Basic course of action User action System response
2. The users click on View 1. The system displays list
Available drugs link of activities.
3. The system display
Available drugs information
4. End use case.

Table 14 use case description for view available drugs in the store

18 | P a g e
Use case number UC 07
Use case name Delete Expired drugs information
Priority High
Actor Store coordinator
Description If the drugs are expired, they must be deleted from the system
Pre-condition The Store coordinator must check the expired date of the drugs
Post-condition The Store coordinator can delete drugs information from the system

Basic course of action User action System response

1. The Store coordinator check 2.The system display expired drugs information
expired date of the drugs 4.The system delete the drug information from the
3. click on Delete button system and display “deleted successfully” message
5. Use case end.

Table 15 use case description for delete expired drugs information

19 | P a g e
1.6. Sequence Diagram

Sequence diagrams show the interaction between participating objects in a given use case. They
are helpful to identify the missing objects that are not identified in the analysis object model. To
see the interaction between objects, the following describe the sequence diagram of each
identified use cases.

user<<Actor>> Home page Login page<<ui>> system controller user Account<<DB>>

Constraint Constraint Constraint Constraint Constraint specified page<<ui>>
Constraint
visit home page ()
login

request login page

click on login link

display login page

Constraint
Constraint Constraint

enter user name and password and click login

check user name&password

error
Constraint Constraint

request spacified page

Constraint
Constraint
Constraint

display specified page

Constraint
Constraint

Figure 5 sequence diagram for login

20 | P a g e
 Explanation

Activity in the system is shown by messages that pass between the objects. These messages are
represented by a line with an arrow. Messages can be sent back and forth, from left to right, and the
arrow shows which is the receiver and which the sender of the message. The arrows are usually
labeled so that you can easily understand the content of the message.

Once the page has loaded, you’re usually presented with a form that allows you to enter your
credentials. This is often just your email address and a password. You enter your data and submit
the form, and this is when the sequence diagram kicks in and shows how useful it can be.

admin <<acyor>> admin choice page<<ui>> create account form <<ui>> system controller user account<<DB>>

Constraint Constraint Constraint Constraint

create account

click on create account link()

request create account form

display the form

Constraint Constraint
Constraint

enter personal information() click form validity

error
add to the system

Constraint Constraint Constraint

display successfully created

Constraint Constraint

Figure 6 sequence for create account

Explanation

Once the page has loaded, admin or user is usually presented with a form that allows creating, or in
other words the information that is used to sign up for the site. The admin requests create account
form and the form displays then fill form using personal credentials, then credential details is
checked by the system and generate error if any otherwise display successfully created account as
an alert message.

21 | P a g e
 Register drugs

store Store coordinator Add drugs

System controller Add drugs<<DB>>
coordinator<<actor> choice<<ui>> page<<ui>>
Constraint Constraint Constraint Constraint

Constraint
click on add drugs link()
Register add drugs form

display the form

check user input

Enter drug information and click on add button()
Constraint error
Add to data base

Constraint
Constraint

Constraint
display successfully registered message

Constraint
Constraint

Figure 7 sequence diagram for register drugs

Explanation

In the register drugs page store coordinator after login , clicks on add drugs link , then registers
drugs to be added after display form for registering drugs, then enters drug information and
clicks add bottom , the system checks drug coordinator inputs and database is stored if no error is
generated , then alert successfulness message.

22 | P a g e
 View
availabledrugs

User<actor> User choice page<ui> View drugs info<ui> System controller drug info<DB>

Constraint Constraint Constraint

click on view available drugs link() Request view page

Display combo box

Constraint

Select from combo box& click view button check available drugs Constraint
Request drug information

Constraint
Display drugs information

Constraint
Constraint Constraint Constraint
Constraint

Figure 8 sequence diagram for view available drugs

Explanation

In this page actor of view available drugs clicks on view available drugs link, then request to
view page and combo box is displayed, then actor selects from combo box and clicks view
bottom, then check directs to page check available drugs , request drug information , then lastly
displays drugs information.

23 | P a g e
 Casher drugs
Casher<actor> choicepage<ui calculate bill <ui> System controller Print
info<DB>
Constraint > Constraint
Constraint Constraint Constraint Constraint

Prepar bill click on calculate bill link()

requested calculate bill page

display calculate <ui>

Constraint Constraint
enter drugs information & click calculate button
check user in put
fetch drug price & calculate

Constraint Constraint

display total price

click print button
Constraint
Constraintprint the bill

Constraint Constraint

Constraint

Figure 9 sequence diagram for prepare bill

Explanation

Actor is the cashier and clicks on calculate bill link , then requests calculate bill page , then
calculate bill page is displayed by System interface ,then cashier inters drugs information and
clicks calculate bill bottom , system checks user input , then fetches drug and calculates user
input requests , then displays total price , then cashier clicks print bottom and prints bill .

24 | P a g e
 Store store coordinator check expire system Drugs
coordinator<actor choicepage<ui> datepage<ui> controller info<DB>
>
Constraint Constraint Constraint Constraint Constraint

Delete expired drugs information

click on check expire date link()

Request the page

Display the page

Constraint
Constraint
enter the current date & click check button
check user input
check expire date

Constraint Constraint

Constraint
Display expired drugs information

check on delete button() Constraint

delete expired drugs information

Constraint
display successfully deleted

Constraint
Constraint

Figure 10 sequence diagram for delete expired drugs

Explanation

Actor is store coordinator and the page is delete expired drugs information, actor clicks on check
expired drugs link, then requests page of its type, then the page is displayed, then enters current
drug date and clicks the check button, system checks user input, if valid, then checks expired
date for the drugs, then displays expired drugs information, then actor checks on delete button,
then delete expired drugs information, then display successfulness message by the system.

25 | P a g e
 Store coordinator update drugs update
Store coordinator<<actor>> Drugs info<<DB>>
choice<<ui>> page<<ui>> controller
Constraint Constraint Constraint Constraint Constraint

Update Drugs info

click on update drugs link()

Request update form

Display the form

check drug info

Constraint
Constraint
Request drug info

Select drug name & click on view button()

Constraint

Constraint
Constraint Display drug information

update drug information &click on save button() Constraint

check drug info
error

Save drug info

Constraint

Constraint Constraint
Display updated successfully

Constraint

Figure 11 sequence diagram for update drugs information

26 | P a g e
 Explanation

Actor is the store coordinator and the page is update drugs information.

Store coordinator clicks on update drugs link, then request update form and the form is displayed
by the system, then actor selects drug name and clicks on view button, then drug information is
displayed, then the store coordinator updates the drug information and clicks save button, then
system checks for validating user inputs and generate error if any and if no such errors are there
the drug information is saved, then lastly system displays successfulness of user input as an alert.

27 | P a g e