Sprint Meetings - CMPUT301W26opcode/opcode GitHub Wiki

Sprint #5 - April 5:

  • UI mockups completed by Bohdana. Some changes are still expected in the codebase so reminded her to stay tuned.
  • Amir completed the poster image functionality and also the qr scanner functionality.
  • Stanli wrote java docs and some unit tests for his fragments.
  • Vedant completed the map functionality and admin functionality (for browsing and deleting user profiles).
  • Ryan almost finsihed with his notifications.
  • Michali worked on some unit tests for lottery mechanism.

Sprint #4 - Thursday, April 2:

  • UML completed (Bohdana waiting for more updates to the codebase)
  • Firebase connection for notifications created by Ryan. Will now focus on providing an interface for notifcations.
  • Vedant finished the comment functionality. Will now focus on admin functionality and then map functionality.
  • Amir focussed on encoding image files into the Event class (for poster functionality). He fixed some bugs that were previously present in the eventcreator fragment.
  • Stanli and Michali fixed some bugs related to waitlistfragment and profilefragment.

Sprint #3 - Monday, March 23rd:

Discussion

  • Reduced the number of user stories
  • Assign and complete your user stories, strict deadline this Friday as next week is reserved for testing and debugging
  • Reminder that Part 4 is due next Friday
  • Agreed that a single person should be responsible for UML and UI mock-up updates/changes (assigned to Bohdana)
  • Addressed bugs that occurred during last week's demo, changes to the model are currently on the refactor branch, will be merged later tonight
  • Reminder to add comments to classses/user stories you worked on

refactor Branch Changes:

  • Removed the Map<String, Applicant> applicants from the Event class and opted to flatten to an Applicant class. This stores the event id, user id and status (and some other data too!)
  • Adopted Builder creation pattern for models. To centralize validation for data passed to constructors, all models can be created using the static builder() method and appropriate builder functions available. The build function will perform the checks on the arguments passed and will return null if anything is invalid. Some validation has not been implemented for sake of development but will be added and refined overtime
  • Separated DBManager.java into separate classes, ApplicantRepository, CommentRepository, EventRepository, UserRepository. These work the same way as DBManager but focuses on separation of concerns i.e. EventRepository strictly handles Event objects. Please at the code for available methods.

Sprint #3 - March 19:

  • Had out demo.
  • Went horrible.
  • Bugs related to accept/decline invitation will be worked on by Vedant and Amir. Additional bugs:

App crashes when a user decides to delete their profile. Instead, the user should be sent to the sign up page.

Provide a separation of events (i.e. provide a view that only shows events that are open, Provide a view that only shows the events that the user has created).

The fragment that let's the user accept/decline an invitation is not working properly (the accept/decline buttons are not showing up).

When a user creates an event and they select registration/Event dates from the Calender widget, the day after the selected date gets saved. For example, if a user clicked on the 19th of March, then somehow the 20th of march is saved.

In the screen that shows the lottery button and the list of applicants, the names of the applicants are not properly showing up, instead, some weird id shows up. Also, the waitlistfragment does not contain enough details about the event, the user should be able to see stuff like event description, event start/end dates, etc.

Sprint #1 - Satuday, February 28th:

  • Use basic views activity when creating UI screens.
  • Use Assignment 0 page 96 as a reference Updated CRC cards (see pinned messages)
  • Admin user stories will be added to CRC cards at a later stage
  • Assigned and decided 23 user stories for the half-way completion
  • Reminder to use test driven development i.e. write a skeleton function and failing unit test, then implement function to solve the test
  • Reminder to use branching to avoid merge conflicts
  • Discussed how entrant, organizer and admin relate (TA question)
  • Added branch protections to main branch (require pull requests, prevent force pushing, require one other reviewer before pushing)