-
Notifications
You must be signed in to change notification settings - Fork 2
Team Meeting
Ze Hui Peng edited this page Nov 28, 2020
·
66 revisions
Celebrate:
- This is our last meeting 🎉🎉
What to discuss:
- Javadoc (PRs need review and approval)
- Mock UI and Storyboard (PR need review and approval), wiki page need to be updated
- UML
- Video Demo
- Use Zoom to record
- Powerpoint slide on the left, emulator/phone projection on the right
Task before next Monday:
- Write some unit test and intent test before the project due time
Celebrate:
- We have finished All User Stories 🎉🎉🎉🎉
What to discuss/What's left for this project:
- Write some Unit/Intent tests
- Javadocs
- Done: Update Product Backlog
- Update Mock UI and Storyboard
- Update UML Diagram
- Record our demo video
What to discuss:
- exising PRs.
Tasks: check is assigned
- Unit testing
- javadoc & generation & deploy on github?
- fix owned list add button hiding the last book
- fix requested detail action button "view all requests" (right now doing nothing)
- google book api
Optional:
- make async buttons progress buttons to prevent spamming
- user detail button in the book detail activities
User Stories left:
- Done with a few WIP
What to discuss:
- Talk about final deliverables
- When should we do the demo video recording?
User Stories left:
- Map (Integration)
- Also allow borrower to view the location
- Scanner (Scan to return and owner Scan to receive)
- Fully Integrate Borrowed Tab
Nice to Have:
- View owner information in detail page (all detail page except owned)
- View borrower information in detail page (owned detail page with a "Borrowed" status)
What to discuss:
- Reminder: complete the peer review form by this Friday, Nov 20
- Discuss everyone's progress on the assigned task from Monday
What to discuss:
- Some notes on the PR that are open:
- Talk about Trung's progress on implementing the map
- Talk about how to refactor Glide/GlideApp related code(see Zehui's comment in #119)
Reminder:
- complete the peer review form by this Friday, Nov 20.
Assign some tasks on the features left:
- Integrate "Accepted" tab (very similar to "Requested")
- Adding a new button in base detail page that will show the owner detail(like how we are showing it in Profile after searching the user)
- Notification
- For the owner's detail page, implement the text and/or features for buttons depending on the book status
- Available - Cannot think of any actions.. Maybe delete the book, or find some way to unrender the button
- Requested - View All Requests? Although we already have this in the three dot popup menu
- Accepted - Scan to hand over the book
- Borrowed - Scan to receive a returned book and denote it as available
- For the "Requested" detail page, implement the text for the button to be "Waiting for Acceptance", and change the color of the button to gray in Java code(not xml file, since the button is shared in all detail pages)
- see here for the mockup example
- What happens when a request is denied?
- For the owner's detail page, implement the feature that disallow owner to edit book if the book status is not "Available"
- see the eclass forum for detail
- For the View Request Activity, should we have a button that allows the owner to reject all requests?
- If owner rejects all request, should the status of the book change? Requested -> Available
Task for next few days:
- Qi - Integrate "Accepted" tab
- Trung - Continue on map
- Lucas - Refactoring code and look into notification
- Meilin - add text to all buttons in detail page
- Khang - Refactoring code and look into scanning to accept/return
- Ze - Refactoring code and disable owner to edit book if book status is not "Available"
What to discuss:
- progress check on opened PRs(a lot 😿)
- #108 - ✔️ after changing to allow either 10 or 13 digits
- #109 - ✔️, two minor comments from khang
- #111 - 🔍 changes made, need someone to review again
- #112 - 🔍 fixed bug found by Lucas, need another round of review
- #114 - ✔️ looks good to merge, this might impact the "Browse" page as the page is not actually display the status of the book
- #115 - ✔️ looks good to merge
- #116 - 🔍 need someone to review, one comment from Zehui, do we want to display books that the user have requested in browse page? Seems to be duplicating with "Requested" tab in "Borrow" fragment
- #117 - 🔍 need someone to review
Task for next few days:
- Try to merge all opened PRs, and assign new tasks for the detail pages
What to discuss:
- progress check on opened PRs
Task for next few days:
- Everyone - address open PR reviews
- Qi - address PR reviews(if any) and Unit test for profile edit
- Khang - Functionality on request
- Lucas - Browse Search
- Meilin - Finish up Detail Page
- Trung - Map
- Ze - Requested page integration
What to discuss:
- check on progress with existing PRs
- loose discussion
During the meeting:
- agreed on Zehui's stacked buttons, agreed on further menu change
What to discuss:
- check on progress with existing PRs
- check on the the features still left to be implemented
- assign tasks for some of the features
Notes and Task for next few days:
Planned Features:
- Browse Book Integration - Khang
- Filter books in "My Books" - Ze
- Delete Photograph - Lucas
- Book Details for borrowers - Meilin
- Map - Trung
- Constraint ISBN to only allow 13 digits - Qi
What to discuss:
All the Part 3 deliverables
- Addressing Feedback:
- Keep this page updated!
- Code Base of Prototype:
- make sure all features are working
- Code Documentation:
- go over progress on javadoc, need javadoc on all our ViewModel classes
- Test Cases:
- go over progress on the process of everyone's unit test/intent test assigned on Monday
- Object-Oriented Design:
- go over progress on updated UML diagram, make sure it's transferred to GitHub from Lucid chart
- Product Backlog:
- go over the updated backlog, identify any User Stories that should be marked as In Progress or Done
- User Interface Mockups and Storyboard Sequences:
- go over progress on UI and Storyboard, make sure the images are transferred to GitHub from Figma
- Sprint Planning and Reviews:
- That will be this page?
- Demonstration:
- During tomorrow's lab time
Task for next few days:
- Finish the unit test/intent tests
- Finish Storyboard and UML and transfer the images to github
What to discuss:
- #88 about test data
- #83 progress/design discussion
- Test cases split work: (unit + intent?)
- create account actions
- user profile edit
- user search
- add book
- (delete book)
- Javadoc split work
- UML + Storyboard update
During the meeting:
- New firebase project used for testing ONLY
- look into how to run multiple test concurrently without data interfering
- demo Espresso Test Recorder
Task for next few days: Unit/Intent/Javadoc:
- create account actions - Meilin
- user profile edit - Qi
- user search - Lucas
- add book - Trung
- (delete book) - Khang
- UML Update - Khang
- Storyboard update - Lucas & Ze
What to discuss:
- discuss about storing image url in book document
- discuss #85: complexity of passing data between activities
- discuss #78: discrepancy of firebaseUser and our user's phone number, possibly getting rid of it
- review all other PRs together, identify issues
- plan onwards
During the meeting:
- not storing url
- good
- remove User.phone and User.displayName (another PR), this PR is good.
- talked about browse fragment search (code design)
- browse page: book list starts from requests, filter for book status where not borrowed/accepted + requests where not current user. book status keep four.
Tasks for next few days:
- create unit tests, intent tests and javadoc
- owned book list filter
More to look into
- notification: look into it
- integrate scan to add with google books isbn api
- integrate browse + borrow fragments
During the meeting:
- Progress check on assigned issues
- Create issues based on user stories
- discuss how a general RecyclerView can be used in multiple fragments
Task for next few days:
- work on your assigned issues, see issue tab for detail
During the meeting:
- Progress check on assigned issues
Task for next few days:
- Study for midterm 🥇
During the meeting:
- Go over Sprint Backlog, identify items to do in the first sprint
- Create issues and start assigning tasks
Task for next few days:
During the meeting:
- Go over the current UI and UML, finalize it and export it to github
Task for next few days:
- Save UML and put it on Github
- Save Storyboard and put it on Github
- For each UI page, give a description
During the meeting:
- Go over the current UI and UML, discuss if anything is missing and/or need to be changed
Notes:
- Process for borrower to return a book? Does borrower need to scan the book? Do both parties(owner & borrower) need to confirm the return?
- Book Details Page for Mock UI
- Where to put buttons for each book in the list? * Fragment that can be clicked with different options * Put it in the book details page
Task for next few days:
- Storyboard: each UI page needs:
- a description on the functionality
- what action can bring the user to this page? (clicking which button? under what condition?)
- Clean up and finalize UML page
During the meeting:
- Go over the current UI and UML, discuss if anything is missing and/or need to be changed
Notes:
- Change 'Owner' Nav to 'Your Library', having 'Your Books' and 'Borrowed Books' tabs
- UML: choose a wrapper logic(currently NotificationManager, could be something else) bases on firebase notification SDK
Questions to ask customer:
- Scanning the book - do both the owner and borrowers have to scan the book for the status to change to "borrowed"?
- Does a book allows to have multiple copies(with the same ISBN)?
- How does borrower return a book? Does the borrower also specify a geo location for both the owner and borrowers to meet?
- Does firebase notification suffice for the notify user story? what kind of notification?
Task for next few days:
- Continue to work on Mock UI and UML
- ask questions above
- Discuss about the necessity of using IDs for Request and Book and User (vs. querying based on unique fields only)
During the meeting:
-
Go over the constructed important classes and activities with the team to determine if any part needs revision
- This is just some ideas, and not the final decision/implementation
-
Assign each team member to either work on the UI Mockup(using Figma) or UML(using Lucidchart)
- Mockup UI - Ze, Lucas, Qi
- UML - Meilin, Khang, Trung
Task for next few days:
- Mockup UI - Construct the login and main screen page, include navigation and top tabs
- UML - Construct the entity classes and common activities, don't worry about relationship as for now
- prioritize more on entity classes
During the meeting:
- Go over the product backlog with the team to determine if any part needs revision Task for next few days:
Construct key classes and activities based on product backlog and user stories
- Each member should come up with classes and activities on the user stories you did in the product backlog
- See the meeting notes for below for your responsible section
During the meeting:
- First Meeting, assign tasks for everyone to start the Product Backlog with some User Stories
Task for next few days:
- Lucas - Books section
- Khang - User Profile and Searching section
- Trung - Borrowing and Return section
- Ze - Photograph and Location section
- Meilin - Requesting section
- Qi - Accepting section