-
Notifications
You must be signed in to change notification settings - Fork 1
Home
This contains all information about the CMPUT 301 Project by this team.
| Name | CCID | GitHub |
|---|---|---|
| Charles Ancheta | cancheta | cbebe |
| Ashutosh Lamba | alamba | ashutoshlamba |
| Kynan Sorochan | krosocha | krosocha |
| Chenxuan Wang | chenxuan | CxLeo |
| Mark Jia | mjia | mosaicthej |
Tool use:
- This wiki
Addressing Feedback
OOP Analysis: Missing requirements. Who is responsible for listing users or how do users search for other users to follow?
We modified the Social class and added the "list the users that one can follow" responsibility. This will be implemented by the Final checkpoint.
Habbits don't need to know which habbit events belong to them?
We modified the Habit CRC card to include the responsibility of knowing which events belong to a Habit, listing HabitEvent as a collaborator.
Visual indicators mentioned in Social but Habbits don't seem to have any sort of strength/visual indicator.
By knowing how many HabitEvents belong to a Habit, it can calculate the consistency of the habit and can then be displayed using a 3-tier visual indicator (red: < 50%, orange: >= 50% and < 75%, green: >= 75%).
Code Base of Prototype
See Part3 branch for the Part 3 code base.
Code Documentation
Our code uses JavaDoc documentation. Due to javadoc program errors, we were not able to compile generated JavaDoc.
Test Cases
Complete intent testing for Login, Habit, Habit Event. Unit testing for utility classes.
Object-Oriented Design
Sprint Planning and Reviews
-
Our team's sprint planning is done using GitHub Milestones.
Demonstration
- To be done after Reading Week (November 16?)
Tool Use
- Still this wiki
Addressing Feedback
Code Base: Didn't see login/Login doesn't work.
We have fixed the login page so that it works to sign in and register, as well as save a users password on their device.
Habits didn't delete.
We fixed the problems with interacting with Firebase so that you can add, edit, and delete a Habit properly.
Code Documentation: More descriptive javadoc is expected.
This was due to people writing Javadocs for other people's code. We addressed this by requiring everyone to create Javadoc for their own code. We have also improved the descriptiveness of our existing Javadoc.
Test Case: Have a set of unit tests that test the logic behind the UI.
We have added tests to different UI models to test their logic.
Object-Oriented Design: Create an additional global/single UML diagram with these details.
Added a global UML diagram.
Sprint Planning: Some meeting points sound like they are from a single person's perspective.
We edited the wording to make it have more of a group perspective.
Code Base of Prototype
See ProjectPart4 branch for the Part 4 code base.
Code Documentation
Our code still uses JavaDoc documentation. More detailed Javadocs have been created to address feedback.
Test Cases
Complete intent testing for Habit reordering, Following, Viewing other person's habits, and Accepting/Rejecting Follows. Unit testing for ViewModel classes and Firestore models.
Object-Oriented Design
Sprint Planning and Reviews
-
Our team's sprint planning is done using GitHub Milestones.
Demonstration
- To be done during our lab on November 30, 2021