OBJECT ORIENTED

ANALYSIS AND
DESIGN

Submitted To:
Dr. Sadaf Hina Project Title:
Online Pharmacy
Assistant Professor
OOAD
Project Team:
 Hasnain Khan
 Mian Hasnain Ikhlaq
 Umair Yameen
 Ahmed Nawaz

Table of Contents:

Details:
An Online Pharmacy is a Pharmacy that operates over the internet and sends
the orders to customers. Home delivery of Medicine are available. Also have
controlled medicine distribution system. Validation and good distribution
practices are must be followed. The shipment of drugs through the mail and
parcel post is also available.
Sometime customer feels inconvenient to travel to the medical store and buy.
In that case it is easy to order online rather than traveling to the store. Our
Online pharmacy only sell medicines only with a prescription. So, we required a
Pre-written prescription.
We can also provide complete information about Doctors at the same page.
Including contact number, address, timing and list of doctors available. The
page is based on basic information about the hospitals and doctors. You can
find some of the renowned doctors from specialized fields on this page. You
can access contact details along with its relevant information of the
professional doctors and surgeons on our web page. You can get hold on the
contact details and consultation timings of doctors.

Taking a look at in general, the online pharmaceutical field is relatively

underdeveloped and an untapped one. In existing systems the details of
doctors are not available. We provide complete details of doctors also at the
same page.
We already have working existing system. But they are not much sufficient to
fulfilled customer requirement’s. These system deliver medicine in one or two
working days via mail/courier service. We add special feature of quick home
delivery in our system. To deliver quality products in hours instead of days.
Existing system also a lack that they supply medicine's without any
prescription. In our system we overcome this problem as well. We never
accept any order without proper prescription.
In view of the foregoing, this work aims to rectify this problem by providing the
platform for the ever-growing pharmaceutical industry in the country.
We will start it phases from a sector then by time increase our project to a city
then a province and finally to whole Pakistan.

Problem Statements:
 Most of the peoples in Pakistan have lack of resources and health
budget.
 Its take time to get required medication because we don’t have such
facilities in our rural areas.
 Sometimes quality of product may be not satisfactory.
 Remedies in payment methods.
 Without prescription supply of medications
 Normally people don’t have awareness about specified doctors.
 Not enlisted different doctors with their specialty.
 No relative information provided.
Proposed solutions for the above mentioned problems in our project are
following.
 Get your medicines at best price with free home delivery.
 Help consumer in saving time and energy.
 Provide trusted and reliable platform for customers.
 Cash on delivery at retailed and discount prices. Provide affordable
medication at your door step.
 We ask for doctor recommendation and prescription before confirming
any order.
 Provide complete details (phone number, address, hospital etc.) about
available doctors at the same page.
 Enlist all doctors with their specialty for example heart specialist, skin
specialist, eye specialist etc. separately enlisted All relevant information
also provided at the same desk.
The aim of the project is to provide a platform which would be easily
accessible for users to perform online ordering of medicines to doorsteps.
The problem statement
The impact of which is
A successful solution would
Nowadays everyone is too busy to go to
market physically and searching for the
things they need with reasonable prices,
as the life is rapidly getting busy. All the
process takes a lot of time as well as a
large no of resources. As nowadays
everyone wants their work to be done
as quickly as possible so the people lack
time to go to the market
There will be no need to go to the
market for purchasing their medicines
they just need to explore our website
which would be so smooth that anyone
can use our website easily with the help
of internet and hence with less
resources
By using our website users can easily
facilitate themselves by using internet
service, placing their order and with a
very little effort and resources. The user
can also be able to upload their
prescription if he lacks proper
knowledge we can facilitate them also
in this regard.

User Requirements:
The proposed system may contain the following set of user
requirements;
 Searching facilities based on various factors such as customer, medicine,
medicine stock, order etc.
  To manage the payment details online.
 To track all the information about stock, payment, orders details,
customer.
 Manage all the information about system.
 Shows the description and information of the customer medicine.
 Allowed prescriptive customer only.
 Increase efficiency of customer management.
 To deals with monitoring the information and transaction of the medical
stock as well.
 To improve editing, adding, and updating the record, which results
proper resource management of customer data.
 Manage the information of customer.
 Manage the information of medicine stock.
 Integration of all records order.
 Home delivery system.
 Different payment methods.
 Complete details about different kind of doctors at the same platform.

Functional Requirements:
Basic functional requirements of the customers in proposed system after
opening, the webpage of online pharmacy should be of sign-in/signup. Then
the customer is going to follow such functions
 To further use the system first of all user must be registered by following
simple user registration functionality.
 After that their will be different user which are using the system so their
must be different login functionality for different users for instance it
must be varies for customer, admin, and manager.
 Customer have access to change their profile settings and Managers
should be able to manage their profiles as well.
 If user forget their password then in proposed system their must be an
option of forget password available to recover their profile.
Home page of our online pharmacy system should have the following
functionalities for the customers;
 Simple GUI for the user.
 A menu bar for complete menu for available functionalities in system.
  Search bar to ease the user to search their desire information.
 To buy more than one item their must be a cart function available for
the user which allows user to add/update desire products.
 After adding items into the cart their must be a button to place/cancel
their order.
 After this process at the end there are different suitable payment
methods for user to avail like online payment by their bank
accounts/credit cards or cash on delivery.
 At the end their must be a receipt showed up at the screen of user with
complete details like order number, delivery date, price etc.
Home page of our online pharmacy system should have the following
functionalities On Managers end;
 Maintenance of data about medicines/doctors.
 Have access to different options about given information.
 Add data into the system.
 Update/delete given information.
 Search data to find desirable information.
Home page of our online pharmacy system should have the following
functionalities On Admins end;
 Give access to customer/manager, which may be vary for both of them.
 Maintain complete record of the system.
 Categories different users.
 Update the system according to user requirements.
Our online pharmacy system should perform following functionalities
automatically;
 Categories different medicines.
 Sort medicine by name as well after adding new items.
 Available medicines record.
 Stock update.
 Rank doctors.
 Organized record about doctors and available medicines.
 Provide complete information about sale, profit and visited customers.

Non-Functional Requirements:
 System availability
 Allowance for maintainability and enhancements
 Recovery from failure
 Reliability
 Safety
 User friendly
 Response time
 Throughput
 Usability
 Order management and communication
 Order verification, confirmation, and fulfillment
 Preparation, distribution, and inventory control, storage, and security
 Administration
 Intervention and monitoring.

Systems Specifications
The “Online Pharmacy” system enables to maintain the computerized
record of customers as well as the medicines and doctors. It will also perform
quick search for the availibility of the medicine as well as from the nearest
possible location of pharmacy to provide quick service. The system
requirement specification(SRS) will also provides a detailed information on the
internal and external view of the system as well as interfaces required by the
Online Pharmacy web page.
This process is determined in two phases, first of all we will specify the
requirements from the abstract provided as the introduction to the system.
Secondly we will refine those on the basis of our business logic.

A.
Medical experts Feedback Precautions
Login Prescription Register Patients
Profile Management History Remedy
Explanation Conversation Suggestions
Expert System Id or Password Recovery Delivery
Address Payment

B.
The concepts closely related to our business logic are as follows
Register Patients Prescription Medical Consultancy
Profile Management Id or Password Recovery Login
History Medical expert

System Functional Requirements:

1.0 Sign-in/Signup
1.1 Registration
1.1.1 First of all user must be registered to use the system.
1.1.2 After registration each user assigned different id.
1.1.3 Assigned id based on given information.
1.1.4 Given id must be unique.
1.1.5 Asked different questions for security and backup purposes.
1.2Login
1.2.1 User should be login to use the system.
1.2.2 Customers and managers should be allowed to view and update
their login information.
1.2.3 Different kind of functionality for manager, admin and customer.
1.3Forget Password
1.3.1 If user forgets his/her password they would be directed to a page to
answer simple questions asked at the time of registration.
1.3.2 After answering these question user must be change their password.
1.3.3 New password must be different from the previous password.
2.0 Add Product
2.1 Should contain an adding product functionality so that manager may
add products in a sorted manner whenever new products are bought.
2.2 Manager should first ask the administrators permission before adding
the new stock.
2.1.1 Once the request is approved, then the manager should proceed to
his liking.
2.1.2 Both Managers and Admin should be able to view products from
product page after adding.
2.1.3 It may contain;
Variables Constraints
 Product_id Char/String (min>=5 && max
<=15)
Product_name Char/String (min>=3 && max
<=25)
Product_cat Char/String Char/String (min>=5
&& max <=15)
Product_price Float
Product_sale_price Float
Stock Integer
3.0 Update/Delete Product
3.1 Should contain an updating and deleting product functionality in a
sorted manner so that admin may update or delete old products
whenever needed.
3.1.1 Manager should first ask the administrators permission before
updating or deleting the stock.
3.1.2 Once the request is approved, then the manager should proceed to
his liking
3.1.3 It may contain

Variables Constraints
Product_id Char/String (min>=5 && max
<=15)
Product_name Char/String (min>=3 && max
<=25)
Product_cat Char/String (min>=5 && max
<=15)
Product_price Float
Product_sale_price Float
Stock Integer

4.0 Catalogue
4.1 View Catalogue
4.1 Offering customers a well-designed catalogue containing all the
products available with exclusive offers, discounts also.
4.1.1 The catalogue may contain all information regarding products etc.
4.1.2 It may contain;
Variables Constraints
Product_id Char/String (min>=5 && max
<=15)
Product_name Char/String (min>=3 && max
<=25)
Product_cat Char/String (min>=5 && max
 <=15)
Product_sale_price Float
4.2 Search Catalogue
4.2.1 Advanced form of product searching functionality.
4.2.2 This functionality offers ease of use for both customer and manager
to directly view the product they are searching for.
4.2.3 It may contain ;
Variables Constraints
Product_id Char/String (min>=5 && max
<=15)
Product_name Char/String (min>=3 && max
<=25)

5.0 Virtual Cart

5.1 Customers should be each assigned a virtual cart.
5.1.1 Providing customers with a shopping cart functionality so that they
may keep their selected products in check.
5.1.2 Products will be added on basis of name with quantity also, into the
cart.
5.1.3 Allow View and change option for cart.
5.1.4 Provide an option for placement of orders. Also view Receipt option.
5.1.5 Upon order placement, an order number is assigned to customers
order with order date. These have no link with test cases.
5.1.6 Provide an option for cancellation of orders.
5.1.7 It may contain;
Variables Constraints
Cart_id Integer
Product_Name Char/String (min>=3 && max
<=25)
Quantity Integer
Price Float
Customer_id Char/String length==13
Password Char/String (min>=3 && max
<=15)
Order_ID Integer
Order_Date Integer

5.2 Payment Method

 5.2.1 After confirming order, Customer is to select the payment method.
They are of two types; Cash on Delivery, Online Transaction
5.3 Receipt generation
5.3.1 For this customer has to press confirm order for purchasing the
products.
5.3.2 Once approved the bill is then calculated and receipt is showed to
the customer.
It may contain ;
Variables Constraints
Product_name Char/String (min>=3 && max
<=25)
Product_sale_price Float
Quantity Integer
Total_Bill Integer

6.0 Check Reports

6.1 Reports maintenance.
6.1.1 Proper maintenance of reports will be conducted.
6.1.2 All sales made per day shall be recorded.
6.1.3 Report of sales made per day will be generated.
6.1.4 Profit will also be taken into account.
6.1.5 Both Manager and Admin will view reports.
6.1.6 It may contain ;
Variables Constraints
Sales Integer
Profit Integer
Use Case:
Para External Initial Requirements
# Entity
1.0 customer A customer “shall” place order for medicine.
1.0 customer A customer “shall” register himself to the system
1.0 System The system “shall” provide a registration process.
1.0 CA CA “shall” accept, reject and temporarily waive the requests on the
basis of credentials provided.
1.0 customer A customer “shall” login to the system and can change his password
1.0 System System “shall” update the customer’s Request
1.0 System System “shall” process different types of updating e.g. updating of his
personal, or shipping details.
1.0 customer A customer “shall” view his details for verification purposes
1.0 CA CA “shall” accept, reject and temporarily waive the requests on the
basis of credentials provided.
1.0 CA System “shall” search any customer details

2.0 System System “shall” generate invoice, confirmation receipt and finally will
place order
2.0 customer User “shall” view the status of their orders by providing the Order
Number
2.0 customer Customer “shall” place the request for the cancellation of the order.
But all these updating and cancellation requests are to be viewed by
the Order Administrator in order to accept, reject, or waive them.
3.0 administrato An action event "shall" be generated for a corresponding administrator
r when a request is placed for updating of orders or customer details etc
3.0 administrato Corresponding administrator "shall" view his Action List containing
r different actions, and correspondingly process these pending actions
3.0 administrato When the action processing is completed or if the action is just a
r notification message then administrator "shall" delete these actions
from the action list
1.5 Allocate Requirements

Para # Requirements Use Case Name

1.0 A customer “will” place order for goods Place Order
 
1.0 A customer “shall” register himself to the Registration Request
system  
1.0 The system “shall” a registration process. Place Order Request
 
1.0 CA “shall” accept, reject and temporarily Process Customer Request
waive the requests on the basis of  
credentials provided.
1.0 A customer “shall” login to the system and Login
can change his password  
1.0 System “shall” update the customer’s Update Request
Request
1.0 System “shall” process different types of Change Status 
updating e.g. updating of his personal, or
shipping details.
1.0 A customer “shall” view his details for View Customer Details
verification purposes
1.0 System “shall” search any customer details Search Customer

1.0 CA “shall” accept, reject and temporarily Accept Customer Request

waive the requests on the basis of Reject Customer Request
credentials provided. View Customer Request
 
2.0 System “will” generate invoice, confirmation Invoice Generation,
receipt and finally will place order.  
2.0 User “shall” view the status of their orders Search Orders
by providing the Order Number
2.0 Customer “shall” place the request for the Change Payment Details,
cancellation of the order. But all these Change Status, 
updating and cancellation requests are to be Change Personal Details
viewed by the Order Administrator in order
to accept, reject, or waive them.
3.0 The System “shall” generate an action event Create Action,
for a corresponding administrator when a
request is placed for updating of orders or
 customer details etc.
3.0 Corresponding administrator “shall ” view View Action, 
his Action List containing different actions,
and correspondingly process these pending
actions

1.6 Priorities Requirements

Para Rank Initial Use Use Case Name

# Requirements Case
ID
1.0 Highest A customer UC_1 Place Order
“will” place
order for
medicines.
1.0 Highest A customer UC_2 Registration Request
“shall” register
himself to the
system
2.0 Highest Customer “will” UC_3 Pay For Order
make payment  
through cash.
2.0 Highest System “will” UC_4 Invoice Generation,
generate
invoice,
confirmation
receipt and
finally will place
order.
2.0 Medium Registered UC_5 Place Order Privileged
customer “will”
order for
medicines.
1.0 Medium The system UC_6 Place Order Request
“shall” provide a  
registration
process.
3.0 Medium The System UC_7 Create Action
“shall” generate
an action event
for a
 corresponding
administrator
when a request
is placed for
updating of
orders or
customer details
etc.
1.0 Medium CA “shall” UC_8 Accept Customer Request
accept, reject UC_9 Reject Customer Request
and temporarily UC_10 View Customer Request
waive the
requests on the
basis of
credentials
provided.
1.0 Medium System “shall” UC_11 Update Request
update the
customer’s
Request.

1.0 Medium System “shall” UC_12 Change Payment Details,

process UC_13 Change Status, 
different types UC_14 Change Personal Details
of updating e.g.
updating of his
personal, or
shipping details.
1.0 Medium A customer UC_15 View Customer Details
“shall” view his
details for
verification
purposes
1.0 Medium System “shall” UC_16 Search Customer
search any
customer
details.
2.0 Medium User “shall” UC_17 Search Orders
view the status
of their orders
by providing the
Order Number
2.0
2.0 Medium Customer UC_19 View All Orders
“shall” place the UC_20 Manage Order
request for the UC_21  
cancellation of
the order. But  
all these
updating and
cancellation
requests are to
be viewed by
the Order
Administrator in
order to accept,
reject, or waive
them.
1.0 Lowest A customer UC_22 Login,
“shall” login to UC_23  
the system and
can change his
password
3.0 Lowest Corresponding UC_24 View Action, 
administrator
“shall ” view his
Action List
containing
different
actions, and
correspondingly
process these
pending actions
3.0 Lowest When the UC_25 Delete Action
action
processing is
completed or if
the action is just
a notification
message then
administrator
“shall” delete
these actions
from the action
list.
1.7 Requirements Traceability Matrix

Sr# Para System Build Use Case Name Category

# Specification Text
1 1.0 A customer “will” B1 Place Order Business
place order for
goods
2 1.0 A customer “shall” B1 Registration Request Business
register himself to
the system
3 1.0 The system “shall” B1 Place Customer Request Business
provide a
registration
process.
4 1.0 CA “shall” accept, B1 Accept Customer Request Business
reject and Reject Customer Request
temporarily waive View Customer Request
the requests on the
basis of credentials
provided.
5 1.0 A customer “shall” B1 Login, Business
login to the system
and can change his
password
6 1.0 System “shall” B1 Update Request Business
update the
customer’s Request
7 1.0 System “shall” B1 Change Personal Details Business
process different Change Shipping Details
types of updating  
e.g. updating of his
personal or
shipping details.
8 1.0 A customer “shall” B1 View Customer Details Business
view his details for
verification
purposes
9 1.0 System “shall” B1 Search Customer Business
search any
customer details
10 2.0 Customer “will” B1 Pay For Order Business
make payment;
 through cash.
11 2.0 System “will” B1 Invoice Generation Business
generate invoice,
confirmation
receipt and finally
will place order

Use case diagram:

System Sequence Diagrams:
Login:
System instruction:
Search Medicine:
Information about Pharmacy:
Get information about System:
Simple Sequence of system: