Medical Hub

[The best way to get your prescription]

A major project report submitted to

Rajiv Gandhi Proudyogiki Vishwavidhyalaya, Bhopal
towards partial fulfillment of
the degree of
MASTER OF COMPUTER APPLICATION
2019-2020

Guided By:
Ms. Sujata Gudge Submitted By:
Department of Shriya Mahajan
Information Technology

Department of Information Technology

SHRI G.S. INSTITUTE OF TECHNOLOGY AND SCIENCE
INDORE (M.P.)
 SHRI G.S. INSTITUTE OF TECHNOLOGY AND SCIENCE
INDORE (M.P.)

Recommendation
The major project report entitled “Medical Hub” submitted by Shriya Mahajan student of
MCA final year in the session 2019-20, towards partial fulfillment of the degree of Master of
Computer Applications of Rajiv Gandhi Proudyogiki Vishwavidhyalaya, Bhopal, is a
satisfactory account of their work and is recommended for the award of degree.

Ms. Sujata Gudge

Dr. Sunita Varma
Project Guide
HEAD
Department of Information
Technology Department of Information
Technology
SHRI G.S. INSTITUTE OF TECHNOLOGY AND SCIENCE
INDORE (M.P.)

Certificate
The major project report entitled “Medical Hub” submitted by Shriya Mahajan student of
MCA final year in the session 2019-20, towards partial fulfillment of the degree of Master of
Computer Applications of Rajiv Gandhi Proudyogiki Vishwavidhyalaya, Bhopal, is a
satisfactory account of their work and is approved for award of the degree.

Internal Examiner External Examiner

Date Date
 Acknowledgement
We are heartily pleased to acknowledge all those people who have helped us in the successful
completion of this project. With great pleasure we express our heartfelt gratitude to our
esteemed guide, Ms. Sujata Gudge Assistant Professor, Department of Information
Technology, S.G.S.I.T.S. Indore. Her persistent encouragement, perpetual motivation,
everlasting patience and valuable technical inputs in discussions have enabled the successful
completion of this project. Her invaluable help, advice and constant encouragement helped us
a lot and provide impetus to the progress of the project. We extend our profound
indebtedness to the Head of the department Ms. Sunita Varma, the word loses their worth
for her invaluable guidance, continuous encouragement and cooperation in every respect.

We sincerely wish to express our gratitude to all the members of staff of M.C.A. who
have extended their cooperation at all times and have contributed in their own way in
developing the project. Successful completion of a project is not an individual effort. It is an
outcome of the cumulative effort of a number of persons, each having his own importance to
the objective. We are thankful to our parents for being a constant source of encouragement in
all our endeavors. Indeed it is their support that helps us through the ups and downs of life.
The support and suggestion of our friends are worth appreciation and thankfulness. A blend
of gratitude, pleasure, great satisfaction and indebtedness is what, we feel to convey to all
those who have directly or indirectly contributed to the successful completion of our project
work.

Shriya Mahajan
 Abstract

The problem of exiting system is the customer have to go to medical store to buy medicines
even if they are not well and sometimes medicine is not available on that particular store so
customer can wait or go to the another store to buy medicine and it used to take lot of time to
get medicines.
The solution of the above problem is buy medicines online. Medical Hub is the web based
application in which customer can search medical store and upload prescription through which
he/she can order the medicines on the nearby medical store only which are registered on our
website.
In this system, Medical store registered to our website so it can receive the prescription which is
uploaded by customer. Medical store seen that prescription and sends medicine to the customer
at home. Medical store also gives some discount or offers to the customer who can order
medicine online.
 Table of Contents
Chapter 1. 1-3
Introduction
1.1 Preamble 1
1.2 Objective 1
1.3 Scope 1
1.4 Organization of Report 2-3

Chapter 2. 4-5
Literature Survey /Conceptual Framework
2.1 Technology Description 4
2.1.1 Java 4
2.2.1 My-SQL 4-5
2.2 Tools Used 5
2.2.1 Visual Paradigm 5
2.2.2 Eclipse IDE 5

Chapter 3. 8-13
Analysis
3.1 Feasibility Study 6
3.1.1 Technical Feasibility 6
3.1.2 Economic Feasibility 6
3.1.3 Operational Feasibility 7
3.2 Requirement Analysis 7
3.2.1 Functional Requirement 7-8
3.2.2 Non Functional Requirement 8
3.3 Information Flow Representation 9
3.3.1 Use Case Diagram of Proposed System 10-11
3.3.2 Class Diagram of Proposed System 12
3.3.3 ER- Diagram of Proposed System 13
3.3.4 Flow Chart of Proposed System 14

Chapter 4. 15-19
Planning
4.1 Software Project Planning 15
4.1.1 Project Complexity 15
4.1.2 Project Size 15
4.1.3 Structure Uncertainty 15
 4.1.4 Risk 16
4.2 Project Tracking and Scheduling 16
4.2.1 Timeline Chart of the Proposed System 16-17
4.3 Team Organization 17-18
4.4 Resources Planning 18
4.4.1 Hardware Requirement 18-19
4.4.2 Software Requirement 19

Chapter 5. 20-23
Design
5.1 System Architecture 20
5.1.1 Architecture Design 20-21
5.2 Interface Design 21-22
5.3 Activity Diagram of Proposed System 22-23

Chapter 6. 24-26
Implementation
6.1 Coding 24
6.2 Testing 24
6.2.1 Unit Testing 25
6.2.2 Integration Testing 26
6.2.3 System Testing 26
6.2.4 Black-box Testing 26

Chapter 7. 27
Conclusion
7.1 Conclusion 27
7.2 Limitations 27
7.3 Future Enhancement 27

References 28
Appendices 29-35
User Manuals 36
 Chapter 1
Introduction

This chapter includes introduction of the project, containing preamble, which is concerned
with preliminary statement of the origin of the problem. With the passage of time, how the
problems did become more complex and what necessary and possible efforts were taken into
account to solve the upcoming problems.

1.1 Preamble

Customer face following problems to buy medicine:

 Sometimes Customer did not get the medicine on particular store.
 If medical store is far more than his house it takes lot of time to go to the store.
 Person who is ill not able to go the store to buy medicine.

1.2 Objective

The main objective of this system to quick medicine delivery to the customers by nearest
medical store by uploading the prescription. We can search medical store and filter based on
customer reviews. Medical store get the request and send medicine to the customers.

1.3 Scope

The Website can be used to perform below activities: -

 This system not only provide good service to the customer like uploading prescription
online but help them to receive the order in a quick time without much delay so it can
reduce both time and effort.
 Medical store also provide some discount or offer to the customer who order medicine.
 Customers give feedback to the medical store, with the help of the feedback medical store
owner get an idea what are the services we should have to improve for customer.

-1-
1.4 Organization of Report
Chapter 1: Introduction

This chapter contains the brief description about the application. It also includes objective and
scope of application.

Chapter 2: Technology Description

This chapter contains the android studio framework needed for implementing the application
and explain the basic concepts for the development of the project and the technology to be
used.

Chapter 3: Analysis

This chapter includes the analysis phase of the system development process. It includes
Feasibility study, Requirement analysis, Specification, Functional Description of the system
with the help of Use-Case Diagram.

Chapter 4: Planning

This chapter deals with the management dexterity. It depicts the software planning process
adopted for the system. It describes the scheduling aspects with the help of the UML diagram
and project schedule table. It specifies the necessary hardware and software required for the
project.

Chapter 5: Design

This chapter elaborates the design process used. In this phase analyzed problem is framed into
a design. It describes the architectural design, data design and the interface design of the
system.

Chapter 6: Implementation

This chapter deals with the implementation part of the system.

Chapter 7: Conclusion

This chapter concludes the main part of the report with the conclusion section.

References

This chapter concludes the references from where the basic concepts have been referred.
 Chapter 2
Literature Survey/ Conceptual Framework

This Chapter gives the information about the tool and the basic resources that were used for the
Successful implementation of this project. The discussion is oriented towards delivering the
Fundamental knowledge of all the resources, tools that were utilized for developing the project.

2.1 Technology Description

2.1.1 Java

Java is an object-oriented, class-based concurrent secured and general-purpose computer

programming language. It is widely used robust technology, Java is Programming language
and platform.

Java is a high level, robust, object-oriented and secure programming language.

Platform: Any hardware or Software environment in which a program runs, is known as a

platform. Since Java has a runtime environment (JRE) and API, It is called a platform.

History

James Gosling initiated Java language project in June 1991 for use in one of his many set-top
box projects. The language, initially called ‘Oak’ after an oak tree that stood outside Gosling's
office, also went by the name ‘Green’ and ended up later being renamed as Java, from a list of
random words.

Sun released the first public implementation as Java 1.0 in 1995. It promised Write Once,
Run Anywhere (WORA), providing no-cost run-times on popular platforms.

2.1.2 My-SQL

My-SQL is an Oracle-backed open source relational database management system (RDBMS)

based on Structured Query Language (SQL). My-SQL Workbench is a visual database design
tool that integrates SQL development, administration, database design, creation and
maintenance into a single development environment for the My-SQL database system.

2.2. Tools Used

Strategic planning involves considering potential internal and external impacts on the
organizations and then mapping out an approach to deal with these impacts. From a marketing
standpoints, strategies consider customer needs, competitive factors and organizational
advantages. There are many tools they can use as they develop and implement ways to ensure
that the strategies and tactics developed are appropriate and plan can be effectively put into
action.

2.2.1 Visual Paradigm

Visual Paradigm is a software tool designed for software development teams to model
business information system and manage development processes. Visual Paradigm supports
key industry modeling languages and standards such as Unified Modeling Language
(UML), SoaML, BPMN, XMI, etc. It offers complete tool-set software companies need
for requirements capturing, process analysis, system design, database design, and etc.

2.2.2 Eclipse IDE

Eclipse is an integrated development environment (IDE) for developing applications using the
Java programming language and other programming languages such as C/C++, Python,
PERL, Ruby etc.
The Eclipse platform which provides the foundation for the Eclipse IDE is composed of plug-
ins and is designed to be extensible using additional plug-ins. Developed using Java, the
Eclipse platform can be used to develop rich client applications, integrated development
environments and other tools. Eclipse can be used as an IDE for any programming language
for which a plug-in is available.
 Chapter 3
Analysis

Analysis is a step of the software development life cycle that results in the specification of
software’s operational characteristics (Function, data and behavior). The activities performed
during analysis indicate the software’s interface with other system elements.

3.1 Feasibility Study

Feasibility study is an analysis of how successfully a project can be completed, accounting for
factors that affect it such as economy, technology, legal and scheduling factors. A project
manager uses feasibility studies to determine potential positive and negative outcome of a
project before investigating a considerable amount of time and money into it.

3.1.1 Technical Feasibility

The technical feasibility assessment is focused on gaining an understanding of the present

technical resources of the organization and their applicability to the expected needs of the
proposed system. It is an evaluation of the hardware and software and how it meets the need
of the proposed system. So after being ensured, we can say yes the project is technically
feasible.

3.1.2 Operational Feasibility

Operational feasibility is a measure of how well a proposed system solves the problems, and
takes advantage of the opportunities identified during scope definition and how it satisfies the
requirements identified in the requirements analysis phase of system development. The
operational feasibility assessment focuses on the degree to which the proposed development
projects fits in with the existing business environment and objectives with regard to
development schedule, delivery date, corporate culture and existing business processes
3.1.3 Economical Feasibility

Economic feasibility is the compulsory part of the feasibility study in which we find out cost
of development, resources (including men, machine and money) required during development
of the project and ensure that the project will be beneficial for both the parties’ software
engineer and user. The project implemented is economically feasible because the resources
and the tools used are of very less cost. The development of the project also requires very less
resources. The software Developed Is Scalable In The Future.

3.2 Requirement Analysis and Specification

Requirements analysis involves frequent communication with system users to determine

specific feature expectations, resolution of conflict or ambiguity in requirements as demanded
by the various users or groups of users, avoidance of feature creep and documentation of all
aspects of the project development process from start to finish. Requirements analysis is a
team effort that demands a combination of hardware, software and human factors engineering
expertise as well as skills in dealing with people. Requirements of the project were to secure
the user data from unauthorized users to read or modify it. Besides this core process, it also
should have a very user friendly interface to handle all the operations of the project very
easily.

3.2.1 Functional Requirements

Functional Requirement defines what a system is supposed to do. It defines the function of a
system and its components. A function is described as a set of inputs, the behavior and
outputs.

The system must provide following functionalities:-

User Can:-

 Registration/Login user.
 Upload Medical Prescription and order medicine.
 Give feedback to the medical store.
Medical Store Can:-

 Registration/Login.
 Receive prescription and receive order request to the users.
 Provide Discount or offer to the customers who order to medicines.

3.2.2 Non-Functional Requirements

Non-Functional Requirement is a requirement that specifies criteria that can be used to judge
the operation of a system, rather than specifies behaviors. They are considered with functional
requirements that define specific behavior or functions.

 Availability
 Recoverability
 Authentication
 Security
 Performance
 Confidentiality
3.3 Information Flow Representation

3.3.1 Use case:-

A use case diagram at its simplest is a representation of a user's interaction with the system
that shows the relationship between the user and the different use cases in which the user is
involved. A use case diagram can identify the different types of users of a system and the
different use cases.

Use-case diagram notations

Use-case:

Use cases are used to represent high-level functionalities and how the user will handle the
system. A use case represents a distinct functionality of a system, a component, a package, or
a class. It is denoted by an oval shape with the name of a use case written inside the oval
shape.

UML Use-Case Notation

Actor:

It is used inside use case diagrams. The actor is an entity that interacts with the system. A user
is the best example of an actor. An actor is an entity that initiates the use case from outside the
scope of a use case.

UML Actor Notation

3.3.1 Use Case diagram of Proposed System:

Fig 3.1 Use Case Diagram of Admin

Fig 3.2 Use Case Diagram of User
3.3.2 Design Class Diagram of Proposed System:

Class diagram in the Unified Modeling Language (UML) is a type of static structure diagram
that describes the structure of a system by showing the system's classes, their attributes,
operations (or methods), and the relationships among objects.

Fig. 3.3 Class Diagram of Proposed System

3.3.3 ER-diagram of Proposed System:
An ER model is a design or blueprint of a database that can later be implemented as a
database. The main components of E-R model are: entity set and relationship set.

Fig. 3.4 ER Diagram of Proposed System

3.3.4 Flow Chart of Proposed System:

Fig. 3.5 Flow Chart of Proposed System

 Chapter 4
Planning

This section deals with the management dexterity. It depicts the software planning process
adopted for the system. It describes the scheduling aspects with the help of the time line chart
and project schedule table. It specifies the necessary hardware and software required for the
project.
4.1 Software Project Planning

The software project management process begins with a set of activities that are collectively
call project planning that involves estimations. Software cost and effort estimation will never
become an exact but can be transform from indistinguishable to as series of systematic steps.

Following things have been estimated before the software development.

4.1.1 Project Complexity

It has strong efforts on uncertainty that is inherent in planning. Our project belongs to
category of evolutions project, as the requirement are very large. An expert team usually
develops such system.

4.1.2 Project size

It is another that can affect the accuracy of estimates. As the project size increases; the
interdependencies among various elements of the software grows rapidly. Therefore, it is
essential that the project size in lines of code.

4.1.3 Structure Uncertainty

The Structure refers to the degree to which requirements have been solidified, the case with
which function can be compartmentalized, and the hierarchical nature of information that
must be processed.
4.1.4 Risk

Risk is measured by the degree of uncertainty in the quantitative estimates established for
resources, cost and schedule.

4.2 Project Tracking and Scheduling

Tracking can be accomplished by conducting periodic project status meetings where in every
Team member reports progress and problems, evaluation results of the reviews conducted
throughout, comparing actual start due to the planned star date for each project task etc. The
project tracking of the proposed system. Scheduling begins with process decomposition.

Table 4.1 Shows the Project Tracking of the Proposed System

S. No. Work Task Description Timeline(week)

1 Requirement Complete specification of 1

Specificatio the system.
n
2 Implementat Implementation of the 3
ion of the project.
system

3 Integration The system should be 2

Testing thoroughly tested by running
all the test cases written for
the system.

4 Final Issues find during the previous 1

Review milestones are fixed

4.2.1 Timeline Chart of the Proposed System

A timeline chart can be developed for the entire project. Alternatively, separate charts can be
developed for each project function or for each individual working on the project. As, a
consequences of this input, a timeline chart is generated also called Gantt chart.
 A Gantt chart is a graphical depiction of the project schedule. A Gantt chart is a type of bar
chart that shows the start and finish dates of the several elements of a project that includes
resources, milestone, tasks and dependencies.

Testing and Final

Integration Testing

Process Implementation

Detailed Design

Requirement
Analysis

Time (in weeks)

Fig 4.1 Time Line Chart of the Proposed System

4.3 Team Organization

There are almost many human organization structure for software development. Their best
team structure depends on the management style of an organization; the number of people
who populate the team and overall problem difficulty are asfollows:
i. Democratic Decentralized (DD)

In our project we are using Democratic Decentralized (DD) team. This software team has no
permanent leader rather “task coordinators are appointed for short durations and then replaced
by others who may coordinate different task”. Decisions on problems approaches are made by
group Conesus. Communication among team member is horizontal.

ii. Controlled Decentralized (CD)

This software engineering team has defined leader who coordinate specific task and secondary
leaders that have responsibility for the sub-tasks. Problem solving remains a group activity,
but implementation of solutions is portioned among subgroups by team leader.
Communication among subgroups may be vertical or horizontal.

iii. Controlled Centralized (CC)

Top level problem solving and internal team coordinate are managed by a team leader.
Communication between the team leader and the team members is vertical.
Thus our software team is democratic decentralized as there is no leader, any of the team
members can give the innovative idea and the best is chosen to be implemented. Decision is a
group activity, and both being an integral part of it. Communication among the team is
horizontal. The DD team structure is applied to problem with relatively lower modularity. The
DD team structure permits generation of free ideas hence leads to innovation and helps in
countering complex problem.

4.4 Resource Planning

Resource planning is the step in writing a business plan that involves identifying the resources
that a proposed business needs to succeed. This includes the hardware and software
requirements of the system as follows:

4.4.1 Hardware Requirements:

 Ram: 4GB or more

 System Type: 64-bit operating system
  Processor: Intel Core i3 or higher (2.10 Ghz)
 Hard disk: 40 GB or more

4.4.2 Software Requirements:

 Front End: HTML, CSS, JavaScript

 Back End: My-SQL
 Operating System: Windows 7 or later
 Tools and Technology: Java, Eclipse IDE
 Chapter 5
Design

Design is a meaningful engineering representation of something that is to be building. It can

be traced to a customer’s requirement and at the same time accessed for quality against a set
of predefined criteria for superior designing. Object Oriented transforms the analysis model
into a design model that serves as a blueprint for the software construction.
5.1 System Architecture

A system architecture or systems architecture is the conceptual model that defines

the structure, behavior, and more views of a system. An architecture description is a formal
description and representation of a system, organized in a way that supports reasoning about
the structures and behaviors of the system.

5.1.1 Architectural Design

It can be defined as the set of structures needed to reason about the software system, which
comprise the software elements, the relations between them, and the properties of both
elements and relations. It is used to represent the structure of the data and program
components that are required to build a computer-based system. The architectural design is
responsible to improve partitioning and allow the reuse of design by giving solutions to
frequently occurring problems. It also describes a particular way to configure a collection of
components (a module with well-defined interfaces, reusable and replaceable) and connectors
(communication link between modules).

Model View Presenter (MVP) is an architectural pattern that devices and inherits most
properties from the Model View Controller (MVC) pattern. The main difference is the
responsibility of the middle layer presenter/controller. While the controller defines behavior
and typically has multiple views that are controlled by it. The presenter in most cases has a
one to one relationship with its view. The other difference is that the view in MVC can
communicate directly with the model but in MVP the presenter is responsible for all
“communication” between the view and the model.

Three-Tier Architecture consists of:-

1. View

2. Presenter
3. Controller

1. View Layer

The view is a rendering layer that shows information to the user and all input events like
button click, text insertion, passes to presenter etc.

2. Presenter Layer

The presenter is responsible for processing the view input events and for querying data from
the model. When data arrives to the presenter, it is processed there and bound to view.

3. Model Layer

The model is everything that we can imagine with data sources- API, Databases, Files, etc.
The model is responsible for retrieving data and can be responsible for listening to data
change (like in a database) and inform the presenter about it.

5.2 Interface Design

User interface design, sometimes also called user interface engineering, is the design of
software application and websites with the focus on the user experience and interaction.
Unlike traditional design where the goal is to make the object or application physically
attractive, the goal of user interface design is to make the user interaction experience as
simple and intuitive as possible what is often called user-centered design. User interface
design often fine and invisible.
 There are four main interfaces in the proposed system names as follows:-

1. Registration

2. Login

3. User Dashboard

4. Medical Store Dashboard

5. Admin Dashboard

5.3 Activity Diagram of Proposed System

Activity diagram is basically a flowchart to represent the flow from one activity to another
activity. The activity can be described as an operation of the system.

The control flow is drawn from one operation to another. This flow can be sequential,
branched, or concurrent. Activity diagrams deal with all type of flow control by using different
elements such as fork, join, etc.

Notations of activity Diagram:-

Stop Point/Initial Point

Activity Activity

Action Flow

Decision Symbol
Fig 5.1 Activity Diagram of Proposed System
 Chapter 6
Implementation

Implementation deal with the actual development of the project. This combines the concept of
coding and testing of the developed system. Coding refers to the converting design blue print
into a computer understandable language like C, C++, Java etc. testing refers to the
identifying errors and bugs into the code. Functional requirements define what a system is
supposed to do. It defines the function of a system and its components. A function is
described as a set of inputs, the behavior, and outputs.

6.1 Coding

Coding is the phase of a software development project where developers actually input the
source code into a computer that will be compiled into the final software program. Source
code is the high level language that is typed into an IDE (interactive development
environment) and stored in a text file on the computer. This text file is compiled into machine
code, which are the instruction actually understood by the computer. Whole coding of
developed system is done under the following Module:

1. Customer Module
2. Admin Module
3. Medical Store Module.

6.2 Testing

System testing of software or hardware is testing conducted on a complete, integrated system

to evaluate the system’s compliance with its specified requirement. System testing falls
within the scope of box testing, and as such, should require no knowledge of inner design of
the code or logic.
6.2.1 Unit Testing

While coding, the programmer perform some tests on that unit of program to know if it is
error free. Unit testing helps us to developers to decide that individual units of the program
are working as per requirement and error free. In this, project individual components is
tested independently.

Table 6.1 Shows the Unit Testing of the Proposed System:

S. No. Scenarios Expecte Actual Status

d Result Result
1 Check whether Successful Successful Successful
application is running
or not
2 Check whether user is Successful Successful Successful
able to register and
login or not
3 Check whether user Successful Successful Successful
is able to upload
prescription or not
4 Check whether Successful Successful Successful
Medical store owner
is able to receive
prescription or not
5 Check whether Successful Successful Successful
Medical store owner
is able to send order
or not
6.2.2 Integration testing

Testing of all integrated modules to verify the combined functionality after integration is
termed as integration Testing. Modules are typically code modules, individual applications,
client and server application on a network, etc. This type of testing is especially relevant to
client/server and distributed system.

6.2.3 System Testing

System testing ensures that the entire integrated software system meets requirements. It tests
a configuration to ensure known and predictable results. An example of system testing is the
configuration oriented system integration test. System testing is based on process
descriptions and flows, emphasizing pre-driven process links and integration points.

6.2.3 Black-Box Testing

Black box testing, also known as Behavioral Testing, is a software testing method in which
the internal structure/design/implementation of the item being tested is not known to the
tester. These tests can be functional or non-functional, though usually functional.

In Device Allocation system user gave different inputs and check the corresponding output.
Whole system and individual modules are tested on the basic of inputs and corresponding
outputs.
 Chapter 7
Conclusion

7.1 Conclusion

The project provides an alternative user interface with the most effective way to order
medicine. It gives to user to upload prescription so user can order the medicine which is
prescribed by doctor. User get receive the medicines at home in less time and less efforts. So,
the overall implementation cost is cheap and it is affordable for a common person.

7.2 Limitations

 Internet connectivity is required.

 System may need maintenance after installation.
 User is necessary to upload prescription.

7.3 Future Enhancements

At an age where everything is going online and people are buying almost everything from
grocery to gadgets on web stores, it is time that the medical and pharmaceutical market catches
up to the trend and indeed it has. You can now fulfilling all your medicinal needs online, at
well.
This website is user friendly and provide ease to customer also saving their precious time and
even money.
 References

[1] https://www.javatpoint.com/java-tutorial

[2] https://www.w3schools.com/java/

[3] https://www.journaldev.com/3793/hibernate-tutorial

[4] https://www.eclipse.org/getting_started/

[5] https://www.tutorialspoint.com/spring/spring_web_mvc_framework.htm

[6] https://www.youtube.com/watch?v=BkRZfxznaOo
 Appendix A
Screen Shots

1. User Dashboard:

It is a home page of Customer Dashboard where he has option to login/Register and he

also search medical store which are register in our website. He also visit our website to
find what facilities we are providing to the customer.

Screenshot No. 1: User Dashboard

2. Medical Store:

It is Medical Store page which shows medical store images who are registered to our website and
they are providing medicine to the customer.

Screenshot No. 2: Medical Store

3. Contact and about us:

It is a Contact and about us page if customer visit to our website and contact to owner then he
contact from this page. It shows what facility we are providing.

Screenshot No. 3: Contact and about us

4. User Registration

It is a User Registration page user have to register to our website and upload prescription to
get medicine at home. In this form user have to fill some details like name, email, mob no
and address.

Screenshot No. 4: User Registration

5. Login Page:

It is a User Login page after the user Registration is complete than this page is open. In this
page customer have just to enter email which he had enter at the time of registration after
that he enter password for login.

Screenshot No. 5: Login Page

6. Admin Dashboard:

It is a Admin dashboard where admin can manage medical stores, shows delivery status,
view user details, see feedback details and medical store details.

Screenshot No. 6: Admin Dashboard

7. Medical Dashboard:

It is medical Store owner dashboard where medical store owner see the details of customers
who have to order medicines, and see the prescription which shows in view order option.
Medical store owner receive prescription and send medicines to the customer.

Screenshot No. 1: Medical Dashboard

 Appendix B
Glossary / Acronyms used

 Dissertation- A treatise advancing a new point of view resulting from research; usually a
requirement for an advanced academic degree.
 Project- Any piece of work that is undertaken or attempted. A planned undertaking.
 Report- A written document describing the findings of some individual or group.