System Requirements Document (SRD)

Project Name: frozen-safety

1. Introduction

The frozen-safety project is a professional, production-level mobile application designed to enhance women's safety. The app, named Safelane, focuses on providing real-time assistance, secure navigation, and emergency response features tailored to the needs of users in Chennai, India. This document outlines the system requirements for the development of the application, ensuring a robust, user-friendly, and scalable solution.

The app aims to empower women by offering features such as an SOS button, safe route mapping, emergency contacts, and a fake call feature. It is designed with a modern, minimalist UI/UX and leverages advanced technologies to ensure reliability and performance.

2. System Overview

The frozen-safety system is a mobile application that integrates multiple safety features into a single platform. It is built using a cross-platform framework (React Native) to ensure compatibility with both Android and iOS devices. The backend is powered by Python (Flask) for lightweight and efficient API handling, with PostgreSQL as the database for structured data storage.

The system's core functionality revolves around:

• Emergency Response: A highly optimized SOS button that sends alerts and live location to emergency contacts.
• Safe Navigation: Route mapping within Chennai, highlighting well-lit roads, police stations, and hospitals.
• Personal Safety Tools: Features like fake calls and emergency contact management.

The app is designed to be intuitive, responsive, and secure, with a focus on user privacy and data protection.

3. Functional Requirements

User Stories:

• As a User, I should be able to press an SOS button that sends my live location and an alert message to my emergency contacts.
• As a User, I should be able to view safe routes within Chennai, including details like well-lit roads, nearby police stations, and hospitals.
• As a User, I should be able to save, edit, and delete emergency contacts.
• As a User, I should be able to access preloaded emergency helpline numbers (e.g., Women’s Helpline, Police, Ambulance).
• As a User, I should be able to simulate an incoming call with a customizable caller name.
• As a User, I should be able to view and edit my profile details, including name, email, and phone number.
• As a User, I should be able to log in securely using email and password or via Google authentication.
• As a User, I should experience smooth animations and transitions throughout the app.

4. User Personas

1. Primary User:

• Description: Women seeking a safety-focused mobile application.
• Goals: Quick access to emergency tools, safe navigation, and personal safety features.
• Technical Proficiency: Moderate (familiar with mobile apps).

2. Admin:

• Description: Backend administrator managing user data and system performance.
• Goals: Ensure system reliability, manage APIs, and monitor data security.
• Technical Proficiency: High (developer-level expertise).

5. Visuals Colors and Theme

Color Palette:

The app will use a calming yet empowering color scheme to evoke trust and safety.

• Background: #F8F9FA (Soft Light Gray)
• Surface: #FFFFFF (Pure White)
• Text: #212529 (Dark Charcoal)
• Accent: #FF6F61 (Empowering Coral Red)
• Muted Tones: #6C757D (Muted Gray)

6. Signature Design Concept

The Safelane app will feature a "Living Safety Dashboard" as its signature design concept.

Concept Details:

• Dynamic Dashboard: The home screen will feature a real-time safety meter that changes based on the user's location. For example:
  • Green: Safe area (well-lit, nearby police stations).
  • Yellow: Moderate safety (less lighting, fewer resources).
  • Red: High-risk area (poor lighting, no nearby resources).
• Interactive Map: The map on the dashboard will display safe routes with animated markers for police stations and hospitals.
• Micro-Interactions:
  • The SOS button will "pulse" gently to draw attention.
  • Cards (Fake Call, Safe Routes, etc.) will have a "flip" animation when selected.
• Transitions: Smooth page transitions with fade-in effects and subtle motion.

This concept ensures the app is visually engaging while keeping safety at the forefront.

7. Non-Functional Requirements

• Performance:

  • SOS trigger must execute within 1 second.
  • Map rendering should not exceed 2 seconds.

• Scalability:

  • Backend should support up to 10,000 concurrent users.

• Security:

  • User data must be encrypted (AES-256).
  • APIs must use HTTPS for secure communication.

• Usability:

  • The app must be intuitive and accessible to users with moderate technical proficiency.

• Localization:

  • Support for English and Tamil languages.

8. Tech Stack

Frontend:

• React Native

Backend:

• Python (Flask)

Database:

• PostgreSQL

Performance Modules:

• C language for SOS trigger optimization

APIs:

• Google Maps API for route mapping

Deployment:

• Docker and Kubernetes for containerization and orchestration

9. Assumptions and Constraints

Assumptions:

• Users will have internet access for most features (e.g., maps, SOS alerts).
• The app will initially target Android and iOS platforms.

Constraints:

• Localization is limited to Chennai in the initial phase.
• Real-time map data depends on the availability of Google Maps API.

10. Glossary

• SOS Button: A button that triggers an emergency alert and shares the user's location.
• Safe Routes: Predefined routes within Chennai that prioritize safety.
• Fake Call: A feature that simulates an incoming call to help users exit uncomfortable situations.
• JWT Authentication: JSON Web Token, a secure method for user authentication.
• AES-256: Advanced Encryption Standard, a secure encryption algorithm.

This document provides a comprehensive roadmap for the frozen-safety project. Suba, let me know if you'd like to refine or expand any section further!