Will rate need a sequence diagram please

The following is a list of required attributes and methods for the objects in your scenario: Object Type Attributes [as type: attribute description] Methods [as name(parameters): return type] Market String: name getName(): String Player Money: credits Float: negotiation skill Market: market Sales Manager Market: market Inventory Float: capacity Float: available capacity Fertilizer Float: price Primary Actor: Player Use Case: Negotiate with sales manager Main Success Scenario: o During an encounter with a pest control company's sales manager selling their fertilizers, the player selects the "Negotiate" option. If the player has sufficient negotiation skill then 1) the player chooses a fertilizer, 2) the player receives a discounted price of the fertilizer, 3) the player pays the discounted price to the sales manager, 4) if there is sufficient inventory space then the player adds the fertilizer to the inventory. Extension (Alternate Scenario) o If the player does not have sufficient negotiation skill, then the player pays the operating fee to the market for using its services. 2. Provide a Sequence Diagram for the given Main Success Scenario and Extensions. Ensure that your diagram includes the following elements at a minimum: Messages with clear sending and receiving objects and directionality Messages must be clearly named and consistent with your Design Class Diagram Messages must be shown in the proper sequence of events Fragment structures (alternatives, option) must be shown clearly We've given you the template below as a starting point. Sales Manager Player :Fertilizer Inventory :Market Actor - The following is a list of required attributes and methods for the objects in your scenario: Object Type Attributes [as type: attribute description] Methods [as name(parameters): return type] Market String: name getName(): String Player Money: credits Float: negotiation skill Market: market Sales Manager Market: market Inventory Float: capacity Float: available capacity Fertilizer Float: price Primary Actor: Player Use Case: Negotiate with sales manager Main Success Scenario: o During an encounter with a pest control company's sales manager selling their fertilizers, the player selects the "Negotiate" option. If the player has sufficient negotiation skill then 1) the player chooses a fertilizer, 2) the player receives a discounted price of the fertilizer, 3) the player pays the discounted price to the sales manager, 4) if there is sufficient inventory space then the player adds the fertilizer to the inventory. Extension (Alternate Scenario) o If the player does not have sufficient negotiation skill, then the player pays the operating fee to the market for using its services. 2. Provide a Sequence Diagram for the given Main Success Scenario and Extensions. Ensure that your diagram includes the following elements at a minimum: Messages with clear sending and receiving objects and directionality Messages must be clearly named and consistent with your Design Class Diagram Messages must be shown in the proper sequence of events Fragment structures (alternatives, option) must be shown clearly We've given you the template below as a starting point. Sales Manager Player :Fertilizer Inventory :Market Actor