-
Notifications
You must be signed in to change notification settings - Fork 8
Meeting #13
nursimacelik edited this page Jan 16, 2021
·
8 revisions
Date: 28.10.2020
Time: 20.00 - 23.00
Platform: Zoom
Note taker: Öncel Keleş
Attendees
- Yasin Kaya
- Göksu Başer
- Burak Berk Özer
- Onur Enginer
- Afra Arslan
- Nursima Çelik
- Öncel Keleş
- Muhammet Tayyip Yazıcı
- Özgürcan Öztaş
- Ahmet Yiğit Gedik
- Kaan Durak
- Nazım Berke Metin
- Revise and update requirements(cont.)
- Choose a new communicator
- There should be a return for exchange and request missing/flawed parts feature for orders. (1.1.7)
- Customers should be able to track their orders with the tracking no only. (1.1.7.2)
- Users should be able to edit their payment methods with password. (1.1.2)
- Users shall earn points according to their purchases. (1.1.8)
- Guests can only rate the product they bought. (1.1.9.4)
- Guests should sign up in order to comment to the product they bought. (1.1.9)
- Notifications should only be sent for the products in the watchlists. (1.1.10)
- Recommendations should be based on purchase history, not activity. (1.1.11.1)
- Recommendations can be based on purchases and their associated weights(price, date, etc.). (1.1.11)
- Customers should be able to message admins if a problem arises after the delivery within guarantee extent. (1.1.12)
- Admins should confirm if a product information is editted by the vendors. (1.1.13)
- Users should be able to edit their birthday information. (1.1.2)
- System should take consent from users to store also their birthday information. (1.2.1.6)
- The article 1.2.2.3 should be removed(1.2.2.1 and 1.2.2.2 already involves this article)
- The article 1.2.4.1 should be removed.
- The card information of the guests won't be stored. (1.2.4.9)
- There should be a list of banned words. (1.2.5)
- Users should not be able to add links to comments. (1.2.5)
- If the above 2 items(17 & 18) are not selected for development, there should be a confirmation system for the comments. (1.2.5)
- Product information on article 1.2.6.1 should be expanded as in 1.1.3.
- Users should not be able to delete the default favorite list and the watchlist. (1.2.7.1)
- If any product on the list is not available, the user cannot add those product to cart while transferring. (1.2.7.2)
- Users should be notified about unavailable products while transferring product from the list to the shopping cart. (1.2.7.2)
- There should be a character limit for messages. (1.2.10)
- There should be a limit on back-to-back messages. (1.2.10)
- The messages should be deleted after a certain amount of time after delivery. (1.2.10)
- Users should be able to create tickets instead of live chat to contact the admins. (1.2.10.2)
- Users should be able to cancel an order only before the product is shipped. (1.2.11.2)
- Users should be able to track return exchanges and part requests. (1.2.11)
- The article 1.2.11.6 should be removed.
- The shipment information in article 1.2.11.4 should be expanded: tracking number, customer adresss, etc.
- Admins should be able to confirm a product edit. (1.2.12)
- Admins shall be able to see and edit message tickets. (1.2.12)
- Users shall only receive notifications from the product on their watchlist. (1.2.13.1 & 1.2.13.2)
- Guests users' card information won't be stored. (2.2.4)
- Birthday will be added to the article 2.2.2.
- Chrome and Firefox versions on the article 2.3.2 should be updated. Only the last year will be covered.
- Only English will be supported. (2.4.3)
- The whole section "2.5 Performance" should be removed.
- Gift card and discount coupon should be removed from the glossary.
- Shipments information should be added to the glossary.
- Should payment be real or dummy? (1.1.8)
- Is EFT necessary? Which payment methods must be implemented? (1.1.8)
- Should we implement a recommendation system or can we use an existing library? (1.1.11)
- Should the guests be able to comment on a product they bought? (1.2.5.2)
- How much Google Maps integration is needed? (1.2.8)
- How should the recommendation system work? Based on search or purchase history? (1.2.9)
- How should we store payments information?
- Özgürcan Öztaş will be the new communicator of the group.
Action No | Action Name | Responsible | Deadline | Completion Time |
---|---|---|---|---|
1 | Ask customer the questions at the next meeting | Everyone | 02.11.2020 17.00 | |
2 | Updating Requirements page accordingly | Öncel Keleş | 02.11.2020 17.00 | 10.11.2020 23.59 |
🏠 Home
💻 Project
-
Software Design
📜 User Manuals
☎️ Group Members
- Current Members -
- Afra Arslan
- Burak Berk Özer
- Göksu Başer
- Nursima Kaya (former communicator)
- Onur Enginer
- Yasin Kaya
- Özgürcan Öztaş (Communicator)
- Öncel Keleş
- Kaan Dura
- Muhammet Tayyip Yazici
- Ahmet Yiğit Gedik
- Nazım Berke Metin
- Former Members -
📃 Milestones
- CMPE451 -
- CMPE 352 -
📃 Meeting Notes
- CMPE 451 Meetings -
-
- Backend Meetings -
- Meeting Recordings -
- CMPE 352 Meetings -
- Meeting #1 (14.02.2020)
- Meeting #2 (20.02.2020)
- Meeting #3 (27.02.2020)
- Meeting #4 (05.03.2020)
- Customer Meeting #1 (05.03.2020)
- Meeting #5 (12.03.2020)
- Meeting #6 (09.04.2020)
- Meeting #7 (16.04.2020)
- Meeting #8 (24.04.2020)
- Meeting #9 (30.04.2020)
- Meeting #10 (07.05.2020)
- CMPE 352 Project Plan -
🔍 Research