Meeting Minutes - SOEN-341-Project/Group-P-soen341project2022 GitHub Wiki

Meeting 1: January 15th, 2022

Review on work to date:

  • Templates for Issues
  • Kanban

Sample PR: automatic issue tracking

If you're making a PR, put # and the issue title.

You can link sub issues as well

To close an issue, put keyword: closes (see templates!)

2 reviews are needed to merge, it should auto-assign and send emails to random team members emails to ensure good quality code

Went over labels created, assign a label to your work to keep everything organized (team label in order to ping two people from the team)

Put anything you're working on (in development) as a draft PR or a PR

(issue = ticket, as well as issue etc.)

Review of Sprint 1 Deliverables and organizing the repository

Meeting 2: January 22nd, 2022

Attendees:

  • Emma Amar
  • Oumar Barry
  • Koosha Gholipor
  • Jungsoo Lee
  • Adamo Orsini
  • Alexandra Spyridakos
  • Ricky Guan

Topics:

Front and back end workload

  • Front: Emma Amar, Alexandra Spyridakos, Adamo Orsini, Ricky Guan
  • Back: Oumar Barry, Koosha Gholipor, Jungsoo Lee

Login page:

  • Discussed if we should have a login page that can identify between the admin, seller, and buyer. The admin would need a specific way to create his username.
  • A bit of confusion if we could make one account that can be accessed by both the buyer and seller.
  • Conclusion: separate page for the buyer and seller.

Buyer's info:

  • E-mail, name. The shipment information would be asked only after the first checkout

User story done during the meeting

The team had another walkthrough on how to use GitHub for Ricky Guan

Discussed on what we should sell: NFT, knitting goods

Task for next meeting:

  • Come up with a name for the e-commerce
  • Upload their individual issue on GitHub

Meeting 3: February 4th, 2022

Attendees:

  • Emma Amar
  • Oumar Barry
  • Koosha Gholipor
  • Jungsoo Lee
  • Adamo Orsini
  • Alexandra Spyridakos

Topics:

Sprint 1 comment review

Discussed how we need to add more user stories, and connect each one of our issues to specific user stories.

Front end discussion

  • Discussed NavBar progress and future improvements
  • Demoed Product filtering

Back end discussion

  • Explained what technologies to use
  • Explored what resources, tutorials to use to learn technologies

Meeting 4: February 8th, 2022

Attendees:

  • Emma Amar
  • Oumar Barry
  • Koosha Gholipor
  • Jungsoo Lee
  • Adamo Orsini
  • Alexandra Spyridakos
  • Ricky Guan

Topics:

Sprint 2 Breakdown

  • Finish 1 core feature, almost complete another (bugs left)
  • Add specific user stories to each issue
  • Allocate story points to each issue
  • Task breakdown for each user story
    • Ask if leaving it in Issue is okay
  • Move some issue milestones to Sprint 3 (for user stories and implementation) (Backend changes issue milestones)
  • Choose 2 acceptance test suites for user stories (Maybe start JUnit for Sprint 3) Jest, Nightmare? TestCafe?
  • Ask about Sprint 3 Junit -> we're not using Java...

Work breakdown

Routing:

- Web page routing (Whoever finishes first)

Browsing:

##### NavBar:
- Search filtering (Adamo)

##### Product Preview: (Adamo)
- Turn Product preview into button
- Remove description
- Remove Add to Cart and View More buttons

##### Product Full Page: (Alexandra)
- Show all product info
- Add to Cart with quantity selector

Profile:

##### Form logic:
- Button deactivated until required fields empty
- Highlight required input fields in red until they are completed

##### Pages:
- Login page (Emma)
- Register page (Jungsoo)
	- Buyer / Seller options -> Change state of form to input different info
- Modify profile (Ricky)
	- Form where user selects what to change
	- List information in input fields, make it editable
	- Make email non interactable (dimmed out)
	- Save button

Story points

  • Router 2
  • Login 2
  • Register 3
  • Modify user info 4
  • Product Full Page 4
  • Linking SideNav filters to product display 7
  • Query users 2
  • Product Grid rendering 4
  • SideNav 4
  • Customer database 2
  • Seller database 2
  • Stack product buttons 2
  • NavBar 4
  • Create database 1
  • Create schema for the database 4
  • SideNav for Product filtering 7 + 4 = 11

Meeting 5: Feb.18th, 2022

Attendees:

  • Emma Amar
  • Adamo Orsini
  • Alexandra Spyridakos

Discussion

  • Pivoted to sellers epic for sprint 2 instead of login epic.
  • Sellers page will have products displayed as in product grid
  • Sellers can add, modify, and delete products from list
  • Addition and modification of products will happen through a sellers form page

Meeting 6 (Team Discord server chat): Feb. 22nd, 2022

Identified test suites to be used for sprint 3:

Front end:

  • using jest for JavaScript and React testing

Back end:

  • using xUnit for SQL testing

Testing is to be implemented in sprint 3

Meeting 7: March 5th, 2022

Attendees:

  • Emma Amar
  • Oumar Barry
  • Koosha Gholipour
  • Jungsoo Lee
  • Adamo Orsini
  • Alexandra Spyridakos
  • Ricky Guan

Discussion

  • See sprint 3 wiki (discussed sprint 3 breakdown and missing tasks left to do)

Meeting 8: March 11th, 2022

Attendees:

  • Emma Amar
  • Oumar Barry
  • Koosha Gholipour
  • Jungsoo Lee
  • Adamo Orsini
  • Alexandra Spyridakos

Discussion

  • What's necessary for sprint 3
  • Pair programming for cart page, and cart cookies
  • Pair programming for backend frontend linking

Meeting 9: March 20th, 2022

Attendees:

  • Emma Amar
  • Oumar Barry
  • Koosha Gholipour
  • Jungsoo Lee
  • Adamo Orsini
  • Alexandra Spyridakos

Discussion

  • Finalizing acceptance tests
  • Confirming what features have been completed by sprint 3
    • Products feature fully completed (connected to backend, refreshes as products are modified / added / deleted)
    • Seller page fully completed (connected to backend, refreshes as products are modified / added / deleted, can add and modify products correctly)
    • Cart page partially completed (cart created, reflects items, but cookies are not created yet)
    • Login / signup partially completed (login page created, sign up page created, account cookies not created yet)
  • Noted down what parts of the sprint 3 rubric have / have not been completed
    • Jungsoo will add risks to closed issues
    • Jungsoo and Emma writing acceptance tests
    • Jungsoo writing frontend acceptance test suites
    • Koosha writing backend acceptance test suites
    • Everyone will ensure their code is clean, readable, with sufficient comments
  • Looked into issues to be done in sprint 4
    • Manage profile page with adjusted seller data grid to show orders instead of products
    • Admin page with current seller data grid
    • Seller page: Remove seller buttons from current data grid, use cookies to decide which seller is logged in
    • Decide architecture, create architecture diagram

Meeting 10: March 30, 2022

Attendees:

  • Adamo Orsini
  • Alexandra Spyridakos

Discussion

  • Discussed API request format for profile editing page.
  • Discuss what is left to do in the project

TODO:

  • block seller from cart
  • fix window popups from pure JS to some html and react (if there's time)
  • complete view orders
  • complete user modify page (in progress - Alexandra )
  • navbar profile pic dropdown needs to be thinned out --> either have seller button in navbar OR manage products in dropdown, not both - Emma
  • fix numbers input for add/modify products - Adamo

Meeting 11: April 3, 2022

Attendees:

  • Adamo Orsini
  • Alexandra Spyridakos
  • Emma Amar
  • Jungsoo Lee
  • Koosha Gholipour
  • Oumar Barry

Discussion

  • going through the sprint 4 requirements
  • view order page is separate
  • sellers and admin cannot purchase items
  • on the cart page: two checks 1) log in before checking out 2) if you're not a user, then you can't make orders
  • documentation
  • directory and package structure (search bar goes with products, register goes with profile (?), maybe make a browse folder with cartpage, searchbar, navbar)
  • refactor (clean up imports (etc.))
  • clean up repo (make sure everything is referenced)
  • go over written report requirement

TODO:

  • managing profile finishing -> admin and seller to be done, user mostly done
  • fix frontend to forbid certain roles from checking out without logging in
  • navbar fixes (profile pic and bugs on signup need to be fixed)
  • address format in register page shouldn't have a comma between street number and name
  • assess priority of tasks
  • refactor directory and package structure
  • clean up code as much as possible (remove commented code)
  • link acceptance test suites to the wiki
  • written report: decisions made and why (explanation) -> js, react, prisma, axios, jest, etc., look through and make sure everything uses camel case, go through css for convention issues (don't rename mui), key files (frontend: cart, grid, productpage backend: (two files tbd)) describe esLint

Meeting 12: April 8, 2022

Attendees:

  • Adamo Orsini
  • Alexandra Spyridakos
  • Emma Amar
  • Jungsoo Lee
  • Koosha Gholipour
  • Oumar Barry

Discussion

  • Assigned open issues to different members
  • Worked on slides presentation
  • Created rough draft and worked through the presentation process
  • Worked on architecture diagram and class diagrams as a team
  • Discussed sprint 4 guidelines and ensured we are on track for the final delivery
  • Started working on group report

TODO:

  • Complete casourel
  • Complete admin page
  • Record demo for presentation
  • Complete presentation slides
  • Practice group presentation
  • Write acceptance tests in all user stories

Meeting 13: April 15, 2022

Attendees:

  • Adamo Orsini
  • Alexandra Spyridakos
  • Emma Amar
  • Jungsoo Lee
  • Koosha Gholipour
  • Oumar Barry

Discussion

  • Worked on the Velocity and Iteration in the group report
  • Worked on the appendix containing the static analysis tools report
  • Discussed and analyzed 10 problems listed in the static analysis tools report

TODO:

  • Work on the Testing and Continuous section of the group report
  • Select the 5 most important unit tests
  • Select the 5 most important acceptance tests
  • Write the project summary in the group report