FETCH DOG DAYCARE AND BOARDING
Software Requirements Specification
1. INTRODUCTION
The software requirement specification documents provide an idea of the entire SRS with
purpose, scope, definitions, references, and overview of SRS. The objective of this document is
to collect and analyze and provide an in-depth summary of the complete Fetch Dog Daycare and
Boarding digital application by defining problem statement in detail. The detailed requirements
and purposes of Fetch Dog Daycare and Boarding application are provided in this document.
1.1 PURPOSE
The purpose of this document is to build an online software to store all customer specific
information for pet’s owners, track of pet information and tracking of pet’s engagement in day
care.
1.2 PRODUCT SCOPE
The scope of this product is to create a digital management system to obtain and track pet owner
information, pet information as well as establishing a dashboard to book day care appointments,
show existing appointments and calendar record of upcoming events.
The application should be PC and MAC Friendly as well as it should work on mobile devices.
The application should be user friendly and secured for clients. Multiple users should be able to
access the app at the same time and should be available 24/7.
1.3 PRODUCT VALUE
The application will help the staff and pet owners with scheduling and booking a spot in day
care, payment processing, managing check-in and checkouts, tracking pet’s vaccination records,
1
and managing employees’ schedules. This will help in managing both employees and customers
as well.
1.4 INTENED AUDIENCE
This project is useful for customers of dog day care and employees of day care. This has been
implemented under the guidance of day care owner and staff. This project will be useful for
clients of day care and staff.
1.5 DEFINITIONS AND ACRONYMS
Configuration It means a product which is available / Selected from a catalogue can be
customized.
SQL
Structured Query Language
APP
Application
1.6 TABLE OF CONTENTS
Serial number
1
Content
Page number
Introduction
1
1.1. Purpose
1.2. Product Scope
1.3. Product Value
2.
1.4. Intended Audience
2
2
1.5. Definitions and
acronyms
2
Overall Description
2.1. User Needs
2.2. Assumptions and
Dependencies
2
1
4
4
5
3.
System Features and
Requirements
15
3.1 Functional Requirements
6
3.1.1 If/then behaviors
6
3.1.2 Data handling logic
3.1.7
3.1.8
3.1.9
System workflows
Transaction handling
Administrative
functions
7
7
7
7
3.1.6 Regulatory and
compliance needs
8
3.1.10 Performance
requirements
3.1.11 Details of operations
8
8
conducted for every
screen.
3.2 External Interface
Requirements
9
3.2.1User interfaces
9
3.2.2
3.2.3
3.2.4
9
9
Hardware interfaces
Software interfaces
Communication
interfaces
3.3 System features
3.4 Non – Functional
10
10
requirements
3.1.1. Capacity
3.1.2. Compatibility
10
11
3.1.3. Reliability and
availability
3.1.4. Scalability
11
11
3.1.5. Maintainability
3.1.6. Usability
3
11
Approval
4
12
2.OVERALL OVERVIEW
This document contains the problem statement that the current system is facing which is to track
information of pet owners, pet’s information, and scheduling employees. It contains a list of the
stakeholders and users of the proposed solution. This document lists and briefly describes the
major features and detailed description of each of the proposed system.
2.1 USER NEEDS
Users of the application should be able to track the customers/ pet owners of day care. When the
staff enters name of the pet owner’s they should be able to find the contact information, address,
emails, and emergency contact information. The software should have all pet specific
information to track they as well should be able to add multiple pets.
Customers should
have access to track pets’ engagement activity in day care, track upcoming appointments and
events and they should be able to book a slot in day care online when required. The customer
should be able to do the following functions:
4

Booking schedules

Monitoring pets by pet owners

Access necessary forms and waivers

Purchasing packages

Bill payments

Able to communicate with Fetch.

Discounts for frequent punch ins (Frequent schedule bookings)

Updates / news about their pets through notification.
The employee /staff should have following functionalities:

Customer Functions

Tracking of vaccination information / special health needs of pets.

Tracking of pet health/behavior updated by pet owners.

Provide tools of Marketing business through text messages, pre drafted emails,
reservation confirmations and reminders, surveys, updates etc.
Administrative Functions

Create employee schedules.

To do lists

Allowing staff to login

Tracking tips received by staff.

Providing updated to pet owners.
2.1 ASSUMPTIONS AND DEPENDENCIES
To launch the app users will need internet in mobile / PC / Mac depending upon which mode
they use. If the phone does not have enough hardware resources available for the application,
there may be scenarios where the application does not work as intended or even at all.
3
SYSTEM REQUIREMENRS
The pet day care application maintains information on pet’s vaccination, day care activities, Pet
owner information and employee schedules. This project has a high priority. The phase 1 of the
requirement focuses on maintaining and updating Pet owner information and pets’ information,
5
pet vaccination records, a dashboard hub for client to get updates about upcoming engagement in
day care.

The project should allow pet owners to book/schedule spot in day care.

Displays major events/ news in day care / engagement activities of pets.

Payment processing

Check in and check outs.
3.1 FUNCTIONAL REQUIREMENTS
3.1.1
If/then behaviors
Scenario 1: Address information and contact information display.
If I select address/ contact information option, then it should display pet owners’ information.
Scenario 2: Payment processing
If I select the payment method, then it should display payment methods available to process the
payment.
Scenario 3: Booking schedule / spot.
If I select the book a spot, then it should display available days and slots for pet day care.
Scenario 4: Vaccination records display
If I put customers name, then I should be able to see how many pets’ owner have and their
vaccination records.
3.1.3 Data handling logic
* The system shall display customer specific info like address, contact info and emergency
information.
6
The system shall display vaccination record of pets upon searching.
The system shall display special events happening in future like birthday celebration, holiday
events etc.
The system shall display pet updates.
3.1.2
System workflows
FETCH PET
DAY CARE
ADMIN
PET OWNER
LOGINS AND
BOOK SLOT
FOR DAY
CARE
MONITOR
PET
ACTIVITIES
AND DAY
CARE
UPDATES
PAYMENT /
ADDING
PAYMENT
METHOD
ADDING
PET
UPDATED/B
EHAVIOUR
PATTERN
SCHEDUL
ING
EMPLOYE
ES
ADDING
PETS
ENGAGEME
NT
ACTIVITIES
3.1.3Transaction handling
The pet owners will use payment methods for booking spots. The transactions are initiated by the
user who interacts with the transaction system through a terminal. Transaction systems can serve
requests submitted in application through mobile/ pc/mac.
3.1.4 Administrative functions
7

Add/ delete customer information.

Add/ delete pet information / updates.

Updating upcoming events

Add schedules for employees.

Adding marketing news / pet engagement activities
3.1.5 Regulatory and compliance needs
The database will have a functional audit trail. The system will limit access to authorized users.
The database can secure data with passwords and security features to protect data from hackers.
3.1.6 Performance requirements
The app will work based on web and has to be run from a web server. The app will take time
to display information depending on internet connection strength which also depends on the
device which is run. The performance may depend upon hardware components of the client/
customer.
3.1.7 Details of operations conducted for every screen.
1. Login Screen (Page): User sees create new account link, username Box, password box
and login in button etc.
2. Username / Password: If correct username and password is entered, it allows them to
login and do actions which they prefer like checking upcoming events, booking
schedule. If an incorrect username or password is typed, then the application will flash
an error message “Username or password is invalid “
3. Book a schedule screen – Once the user logins and click on the link book a
slot/schedule then it will take to another screen with calendar and available time slots to
book the spots. The unavailable spots will be greyed out and available spots will be
green.
8
4. Payment screen – When the user clicks payment link and then it will take to the
payments screen with available payment methods. User can select the payment method
they prefer and then it will take to another payment secured page for transaction. If the
transaction was unsuccessful then it will display error message – “Transaction
unsuccessful “.
3.2
EXTERNAL INTERFACE REQUIREMENTS
There are many types of interfaces as such supported by the application software namely: User
interface, software interface and Hardware interface.
3.2.1 User interfaces
The user interface for the software shall be compatible to any browser such as Google
chrome, Mozilla Firefox or Microsoft edge by which user can access the application.
The user interface shall be implemented by using any tool or software package like
JavaScript, MySQL Server, and PHP.
3.2.2 Hardware interfaces
The application must run over the internet, all the hardware shall require connecting internet
will be hardware interface for the system. For example – Internet modem, WAN-LAN and
ethernet.
3.2.3 Software interfaces

The application shall communicate with the configurator to identify all the
available elements to configure the product.

9
The application shall handle many users simultaneously.

Bill pays system to identify available payment methods, validate the
payment and process payment securely.

The application shall communicate with record management system to
pull up records of vaccination for pets.

The software should allow to communicate with user and owners of fetch.

The application shall communicate with the content manager to identity all
the events in day care, promotions and marketing.

The application shall communicate with booking management system so
that clients can book slot for day care.

The application shall use safe and secure software which will allow pet
owners to complete secured transaction.
3.2.4 Communication interfaces
The application will use the HTTP Protocol for communication over the internet and TCP/IP
Protocol suite for intranet communication.
3.3 SYSTEM FEATURES
The application maintains database of information on pets, pets’ vaccination records,
customer information, employees’ information and payment information. This project has a
high priority to manage both customer request and employees record management.
3.4 NON-FUNCTIONAL REQUIREMENTS
3.4.1 Security
The application should provide a secure login to the users by using advanced secure login
algorithms and provide access only to the authorized users. The application will be relying on
database application; therefore, the weak authentication threat needs to be managed well.
10
3.4.2 Capacity
The application shall support future scalability to accommodate increasing customer
demands. The application shall handle a growing number of requests to book a spot in
day care without performance degradation.
3.4.3 COMPATIBILITY
The system should be able to accommodate new customer information and vaccination
records/ behavioural updates and updating pet owner information.
3.4.4 Reliability and availability
The application should be able to let users’ books schedule and access information
related to the pet and monitor their pets’ activities. The application can be used by
multiple users at a time like employees and pet owners. Downtime after a failure shall not
exceed x hours. The system shall be completely operational at least X% of the time.
3.4.5 Scalability
The application should handle multiple users at a time and provides information without
any delay. Also, the app should be able to handle multiple requests at a time like booking
slots and payment processing.
3.4.6 Maintainability
The application must support regular updates to match compatibility with latest web
technologies, bug fixes and security patches.
3.4.7
Usability
The application should satisfy a maximum number of customers needs like booking
schedules, monitoring pet’s activities, accessing event news and scheduling employees
11
work time. It should be accessible on multiple devices including desktop and mobile
devices.
4
APPROVAL
Approval required from following necessary stakeholders:





12
Fetch Owner
Fetch Staff member (SME)
Business Analyst
Project Manager
System Architect