Skip to content

COS301-SE-2024/AI-Trip-Creator

Repository files navigation

AI-Trip-Creator

The Rolling Capstones

Coverage Status System Status Dependencies GitHub issues

Table of contents

  • Purpose of project
  • Demo links
  • Documentation
  • Team members
  • Repository information

Purpose of project

The purpose of this application is to use the power of an AI chatbot and virtual assistant to aid users in planning for trips. At a high level, the web application should achieve the following:

  1. Reduce the difficulty of planning trips: Reduce the cognitive load that comes with trip planning by presenting the user(s) with curated travel plans that cater to their needs
  2. Provide personalized experiences: The application should create itineraries based on user preferences to ensure an enjoyable and memorable trip
  3. Time and Cost effective The application should provide users with plans based on their wants while saving them time (which could be spent preparing for the trip) and ensuring that they do not have to pay more than what is necessary for their trip.
  4. Provide a user-friendly interface The interface should be quick to learn and easy to understand providing the user(s) with all the information they need to ease the process of travel planning.

Demo links

Demo1-video-

Documentation

Deployed application: ai-trip-creator.web.app/

Team Members

Member Contact Description
Thashlene Moodley Gmail LinkedIn
I am a final year student
Nthati Rampa Gmail LinkedIn
I am a final year student
Lerato Gololo Gmail LinkedIn
I am a final year student
Heinrich Niebuhr Gmail LinkedIn
I am a final year student

Repository Information

Git Flow

We will be using the git flow branching strategy. The benefit of using this is that it facilitates parallel development, which will allow our code to remain stable at all times.

We will have the following branches:

  • Main
  • Develop
  • Feature
  • Release
  • Hotfix

Newly-created features will be based off the develop branch and merged back once it passes the testing and reviews by other members of the team.

Naming conventions

The branches wil make use of the following naming conventions:

1)The name should be concise and descriptive, clearly reflecting what work will be done in the branch. e.g. feature/login

2)Lowercase and Hyphen-separated for long names