Skip to content

Weekly Report 2

Choo Shee Yeow edited this page Mar 13, 2020 · 1 revision

Date: Feb 18, 2020

Attendees

Mushroom, Yuxin, Ruohan, Jeremy

As a team, we did preparation for project part 3.

what we did

  • Start working on distributed part from first meeting
  • Pair programming

Work distribution

Group 1: Mushroom & PangKai

  • Created User, Wallet, AccountInfo, BankAccount, DriverInfo classes

  • Constructors, getters and setters

    Problem meet

    • Need to get access about database in order to register and update information (need to merge)

    • Need to change UML diagram ( working )

    • Need to learn how to build QR code and scan it ( working )

    Comment

    • Need to merge and test the code in order to push to master branch

Group 2: Yuxin & Ruohan

  • Merging and testing the Google Map functionalities Part with its View part.

    Problem meet

    • Unable to display map fragment ( solved )
    • Unable to locate device location in Map fragment ( solved )
    • Unable to draw the driving route given two locations marked ( solved )
    • Unable to interact with database, i.e., cannot match rider with open request with potential driver ( working )

Group 3: Jeremy & Zhiyuan

  • created DatabaseHelper class, constructor

  • created basic methods

    1. add request
    2. delete request
    3. update request
    4. add record
    5. delete record
  • work on queries (storing, retrieving and deleting custom object from or to Firebase cloud)

    1. queryRiderOpenRequest

    Problem meet

    • Unable to store and retrieve custom object ( solved : create empty constructor, use toObject() method instead of getString() method in demo)

    • Unable to return value obtained ( solved : use interface as a listener to get notified and transfer data for update)

Merged

Group 1: Mushroom & PangKai & Group 3: Jeremy & Zhiyuan

  • Data base part & user part & system part be merged (expect for QR), still testing
  • Jeremy's and Mushroom's branch contained merged code ( not completed )

Future Meetings (improvement):

  • Every Friday (suggestion)
  • Merge working code every meeting
  • Decide task for next meeting
  • At least one member of the paired group must attend (User, Map, Database)
  • All code must have good coding style and comment
  • Reference and learning resource URL need to be added to temporary read me, so that other member can learn without bother others

Clone this wiki locally