d AhAlysis Modeling Questions Consid er an online shopping system as a target software development project. ne ollowing is part elicitation. memno resulted from a customer meeting during reqirement (1) In general, any customer visiting the system's web interface ave can view all items for available for sale. However, only those customers who have regis tered membership can make purchases (adding items to a shopping cart and che card service, debit card associated with a valid checking account, an cking out). thods, including credit third-party (2) A member customer can check out using different payment me (3) A third-part (4) The system enforce (5) A dedicated delivery department is in charge of item delivery. payment service (e.g., PayPal). regardless of the customer being a member or just a casual visitor. customer can choose to cancel the order if the total number of items included in the y authentication service is used to verify the identity of a customer s a confirmation policy in order processing: when checking out, a transaction exceeds 20. Suppose you are not familiar with this product or its business domain, thus you do not have a clear idea about the requirements. Further, in the initial communication with the customers, it seems that they are not able to describe what they really war In this situation, what would you do (think from the perspective of requirements elicitation)? Why? [3pts] t either