Use cases and create sequence diagram and system sequence

Question

Please see use cases and create sequence diagram and system sequence diagram for each.

USE CASE #1	CreateFeedback (BASE)
USE CASE Name	CreateFeedback
ACTOR	SELLER
Goal (1 phrase)	The buyer can give feedback on the item they purchase
Overview and scope	Once the buyer receives their item, they can log into the system, DREX4LESS and give their feedback/review of the item they received.
Level	Primary
Preconditions	User signifies they would like to give feedback of item. User is already Logged in and Authenticated on Web Portal.
Postconditions in words (write in passive and past tense)	An item must have been purchased in order to give feedback. Or user can give feedback on an item that is yet to be received. User will click on purchase history to locate item. Feedback can be good or bad depending on the buyer experience with the seller and item.
Trigger	The feedback button was clicked
Included Use Cases	ShowLinkedItems
Extending Use Cases
MAIN SUCCESSFUL SCENARIO for this Use Case in numbered sequence   Reference "included use cases" in this section using INCLUDE ius_name	Actor Action	System Action
	1. SELLER clicks on Create Feedback Button	2. Include ShowlinkedItems
	3. SELLER clicks on desired Item	4. DREX4LESS System prompts user to enter review of the item
	5. User enters review of the item and saves it.	6. DREX4LESS prompts user to ViewFeedback to make corrections if need be.
Priority in scheduling	Medium
Frequency	Once per run
Business rules and data logic	User must enter the correct credentials. If the user enters the correct credentials, user is able to view purchase history. User will select the item. User will click the review button. User will enter feedback on the item and save.
Other non-functional requirements	Windows standard user interface
Superordinates
Developer	Bradlyn Blanton
Creation date and last modified date	05/12/2016
Other Comments

Other use cases in the attached file.

Attachment:- use cases.rar