Non Functional Requirements (NFR)

---

Version 0.3

Version History

Version	Author	Modification	Date
0.1	Flávio	Document created	29/04
0.2	Marcelo Martins	Topics created	01/05
0.3	Adailson Santos	Introduce document at wiki	10/05

1. Introduction

1.1. Goal

This document is intended to document the non-functional requirements raised and validated with the client. These requirements are those that are not designed for use cases.

1.2. Scope

This document is intended to describe the non-functional requirements present in the TechVet application

1.3. Definitions, Acronyms and Abbreviations

NFR	Non-functional Requirements

2. Non-functional Requirements

2.1 Requirements Identification

ID	Name	Description	Tipe
NFR1	Availability	The system must be available for 24 hours for 7 days a week	Availability
NFR2	Hardware	The system can be accessed through any browser: chrome, firefox and safari	Compatibility
NFR3	Login	Only registered users can access	Security
NFR5	Upload file	The system should recognize PDF files when uploading	Support
NFR6	File format	The system should generate your PDF files	Support
NFR7	Databases	The DBMS must use MySQL 5.7.18	Infrastructure
NFR8	Programming language	The system uses the Java language for implementing the backend and ReactJS for the frontend	Implementation
NFR9	Encryption	The system must have a validator field so that customer information is not visible to those who do not have access	Security