Meeting minutes - CMPUT301F17T13/cat-is-a-dog GitHub Wiki

2017-11-30

Attending: James, Nathan, Leland, Abid

  • Got testing working (see wiki page)
  • No feedback or things to change for Part 4
  • Work on finishing Part 5

2017-11-24

Attending: James, Kevin, Nathan, Leland, Abid

  • Demo
  • Discussion about Firebase database abstraction
  • Discussion about test mocking for Firebase
    • Ian suggests looking into super mock

2017-11-09

Attending: James, Kevin (remote), Nathan, Leland, Abid (remote)

  • Kevin finished: Get my habits, get todo habits.
  • Kevin is finishing up create habit and will merge into master tonight.
  • James blocked by current project status. Will implement Firebase by deadline.
  • Nathan working on create habit events and Google Maps integration.
  • Leland blocked by Kevin and will implement habit details.
  • Abid will work on app drawer

2017-11-02

Attending: Ian, James, Kevin, Abid, Nathan, Leland

  • Ken was surprised about Kevin's evening midterm
  • Wow factors ideas:
    • Geofencing, habits based on location
    • Shared habit amongst group
    • No alternative authentication
    • Messaging between habit friends
    • Habit gallery
    • "Habit jar" - charitable donation
    • Mine bitcoin in background
  • Next week: Ian away. Meet amongst ourselves.
  • Use cases for next week:
    • Assignment 1-related tasks
  • Think about online integration

2017-10-26

Attending: Ian, James, Abid, Nathan, Leland

  • Project Part 3 complete (UML, design, etc.)
  • Whenever possible use a library
  • Ian checked that tests run
  • Non-trivial case: Character limitations
  • Ian: UML looks good for the most part
  • Ken using entitiy, boundary, control layer terminology. Same idea as MVC.
  • In the activities, no onCreate or standard methods (only things like button clicks)
  • EventMap handles clicks, scrolling, etc. on map
  • Loation helper does GPS handling
  • Discussion with Ken: With the way with Firebase made, must be tightly coupled with object models
    • TODO: Include as a note
  • Only refer to feedback made before the deadline
  • Most important things are
  • Offline functionality not in use cases because they are not customer-facing
    • Decision: Offline/online behaviour is not a use case but a requirement.
    • James: We will add in some use case for offline behaviour
  • Skeletal code for code is complete
  • Two more meetings with Ian before Part 4 due date, possibly one more meeting with another TA
    • Ian away November 3 to 15
  • Ian: Will try to finish Assignment 1 UML by next week

2017-10-19

Attending: Ian, James, Nathan, Leland

  • Marks before the weekend
  • Can change UML diagram later
  • For part 2, lots of nit-picky comments:
    • Should fix newline in script
    • User story 01.02.01 forgot to be listed, assuming it's under use case 1
    • Marks are not final
    • In view habit, "pressing the delete button deletes the user interface" should likely be reworded (meant to say habit)
    • Clarification: Reject photos larger than the size limit
      • Suggestion: Compress images for thumbnail (two lines of code)
    • Missing user story 03.01.01
    • Clearly defined on story board, but not described in user stories
    • Good that we're thinking of permissions
    • Feedback: To change: Add related use cases (e.g. to follow a habit we first need to create a habit). Might be helpful for dependency tracking.
    • UI and storyboard are "really good"
    • Top left hamburger menu is currently intended to be the same on every page
    • Would rather see delays with a weekly schedule then no delays with a longer timeline for each goal
    • Which license? Specify that we're using MIT.
      • Post-meeting: Changing to Apache 2.0
  • Part 3:
    • James and Kevin are doing preliminary UML diagrams
    • Question: How detailed does the UML diagram need to be?
      • Answer: For this part, we should plan out all the classes. Implementation (public members and methods) should be specified. This can be changed later.
    • Question: Focus on the most important UML classes.
      • Answer: Make sure we give a general idea. Similar to lecture quiz.
    • Make sure we have a project with tests.
    • No React Native
    • Don't "go insane" on the tests.
    • Should not be "massive" changes in architecture.
    • When in doubt, err on the side of simplicity.
    • If we want to use libraries, email email Ian
    • Fine with APIs, just not black magic
  • Mention design patterns on diagram
  • This is an object-oriented design and analysis class
  • This isn't a "real" development scenario
  • Question: Do test cases need to compile?
    • Answer: No, but no pseudo code. Should aim for tests to run and fail.
  • Use whatever API version
  • Start thinking about "wow" factor