Chapter 1

INTROUDUCTION

1.1 ABOUT PROJECT

‘PET SEARCH’ is used for proposing adoption of pets and pet’s health care service,
which provides an efficient way to keep track on pet’s health. In the age of Smart phones and
technology where one can have applications on every aspect of our lives, having an
application that addresses treating of pets in their home or in their current location is a must.
The PET SEARCH is a WEB BASED and android (WEB-VIEW) application that provides
an efficient and time saving method for the users to get treated their pets according to their
convenient place or location. This application also provide a platform for pet’s seller and
buyers, if owner wish to sell their pet they can post the pet information. Pet lovers can search
a pet and send a request for pet owners. Nearby search option is provided for veterinary
hospital, medical store and pet shop, this activity will be done based on Google map API
(longitude and latitude).

1.2 PROBLEM DEFINATION

‘PET SEARCH’ application is being developed to lessen the responsibility of the
owner regarding the pet’s health condition, diet plans, taking doctor’s appointment for its
monthly health checkups and to get relevant information about how to keep up the pets health
and tips for keeping the pets clean and hygiene.

1.3 OBJECTIVES

 The main objective is to provide an easy and simple platform for buying and selling
of pets.

 Suggestions from different doctors can be taken regarding the pet’s health and
vaccination.

 Provide a platform to get monthly reminders regarding health checkups and

vaccination for pets.

 Searching for variety of breeds in all categories of pets.

 Nearby search option for veterinary hospital, medical store and pet shop, it saves the
owner’s time.
 Chapter 2
LITERATURE SURVEY

1. Petango

 Focuses on adopting homeless pets and providing shelter for those pets.
 Also make a way for selling the pets.

PET SEARCH:
 Provide a platform for sellers to sell the pets.
 Buyers can search for required breeds of pets.
 Buyers can look for the breeds within their locality.

2. All Paws

 Provide a platform for searching pets and adopting the pets.

 Mainly focuses to rescue homeless, abused and neglected dogs and cats.
 Also provide necessary medical care or behavioral help they need.

PET SEARCH:
 Pet owner can consult doctor and can get the prescription regarding pet’s
health.
 Get reminder about monthly vaccination.
 Chapter 3
REQUIREMENT ANALYSIS AND SPECIFICATION

3.1 Introduction
The introduction of the Software Requirements Specification (SRS) provides an
overview of the entire SRS with purpose, scope, definitions, acronyms, abbreviations,
references and overview of the SRS. The aim of this document is to gather and analyze and
give an in-depth insight of the complete PET SEARCH by defining the problem statement in
detail. Nevertheless, it also concentrates on the capabilities required by businessmen and their
needs while defining high-level product features. The detailed requirements of the PET
SEARCH are provided in this document.

3.2 Purpose
The purpose of the document is to collect and analyze all assorted ideas that have
come up to define the system, its requirements with respect to consumers. Also, we shall
predict and sort out how we hope this product will be used in order to gain a better
understanding of the project, outline concepts that may be developed later, and document
ideas that are being considered, but may be discarded as the product develops.
In short, the purpose of this SRS document is to provide a detailed overview of our
software product, its parameters and goals. This document describes the project's target
audience and its user interface, hardware and software requirements. It defines how our
client, team and audience see the product and its functionality. Nonetheless, it helps any
designer and developer to assist in software delivery lifecycle (SDLC) processes.

3.3 Scope

This SRS is also aimed at specifying requirements of software to be developed but it

can also be applied to assist in the selection of in-house and commercial software products.
The standard can be used to create software requirements specifications directly or can be
used as a model for defining an organization or project specific standard. It does not identify
any specific method, nomenclature or tool for preparing an SRS. This document represents
specification of the SCM system requirements. It serves as the baseline document on which
the subsequent software development life cycle phases are built.
1. The users of this application find an easy way to take care of their pets, and get
monthly reminders for their pet’s health checkups.
2. Helps in taking doctor’s appointment to get the pets health checkups on time even in
our busy schedule.
 3. As it’s a Web application it can be opened from any device and the users can check
for the updates regarding their pet’s health, doctor’s appointments and searching for
different breeds of pets whenever needed.

3.4 Definitions, Acronyms, and Abbreviations

User: One who wishes to use this application.

Owner: One who uploads the details of pets and share his location.
Doctor: Receives the request from the user and sends the prescription and date of
appointment.
Medical stores: Provides the necessary medicines and food for the pets.

3.5 Overview

The remaining sections of this document provide a general description, including

characteristics of the users of this project, the product's hardware, and the functional and data
requirements of the product. General description of the project is discussed in section 2 of
this document. Section 3 gives the functional requirements, data requirements and constraints
and assumptions made while designing the PET SEARCH. It also gives the user viewpoint of
product. Section 3 also gives the specific requirements of the product. Section 3 also
discusses the external interface requirements and gives detailed description of functional
requirements. Section 4 is for supporting information.

3.5.1 Overall Description

This document contains the problem statement that the current system is facing. It further
contains a list of the businessmen and users of the proposed solution. It also illustrates the
needs and wants of the pet owner is identified. It further lists and briefly describes the major
features and a brief description of each of the proposed system. The following SRS contains
the detail product perspective. It provides the detail product functions of PET SEARCH with
user characteristics permitted constraints, assumptions and dependencies and requirements
subsets.
The main objective of the project is to lessen the responsibility of the owner regarding the pet’s
health condition, diet plans, taking doctor’s appointment for its monthly health checkups and to get
relevant information about how to keep up the pets health and tips for keeping the pets clean and
hygiene.

3.5.2 Product Perspective

Proposed system mainly provide rich user interface to access the website and also
provides a user friendly and advance technology to enhance the user services .This
application is also provide a platform for pet’s seller and buyers, if owner wish to sell their
pet they can post the pet information where pet lovers can search a pet and send a request for
pet owners. Nearby search option for veterinary hospital, medical store and pet shop, this
activity will be done based on Google map API (longitude and latitude). 
3.5.3 Product Functions
The application provides the functionalities like:
 Location Identifier
 Nearest Hospital Notify
 GPS tracking

3.5.4 User Characteristics

User/Owner: User is the one who uses the application and upload his pet details and
can also find the near by hospitals and consults the doctor.
 Can have own account.
 Upload pet details.
 Find near by hospitals.
 Consult doctors.
 Approve or rejects buyers request.

Doctor: Doctor, view the pet’s health status and provide prescription and appointment
if needed.
 View pet’s health report.
 Gives prescription.

Entrepreneur: View the pet details and also request from the sellers or buyers and
then approve or reject their requests.
 View pet details.
 View request
 Approve or reject request.

Medical shop: View requests and provides the medicines.

 View request.
 View medicine.
 Approve or reject request.

3.5.5 General Constraints

The system has many constraints. For example, the system must be web-based and all
tools must be compliant with .Net technologies, i.e., We must use PHP and JAVASCRIPT as
programming language and MS SQL as DBMS. Users must have register first on site as user
then can login into the application.
3.5.6 Assumptions and Dependencies

PET SEARCH must be compatible with all type of versions if not possible to ensure
compatibility in one package, create different package per version (or version range) basis.

3.8 Specific Requirements

Specific requirements will be full fill in PET SEARCH extension.

Requirement of this extension is written in priority-wise.
Specific requirements are categories on following sections:
 External Interface Requirements,
 Functional Requirements,
 Use Cases,
 Class / Objects,
 Non Functional Requirements,
 Inverse Requirements,
 Design Constraints,
 Logical Database Requirements, and
 Other Requirements.

3.9 External Interface Requirements

User Interfaces: The system is a web base system so, it will interact with its users with
web components interface. The users move through pages containing activities or
direction to some other activities.

3.9.1 Hardware Interfaces

Processor : Pentium I or above.
RAM : 128 Mb or above.
HDD : 20 Gb or above.

3.9.2 Software Interfaces

 Operating system : Windows 7 and above.
      Coding Language :  ASP.Net.
    Data Base             :  SQL Server 2008
Tool : Visual studio 2010
 3.10 Functional Requirements

Pet Search has multiple functional requirements.

3.2.1.1 User Login

3.2.1.1.1 Introduction: User is a login enabled entity means for accessing resources
user must have login first using login function.
3.2.1.2 Inputs:
 Email ID
 Password
3.2.1.1.3 Processing: After inputting the email and password there must be validation
3.2.1.1.4 Outputs: If validation succeed then vendor get their account access
otherwise show them some error message on login window.
3.2.1.1.5 Error Handling: There must be client side and server side error handling.

3.2.2.2 User Registration

3.2.2.1.1 Introduction: If merchant is not register yet then a registration function will
invoke
3.2.2.1.2 Inputs:
 Name
 Email
 Contact number
 Password
 Confirm password
3.2.2.1.3 Processing: Registration functionality will save all the details and send a
request to admin for approval.
3.2.2.1.4 Outputs: Show message on successful save of account request after approval
send an approved message to vendor.
3.2.2.1.5 Error Handling: Same email can’t be registered twice.

3.11 Non-Functional Requirements

3.11.1 Performance Requirements:

The product should support the end users requirements. The product is capable of
processing when the large numbers of files are provided as input and also it must be
interactive and the delays involved should be less .So in every action-response of the system,
there are no immediate delays.
3.11.2 Safety and Security Requirements:

The system should be designed in a secured way by applying safety measures.

Information transmission should be securely transmitted to nodes without any changes in
information. Special exception handling mechanism should be in place to avoid system
errors.

3.11.3 Reliability:
 The system must provide a password enabled login to users to avoid any
foreign entity changing the data in the system.
 The system should not update the database for any failed processes.

3.11.4 Usability
 The system must be easy to use by the entire user such that they do not
need to read and extensive amount of manuals.
 The system must be quickly accessible by the entire user.
 The system must be intuitive and simple in the way it displays all the
relevant data and relationship.
 Chapter 4
SYSTEM DESIGN

4.1 Introduction
4.1.1 Scope:
The system Design (SD) describes how the functional and non-functional
requirements gathered in the requirement phase, preliminary user-oriented functional
design transform into more technical system specifications from which the system is
built. This phase describes the design goals and considerations, provides a high-level
overview of the system architecture, and describes the data design associated with the
human-machine interface and operational scenarios.

4.1.2 Overview:

The system design documents and tracks the necessary information required to
effectively define architecture and design of PET SEARCH system in order to give the
development team guidance on the architecture of the system to be developed. Design
documents are incrementally and iteratively produced during the system development life
cycle, based on the particular circumstances of the PET SEARCH project and the
audience is the project manager, project team and development team. Some portion of
this document such as the User Interface may be shared with the user and other actors
whose input to UI is needed.

4.2 System Architecture

System architecture is conceptual model that defines the structure, behavior and more
views of the system. An architecture description is a formal description and representation of
a system, organized in way that supports reasoning about the structures and behavior of the
system.
 4.2.1 Architecture Design
The architecture design defines the structure, behaviour and the various views of the PET
SEARCH system. This system contains three tire architecture of the PET SEARCH is:

BOOTSTRAP

MySQL
JAVA SCRIPT
HTTP SQL
WEB
BROWSER

DATABASE
WEB SERVER SERVER
MONITOR HTML TABLE
SCREEN

4.2.3 User Interface Design

User interface design provides a simple form of authentication process through registration
and login pages given especially to users. Once user register and login into the system they
would search for their pets or can post about their pets.
4.2.4 Workflow:

START

ENTER
CREDENTIALS

VALIDATE

SELECT DATA
LOAD DATA

STORE IT IN DB

4.2.5 Detailed DFD

Level 0 DFD

Upload Pet
Details

Privacy
preserving and
data
access

Find Near by Find

Veterinary Doctors
Hospitals
Level1 User

Register Users

Find Contact View

Hospitals Doctors Prescription

Upload pet View Approve/Reje

Login
details Requests ct Request

Pet
Details

Level1 Doc

Register Doctor

View Pet Give

Login
Details Prescription

Pet
Details

Level1 Entrepreneur
 Register Entrepreneur

Approve/Reje
Login Pet Details View request
ct Request

Pet
Details

Level1 medical shop

Medical
Register
Shop

View Approve/Reje
Login View Request
Medicine ct

Request

4.2.6 Activity Diagram

4.2.6.1 USER

New Users

No Yes

Register with details

Login to Application

No
Valid User

Yes

Upload Pet Details View request

Approve/Reject
Find Hospitals
Request

Contact details

View Prescription

logout

4.2.6.2 ENTREPRENUER
 New Enterprenur

No Yes

Register with details

Login to Application

No
Valid User

Yes

Pet Details

Send Details

Approve/reject

logout

4.2.6.3 DOCTOR
 New Doctor

No Yes

Register with details

Login to Application

No
Valid User

Yes

Pet Details

Give Prescription

logout

4.2.6.4 MEDICAL SHOP

 New Medical Shop

No Yes

Register with details

Login to Application

No
Valid User

Yes

Pet Details

Send Request

Approve/Reject

logout

4.2.7 Use Case Diagram

Use case diagram for the PET SEARCH shows the various actors involved in the system,
their functionalities with respect to the system.

4.2.7.1 DOCTOR

Pet Search

Register

Login

Pet details

Doctor
Give Prescription

Logout

4.2.7.2 MEDICAL SHOP

 Pet Search

Register

Login

View Request

Medical
shop VIew Medicine

Logout

4.2.7.3 USER
 Pet Search

Register

Login

Upload Pet details

View Request

User
Approve/Reject Request

Find Hospitals

Contact Details

View Prescription

Logout

4.2.7.4 ENTREPRENUER
 Pet Search

Register

Login

Pet details

Send Request
Enterpre
nur
Approve/Reject Request

Logout

4.2.8 SEQUENCE DIAGRAM

4.2.8.1 USER SEQUENCE

Users: Server: Database:

Login Validate

Users
Homepage Validated

Upload Pet
Details

View request Fetch List

Find Hospitals

View Contact
Fetch List
Details

View
Prescription Store

View Details Fetch List

Logout

Logged out

4.2.8.2 DOCTOR SEQUENCE

 Doctor: Server: Database:
Login Validate

Doctor
Homepage Validated

Pet Details

View Details Fetch List

Give Prescription

Details Fetch List

Logout

Loggedout

4.2.8.3 ENTREPRENUER SEQUENCE

 Enterprenur: Server: Database:
Login Validate

Enterprenur
Homepage Validated

Pet Details

View Details Fetch List

Send Request

Approve/Reject Fetch List

Logout

Loggedout

4.2.8.4 MEDICAL SHOP SEQUENCE

Medical Shop: Server: Database:
Login Validate

Medical Shop
Homepage Validated

View Request

Request Details Fetch List

View Medicine

Approve/Reject Fetch List

Logout

Loggedout

Chapter 5
 DATABASE

The database schemas that are used in PET SEARCH are as follows:
Table 5.1 USER
Field Data type Size Constraints Description
User id Varchar 30 PK To store userid
User name Varchar 30 Not null To store user name
User pswd Varchar 8 Not null To store password
email Varchar 30 Not null To store email
Phone num Varchar 10 Not null To store phone num
Typeofuser Varchar 10 Not null To store type of user
City varchar 30 Not null To store city

Table 5.2 ENTREPRENUER

Field Data type Size Constraints Description
Name varchar 30 Not null To store name
email varchar 30 Not null To store email
Phone num varchar 10 Not null To store phone num
Longitude/latitude varchar 30 Not null To store
longitude/latitude
Service des varchar 30 Not null To store type of
service provided
City varchar 30 Not null To store city

Table 5.3 DOCTOR

Field Data type Size Constraints Description
Doctor id varchar 30 PK To store doctor id
Doctor pswd varchar 30 Not null To store doctor pswd
Doctor name varchar 30 Not null To store name
Doctor email varchar 30 Not null To store email
Doctor address varchar 30 Not null To store address
Doctor phone num varchar 10 Not null To store phone num
Specialized id varchar 30 PK To store specialized
id
City varchar 30 Not Null To store city

Table 5.4 MEDICAL STORE

Field Data type Size Constraints Description
Medical id varchar 30 PK To store id
Medical pswd varchar 30 Not null To store pswd
Medical name varchar 30 Not null To store name
Medical email varchar 30 Not null To store email
Medical address varchar 30 Not null To store address
phone num varchar 10 Not null To store phone num

Table 5.5 MEDICATION INFO

Field Data type Size Constraints Description
Med id Varchar 30 PK To store
medicine id
Med name Varchar 30 Not null To store
medicine name
Med frequency Varchar 30 Not null To store
frequency of
medicine
Med quantity varchar 30 Not null To store
quantity of
medicine
Treatment id varchar 30 PK To store
treatment id

Table 5.6 TREATMENT INFO

Field Data type Size Constraints Description
Treatment id Varchar 30 PK to store
treatment id
Pet id Varchar 30 PK To store pet id
Doc id Varchar 30 PK To store doctor
id
Visit date Varchar 10 Date To store visit
date
Medication id varchar 30 PK To store
medication id
Prescription Varchar 30 Not null To store the
prescription
suggested
Next visit date varchar 10 Date To store next
visit date

Table 5.7 PET INFO

Field Data type Size Constraints Description
Pet id Varchar 30 PK To store pet id
Pet breed Varchar 30 Not null To store pet
breed
Pet age Varchar 30 Not null To store pet age

Table 5.8 SCHEDULE INFO

Field Data type Size Constraints Description
Schedule id Varchar 30 PK To store
schedule id
Schedule doc id Varchar 30 PK To store
scheduled doc id
From time Varchar 30 Not null To store time
To time Varchar 30 Not null To store time
Date Date 10 Not null To store date
Status Varchar 30 Not null To store status

Chapter 6
 TESTING
6.1 INTRODUCTION
The test report describes the summary of the result of the test performed on the project
PET SEARCH. It provides a brief description of the result expected and unexpected results,
problems, or defects that occurred during testing.

6.2 Testing process done for the project

Testing is the process of evaluating a system or its components with the intent to find
whether it satisfies the specified requirement or not. The following testing are done for the
project PET SEARCH

6.2.1 TEST CASES

A test case is set of conditions or variables under which a tester will determine
whether a system under test satisfies requirement or works correctly. The process of
developing test case can also help find problems in the requirements or design of an
application. The following tables shows the test cases and scenarios that are generated along
with the required inputs to the given scenario, expected output, actual output and the result
whether the test passes or fails.
Table: test case with positive scenarios
Test case no Scenarios Inputs Expected Actual Result
output output
1 Verify Enter the Should Successfully Pass
Registration email and register registered
other details successfully
2 Verify login Enter email Should login Successfully Pass
and password successfully logged in
3 Search pets Click on Should View pet Pass
breed display pet details
breeds
4 Send request Click request Should view Should view Pass
to sellers request request detail
5 Approve Click accept Should View Pass
request request to update and approved
buyers view request request detail
6 Reject Click on Should Successfully Pass
request reject request remove the rejected
button request
7 Nearby Click on Should Views Pass
search nearby display
 search nearby nearby search
search place

Table: test case with negative scenarios

Test case no Scenarios Inputs Expected Actual Result
output output
1 Verify Enter invalid Display error Invalid email Pass
Registration email and or password
other details
2 Verify login Enter invalid Display Invalid email Pass
email and password or password
password incorrect
3 Post pet Address field Displays Address must Pass
details is empty cannot post be filled
details
4 Send request Click on send Displays Displays Pass
request invalid enter all
details details

Chapter 7
 SCREEN SHOTS
SCREEN SHOTS
Home page of application

User registration page

User login page

Posting pet information page

Search pet page

Nearby search page

Request from buyers page

Post business page

Chapter 8
CONCLUSION
8.1 Conclusion
 The PET SEARCH is an application that provides an efficient and time saving
method for the users to get treated their pets according to their convenient place or location.
This application also provides a platform for pet’s sellers to sell their pet and buyers can post
the pet information. Pet lovers can search a pet and send a request for pet owners. Nearby
search option is provided for veterinary hospital, medical store and pet shop, this activity will
be done based on Google map API (longitude and latitude).

8.2 Reference

1. http://www.bideawee.org
2. http://www.petfinder.com
3. http://www.adoptapet.com
4. http://www.theshelterproject.com