Home

Welcome to the project-theynotlikeus wiki!

Members:

Project Part 2 Deliverables:

Project Part 3 Deliverables:

Project Part 4 Deliverables

Meeting 1 Notes

Meeting 2 Notes

Discuss what we are planning to do for project part 2.
Split up the work.
Mainly looking at UI mockups
Add comments on all frames brief summary
Make sure all frames are linked (arrows)
CRC cards, as long as you have them defined in the wiki
Make a few model classes on what you anticipate the classes to be (model class, event class, etc)
We can also add png as long as it is defined.
Some examples will be provided.
TA does not care too much about CRC cards
Break user stories down into sub issues
40% of the user stories should be finished by the halfway point in project part 3
Select those 40% right now for this part of the project, can be used as a tag on github to show a halfway point.
Being given story points on each of the tickets that basically tell you how much effort you need to do the fix. This is assigned by the team
Make sure the user stories don't have more than 5 points, so difficulty should not be over 5 points in difficulty to effectively break down the project and feature.
For example, function = 3 points, UI change = 1, activity with new features and fragments = 5 points
As long as you are splitting up the work.
An example will be sent to us for how to do the user stories.
Mui.com can download xml files to basically create xml files > Material ui > components

Meeting 3

February 12, 2025
In this meeting we went through the story board and mockups
For the administrative fragment - you can stick to the toggle
The log out function can be a wow factor - you can put the log out button on the edit profile fragment
Focus on the wow factor at the end
Export the figma file as a PDF to submit (you can screenshots too if its easier)
The story board is okay as long as it isn't too cluttered each deliverable should have a page inside the wiki
the figma looks good -we are getting 100!
Backlogs or user stories look good too.
When you start implementing, someone should make all the dummy classes.
Make all the classes and screens/ XML at the start
2 people will create all the fragments and connect them together before working on each fragment

Meeting 4

Main issue is in backlogs: some did not have descriptions
Feature you write more for, user stories are more general. So basically, write more detailed things for the features on the tickets.
CRC cards naming is off
Organize wiki side bar so everything is more clear.
Use the user stories and then use the features to write up the details.
For part 3, focus on: making the prototype, include the comments for each method/functions, and classes, and include test cases. UML diagram should be made. As long as you are done the 40% portion of the code, the prototype should be good.
Nymur demonstrated what we have so far. So far it is good.
Focus on the testcases, assign each person using the issue board on github.

Meeting 5

March 5, 2025
For the UML diagrams: the structure is good, but the relations are needed, add the relationships manually.
Nymur explained the code structure to Nandan.
Should have controllers to add, delete, edit in the database. Focus on this in part 4.
Part 3 demo is next week and it looks good! More than 40% so it is good
He is not going to look at the contributions lol
Javadocs will be added, UML being fixed, etc.
Controllers will be based on how database is set up ex. one for the mood, one for the users, etc.
Need the testcases, CI (if you can, not necessary), UML diagrams.
For project part 4: can organize everything in folders, have controllers.

Meeting 6

Meeting 7

Meeting 8

Nymur updates Nandan on the fixes to the app so far. (photo, offline, photo limit, material ui, etc.)
Wow factor: notify user for user and admin upon post
Improve colour scheme to be more readable, and edit colour in general :).....
Test cases: split up complex test cases into several files rather than just one.
Include CI

Navigation Menu