Altara System Requirements Document

Introduction

The Altara project is designed to create an application specifically for air hostesses, enabling them to track their health, share rosters with fellow crew members, and communicate through a chat functionality. This document outlines the system requirements for the Altara application.

System Overview

The Altara application aims to enhance the daily operations and well-being of air hostesses by providing a comprehensive platform for health tracking, roster management, and communication. The application will be accessible via mobile devices, ensuring ease of use and accessibility for air hostesses on the go.

Functional Requirements as Story Points

• As an Air Hostess, I should be able to track my health metrics such as steps, sleep, and hydration levels.
• As an Air Hostess, I should be able to log my health data manually and view historical trends.
• As an Air Hostess, I should be able to share my roster with friends who are also crew members.
• As an Air Hostess, I should be able to view the rosters of my friends who have shared them with me.
• As an Air Hostess, I should be able to chat with other crew members within the app.
• As an Air Hostess, I should be able to create group chats for team communication.
• As an Air Hostess, I should be able to receive notifications for new messages and roster updates.

User Personas

• Air Hostess: The primary user of the application, responsible for tracking personal health metrics, managing and sharing rosters, and communicating with fellow crew members.

Core User Flows

• Air Hostess logs into the app -> Tracks health metrics -> Shares roster with friends -> Engages in chat with crew members.
• Air Hostess receives a notification -> Opens the app -> Views updated roster or new chat message -> Responds or takes action as needed.

Visuals Colors and Theme

• primary: #1A73E8 (a deep blue for a professional and calming effect)
• primary_light: #E8F0FE (a light blue for hover states and secondary UI)
• secondary: #FF7043 (a coral hue for headlines and emphasis)
• accent: #FFCA28 (a vibrant yellow for CTAs and active states)
• highlight: #FFB300 (a warm amber for hover states and notifications)
• bg: #FFFFFF (a clean white background)
• surface: rgba(250, 250, 250, 0.8) (a subtle card/panel background)
• text: #202124 (a dark grey for primary text)
• text_muted: #5F6368 (a softer grey for secondary text)
• border: rgba(218, 220, 224, 0.2) (a subtle border color)

Signature Design Concept

The Altara app will feature an interactive "Flight Path" design on the home page. This concept will visualize the air hostess's journey through a dynamic flight path animation. As the user interacts with the app, the path will animate to show different stages of their day, such as health tracking, roster updates, and chat interactions. The path will be a continuous loop, with icons representing each feature that animate when hovered over or clicked. This will be implemented using motion/react for smooth transitions and interactions.

Landing Hero Motion Brief

The landing hero will depict a stylized airplane flying across a map, with waypoints representing health tracking, roster sharing, and chat features. As the airplane reaches each waypoint, the corresponding feature will animate into view, demonstrating its functionality. This loop will last 10 seconds and will be responsive to screen size, ensuring a seamless experience across devices.

Interaction Model & Motion Direction

The intended interaction model for the Altara app's landing page is "animated." This will include moderate scroll-triggered reveals, hover transitions, and spring physics on interactive elements to create a polished and engaging user experience.

Non-Functional Requirements

• The application must be responsive and accessible on both iOS and Android devices.
• Data privacy and security must be ensured for all user information.
• The application should support offline access for viewing rosters and health data.

Tech Stack

• Frontend: React Native for mobile app development
• Backend: Python with FastAPI
• Database: MySQL for structured data management
• AI Models: Not applicable
• Local Orchestration: Docker for containerization
• Server-Side Orchestration: Kubernetes for deployment and scaling

Assumptions and Constraints

• The application will primarily be used by air hostesses, so the design and functionality will cater to their specific needs.
• Internet connectivity may be intermittent; hence, offline capabilities are crucial.
• The app must comply with relevant aviation industry regulations and data protection laws.

Glossary

• Air Hostess: A flight attendant responsible for the safety and comfort of passengers.
• Roster: A schedule that outlines the working hours and flight assignments for crew members.
• CTA: Call to Action, a prompt for users to engage with the app.

This document provides a comprehensive overview of the requirements for the Altara application, ensuring that all necessary features and functionalities are clearly defined and aligned with the project's goals.