Meeting Notes

Meeting Update:

• Date: Feb, 23 Meeting with All group members
  • Contribution of Task
  • Meeting Summary:
    • David + Karl: interface
    • Zhiyang + Austin: Organizer + firebase
    • Wei + Kaining: Attendee + firebase
    • Each group in charge with their own JavaDoc, test, UML

---

• Date: Feb, 28 Meeting with TA
  • Solution of QRCode saving in firestore: TA suggested us transfer QRCode to the specific format, then save in the database. When needed, transfer back to the QRCode original format.
  • Question about login: No needed login page, just use Authentication function from android studio, give every user an UNIQUE ID

---

• Date: Mar, 1st Meeting with All group members
  • Database Structure

    Users Collection:

    • User1
      • userID: String
      • list<A>: Array of EventID
      • list<O>: Array of EventID
      • Name: String
      • Phone: String
      • Email: String
      • University: String

    Events Collection:

    • Evnt1
      • EventID: String
      • OrangnizelID: String
      • List<A>: Array
      • QRCodeString: String
      • Information14: String

---

• Date: Mar, 3rd
  • Removed user stories 03.03.X
  • Moved check-in USs (US 01.02.01, US 01.01.01, US 01.01.02 and US 02.01.01) and relative functions to part4

---

• Date: Mar, 6th
  • Moved Admin USs (US 04.X.X) to part4 since we are running out of time and the missing event list implementation
  • We are missing UserList and EventList implementations in the current code, planning: add those in part4

---

• Date: Mar, 13 Meeting with All group members/ demo with TA
• Final check the data structure in firestore.
• Contributed the tasks for final check point.
• Design and reconstruct the organizer class

---

• Data: Mar, 20 Meeting with TA
• Talking about operation of image display with TA
• TA gave us advise is that transfer to base64 to saved in firestore.

---

• Data: Mar, 27 Meeting with TA
• Report basic process of our project to TA

---

• Data: Apr, 3 Meeting with TA
• Double check the process of login with TA
• Communicated about operation of map with TA

Team Contributions

Austin

• Event, User, Organizer, Attendee concepts
• Implement Event, User, and Organizer models
• Design the back-end structure
• Maintain and update the product backlog
• Make some AndroidTests and UnitTests
• Write and generate Javadoc for back-end models (javadoc at /doc/javadoc)
• model class test and Javadoc
• Admin back-end
• map activity
• user's event page(back-end)

Zhiyang

• Design the structure of the Firebase database
• Collaborate with Wei to implement the Firebase database
• Focus on QR code implementation and related designs
• Upload/ update event image (front-end/ back-end)
• display event image (front-end/ back-end)
• delete and edit user profile picture (front-end/ back-end)
• auto generated user profile picture for default user (front-end/ back-end)

Wei

• Design the structure of the Firebase database
• Mainly implement the Firebase database (with Zhiyang)
• Develop and design the random ID generator for Event and User

David

• Front-end
• UI design
• Overall front-end implementation
• update storyboard
• Admin (front-end)
• organizerNotification class (back-end)

Haokai

• Front-end
• User interface and experience
• Storyboard Sequences
• QR Code Scanner
• user's event page(front-end/ back-end)
• user's event receive notification page
• user's sign up/checkin (front-end)

Kaining

• Focus on the implementation of the Attendee model
• Back-end implementation
• Object‐Oriented Design (OOD)

Summary

• Austin: To finalize the back-end structure by the next meeting.
• Zhiyang & Wei: To complete the Firebase database implementation.
• David & Haokai: To present initial front-end prototypes.
• Kaining: To finalize the Attendee implementation details. To design OOD