Pet Shop System

David Luiz dos Santos

Requirements Document
Pet Shop
Version 1.0
David Luiz dos Santos
 Change History
Data Version Description Author
29/10/2021 1.0 Start of requirements document David
 Content
1. INTRODUCTION 4
1.1 OVERVIEW OF THE DOCUMENT 4
1.2 CONVENTIONS, TERMS, AND ABBREVIATIONS 4
1.2.1Identification of requirements 4
1.2.2Requirements priorities 5
[Link] DESCRIPTION OF THE SYSTEM 5
2.1 SCOPE AND RELATED SYSTEMS 5
[Link] REQUIREMENTS (USE CASES) 6
[Link]-FUNCTIONAL REQUIREMENTS 7
[Link] REQUIREMENTS 8
5.1 RISK ASSESSMENT MATRIX 8
[Link] MATRIX - FUNCTIONAL REQUIREMENT 9
[Link] 10

Requirements Document Page3of12

1. Introduction
This document specifies the requirements of the Pet Shop system, providing to the
developers the necessary information for the project and implementation, thus
as for the execution of tests and system approval.

1.1 Overview of the document

In addition to this introductory section, the following sections are organized as
described below.
Section 2 - General description of the system: provides an overview of
system, characterizing its scope and describing its users.
●Section 3 – Functional requirements (use cases): specifies all the cases
use of the system, describing the event flows, priorities, actors,
inputs and outputs of each use case to be implemented.
Section 4 - Non-functional requirements: specifies all non-functional requirements
functionalities of the system, divided into usability, reliability requirements,
performance, security, distribution, compliance with standards and requirements
hardware and software.
Section 5 - Security Requirements: specifies all the requirements
security related to functional and non-functional requirements
Section 6 – Traceability Matrix:
Section 7 - References: presents references to other documents
used for the preparation of this document.

1.2 Conventions, Terms, and Abbreviations

The correct interpretation of this document requires knowledge of some
conventions and specific terms, which are described below.

1.2.1 Identification of requirements

By convention, the reference to requirements is made through the name of the subsection where
they are described, followed by the requirement identifier, according to the
specific specification follows: [subsection name. requirement identifier]. For example,
the functional requirement [RF016 Data Recovery] must be described in a
subsection called 'Data Recovery', in a block identified by the number
[RF016]. The non-functional requirement [NF008 Usability]. Screen Size] must
to be described in the non-functional requirements section of Usability, in a block
identified by [NF008]. Security requirements must be in a block
identified by [RS009 – Battery]
The requirements must be identified with a unique identifier. The numbering
starts with the identifier [RF001], [NF001] and [RS001] and continues to be
increased as new requirements arise.

1.2.2 Priorities of requirements

To establish the priority of the requirements, in sections 4 and 5, the following were adopted
denominations 'essential', 'important' and 'desirable'.

Requirements Document Page4of12

1. Essential is the requirement without which the system does not function.
Essential requirements are indispensable requirements that must be
implemented imperatively.
2. Important is the requirement without which the system starts functioning, but
in a unsatisfactory manner. Important requirements need to be implemented, but,
if they are not, the system can still be implemented and used.
3. Desirable is the requirement that does not compromise the basic functionalities of
system, that is, the system can function satisfactorily without it. Requirements
desirables can be left for later versions of the system, if there is no
tempo hábil para implementá-los na versão que está sendo especificada.

2. General description of the system

2.1 Scope and related systems

THE PETSHOP PROJECT WILL BE A CUSTOMIZED MANAGEMENT SYSTEM FOR THE
CLINIC AND PET STORE. IT WILL HAVE AS MAIN CHARACTERISTICS THE
MANAGEMENT OF YOUR CLIENTS AND ANIMALS, SALES OF PRODUCTS AND
VETERINARY ASSISTANCE.

Requirements Document Page5of12

3. Functional requirements (use cases)

ID Requirement Description Priority

RF001 Registration of the Functional Requirement that deals with all the Essential
client fields related to registration of
clients.

Form Fields:
*Data do cadastro:String (00/00/0000)
*Nome do cliente: String(max. 250 caracteres)
*Telefone/Whatsapp: String(00)00000-0000
Social Networks: String
*Instagram:String
*Facebook:String
Others:String
*CEP: String;(00000-000)
*Bairro: String
*Cidade: String
*Estado: String
*Logradouro: String (max.250 caractere)
*Número: Number
RG: String(xxxxxxxx-x)
CPF: Number ([Link]-xx)
*Tipo de cliente:String
*Vip:String;(de 1 a 5 atendimentos)
*Gold:String;(from 5 to 10 services)
*Premium:String;(from 10
attendances)
Base registration
Register Institution: String;
. register Period:String;
Register Course:String;

Change:
Changes will only be allowed with permission
by an authorized employee.
Exclusion:

It will only be allowed to change with permission

of an authorized employee.
List: it will be allowed to search for the client by
nome, cpf.
web service:[Link]
RF002 Registration of the Functional Requirement that addresses all the Essential
animal fields related to registration of
clients' animals.

Form Fields:
*Nome do animal: String(max. 250 caracteres)

Requirements Document Page6of12

 *Nome do dono: String(max. 250 caracteres)
Owner's CPF: Number ([Link]-xx)
Animal species: String(max. 250 characters)
Animal breed String(max. 250 characters)
*Peso:Number
*Altura:Number
Disease: String (max. 250 characters)
Animal color: String(max. 50 characters)
Animal age: Number
*Sexo do animal: Number
*Notes: String (max. 250 characters)
RF003 Registration of the Functional Requirement that deals with all the Essential
Employee fields related to registration of
employees.

Form Fields:
*Nome: String(max. 250 caracteres)
*Telefone: String(00)00000-0000
RG: Number(xxxxxxxx-x)
CPF: Number ([Link]-xx)
*CEP: Number;(00000-000)
webservice:[Link]
*Bairro: String
*Cidade: String
*Estado: String
*Logradouro: String (max.250 caractere)
*Número: Number
Function: String (max. 100 characters)
Working Hours: String(max.250 characters)
*Salário: Number([Link],xx)
Bank account: String(max.250 characters)

RF004 Registration of the Functional Requirement that addresses all of the Essential
order relative fields for order registration.

Form Fields:
*Número do pedido: String(max. 250 caracteres)
*Tipo do serviço: String(max. 250 caracteres)
*Banho:String
*Tosa:String
Uberdog:String
Inquiries:String

Requirements Document Page7of12

 Training:String
Product type: String(max. 250 characters)
Rations:String
*Petisco:String
*Farmácia:String
*Brinquedos:String
Accessories:String
*Tipo de animal: String(max. 250 caracteres)
Animal age: Number
Animal's gender: Number
RF005 Registration Functional requirement that deals with all the Essential
Shape of relative fields for the registration of the forms of
Payment payments.

Form Fields:
Order number: String(max. 250 characters)
Payment methods: String(max. 250
characters)
*Dinheiro:String
*Cartão de débito:String
*Cartão de crédito:String
*Boleto:String
Pix:String

4. Non-functional requirements

ID Requirement Description
RNF001 SERVER requirement
product The system must have at least the following
requirement of configuration. SSD HD 1TB ...
efficiency USERS
requirement of The system must have at least the following
space configuration. SSD hard drive 1TB ...
RNF002 Requirement: All forms must have Arial font, black,
product - size 12, with a light background on the screen preferably
requirement of of white color.
ease
for use
RNF003 Requirement for all forms must have the save buttons.
product - search, cancel and exit.
requirement of
ease
for use
RNF004 Requirement of The system will be implemented in the Language of
product Java programming, thus being portable in the
requirement of most used platforms (Windows, Linux).
ease
for use

Requirements Document Page8of12

RNF005 Requirement: A documentation containing the diagram will be made.
product classes, since the language used follows the
requirement of paradigm of object-oriented programming. and also
ease information about the project source code.
for use

Requirements Document Page9of12

5. Security Requirements

ID Danger Solutions
[RS001] If any information is invalid A window will be
(não preenchida) presented informing that the data
for registration are incomplete.

[RS002] If the animal needs medicine, The system should allow the veterinarian
surgery or being hospitalized. add a new entry to the history of
animal.
[RS001] If any information is invalid If any input is not provided, the
(not filled) [RS002] the program will notify the veterinarian in the field
white, and will ask if the user wants
proceed anyway.

5.1 Risk Assessment Matrix

Requirements Document Page10of12

6. Traceability Matrix – Functional Requirement

Requirements Document Page11of12

7. References

1. Based on the requirements document available at <[Link]

j&q=&esrc=s&source=web&cd=3&sqi=2&ved=0CCwQFjAC&url=http%3A%2F
/[Link]/attachments
%2F169%[Link]&ei=kPnfUWKIs6XyATC5IC4Bw&usg=AFQjCNESjuE4x3e
3nXsTuY3tnt4aqobn1A&bvm=bv. 72197243,d.b2U&cad=rja>
2. SOMMERVILLE, Ian. Software Engineering, 8th edition. Pearson, Addison Wesley, v. 8, n. 9, p.
10, 2011.
[Link], Roger; MAXIM, Bruce. Engenharia de Software-8ª Edição. McGraw Hill Brasil, 2016.

Requirements Document Page12of12