PrettyGirlz, LLC ‐ Candy Store Application Requirements Document - Wiz-DevTech/prettygirllz GitHub Wiki

PrettyGirlz, LLC - Candy Store Application Requirements Document

  1. Project Overview PrettyGirlz, LLC is an online store specializing in candy, teen fashion, and lifestyle products. This document outlines requirements for a Java-based web application using:
  • Backend: Spring Boot, Maven
  • Frontend: JSP, Bootstrap
  • Database: MongoDB
  • Architecture: Microservices
  • Key Features: User roles, product management, avatar-based fashion previews, integrated chat, and QR-based pickup system
  1. Core Features 2.1 User Management Roles:
  • Admin: Manages users, products, and system settings
  • Seller: Adds/manages products and drop zones
  • Customer: Browses, purchases, and uses chat features User Flow:
  • Registration with email verification
  • Password recovery
  • Profile management (avatar upload, address book) 2.2 Product Modules Candy Store
  • Product catalog with filters
  • Shopping cart and checkout
  • Review system with photo upload Fashion Store
  • Clothing/accessory catalog
  • Avatar-based virtual try-on
  • Outfit sharing in chat 2.3 Delivery System Options:
  1. Home Delivery
    • Standard address collection
    • Delivery tracking
  2. Drop Zone Pickup
    • Seller-defined locations (schools, malls)
    • Location photos and descriptions
    • QR code verification system QR Process:
  3. System generates unique QR per drop zone
  4. Customer receives QR via email/app
  5. Seller scans QR to confirm pickup 2.4 Chat Systems Two Modes:
  6. Product Chat
    • Discuss specific items
    • Photo sharing
  7. Social Feed (TikTok-style)
    • Public posts with comments/likes
    • Media upload (images/videos)
  8. Technical Specifications 3.1 System Architecture plaintext Copy Download

prettygirlz-app/
├── user-service/ # Auth & profiles
├── product-service/ # Candy/fashion items
├── delivery-service/ # Drop zones & QR
├── chat-service/ # Real-time messaging
└── web-ui/ # Frontend 3.2 Database Schema Collections:

  • users (auth data, roles)
  • products (candy/fashion items)
  • drop_zones (location data + QR info)
  • chats (threads and messages) 3.3 APIs & Integrations
  • Google Maps API (optional for location tagging)
  • ZXing Library (QR generation)
  • Cloudinary (image uploads)
  1. UI/UX Requirements 4.1 Design System
  • Color Palette: Warm brights (pink, peach, purple)
  • Avatars: Cartoon-style for fashion previews
  • Responsive Layout: Mobile-first design 4.2 Key Screens
  • Product Pages: Clean grids with filter sidebar
  • Checkout Flow: Clear delivery option selection
  • Seller Dashboard: Drop zone management tools
  1. Non-Functional Requirements 5.1 Performance
  • Page load <2s for 90% of requests
  • Support 500 concurrent users 5.2 Security
  • Password hashing (BCrypt)
  • QR data encryption
  • Role-based access control 5.3 Maintainability
  • Modular microservices
  • Comprehensive logging
  • API documentation (Swagger)
  1. Project Timeline PhaseDurationCore Architecture2 WeeksUser Modules3 WeeksProduct Modules3 WeeksDelivery System2 WeeksChat Features2 WeeksTesting & Polish2 Weeks
  2. Success Metrics
  • 90% successful QR pickups
  • <5% cart abandonment
  • 75% user retention at 30 days Approval Prepared for: PrettyGirlz, LLC Author: [Your Name] Date: [Today's Date] Next Steps
  1. Finalize design mockups
  2. Set up CI/CD pipeline
  3. Begin sprint planning [Document Version: 2.0] [Last Updated: [Today's Date]]