Thus question is of Software Requirement engineering. Write a user story for use case'Product Availability' of E-shopping project.

Create a storyboard for the user story. Do the work according to the given template First Create user Story like example given in follwing template.Write conversation,Comfirmation and acceptance criteria as given following.

SEARCH ENGINE extends CHECK OUT PRODUCT LIST include include PAYMENT VIEW/UPDATE CART include include Cash on delivery Credit card QUERIES ADMIN USER SIGNIN PRODUCT AVAILABILITY RIVIEW PROMOTION CHAT WITH SELLERS ADD PRODUCTS VENDORS Scenario Id and name UR-07 Product availability Created by Muzalfa Pervaiz date created ws 1/25/2021 Primary actor Admin Secondary actor description The admin can check the stock and can see which products are available and which products are going to be out of stock. He will be able to check the quantities of product left and which are the most selling products etc. The Admin decides to view their selling statistic of their products. Trigger Pre-conditions System must be fully configured; appropriate user ID and passwords must be obtained. Post conditions 1. The product is in the stock 2. The product is out of stock Normal flow 1. The Administrator selects the function "Administrator Panel". 2. The Administrator selects "Check Stock" 3. The system displays the list of product's stock arrange by product name. 4. The Administrator inserts the name of product in search box. 5. The system displays the searched product stock and then it will be shown to him product is available or not. Alternative flow Add the product Admin can also add the products. Update the product list. exceptions He should search the product list to check if the product is available or not. high priority Frequency of use Daily Business rules Product Information assumptions Product need to be available (A CARD defines a US with Who, What, Why, See the examples below. Each W is underlined respectively, Actor(who), what(feature/usecase), why(need)) As a registered user, I want to reset my password, so that I can get back into the site if I forget my Password. (Conversation is the detailed communication between Stakeholder and developer (team members) where the primary focus is to perform DEEP analysis. Conversation is always initiated by SH (stating his/der needs). At the end of the conversation, the SH and developer come to the same agreement) User Story 01 CARD As a registered user, I want to reset my password, so that I can get back into the site if I forget my Password. CONVERSATION Actor Developer CONFORMATION Acceptance criteria: AC 01 AC 02 AC 03 SEARCH ENGINE extends CHECK OUT PRODUCT LIST include include PAYMENT VIEW/UPDATE CART include include Cash on delivery Credit card QUERIES ADMIN USER SIGNIN PRODUCT AVAILABILITY RIVIEW PROMOTION CHAT WITH SELLERS ADD PRODUCTS VENDORS Scenario Id and name UR-07 Product availability Created by Muzalfa Pervaiz date created ws 1/25/2021 Primary actor Admin Secondary actor description The admin can check the stock and can see which products are available and which products are going to be out of stock. He will be able to check the quantities of product left and which are the most selling products etc. The Admin decides to view their selling statistic of their products. Trigger Pre-conditions System must be fully configured; appropriate user ID and passwords must be obtained. Post conditions 1. The product is in the stock 2. The product is out of stock Normal flow 1. The Administrator selects the function "Administrator Panel". 2. The Administrator selects "Check Stock" 3. The system displays the list of product's stock arrange by product name. 4. The Administrator inserts the name of product in search box. 5. The system displays the searched product stock and then it will be shown to him product is available or not. Alternative flow Add the product Admin can also add the products. Update the product list. exceptions He should search the product list to check if the product is available or not. high priority Frequency of use Daily Business rules Product Information assumptions Product need to be available (A CARD defines a US with Who, What, Why, See the examples below. Each W is underlined respectively, Actor(who), what(feature/usecase), why(need)) As a registered user, I want to reset my password, so that I can get back into the site if I forget my Password. (Conversation is the detailed communication between Stakeholder and developer (team members) where the primary focus is to perform DEEP analysis. Conversation is always initiated by SH (stating his/der needs). At the end of the conversation, the SH and developer come to the same agreement) User Story 01 CARD As a registered user, I want to reset my password, so that I can get back into the site if I forget my Password. CONVERSATION Actor Developer CONFORMATION Acceptance criteria: AC 01 AC 02 AC 03