Pharmacy Management Information System

PHARMACY MANAGEMENT INFORMATION
SYSTEM
Submitted By
SehrishWasif (15-arid-3410)
Tayyaba-un-Nisa (15-arid-3411)
Qurat-ul-Ain (15-arid-3407)
Master of Computer Science (MCS)
Submitted To
Hamid Awan
Barani Institute of Management

Sciences
University of Arid Agriculture,

Rawalpindi
Department of Computing & Information Technology

Session 2015-17
ACKNOWLEDGEMENTS
We wish to express our thanks to Almighty Allah for helping us in

conducting this project and to Holy Prophet (Peace Be Upon Him).
Teacher is like an energy wave that penetrates into the dense fog of illiteracy
and indifferentism making this hidden under its superiors coverable for
perception.
With this spirit of thoughts and deep sense of acknowledgment, we pay

humble gratitude to our teacher Hamid Awan, for his absorbing attitude in
the procedural matters as well as for his interested supervision.
We are extremely grateful to our seniors for their co-operation during this
project.
SehrishWasif __________
Tayyab-un-Nisa __________
Qurat-ul-Ain __________
Faculty of Computing& Information Technology, Barani Institute of Management Sciences. 1

DEDICTION
We would like to dedicate our work to our parents for providing us with the
opportunity to engage in this system. Without their support, we might not
have found ourselves at BIMS, nor had the courage to engage in this task
and see it through. They are all aware how this project and our studies
throughout our two years at BIMS have formulated our outlook,
determination, motivation and perspective that will sculpt our future.

DECLARATION
We SehrishWasif D/o Ch. WasifElahi roll#15-arid-3410, Tayyab-un-Nisa D/o
JavedAkhter roll#15-arid-3411 and Qurat-ul-Ain D/o Shahid Aliroll#15-arid-3407
students of Master of Computer Science, Department of Computing & Information
Technology,Barani Institute of Management Sciences, Pakistan, hereby solemnly
declare that the data quoted in this thesis titled “Pharmacy Management
Information System” is based on our original work, and has not yet been submitted
or published elsewhere.
SehrishWasif ______________
Tayyab-un-Nisa ______________
Qurat-ul-Ain _______________
I certify that SehrishWasif D/o Ch. WasifElahi roll#15-arid-3410, Tayyab-un-Nisa
D/o JavedAkhter roll#15-arid-3411 and Qurat-ul-Ain D/o Shahid Aliroll#15-arid-
3407 students of Master of Computer Science,Department of Computing &
Information Technology, Barani Institute of Management Sciences, Pakistan,
worked under my supervision and the above stated declaration is true to the best of
my knowledge.
Hamid Awan_______________
Barani Institute of Management Sciences, Rawalpindi, Pakistan.
Email: hamidawan@gmail.com
Dated: July ____, 2017

PROJECT COMPLETION CERTIFICATE
It is verified that this thesis titled “Pharmacy Management Information
System” by SehrishWasif D/o Ch. WasifElahi roll#15-arid-3410, Tayyab-
un-Nisa D/o JaavedAkhterroll#15-arid-3411 and Qurat-ul-Ain D/o Shahid
Aliroll#15-arid-3407 students of Master of Computer Science, Department
of Computing & Information Technology, Barani Institute of Management
Sciences, Pakistan, contains sufficient material required for the award of
above said degree.
Hamid Awan _______________
Barani Institute of Management Sciences, Rawalpindi, Pakistan.
Email: hamidawan@gmail.com
Muhammad Asif Ali Khan _________________

Head of Department,
Barani Institute of Management Sciences, Punjab, Pakistan.

PREFACE
Today, Computer plays an important role in every field of life. It also makes
great impact on the field of Pharmacy. Today, all pharmacy dealers want to
implement their daily transactions in the computerized database, because
they face many difficulties in manual working.
The software “Pharmacy Management Information System” fulfills the
requirements of every pharmacy dealer. In this software, user can handle all
necessary transactions quite easily. This software is especially useful for
those pharmacy dealers who feel difficulties in understanding the manual
transactions.
It is hoped that this software will be found much more useful for every user.
Any suggestion from the user side for the improvement of this software shall
be highly appreciated.

TABLE OF CONTENTS

LIST OF FIGURES 10
LIST OF TABLES 11
ABSTRACT 12
CHAPTER 01 - INTRODUCTION 13
1.1 Introduction 14
1.2 Scope 14
1.3 Objective 15
1.4 Tools for Development 15
1.4.1 Hardware Requirements 15
1.5 Expected Outcome 15
1.6 Activity Index 16
CHAPTER 02 - STUDY OF EXISTING SYSTEM 17
2.1 Existing System 18
2.1.1 Disadvantages of Existing System 18
2.2 Proposed System 19
2.2.1 Benefits of Proposed System 19
CHAPTER 033- REQUIREMENT ANALYSIS 22
3 Requirement Analysis 23
3.1 Functional Requirements 23
3.1.1 Login 23
3.1.2 Manage Items 23
3.1.3 Manage Users 23
3.1.4 Cash Adjustment 24
3.1.5 Stock Adjustment 24
3.1.6 Manage Manufacturer 24
3.1.7 Manage Categories 24

3.1.8 Manage Customers 24
3.1.9 Manage Items 24
3.2 Non-Functional Requirements 25
3.2.1 Performances 25
3.2.2 Reliability 25
3.2.3 Security 25
3.2.4 Scalability 25
3.2.5 End of Use 25
3.2.6 Fault Tolerance 25
3.2.7 Accessibility 26
3.2.8 Audit of Control 26
3.2.9 Documentation 26
3.2.10 Efficiency 26
3.2.11 Effectiveness 26
3.2.12 Maintainability 26
3.2.13 Resource Constraints 26
3.2.14 Compatibility 27
3.3 Use Case 28
3.3.1 Use Case Diagram 28
3.3.2 Use Cases 29
CHAPTER 043- SYSTEM DESIGN 32
4.1 System Design 33
4.1.1 Inventory Management 33
4.1.2 Purchases 34
4.1.3 Purchase Return 34
4.1.4 Sales 34

4.1.5 Sales Return 34
4.1.6 Stock Adjustment 35
4.1.7 Supplier / Distributor Management 35
4.1.8 Customer Management 36
4.1.9 Cash Adjustment 36
4.1.10 User Management 37
4.1.11 Item Management 37
4.1.12 Categories 37
4.1.13 Items 38
4.2 System Model 38
4.2.1 Sequence Model 38
4.2.2 Data Model 42
CHAPTER 053- SYSTEM TESTING 46
5.1 Login 47
5.2 Add User 48
5.3 Delete User 49
5.4 Add Item 49
5.5 Delete Item 50
5.6 Add Distributor 51
5.7 Delete Distributor 51
5.8 Add Manufacturer 52
5.9 Delete Manufacturer 53
5.10 Add Category 54
5.11 Delete Category 54
5.12 Add Customer 55
5.13 Delete Customer 56

CHAPTER 063- DESIGNATION MANUAL 58
6.1 Login Form 59
6.2 Main Screen 60
6.3 Manage Users 61
6.4 Manage Category 62
6.5 Manage Manufacturer 63
6.6 Manage Distributor 64
6.7 Manage Item 64
6.8 Manage Customer 65
CHAPTER 073- CONCLUSION & FUTURE WORK 66
7.1 Conclusion 67
7.2 Future Work 67
REFERENCES 69

LIST OF FIGURES
Figure 3.3.1 Use Case Diagram for PMIS 28

Figure 4.2.2 Data Model (1) 42
Figure 4.2.1-1 Sequence Model – Login 38
Figure 4.2.1-2 Sequence Model – User 39
Figure 4.2.1-3 Sequence Model – Distributor 39
Figure 4.2.1-4 Sequence Model – Manufacturer 40
Figure 4.2.1-5 Sequence Model – Item 40
Figure 4.2.1-6 Sequence Model – Category 41
Figure 4.2.1-7 Sequence Model – Sales Purchase/Inventory 41
Figure 6.1 Login 59
Figure 6.2 Main Screen 60
Figure 6.3 Manage Users 61
Figure 6.4 Manage Category 62
Figure 6.5 Manage Manufacturer 63
Figure 6.6 Manage Distributor 64
Figure 6.7 Manage Items 64
Figure 6.8 Manage Customer 65

LIST OF TABLES
Table 1.6 Activity Index 16

Table 3.3-1 Use Case 1 29
Table 5.1-1 Test Case 1 – Login 47
Table 5.1-2 Test Case 2 – Add User 48
Table 5.1-3 Test Case 3 – Delete User 49
Table 5.1-4 Test Case 4 – Add Item 49
Table 5.1-5 Test Case 5 – Delete Item 50
Table 5.1-6 Test Case 6 – Add Distributor 51
Table 5.1-7 Test Case 7 – Delete Distributor 51
Table 5.1-8 Test Case 8 – Add Manufacturer 52
Table 5.1-9 Test Case 9 – Delete Manufacturer 53
Table 5.1-10 Test Case 10 – Add Category 54
Table 5.1-11 Test Case 11 – Delete Category 54
Table 5.1-12 Test Case 12 – Add Customer 55
Table 5.1-13 Test Case 13 – Delete Customer 56

ABSTRACT
This report describes the functions of “Pharmacy Management Information

System”. Our software provides the best reliability to the user when he
wants to access the system. The system will maintain the complete record of
drugs, customer, companies, its branches and the invoice of the sale.

CHAPTER 1
INTRODUCTION

CHAPTER-1
1. INTRODUCTION
1.1 Introduction
Information and Communication Technology plays a great role in different
fields and areas. Pharmacy system is one area which is also affected.
It is necessary to ensure a technologically appropriate, efficient, affordable,

user friendly system to benefit the pharmacy industry. For this reason, this
system is being built.
The system will ensure availability of sufficient quantity of drugs and

consumable materials for the customer.
In general, the system is based on computer technology that gives service for
users. The system will help removing time wasting, saving resources, allow
easy access to medicine, as well as bring on more security on the data
compared to manual system.
1.2 Scope
The scope of our system is very wide because it efficiently uses the
database rules and also according to the market values which envisaged that
our project will satisfy our end user also. Furthermore, this application is a
part of Hospital Management Information System (HMIS).
With the development of specific drug system, the emphasis of the

Pharmacist’s responsibility has moved towards the utilization of scientific
knowledge in the proper use of modern devices and the protection of the

public against dangers.
1.3 Objective
It is a user friendly application for Pharmacist which reduces the burden
and helps to manage all sections of Pharmacy like Medicine Management
and Billing etc., which improve the processing efficiency.
In Pharmacy, Billing management is the key process including the safe data
store about medicine as well as fast searching, delete and update of
medicines.
1.4 Tools for Development

The Pharmacy Management Information System would be developed
using the following tools and technologies:
 Microsoft Windows 7 or above Operating System
 Microsoft Visual Studio 2012
 Microsoft SQL Server 2014
 Microsoft .Net framework 4.5
 ASP.net Framework(C#)
1.4.1 Hardware Requirements

Intel Core i5 computers with a 2GB RAM, 80GB hard disk to be used
as a hardware requirement for this system.
1.5 Expected Outcome

The application is expected to provide an easy-to-use Pharmacy
Management Information System with a high accuracy.

1.6 Activity Index
No Activity Duration Deliverables

1. Proposal & Review 2 Weeks Approved Proposal Document
2. System Analysis 3 Weeks SRS
3. System Design 2 Weeks Design Document
4. System Development 3 Weeks Executable Deliverable 1
5. Development Review 2 Weeks Executable Deliverable 2
6. System Testing 1 Week Executable Deliverable 3
7. System Integration & 1 Week Executable Deliverable 4

Implementation
8. Write-up of user 2 Weeks User Manual Document
Manual
Table 1.6 Activity Index

CHAPTER 2
STUDY OF EXISTING
SYSTEM

CHAPTER-2
2. Existing & Proposed System
2.1 Existing System
The existing system was manually base system which is almost all
works done on papers / files. This system requires the pharmacist to
manually monitor each drug that is available. Ordering of drugs is also being
done manually. Significant time is allocated for writing order as one needs to
go through the stock’s balance and rough estimate of the amount to order.
This usually led to mistakes. Thus, the workload of a pharmacist increases.
2.1.1 Disadvantages of the Existing Systems
 Medicine data search in order to buy, audit and other related works
is very difficult
 Maintenance of ever-growing files and folders is a very tough job
 Data Security is very difficult
 Shelf arrangement method is difficult to take in mind
 Manual Searching of Medicine on shelf is difficult
 Difficult to maintain finished or sold medicine record
 User cannot maintain record efficiently
 Existing system does not arrange medicine in systematic way
 Chances of errors are high
 Data redundancy and inconsistency makes the existing system odd
and inefficient.

2.2 Proposed System
The Pharmacy Management Information System is design based in order to

illuminate the problem of the current system. This accessibility of the
information is will be great advantage as it reduced medical errors.
The system handles all aspects of the inventory control function. It allows
the pharmacist to receive new batches of drugs, delete obsolete drugs and
modify the current dosage and identification of drug in the database.
With the proposed system, the pharmacist will be able to monitor the
movement of the drugs with ease. Implementation of proposed system will
reduced the time spent for paperwork.
2.2.1 Benefits of Proposed System
 Efficient System
In our proposed system, user can easily maintain their
record with quite efficient.
 Removing Data Redundancy

In our proposed system, we remove the data redundancy.
Now, we get the information in a single place.
 With No Wastage of Space

In the proposed system, our client did not require more
space. It can only require a little space where they adjust their
computer.

 Minimum or Less Labor Required
They can also required less labor in fact only one person
which can handle their daily transactions quite easily.
 Data Accuracy
Our proposed system is also accurate because now they
don’t enter a single record in so many registers but only in one single
computer.
 Data Consistency
The major benefit of our proposed system is Data
consistency. Now, if we change data in one portion of the system, it
can automatically change data in every related portion. We can also
take modification in the proposed system.
 Data Summary or Report

Now, It is very easy to make the Summary or report of
daily transactions at the end of the day.
 Data Security
In our proposed system, our client has security. Now only an
authorized person can enter in this system.

CHAPTER 3
REQUIREMENT ANALYSIS

CHAPTER-3
3. Requirement Analysis
This chapter provides analysis of the requirements of the proposed system.

There are two major types of requirements for the proposed system:
a. Functional Requirements (FRs)
b. Non Functional Requirements (NFRs)
These requirements are described in the following sections:
3.1 Functional Requirements
Functional requirements are the primary requirements that are to be fulfilled

by the application. Their fulfillment allows the user to use the application.
The proposed system provides features for different type of users. The
following subsections illustrate functional requirements to be fulfilled by the
proposed system.
3.1.1 Login
Admin will be able to Login into the system with his unique username
and password
3.1.2 Manage Items
Admin need sufficient access to his system so he/she can manage
item, form this he can keep record of all the items in his Pharmacy.
3.1.3 Manage Users
Admin need to manage the end users who are using his software in the
Pharmacy, he needs sufficient access to monitor the end users.

3.1.4 Cash Adjustment
The most important requirement is the “Cash Adjustment”. Admin
needs check and balance of the cash flow. It also includes profits and
loss.
3.1.5 Stock Adjustment
Having complete and proper details about the stock is vital for the
Pharmacy. Every stock detail should be visible to the admin.
3.1.6 Manage manufactures
Manufactures are the companies which are providing items for the
Pharmacy, so managing manufactures it is very important.
3.1.7 Manage Categories
Categories are made when items are divided into sub-categories.
Admin has rights to manage the Categories which also have different
sub-Categories according to the requirements.
3.1.8 Manage Customers
Customers are managed by Admin. Record of the customers will also
maintain in the database.
3.1.9 Manage Items
Items are managed by Admin. Items can be added, updated and
deleted according to the user requirement.

3.2 Non Functional Requirement
3.2.1 Performance
The software would be able to perform desired tasks in reasonable unit
of time.
3.2.2 Reliability
The software would perform desired tasks as expected.
3.2.3 Security
Since Biometric Attendance & Identity Validation System (BAIVS)
would include sensitive personal data like photographs and thumb
impressions of staff and students, the system would provide access to
only legitimate users. The physical security however, is responsibility
of the institution running the system.
3.2.4 Scalability
The proposed system would be scalable to support extended number of
users and/or computing nodes.
3.2.5 Ease of Use

The proposed system would be user-friendly and would provide
Graphical User Interface (GUI).
3.2.6 Fault Tolerance

The system would provide basic fault tolerance for data processing. It
would include failure of some task would not cause other tasks or data
to fail.

3.2.7 Accessibility
The proposed system would be GUI-based desktop application to
installed on each computing node running the application in the
premises of the institution.
3.2.8 Audit and control

The system would provide administrative rights to control data items.
3.2.9 Documentation
The system would also provide user and technical documentation
supporting the usability and maintainability.
3.2.10 Efficiency (resource consumption for given load)

The proposed system would provide efficient resource utilization. The
resources would include CPU, memory, hard disk, thumb scan,
printer(s), etc.
3.2.11 Effectiveness (resulting performance in relation to effort)

The proposed system would effectively maintain the book keeping and
speed up the data processing with ease of use.
3.2.12 Maintainability
The proposed system would be easy to maintain and extend. Minor
modification to the system would not cause harm to the running
application.
3.2.13 Resource constraints (processor speed, memory, disk space,

network bandwidth etc.)
The proposed system would not require any special processing power
that is not available in market.

3.2.14 Compatibility
The proposed system would be compatible to other applications
installed on the system.

3.3 Use Case
3.3.1 Use Case Diagram
Figure 3.3.1 Use Case Diagram for PMIS

3.3.2 Use Cases
TABLE 3.3-1 USE C ASE 1
Use Case Login

Actor Administrator/User
Description The use case begins when the actor indicates the
intent to login to the system. It ends when the
actor is logged in or cancels login.
Pre-Condition The login exists
Post-Condition The actor logs in successfully
Use Case Manage Categories

Actor Administrator
intent to view, update, add or delete Categories
record. It ends when the actor closes the
Category form.
Pre-Condition 1-The Categories record exists for editing/view.
2-The actor is logged in
Post-Condition The Categories record is added r updated.
Use Case Manage Customer Records

Actor Administrator
intent to view, update add or delete Customer’s
Customer form...
Pre-Condition 1-The Customer’s record exists for editing/view.
2-The actor is logged in
Post-Condition The Customer’s record is added or updated.

TABLE 3.3-4 USE CASE 4
Use Case Manage User Records

Actor Administrator
intent to view, update, add or delete user’s record.
It ends when the actor closes users form.
Pre-Condition 1-The user’s record exists for editing/view.
2-The actor is logged in.
Post-Condition The user’s record is added or updated.
Use Case Manage Item Records

Actor Administrator
intent to add, update, delete or view item’s record.
Categories and Manufacturers can be searched.It
ends when the actor closes the form.
Pre-Condition 1-The Item’srecord exists for editing/view.
Post-Condition The item’s record is added or updated.
Use Case Manage Distributor Records

Actor Administrator
intent to add, update, delete or edit distributor’s
record. It ends when the actor closes the Distributors
form.
Pre-Condition 1-The distributor record exists for editing/view.
Post-Condition The distributor’s record is added or updated.

Use Case Manage Manufacturer Records

Actor Administrator
intent to add, update, delete or edit manufacturer’s
Manufacturer form.
Pre-Condition 1-The Manufacturer record exists for editing/view.
Post-Condition The Manufacturer’s record is added or updated.

CHAPTER 4
SYSTEM DESIGN

CHAPTER-4
4. System Design
4.1 System Design
System Design is the process of defining the architecture, modules,

interfaces and data for a system to satisfy specified requirements. System
Design could be seen as the application of systems theory to product
development.
Until the 1990s, system design had a crucial and respected role in the data
processing industry. In the 1990s, standardization of hardware and software
resulted in the ability to build modular systems. The increasing importance
of software running on generic platforms has enhanced the discipline of
software engineering.
4.1.1 Inventory Management
Inventory management is the supervision of non-capitalized assets

(inventory) and stock items. A component of supply chain
management, inventory management supervises the flow of goods
from manufactures to warehouses and from these facilities to point of
sale.
In this system, inventory management plays an important role. We are

managing inventory levels to driving cash flow and profitability. We
maintain adequate records of items sold, items received and items in
inventory. There is an inventory balance plus a receipt of product,
minus the actual sale of product to reflect the quantity in hand. This
has to be done automatically.

4.1.2 Purchases
Purchasing requires knowing the right quality and quantity to buy,
when to order, at what price, and from what sources.
This system clarifies all the issue regarding purchasing the specific
item with right quantity and at exact time also.
4.1.3 Purchase Return
Purchase returns are also provided in the system which allows for
refunds that can be received back.
4.1.4 Sales
The early days of using a cash register and pen and notebook for
accounting and processing transactions are no longer an effective
means of keeping up with today’s advancements in business
technology.
This system provides with a real-time detailed report of sales. This
allows to assess what items are being sold and what items are lagging
in sales. Transactions are processed much quicker.
4.1.5 Sales Return
A sales return is supply sent back by a buyer to the seller, usually for
excess quantity ordered, excess quantity purchased, defective items,
item specifications are incorrect, sent wrong items and expired items.
The seller records this return as a debit to a sales returns account and

credit to the accounts receivable account; the total amount of sales
returns in this account is a deduction from the reported amount of
gross sales in a period, which yields a net sales figure.
4.1.6 Stock Adjustment
A stock adjustment is used to adjust stock for any number of reasons

such as write-offs, stock-takes etc.
From time to time one must adjust item quantities and values. If stock
gets damaged, then we have to write off some of our stock or revalue
it.
This system provides stock adjustment in a way that every item is

available according to its sale. No extra or irrelevant item being
placed. So this systems stock leads towards the profitable sale of a
user.
4.1.7 Supplier / Distributor Management
Supplier management is the discipline of strategically planning for,

and managing, all interactions with third party organizations that
supply goods and/or services to an organization in order to maximize
the value of those interactions. In many fundamental ways, supplier
management is similar to customer management.
Almost all suppliers have distributor evaluation mechanisms. Supplier
evaluation parameters for distributors often includes sales volume and
growth, selling their more profitable products, prompt payment,
market share, customer development and customer service.

4.1.8 Customer Management
Customer retention and loyalty are important goals for successful

business. At the heart of customer management is the customer
database. Customer data is an extremely valuable asset of any
business. A business that has clean, correctly formatted and accurate
data will be able to provide a good level of service as well as saving
time and money.
This system provides the facility for making a database of customer

and importantly customer feedback option is very useful. Positive
feedback of a customer can offer even more great service & negative
feedback can be corrected and acted upon.
4.1.9 Cash Adjustment
Positive cash flow is the key to running a successful business.

Understanding your cash flow is key to knowing where your revenue
is coming from and where it is going.
Profit & Loss statements give a snapshot of the net income of a

business. That’s all done by subtracting all expenses from the total
revenue.
This system brings the automatic cash adjustment on daily / monthly /

quarterly / yearly basis.
4.1.10 User Management

User management is an authentication feature that provides
administrator with the ability to identify and control the state of users
logged into the system.
This system enables to create and manage login credentials for each
user.
Only one username and password is required to access all applications
that are available to the user.
4.1.11 Item Management
Item management is one of the most important processes that has to

be organized. An item can be any entity that is independent with
respect to product data management and has an identifier. Item has to
be define according to its needs.
4.1.12 Categories
Category management is a retailing and purchasing concept in which

the range of products purchased or sold is broken into discrete groups
of similar or related products; these groups are known as product
categories.
This system provides the opportunity to maintain the stock in its

respective category e.g. medicine record maintains in medicine
category, cosmetics record maintains in cosmetics category etc.

4.1.13 Items
Item includes tablets, capsules, syrups, surgical items, cosmetics,

general items. This system maintains the item record according to its
define category. As already mentioned, panadol (item) is a tablet lies
under medicine category.
4.2 System Models
4.2.1 Sequence Models
Error! Reference source not found. To Error! Reference source

not found. 7 demonstrate sequence diagrams of the Pharmacy
Management Information System.
Login
Figure 4.2.1-1 Sequence Model – Login
User
Figure 4.2.1-2 Sequence Model – User
Distributor
Figure 4.2.1-3 Sequence Model – Distributor
Manufacturer

Figure 4.2.1-4 Sequence Model – Manufacturer
Item
Figure 4.2.1-5 Sequence Model – Item

Category

Figure 4.2.1-6 Sequence Model – Category
Inventory
Figure 4.2.1-7 Sequence Model – Inventory

4.2.2 Data Model
Following figures illustrates the system data model for Pharmacy

Management Information System.
Figure 4.2.2 Data Model (1)



CHAPTER 5
TESTING

CHAPTER-5
5. Testing
Testing the application is a vital activity during the software development

life cycle. It helps maintaining Software Quality Assurance (SQA).
5.1 Testing the Pharmacy Management Information System
The major modules for our proposed applications include administration,

Item registration, Sales & Purchase, Customer & user management.
Login
Login
Test Engineer: Sehrish Wasif
Test Case ID: TC1
Related UC/FR/NFR UC1
Date: 26-07-2017
Purpose: Application user authentication
Pre-Req: None
Test Data: User ID and password
Steps: 1. Run the application

2. Enter User ID
3. Enter Password
4. Click login
Status: Pass
Table 0-7 Test Case 1

Add User
Add User
Test Case ID: TC2(a)
Related UC/FR/NFR UC2(a)
Date: 26-07-2017
Purpose: Add new user record
Pre-Req: User logged in
Test Data: User ID, Password
Steps: 1. Enter User ID and Password

2. Click Save button
Status: Pass

Delete User
Delete User
Test Case ID: TC2(b)
Related UC/FR/NFR UC2(b)
Date: 26-07-2017
Purpose: Delete an existing user record
Test Data: User ID, Password.
Steps: 1. Select a user by clicking a row in the data grid.

2. Click on Delete button. The user’s data will be deleted from
the appropriate fields.
Status: Pass
Add Item
Add Item
Related UC/FR/NFR UC3(a)
Date: 26-07-17
Purpose: Add new item record

Test Data: Item ID, Item Name, Category, Manufacturer, Item Code,
Opening Stock, Current Stock and Unit Price.
Steps: 1. Enter Item ID and Item Name.

2. Select specific Category.
3. Select specific Manufacturer.
4. Enter Item Code, Opening Stock, Current Stock and Unit
Price.
Status: Pass
Delete Item
Delete Item
Test Case ID: TC3(b)
Related UC/FR/NFR UC3(b)
Date: 26-07-17
Purpose: Delete an existing Item
Test Data: Item ID, Item Name, Category, Manufacturer, Item Code,
Opening Stock, Current Stock and Unit Price.
Steps: 1. Select an Item by clicking a row in the data grid.
2. Click on Delete button. The selected item will be deleted
from the appropriate fields.
Status: Pass

Add Distributor
Add Distributor
Related UC/FR/NFR UC5a)
Date: 26-07-17
Purpose: Add new distributor record
Pre-Req: User Logged in
Test Data: Distributor ID and Distributor Name
Steps: 1. Select Distributor from “Application” drop down list.

2. Enter Distributor ID and Distributor Name.
3. Click on Save button. The Distributor will be added..
4. Click on Save button
Status: Pass
Delete Distributor
Delete Distributor
Date: 26-07-17
Purpose: Delete distributor record

Test Data: Distributor ID and Distributor Name
Steps: 1. Select Distributor from “Application” drop down list.

2. Select Distributor by clicking a row in the data grid.
from the appropriate field.
Status: Pass
Add Manufacturer
Add Manufacturer
Date: 26-07-17
Purpose: Add new Manufacturer record
Test Data: Manufacturer ID and Manufacturer Name

Steps: 1. Select Manufacturer from “Application” drop down list.
2. Enter Manufacturer ID and Manufacturer Name.
3. Click on Save button. The new Manufacturer will be
added.
Status: Pass
Delete Manufacture
Delete Manufacture
Date: 26-07-17
Purpose: Delete Manufacture record
Test Data: Manufacture ID Manufacture Name
Steps: 1. Select Manufacture from “Application” drop down list.

2. Select Manufacture by clicking a row in the data grid.
from the appropriate field.
Status: Pass


Add Category
Add Category
Date: 26-07-17
Purpose: Add new Category record
Test Data: Category ID and Category Name
Steps: 1. Select Category from “Application” drop down list.

2. Enter Category ID and Category Name.
3. Click on Save button. The new Category will be added.
Status: Pass
Delete Category
Delete Category
Date: 26-07-17
Purpose: Delete Category record

Test Data: Category ID and Category Name
Steps: 1. Select Category from “Application” drop down list.

2. Select Category by clicking a row in the data grid.
3. Click on Delete button. The selected Category will be
deleted from the appropriate field.
4. Click on Save button.
Status: Pass
Add Customer
Add Customer
Date: 26-07-17
Purpose: Add new Customer record
Test Data: Customer ID, Customer Name, Contact Person, Phone Number
and City.

Steps: 1. Select Customer from “Application” drop down list.
2. Enter Customer ID, Customer Name, Contact Person,
Phone Number and City.
3. Click on Save button. The new Customer will be added.
Status: Pass
Delete Customer
Delete Customer
Date: 26-07-17
Purpose: Delete Customer record
Test Data: Customer ID, Customer Name, Contact Person, Phone Number
and City
Steps: 1. Select Customer from “Application” drop down list.
2. Select Customer by clicking a row in the data grid.
3. Click on Delete button. The selected Customer will be
deleted from the appropriate field.
4. Click on Save button.
Status: Pass

CHAPTER 6
DESIGNATION MANUAL

CHAPTER-6
6. Design Manual
This chapter describes the designation manual of the Pharmacy Management

Information System.
6.1 Login Form
Login screen enables the user to login to the system. The user has to provide
a valid user login and password to login.
Figure 6.1 Login

6.2 Main Screen
This is the navigation screen that lets users perform various tasks using
menu items.
Figure 6.2 Main Screen

6.3 Manage Users
This command enables the admin user to add/delete or activate/deactivate

application users.
Figure 6.3 Manage Users

6.4 Manage Category
This command enables the user to add/delete the Category.
Figure 6.4 Manage Category

6.5 Manage Manufacturer
This command enables the user to add/delete the Manufacturer of the
specific item.
Figure 6.5 Manage Manufacturer

6.6 Manage Distributor
This command enables the user to add/delete the Distributor.
Figure 6.6 Manage Distributor
6.7 Manage Item

This command enables the user to add/delete the Item.
Figure 6.7 Manage Item

6.8 Manage Customer

This command enables the user to add/delete the Customer record.
Figure 6.8 Manage Customer

CHAPTER 7
CONCLUSION
& FUTURE WORK

CHAPTER-7
7.1 Conclusion
Pharmacy Management Information System is intended to provide the user

to utilize Pharmacy System for Pharmacy items and reporting. This
application also provides basic Management Information System (MIS) for
keeping records of Items, Category, Manufacturer, Distributor and
Customer.
7.2 Future Work
Future extensions include integration of Hospital Management module for

detailed record keeping of hospital staff, payroll, finance and office
administration (workflow). Another extension dimension includes searching
of the required Item/Manufacturer/Distributor. System automatically
highlights the items which have nearby expiry date.

REFERENCES

REFERENCES
Use IEEE transaction style for references
Search on the web for how to cite a web article, a book and/or a research
paper (conference/jpurnal) in IEEE style.
[1] Database Systems, Principles, Design and Implementation by

Catherine Ricardo, Iona College New Rochelle, New York
[2] http://en.wikipedia.org/wiki/Pharmacy Management System
[3] http://en.wikipedia.org/wiki/Database
[4] http://google.com/Documentation
[5] http://google.com/what is user manual?

Pharmacy Management Information System

Uploaded by

Document Information

Original Description:

Original Title

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

Pharmacy Management Information System

Uploaded by

Copyright:

Available Formats

PHARMACY MANAGEMENT INFORMATION

Master of Computer Science (MCS)

Barani Institute of Management

University of Arid Agriculture,

Department of Computing & Information Technology

We wish to express our thanks to Almighty Allah for helping us in

With this spirit of thoughts and deep sense of acknowledgment, we pay

Faculty of Computing& Information Technology, Barani Institute of Management Sciences. 1

Faculty of Computing& Information Technology, Barani Institute of Management Sciences. 2

JavedAkhter roll#15-arid-3411 and Qurat-ul-Ain D/o Shahid Aliroll#15-arid-3407

students of Master of Computer Science, Department of Computing & Information

Technology,Barani Institute of Management Sciences, Pakistan, hereby solemnly

I certify that SehrishWasif D/o Ch. WasifElahi roll#15-arid-3410, Tayyab-un-Nisa

D/o JavedAkhter roll#15-arid-3411 and Qurat-ul-Ain D/o Shahid Aliroll#15-arid-

3407 students of Master of Computer Science,Department of Computing &

Information Technology, Barani Institute of Management Sciences, Pakistan,

Faculty of Computing& Information Technology, Barani Institute of Management Sciences. 3

Muhammad Asif Ali Khan _________________

Faculty of Computing& Information Technology, Barani Institute of Management Sciences. 4

Faculty of Computing& Information Technology, Barani Institute of Management Sciences. 5

Faculty of Computing& Information Technology, Barani Institute of Management Sciences. 6

Faculty of Computing& Information Technology, Barani Institute of Management Sciences. 7

Faculty of Computing& Information Technology, Barani Institute of Management Sciences. 8

Faculty of Computing& Information Technology, Barani Institute of Management Sciences. 9

Faculty of Computing& Information Technology, Barani Institute of Management Sciences. 10

Figure 3.3.1 Use Case Diagram for PMIS 28

Faculty of Computing& Information Technology, Barani Institute of Management Sciences. 11

Table 1.6 Activity Index 16

Faculty of Computing& Information Technology, Barani Institute of Management Sciences. 12

This report describes the functions of “Pharmacy Management Information

Faculty of Computing& Information Technology, Barani Institute of Management Sciences. 13

Faculty of Computing& Information Technology, Barani Institute of Management Sciences. 14

It is necessary to ensure a technologically appropriate, efficient, affordable,

The system will ensure availability of sufficient quantity of drugs and

With the development of specific drug system, the emphasis of the

Faculty of Computing& Information Technology, Barani Institute of Management Sciences. 15

1.4 Tools for Development

1.4.1 Hardware Requirements

1.5 Expected Outcome

Faculty of Computing& Information Technology, Barani Institute of Management Sciences. 16

No Activity Duration Deliverables

2. System Analysis 3 Weeks SRS

3. System Design 2 Weeks Design Document

4. System Development 3 Weeks Executable Deliverable 1

5. Development Review 2 Weeks Executable Deliverable 2

6. System Testing 1 Week Executable Deliverable 3

7. System Integration & 1 Week Executable Deliverable 4

Table 1.6 Activity Index

Faculty of Computing& Information Technology, Barani Institute of Management Sciences. 17

Faculty of Computing& Information Technology, Barani Institute of Management Sciences. 18

2.1 Existing System

2.1.1 Disadvantages of the Existing Systems

Faculty of Computing& Information Technology, Barani Institute of Management Sciences. 19

The Pharmacy Management Information System is design based in order to

2.2.1 Benefits of Proposed System

 Removing Data Redundancy

 With No Wastage of Space

Faculty of Computing& Information Technology, Barani Institute of Management Sciences. 20

 Data Summary or Report

Faculty of Computing& Information Technology, Barani Institute of Management Sciences. 21

Faculty of Computing& Information Technology, Barani Institute of Management Sciences. 22

This chapter provides analysis of the requirements of the proposed system.