AI Trip Creator

The Rolling Capstones

Table of Contents

• Project Overview
• Demo Links
• Documentation
• Team Members
• Repository Information
  • Git Flow
  • Branch Naming Conventions
  • ufujefje

Project Overview

AI Trip Creator is a web-based platform leveraging AI chatbots and virtual assistants to help users efficiently plan trips. The app focuses on the following key goals:

1. Simplify Trip Planning
   By providing curated travel plans, it reduces the cognitive load on users.

2. Personalized Experiences
   Tailors itineraries to match individual preferences, making every trip unique and enjoyable.

3. Time and Cost Efficiency
   Saves time and helps users find cost-effective options without compromising on quality.

4. User-Friendly Interface
   A simple, intuitive design ensures that users can easily navigate and get the information they need to plan their trips effortlessly.

Demo Links

• [Demo 1 Video]()
• [Demo 2 Video]()

Virtual Demo

https://drive.google.com/file/d/15tDvLCZCc0uERenIynd-HIDnCtTUvdUQ/view?usp=sharing

Documentation

Project Documentation:

• Demo 1 Documentation
• Demo 2 Documentation
• Demo 3 Documentation
• Architectural Document
• Coding Standards
• Reliability Test Report
• Usability Test Report
• User Manual
• Technical Installation Guide

Additional Resources:

• Project Board
• Deployed Application

Team Members

Member	Contact	Description
Thashlene Moodley		Final year Computer Science student
Nthati Rampa		Final year Computer Science student
Lerato Gololo		Final year Computer Science student
Heinrich Niebuhr		Final year Computer Science student

Repository Information

Git Flow

We follow the Git Flow branching strategy, which allows parallel development and ensures a stable codebase at all times. The main branches we use are:

• Main
  For production-ready code.

• Develop
  For integration and testing.

• Feature
  For developing new features.

• Release
  For preparing production releases.

• Hotfix
  For urgent fixes to production.

New features are branched off from develop, tested, and reviewed before being merged back into develop.

Naming Conventions

Branch names follow these conventions:

1. Concise and Descriptive
   Use clear names that reflect the purpose of the branch. Example: feature/login.

2. Lowercase and Hyphen-Separated
   For long branch names, use hyphens for clarity. Example: hotfix/server-crash.