Meeting Minutes #11 - katkes/better_call_soen_soen341projectF2023 GitHub Wiki

Date: November 13th 2023

Time: 3:00 PM - 4:15 PM

Location: FG - Online

Attendees:

  • Keshan Kathiripilay
  • Mohamed Sanoko
  • Carlo Aldabi
  • Arnab Das
  • Tahsin Islam

Agenda:

  • Go over issues
  • Think of idea that makes us stand out
  • Clean code base

Issues:

  • Broker shall save listing
    • Issue(s): 57
  • Storage of issues
    • Issue: 56, 55, 51, 41, 40
    • 56: Database must store each offer uniquely. Offers can only be made on listings with a for sale status. Offers contain a price and have 2 associations, a listing and profile of the user who initiated the offer.
  • Search
    • Issue(s): 50, 37, 26, 25, 22, 12, 9
    • Search for property postings
    • Search for brokers
  • Submit Offer
    • Issue(s): 49, 46, 36, 34
  • Reschedule visit option
    • Issue(s): 48
  • Broker should receive offer
    • Issue(s): 47, 45, 33
  • Request for property visit
    • Issue(s): 42, 30, 29, 20, 17, 7
  • UML for data
    • Issue(s): 28, 27, 26
    • Types:
      • Broker
      • User
      • Property
  • Mortgage calculator
    • Issue(s): 13
  • CRUD operations frontend

Timeline:

  1. Search
  • a. Search for properties
    • i. Tie backend to frontend
  • b. Search for brokers
  1. Request for property visit
  • a. Mortgage calculator
  1. Submit offer
    • a. Storage of offers
  2. Broker should receive offer
  3. Broker shall save listing for later viewing (favourites)
  4. Reschedule visit options
  5. UML for data

Idea that makes us stand out:

  • Email users

    • Done with Django
    • Suggested estates based on what you’re looking at
    • Pay to make your posting higher/more frequent
    • Search optimization
      • Multiple inputs
      • Extending scope of search

  • Code clean

    • Clean up on Wednesday for SCRUM meeting: 10:30 AM