📖
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
  1. 3.0 Functional Requirements
  2. 3.1 Primary Features of the Product

3.1.1 User Authentication

This page contains the required information about the engineering of the user authentication feature on the website.

To ensure the safety and security of the data of our users, we're implementing two user authentication features in our platform.

AUTHENTICATION FEATURE
SERVICE INTEGRATED
PURPOSE OF USING THE SERVICE
PURPOSE OF INTEGRATING THE FEATURE

  1. Username and Password

Firebase Authentication API

At the moment, the team doesn't have a backend developer. To implement this feature, we're opting to make use of the Firebase API as it's available at little to no cost, and Firebase provides Backend-as-a-service functionalitites.

The purpose of this feature is to ensure the security of our users data on our platform.

  1. Two-Factor Authentication

Authenticator Apps

Authenticator applications are more secure than your regular SMS OTPs. This eliminates the disadvantages that come with that.

The purpose of this feature is to ensure the security of our users data on our platform.

Access to the code files for this feature will be available on our GitHub repository.

Previous3.1 Primary Features of the ProductNext3.1.2 Search Feature

Last updated 2 years ago