📖
Autocator TRD - Team Amadioha
  • Autocator Application - Technical Requirement Document
  • Table of Content
  • 1.0 Project Overview
  • 2.0 System Architecture
  • 3.0 Functional Requirements
    • 3.1 Primary Features of the Product
      • 3.1.1 User Authentication
      • 3.1.2 Search Feature
      • 3.1.3 Home Page
      • 3.1.4 Customer Chat Feature
      • 3.1.5 User Account Creation
      • 3.1.6 Payment Platform
      • 3.1.7 User Feedback
      • 3.1.8 Reminders
  • 4.0 Non-Functional Requirements
  • 5.0 Documents
  • 6.0 Product Timeline
Powered by GitBook
On this page

4.0 Non-Functional Requirements

This section contains the non-functional requirements of our website and how we plan to engineer them.

The specifications for our web application's non-functional needs outline the operational capabilities and limitations of the system while also attempting to increase functionality. The following are the specifications that are putting into consideration:

  1. Performance: We will ensure that the speed, scalability, and responsiveness of the system are smoothly running.

  2. Security: This requires our product to be equipped with protection mechanisms to protect its data from unauthorized access, as well as detect and recover from security breaches.

  3. Usability: This requires our product to be easy to use and understand by our users.

  4. Reliability: This requires our product to function correctly, optimally and consistently under normal and intense conditions.

  5. Maintainability: This requires implementing systems that aid with maintaining the system, including testing, debugging, and modifying the product.

  6. Portability: This requires our product to be easily transferred to different hardware or software environments.

  7. Compliance: This requires our product to adhere to laws, regulations, industry standards, or company policies.

Previous3.1.8 RemindersNext5.0 Documents

Last updated 2 years ago