“Medicine Home Delivery Website”

YOUNAS NABI 15-arid-3525

FAHEEM IQBAL 15-arid-3443
HAMMAD AHMED 15-arid-5752
ATIF NISAR 15-arid-3431

Department of Computer Sciences & Information Technology

Barani Institute of Management Sciences Rawalpindi
[2015-2019]

i
 “Medicine Home Delivery Website”

by

YOUNAS NABI 15-arid-3525

FAHEEM IQBAL 15-arid-3443
HAMMAD AHMED 15-arid-5752
ATIF NISAR 15-arid-3431

A FYP documentation submitted in partial fulfillment of

The requirement for degree of

Bachelor
in
Computer science

Department of Computer Sciences & Information Technology

Barani Institute of Management Sciences Rawalpindi
[2015-2019]

ii
 CERTIFICATION
I hereby undertake that this research is an original one and no part of this thesis
falls under plagiarism, If found otherwise at any stage, I will be responsible for the
consequences.
Name: Younas Nabi Signature: ______________
Registration Number: 15-arid-3525 Date: ______________
Name: Faheem Iqbal Signature: ______________
Registration Number: 15-arid-3443 Date: ______________
Name: Hammad Ahmed Signature: ______________
Registration Number: 15-arid-5752 Date: ______________
Name: Atif Nisar Signature ______________
Registration Number: 15-arid-3431 Date: ______________

Certified that the contents and form of thesis entitled “Medicine Home
Delivery Website” submitted by “Younas Nabi, Faheem Iqbal, Hammad Ahmed,
and Atif Nisar” has been found satisfactory for requirements of the degree.

Supervisor: Sir Seemab Zafar

Signature ___________
Date: ___________

iii
 DEDICATION

We would like to dedicate our work to our respected parents who have been
there to appreciate, support and push us up in our hard times throughout our
academic life .We also like to dedicate a part of our work to our respected and kind
teachers that making us able to think wide and sharp in all prospective life.

iv
 TABLE OF CONTENT

CHAPTER 1..................................................................................................................1

INTRODUCTION.........................................................................................................1

1.1 PROJECT OBJECTIVES..........................................................................................2

1.2 PROJECT OVERVIEW............................................................................................2

1.3 PROJECT SCOPE.....................................................................................................2

1.4 TOOLS FOR DEVELOPMENT...............................................................................3

1.4.1Back-end Tools and Technologies..........................................................................3

1.4.2Front-End Tools and Technologies.........................................................................3

1.4.3Other Tools and Technologies................................................................................3

1.5HARDWARE REQUIREMENT...............................................................................3

1.6 DEPLOYMENT........................................................................................................3

CHAPTER 2..................................................................................................................4

STUDY OF EXISTING SYSTEM...............................................................................4

2.1 EXISTING SYSTEM................................................................................................5

2.1.1 Disadvantages of the Existing Systems Process....................................................5

2.2 PROPOSED SYSTEM..............................................................................................5

2.2.1 Benefits of Proposed System..................................................................................5

CHAPTER 3..................................................................................................................7

REQUIREMENT ANALYSIS.....................................................................................7

3.1 SYSTEM REQUIREMENT SPECIFICATION.......................................................8

3.1.1Product Description.................................................................................................8

3.1.2Problem Statement..................................................................................................8
3.2 SYSTEM OBJECTIVES...........................................................................................8

3.3 SYSTEM REQUIREMENT......................................................................................8

3.3.1 Non Functional Requirements................................................................................8

3.3.1.1. Efficiency Requirement......................................................................................8

3.3.1.2. Reliability Requirement.....................................................................................8

3.3.1.3 Usability Requirement.........................................................................................8

3.3.1.4 Implementation Requirement..............................................................................9

3.3.1.5 Delivery Requirement.........................................................................................9

3.3.1.6Security.................................................................................................................9

3.3.1.7Availability...........................................................................................................9

3.3.2 Functional Requirements........................................................................................9

3.3.2.1 User.....................................................................................................................9

3.3.2.2 Admin................................................................................................................10

3.4 Use case Figure.......................................................................................................12

3.5 Use Cases................................................................................................................13

CHAPTER 4................................................................................................................17

SYSTEM DESIGN......................................................................................................17

4.1 INPUT AND OUTPUT DESIGN...........................................................................18

4.1.1 Input Design.........................................................................................................18

4.1.2 Output Design.......................................................................................................19

4.2 DATABASE............................................................................................................19

4.3 SYSTEM TOOLS...................................................................................................19

4.3.1. Front End.............................................................................................................19

4.3.2 Back End..............................................................................................................20

4.4 TABLES FIGRES...................................................................................................20

4.5 Sequence Models.....................................................................................................23

CHAPTER 5................................................................................................................30

SYSTEM TESTING....................................................................................................30

5.1 Testing the Medicine Home Delivery Website.......................................................31

CHAPTER 6................................................................................................................35

DESIGNATION MANUAL........................................................................................35

6.1 Registration.............................................................................................................36

CHAPTER 7................................................................................................................40

CONCLUSION AND FUTURE WORK...................................................................40

7.1 CONCLUSION.......................................................................................................41

7.2 FUTURE WORK....................................................................................................41

REFERENCES............................................................................................................42
 List of Tables

Table 3.5.1 USE CASE 1..............................................................................................13

Table 3.5.2 USE CASE 2..............................................................................................13
Table 3.5.3 USE CASE 3..............................................................................................14
Table 3.5.4 CASE 4.......................................................................................................14
Table 3.5.5 USE CASE 5..............................................................................................15
Table 3.5.6 USE CASE 6..............................................................................................15
Table 3.5.7 USE CASE 7..............................................................................................16
Table 3.5.8 USE CASE 8..............................................................................................16
YTable 5.1.1 Test Case Registration Account
………………………………………...31
Table 5.1.2 Test case Login...........................................................................................32
Table 5.1.3 Test case Add to cart..................................................................................33
Table 5.1.4 Admin Login..............................................................................................34
 List of Figures

YFigure 4.4.1 USER.....................................................................................................20

Figure 4.4.2 ITEMS DETAILS.....................................................................................21
Figure 4.4.3 ORDERS DETAIL...................................................................................21
Figure 4.4.4 ORDERS...................................................................................................22
Figure 4.4.5 COMPANY...............................................................................................22
Figure 4.4.6 CLASS......................................................................................................22
Figure 4.4.7 CATEGORY.............................................................................................23

YFigure 4.5.1 Sequence Model–Login.........................................................................24

Figure 4.5.2 Sequence Model–Manage user..................................................................25
Figure 4.5.3 Sequence Model–Manage Products...........................................................26
Figure 4.5.4 Sequence Model– Manage Records..........................................................27
Figure 4.5.5 Class Diagram...........................................................................................28
Figure 4.5.6 ER- Diagram.............................................................................................28

YFigure 6.2.1 Login......................................................................................................37

Figure 6.2.2 Error for login page with wrong id or password.......................................38
Figure 6.2.3 Home Page................................................................................................38
Figure 6.2.4 Contact Us.................................................................................................38
Figure 6.2.5 Admin Panel..............................................................................................38
 ACKNOWLEDGEMENT

I take this moment to thank Allah and Holy Prophet (Peace Be Upon Him),
Almighty for blessing us with his grace and taking our endeavor to a successful
culmination. We extend our sincere and heartfelt thanks to our esteemed guide
Mr. SEEMAB ZAFAR, for providing the right guidance and advice at the crucial
junctures and for showing the right way. We extend our sincere thanks to our respected
Head of department Sir ASIF KHAN, for allowing us to use the facilities available.
I would like to thank the other faculty members also, at this occasion. Last but not the
least, we would like to thank our friends and family for the support and encouragement
they have given us during the course of our work.

YOUNAS NABI

FAHEEM IQBAL

HAMMAD AHMED

ATIF NISAR
 CHAPTER 1

INTRODUCTION
 This project is a web based medicine home delivery system for an existing
shop pharmacy 24.Online delivery of medicine is the process whereby consumers
directly buy medicines from a seller, without an intermediary service, over the
Internet. It is a form of electronic commerce. This project is an attempt to provide the
advantages of online medicine home delivery to customers of a physical shop. It
combines the click-and-brick operations in a pharmacy business. It helps to buy the
products in the shop anywhere through Internet. Thus the customer will get the service
of online medicine home delivery from his/her favorite shop.

1.1 PROJECT OBJECTIVES

The objective of the project is to make a website to sale items in an existing
pharmacy shop. In order to build such a website complete web support need to be
provided. A complete and efficient website which can provide the online medicine
home delivery experience is the basic objective of the project.

1.2 PROJECT OVERVIEW

The central concept of the website is to allow the customer to shop virtually
using the Internet and allow customers to buy the medicines and other articles of their
desire from the store.
The Server process the customers and the items are shipped to the address
submitted by them. The website was designed into two modules first is for the
customers who wish to buy the articles. Second is for the pharmacist who maintains
and updates the information pertaining to the articles and those of the customers. The
end user of this product is an admin, an employee of the pharmacy where the
application is maintained and monitors for real-time queries of the online customers.
The website which is deployed at the customer database, the details of the items are
brought forward from the database for the customer view based on the selection
through the menu and the database of all the products are updated at the end of each
transaction.
1.3 PROJECT SCOPE:
 This system can be implemented to any shop in the locality or to multinational
branded shops having retail outlet chains. The system recommends a facility to accept
the orders Monday-Friday8.00 -19.00, Saturday 9.30-17.00 and Sunday 9.30-15.00 at a
home delivery facility which can bring ease in buying medicine for the customers.
The online portal provided a joy and ease to their customers, the shops won’t
be losing any more customers to the trending online shops such as flip cart or eBay.

1.4 TOOLS FOR DEVELOPMENT

Our website is based on the following tools and computer languages:

1.4.1Back-end Tools and Technologies

Microsoft SQL Server v17.9 2018

1.4.2Front-End Tools and Technologies

Microsoft visual studio 2017
ASP.Net 4.5
CSS
JavaScript 1.8.5
AJAX

1.4.3Other Tools and Technologies

Microsoft word 2013 (for documentation)

1.5HARDWARE REQUIREMENT
computers equipped with a Pentium 4 processor or higher, The computer must
have approximately 100MB of free hard drive space and 128MB of RAM.

1.6 DEPLOYMENT
Google chrome Version 75.0.3770.100 (Browser)
Server side operating system windows server 2008
Client side operating system Android, windows XP and above
 CHAPTER 2

STUDY OF EXISTING SYSTEM

 System analysis is the process of gathering and interpreting facts,
identifying problems and using the information to recommend improvements on
the system. System analysis is a problem solving activity that requires intensive
communication between the system users and system developers. System
analysis or study is an important phase of any system development process. The
system is viewed as a whole, the inputs are identified and the system is
subjected to close study to identify the problem areas. The solutions are given as
a proposal. The proposal is reviewed on user request and suitable changes are
made. This loop ends as soon as the user is satisfied with the proposal.

2.1 EXISTING SYSTEM

The current system for purchasing medicine is to visit the pharmacy manually.
People visit the pharmacy physically which require effort and time customer give the
prescription to the pharmacist ,she/he read the prescription and then collect medicine
from racks and generate bill by using Abuzar Point of sale system. Current system
process working on Abuzar and manage all selling and purchasing process.
1. It is less user-friendly.
2. User must go to shop and select products.
3. It is a time consuming process
4. Not in reach of distant users

2.1.1 Disadvantages of the Existing Systems Process

Do not have online home delivery system
Time consuming

2.2 PROPOSED SYSTEM

In the proposed system customer need not go to the shop for buying the
medicine. In the proposed system customer can visit website and order medicine
from home or office without visiting pharmacy physically so that they can save
their precious time.
 Customer can search medicine by name, category and manufacturer .Moreover
they can upload prescription provided by their doctor.
Website will increase sales of client since having internet access means
customers access to the pharmacy website from anywhere .In home delivery
medicine service customers are allowed to create account on the website in order to
purchase medicine, if they are familiar with medicine or they have a prescription
2.2.1 Benefits of Proposed System
User Friendly Interface
Friendly User Interface Ease to use for customers.
Market Available at Home
Buyer doesn’t need to go out and drive to store just sit in front of laptop or
mobile and reached to the market.
Product Replacement
Facility of replacement of product’s the undesired products or any issue
related to products.
Time Saving Method
Saves the customer and Administrator’s precious time
 CHAPTER 3

REQUIREMENT ANALYSIS
3.1 SYSTEM REQUIREMENT SPECIFICATION
3.1.1Product Description:
The system consists a web site which can provide the online medicine
home delivery service. Web site should be able to help the customer for
selecting his item and to help the owner in managing the orders from the
customers.
3.1.2Problem Statement:
As online home delivery system became a trend nowadays the regular
shops are losing their customers to online brands. Customers have effortless
shopping experience and saving time through online medicine home delivery
system. For competing with those online brands, if shops are providing an
online portal where their customers can shop through internet and get the
products at their doors it will increase the number of customers.

3.2 SYSTEM OBJECTIVES

To provide an online medicine home delivery web site for the same shop.

3.3 SYSTEM REQUIREMENT

3.3.1 Non Functional Requirements

3.3.1.1. Efficiency Requirement

When an online medicine home delivery system implemented customer
can purchase product in an efficient manner.

3.3.1.2. Reliability Requirement

The system should provide a reliable environment to both customers
and owner. All orders should be reaching at the admin without any errors.

3.3.1.3. Usability Requirement

The web site is designed for user friendly environment and ease of use.
3.3.1.4. Implementation Requirement
Implementation of the system using css, AJAX, ASP and html in front
end with Microsoft C# as back end and it will be used for database
connectivity. And the database part is developed by sql. Responsive web
designing is used for making the website compatible for any type of screen.

3.3.1.5. Delivery Requirement

The whole system is expected to be delivered in four months of time
with weekly evaluation by the project guide.

3.3.1.6 Database Security

Unauthorized person cannot access the panel and database, do
not read and write the information.

3.3.1.7Availability
This website will be available Monday-Friday8.00 -19.00, Saturday 9.30-17.00
and Sunday 9.30-15.00.

3.3.2 Functional Requirements

It is the primary requirements that are fulfilled by our web site .It’s allowing
the users, customers to use our website at the level of ease .The purpose of our
website is to provide the full information that is required to the user. Here is the
following requirement that is fulfilled by our system.

3.3.2.1 User

User Login
This feature used by the user/admin to login into system. A user/admin
must login with his user name and password to the system after registration. If
they are invalid, the user not allowed to enter the system.

- Username and password will be provided after user registration is confirmed.

- Password should be hidden from others while typing it in the field

Register New User

A new user will have to register in the system by providing essential
details in order to view the products in the system. The admin must accept a
new user by unblocking him.

- System must be able to verify and validate information.

- The system must encrypt the password of the customer to provide security.

Add To Cart
The user can add the desired product into his cart by clicking add to cart
option on the product. He can view his cart by clicking on the cart button. All
products added by cart can be viewed in the cart. User can remove an item
from the cart by clicking remove. After confirming the items in the cart the
user can submit the cart by providing a delivery address. On successful
submitting the cart will become empty.
- System must ensure that, only a registered customer can purchase items.

Search Products
The user can search the desired product. He can view description of
product. After confirming the items in the search user can select it into cart by
providing a delivery address.

Upload Prescription
The user can upload the prescription if user cannot read the doctor prescription.

3.3.2.2 Admin

Manage User
The administrator can add user, delete user, view user.
Manage Products
The administrator can add product, delete product, hide product and view product.

Manage Orders
The administrator can view orders and delete orders.
-The system must identify the login of the admin.
-Admin account should be secured so that only owner of the shop can access that
account
3.4 Use case Figure
 3.5 Use Cases

Table 3.5. USE CASE 1

Case Register
tor rs
cription The Use case is start when the actors signup.

e-condition The signup exists

-condition The signup in successful

Table 3.5. USE CASE 2

Use Case Login

tor Administrator/users
cription The use case is start when the actors will be Login to
the admin/user panel. It will be finish when the
actors will be logout.

e-condition The login exists

actor logged in.

-condition The logs in successful

 Table 3.5. USE CASE 3

Use Case Manage Database

tor Administrator
cription The use case is start when the actor will be Login and
access Manage Database.

e-condition records exist for editing.

actors logged in.
-condition records edited successfully.

Table 3.5. CASE 4

Use Case Manage Orders

tor Administrator
cription The use case is start when the actor will be Login and
access the mange orders.

e-condition order exist for editing.

actor’s logged in.
-condition record updated successfully.
 Table 3.5. USE CASE 5

Use Case View Products

tor Users
cription The use case is start when the actor will be online and
access the view posts. It will be finish when the
actors will be logout.

e-condition records exist for View.

-condition record viewed successfully.

Table 3.5. USE CASE 6

Use Case Upload prescription

tor Users
cription The use case is start when the actor will be Login and
access the Upload prescription. It will be finish
when the actors will be logout.

e-condition w table exists for upload prescription.

users logged in.

-condition Prescription uploaded successfully in database.

Table 3.5. USE CASE 7

Use Case Search Products

Actor Users
Description The use case is start when the actor will be
online and access the search products. It will be
finish when the actors will be logout.

Pre-condition The records exist for search.

Post-condition The record searched successfully.

Table 3.5. USE CASE 8

Use Case Add to cart

Actor Users
Description The use case is start when the actor will be
Login and access add to cart. It will be finish
when the actors will be logout.

Pre-condition The records exist for add to cart.

The actor logged in.

Post-condition Add to cart successfully.

 CHAPTER 4

SYSTEM DESIGN
 System design is the solution for the creation of a new system. This phase
focuses on the detailed of the feasible system. It emphasis on translating design.
Specifications to performance specification. System design has two phases of
development
-Logical design

-Physical design
During logical design phase the analyst describes inputs (sources), output
(destinations), databases (data stores) and procedures (data flows) all in a format that
meets the user requirements. The admin also specifies the needs of the user at a level
that virtually determines the information flow in and out of the system and the data
resources. Here the logical design is done through data flow diagrams and database
design. Physical design produces the working system by defining the design
specifications, which specify
Exactly what the candidate system must do. The programmers write the
necessary programs that accept input from the user, perform necessary processing on
accepted data and produce the required report on a hard copy or display it on the
screen.

4.1 INPUT AND OUTPUT DESIGN

4.1.1 Input Design:
Input design is the link that ties the information system into the world of its
user. The input design involves determining the inputs, validating the data, minimizing
the data entry and provides a multi-user facility. Inaccurate inputs are the most
common cause of errors in data processing. Errors entered by the data entry operators
can be controlled by input design. The user-originated inputs are converted to a
computer based format in the input design. Input data are collected and organized into
groups of similar data. Once identified, the appropriate input media are selected for
processing. All the input data are validated and if any data violates any conditions, the
user is warned by a message. If the data satisfies all the conditions, it is transferred to
the appropriate tables in the database. In this project the student details are to be
entered at the time of registration. A page is designed for this purpose which is user
friendly and easy to use. The design is done such that users get appropriate messages
when exceptions occur.
4.1.2 Output Design:
Computer output is the most important and direct source of information to the
user. Output design is a very important phase since the output needs to be in an
efficient manner. Efficient and intelligible output design improves the system
relationship with the user and helps in decision making. Allowing the user to view the
sample screen is important because the user is the ultimate judge of the quality of
output. The output module of this system is the selected notifications.

4.2 DATABASE
Database Design:
Databases are the storehouses of data used in the software systems. The data is
stored in tables inside the database. Several tables are created for the manipulation of
the data for the system. Two essential settings for a database are
The field that is unique for all the record occurrences.
The field used to set relation between tables.
Normalization is a technique to avoid redundancy in the tables.

4.3 SYSTEM TOOLS

The various system tools that have been used in developing both the front end
and the back end of the project are being discussed in this chapter.
4.3.1. Front End:
ASP.Net, HTML, CSS, JAVA SCRIPT and AJAX are utilized to implement the
frontend.
Active Server Pages (ASP.Net)
ASP.NET is a web application framework used to build web application and
web services.
Hyper Text Markup Language (HTML)
HTML is a syntax used to format a text document on the web.
Cascading Style Sheets (CSS)
CSS is a styling language-is set of rules to tell browsers how your web page
should look.
Java Script
JS is a dynamic computer programming language. It is most commonly used as
part of web browsers, whose implementations allow client-side scripts to interact with
the user, control the browser, communicate asynchronously, and alter the document
content that is displayed.
Java Script is used to create popup windows displaying different alerts in the
system like “User registered successfully”, “Product added to cart” etc.

4.3.2 Back End

The back end is implemented using SQL which is used to design the databases.

Microsoft C Sharp(C #)
C# is mostly used with Microsoft's .NET framework to design web forms, web
applications, windows applications etc. Website and web application development
using Asp
Microsoft SQL Server
SQL is a language used to build database applications that need to query
relational database. SQL has statements such as CREATE, SELECT, INSERT,
UPDATE, etc.
An application software called SQL server management studio is used to design tables
in SQL.
4.4 TABLES FIGRES
Figure 4.4. USER

Figure 4.4. ITEMS DETAILS

Figure 4.4. ORDERS DETAIL

Figure 4.4. ORDERS

Figure 4.4. COMPANY

Figure 4.4. CLASS

Figure 4.4. CATEGORY
4.5 Sequence Models

Login

Figure 4.5.1 Sequence Model-Login

MANAGE USERS

Figure 4.5. Sequence Model–Manage user

Manage Products

Figure 4.5. sequence Model–Manage Products

Manage Records

Figure 4.5. sequence Model– Manage Records

Figure 4.5. CLASS DIAGRAM

Figure 4.5.6 ER-DIAGRAM

 CHAPTER 5

SYSTEM TESTING
 Testing the software application is an important activity in software
development life cycle (SDLC). It helps in maintaining quality of the system.

5.1 Testing the Medicine Home Delivery Website

Table 5.1 Test Case Registration Account

Test Engineer Atif Nisar

Test Case ID TC1

Related UC1
UC/FR/NFR
Date 12-6-2019

Pre Requisite: None

Steps

1. Enter User Full Name.

2. Enter User password.
3. Enter confirm password.
4. Enter user email.
5. Enter address.
6. Enter phone number.
7. Click Register Button.

Status Pass

Test Case 1

Table 5.1 Test case Login

 Test Engineer Faheem Iqbal

Module Name Login

Test Case ID TC2

Related UC/FR/NFR UC2

Date 12-6-2019

Test Data User Email and password.

Steps

1. Enter Email.
2. Enter Password.
3. Click login button.

Provide valid User=faheem@gmail.com

username
Provide valid Password=1234
password
Expected Result User logs in

Actual result User logs in

Status Pass

Test Case 2
Table 5.1 Test case Add to cart

Test Engineer Hammad Ahmed

Test Case ID TC2

Related UC/FR/NFR UC18

Date 12-6-2018

Pre-Requisite: Logged in

Steps

1. Add to cart.
2. Go to cart.
3. Manage quantity.

User select a product and Product is added to the shopping cart.

clicks add to cart
Expected Product is added.

Actual Product is added

Status Pass

Test Case 3

Table 5.1 Table 5.1.4 Admin Login

Test Engineer Younas Nabi

Test Case ID TC2

Related UC/FR/NFR UC1

Date 12-6-2019

Test Data Admin Email and password.

Steps

1. Enter Email.
2. Enter Password.
3. Click login button.

User enters wrong Display message password or email is incorrect

password
User enters wrong email Display message password or email is incorrect

User enters valid email User log in successfully

and password
Expected result User log in successfully

Actual result User log in successfully

Status Pass
Test Case 4
 CHAPTER 6

DESIGNATION MANUAL
Design Manual
This chapter describes the designation manual of Medicine Home Delivery Website.

6.1 Registration
The interested visitor need to register.

Figure 6. Registration
 Figure 6.1. Error display without enter registration detail

Figure 6. Login Form

User need to login with valid user name and password.

Figure 6.2. Login

Figure 6.2. Error for login page with wrong id or password

Figure 6.2. Home Page

Figure 6.2. Contact Us

Figure 6.2.5Admin Panel
 CHAPTER 7

CONCLUSION AND FUTURE WORK

7.1 CONCLUSION
The project entitled online medicine home delivery website was
completed successfully. The system has been developed with much care and
free of errors and at the same time it is efficient and less time consuming. The
purpose of this project was to develop a web application for purchasing items
from a shop. This project helped us in gaining valuable information and
practical knowledge on several topics like designing web pages using html, css,
ASP and AJAX usage of responsive templates and management of database
using sql. The entire system is secured. Also the project helped us
understanding about the development phases of a project and software
development life cycle. We learned how to test different features of a project.
This project has given us great satisfaction in having designed an application
which can be implemented to any nearby shops or branded shops selling
various kinds of products by simple modifications. There is a scope for further
development in our project to a great extent. A number of features can be
added to this system in future like providing Moderator more control over
products so that each moderator can maintain their own products. Another
feature we wished to implement was providing classes for customers so that
different offers can be given to each class. System may keep track of history of
purchases of each customer and provide suggestions based on their history.
These features could have implemented unless the time did not limited us.

7.2 FUTURE WORK

The future work regarding this project can be that it can be enhanced by
making an android application for this system. Another future work can be that
this software application can be design for a specific organization.
We will add appointment system in our web site that will generate appointments for
the users looking for counseling.
REFERENCES

[1] https://en.wikipedia.org/wiki/pharmacy
[3] https://www.w3schools.com/htmL/html_scripts.asp
[4] https://www.youtube.com/ASP.net
[5] https://www.sehat.coms
[6] https://www.w3schools.com/css/default.asp