Customer Meeting 1 - bounswe/bounswe2020group1 GitHub Wiki

Customer Meeting 1 Notes

Date & Time: 24.02.2020 14.00-14.45

Location: NETLAB

Participants:

No Name
1 Onur Kılıçoğlu (Notetaker)
2 Mehmet Çelimli (Communicator)
3 Meriç Turan (Customer)

Agenda

  1. Getting feedback on the first version of the requirements.
  2. Asking questions about the unclear parts of the requirements.

Notes

  1. Feedbacks are taken.
  2. Talked about the misclassification of the requirements.
  3. Questions about the requirements are answered by the customer.

Answers to the questions:

  1. Are users going to have a comment history?
  • Comment history should belong to a product itself and it will be under a product page if exists.
  1. What will be the difference between the functionalities of shopping lists and shopping carts?
  • Shopping carts should include the set of items which the users are currently interested in and want to buy next. Shopping lists are like wish lists. Users can create a shopping list to save the items that they are interested in but planning to buy later instead of now. Both shopping lists and shopping carts should be stored when users go offline.
  1. Should the descriptions of products also be included in the search?
  • The descriptions of the products shall be included in the search.
  1. What exactly is expected from the semantic search requirement?
  • Semantic search property of the search utility should be able to offer semantically close search results in addition to the direct matched results. An example to this is given by customer as: “If you search for cat related items in addition to the cat related items the platform should also show other pet related items such as but not limited to dog related items because of the semantic closeness of the concepts.” .
  1. What is the difference between average customer review and rating?
  • Both concepts are used in the same context.
  1. Viewing the total amount spent on the platform will make customers more aware of their expenses and cause them to try to reduce the money they spent on the platform. How sensible is this?
  • This amount should be saved as mentioned no matter what. The value shown to the customer can be called customer points or money spent in the system but it doesn’t change the requirement to store this amount as mentioned.
  1. Can vendors also cancel an order without the occurence of a problem? Or do they need a valid reason that they explain to the admins and can only cancel with the approval of the admins?
  • The vendor can cancel the order without the occurrence of a problem during the processing stage. When the vendor wants to cancel a product, the vendor should send a cancel request to the admin and the admin will cancel the order.
  1. In which cases are notifications sent? (price changes, product is now in stock, the product is now sent by cargo)?
  • The customer mentioned that this is a design choice. However the customer recommended that an alert like notification when the price of a product goes down would be good to have in the system. And the system can create an alert list for the products.
  1. In what relation are products recommended?
  • Recommendation system can use any kind of relevant information in the system that can be used to recommend a product. The customer suggested that information on the search history, the products that are viewed and bought should be used when recommending a product however any kind of additional information that makes sense can be used in recommendation.